> For the complete documentation index, see [llms.txt](https://docs.makapay.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.makapay.io/point-of-sale-pos/tips.md).

# Tipping

Let customers add a tip at the checkout before the payment is created. The tip is folded into the single payment the customer makes, and the merchant sees the subtotal, the tip, and the total on every invoice in the back office.

## Enabling Tips on a Business

Tipping is configured per business in **Dashboard → POS → Businesses** (create or edit a business):

| Setting              | Description                                                                                             |
| -------------------- | ------------------------------------------------------------------------------------------------------- |
| **Tipping**          | Master switch. When on, the checkout shows a tip step after the amount step.                            |
| **Tip presets**      | Percentages of the subtotal shown as one-tap options. Defaults to **5%, 10% and 15%**. Up to 6 presets. |
| **Allow custom tip** | Lets the customer type their own tip amount on a keypad.                                                |

Cashiers must log in again after changing these settings so the terminal picks up the new configuration.

## What the Customer Sees

1. The cashier enters the subtotal as usual.
2. The screen asks **"Would you like to add a tip?"** and shows the preset percentages with the exact tip amount under each one (e.g. `10%` → `€2.50`), plus **No tip** and, when allowed, **Custom**.
3. A summary shows **Subtotal**, **Tip** and **Total**.
4. The cashier taps **Continue**. The network/token step and the QR code use the **total including the tip**, so the customer pays once.

Tips are calculated in the business's fiat currency and rounded to that currency's smallest unit (cents, or whole units for JPY, KRW, ISK and HUF). They are then converted to crypto together with the subtotal at the same exchange rate and spread.

## What the Merchant Sees

* **POS Activity** (`Dashboard → POS → Activity`) has a **Tips** summary card at the top (total tips for the filtered business, cashier and date range, per currency) and shows `Subtotal … · Tip …` under the amount for every payment that included a tip, with the percentage when a preset was used. Below the summary, **Tips by terminal** and **Tips by business** break the same totals down per cashier and per business.
* **POS Overview** shows a **Tips collected** card next to the transaction count.
* The **payment detail panel** lists **Subtotal** and **Tip** rows next to the usual amount, received amount and fees.
* **Exports** (Excel / PDF) include an optional **Tip** column.
* The payment description reads `POS Payment - €27.50 (incl. €2.50 tip)`.

## Limits and Fees

* Minimum-amount checks apply to the **subtotal**; the tip is added on top.
* Maximum-amount limits apply to the **total** the customer pays.
* Platform fees are calculated on the total (subtotal + tip), exactly like any other payment.

## Troubleshooting

**The tip step does not appear** — tipping is off for this business, or the cashier logged in before it was enabled. Turn it on in the business settings and log in again.

**"Tipping is not enabled on this terminal"** — the terminal sent a tip for a business that has tipping disabled. Re-login on the terminal to refresh its configuration.


---

# 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.makapay.io/point-of-sale-pos/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.
