> 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/t650-how-tos/how-to-add-a-tip-to-a-sale.md).

# How To Add A Tip To A Sale

{% hint style="warning" %}
Please ensure that this feature is enabled on the device first before performing this step. The step below is for the terminal in manual/standalone mode
{% endhint %}

{% stepper %}
{% step %}

### Enter Amount on Sale Screen

First enter the payment amount on the screen and then tap the Card button.
{% endstep %}

{% step %}

### Tap the required Tip Amount

It will prompt a screen that says 5%, 10% Custom amount or No Tip (If the screen does not prompt, please contact us to enable this)
{% endstep %}

{% step %}

### Payment Screen including Tips

A customer can then insert, swipe, or tap their card or device. Also, select other payment options, such as Klarna
{% endstep %}

{% step %}

### Payment Processing

The terminal then connects to our payment processing and receives an approval response.
{% endstep %}

{% step %}

### Select Receipt Option

Then select the receipt option.
{% endstep %}

{% step %}

### Transaction Complete

The transaction is now complete. 
{% endstep %}
{% endstepper %}

#### [<mark style="color:$success;">Back to T650P - How To Guides</mark>](/t650-how-tos/t650p-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/t650-how-tos/how-to-add-a-tip-to-a-sale.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.