> 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/v400m/how-tos/how-to-enable-tips.md).

# How to Enable Tips

Turn on the tip function on your V400M so customers can add a tip.

{% hint style="info" %}
**Use this when** you want to give your customers the option to add a tip when they pay.
{% endhint %}

When tips are turned on, your customers can add an extra amount to their payment as a tip.

## Turn on tips

{% stepper %}
{% step %}

### Open the menu

Press **4** and **6** at the same time, then enter password **1234** and press the **green button**.
{% endstep %}

{% step %}

### Go to Tip configuration

Select **Administration > Settings > Tip configuration**.
{% endstep %}

{% step %}

### Turn on tips

Tick the box next to **"Tip Enabled"**.
{% endstep %}

{% step %}

### Save and leave the menu

Press the **red button** to close the menu. Your settings are **saved automatically**.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
Tips are now turned on. Your customers will be able to add a tip when they pay.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: enable tips, turn on tips, tip function, add a tip, gratuity, tip configuration. Search terms: tip, tips, gratuity, tip enabled, tip configuration, extra amount.

</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/v400m/how-tos/how-to-enable-tips.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.