> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-nordics/t650/how-tos/how-to-add-a-tip-to-a-sale.md).

# How to Add a Tip to a Sale

Add a tip to a sale on a T650 terminal in standalone mode.

{% hint style="info" %}
**Use this when** you need to add a tip to a sale on a T650 terminal in manual/standalone mode.
{% endhint %}

{% hint style="warning" %}
Make sure the tipping feature is enabled on the device before following these steps. If the tip prompt doesn't appear, contact us to enable it.
{% endhint %}

## Add a tip

{% stepper %}
{% step %}

### Enter the amount

Enter the payment amount on the Sale screen, then tap the **Card** button.
{% endstep %}

{% step %}

### Choose the tip amount

The screen prompts **5%**, **10%**, **Custom amount**, or **No Tip**. Tap the required tip amount.
{% endstep %}

{% step %}

### Take the payment

The customer can insert, swipe, or tap their card or device, or select another payment option such as **Klarna**.
{% endstep %}

{% step %}

### Wait for approval

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

{% step %}

### Choose a receipt option

Select the receipt option.
{% endstep %}

{% step %}

### Done

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

<details>

<summary>Keywords</summary>

Also called: add a tip, tipping, gratuity, tip amount, add gratuity. Search terms: tip, tipping, gratuity, 5%, 10%, custom tip, sale.

</details>


---

# 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://docs.verifone.com/support-nordics/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.