> 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-norway/v400c/veiledninger/slik-aktiverer-du-tips.md).

# Slik aktiverer du tips

Slik gir du kundene dine mulighet til å legge til tips når de betaler med din V400c.

{% hint style="info" %}
**Bruk denne siden når** du vil at kundene dine skal kunne legge til tips når de betaler med din V400c.
{% endhint %}

Når funksjonen er slått på, kan kunden legge til et ekstra beløp som tips i forbindelse med betalingen.

## Før du begynner

For å åpne menyen, trykk **4** og **6** samtidig, og skriv deretter inn passordet **1234** og trykk på **den grønne knappen**.

## Aktiver tips

{% stepper %}
{% step %}

### Åpne innstillingene for tips

1. Åpne menyen.
2. Velg **Administrasjonsmeny > Settings > Tip configuration**.
   {% endstep %}

{% step %}

### Slå på tips

Kryss av for **Tip Enabled**.
{% endstep %}

{% step %}

### Lukk menyen

Trykk på **den røde knappen** for å lukke menyen. Innstillingene lagres automatisk.

✅ **Tips er nå aktivert** — kundene dine kan legge til tips når de betaler.
{% endstep %}
{% endstepper %}


---

# 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-norway/v400c/veiledninger/slik-aktiverer-du-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.