> For the complete documentation index, see [llms.txt](https://helpcenter.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.verifone.com/v240m-how-tos/how-to-process-charge-only.md).

# How to Process Charge Only

1. **Access the Sale Screen** \
   After logging in, go to the Sale screen.
2. **Open the Menu** \
   Tap the blue banner at the top of the screen.
3. **Select Charge Only** \
   Choose Charge Only from the menu. You will return to the Sale screen, and above Enter Amount, it will now display Charge Only.
4. **Enter the Amount** \
   Type the amount you wish to charge. Important: This must match the value from the original Authorisation Only transaction.
5. **Enter the Auth Code** \
   Input the Auth Code from the previous Authorisation Only transaction.
6. **Present the Card** \
   Insert, swipe, or tap the card when prompted.
7. **Complete the Charge** \
   Once the card is processed, the terminal will confirm that the charge for the Auth Code has been successfully completed.

#### [<mark style="color:$success;">Back to V240M - How To Guides</mark>](/v240m-how-tos/v240m-how-to-guides.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpcenter.verifone.com/v240m-how-tos/how-to-process-charge-only.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.