> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/points/points-in-the-kiosk.md).

# Points in the Kiosk

Customers can **scan their QR code** at any point before payment. This enables customers to earn or use points.

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2Fimn13GSgCGnbBuV366Is%2Fwelcome.jpg?alt=media&amp;token=dbd9201a-d9b4-457d-88f4-fb4598c4ebc7" alt="" width="375"><figcaption></figcaption></figure>

## Using Points

Customers may redeem their available loyalty points to cover part or all of the total amount.

* If points cover the **full value** of the order, no payment terminal is triggered. The order is immediately processed as **paid** and the order number is shown in the screen.
* If points cover a **partial amount**, the remaining balance is paid through the standard payment process.

## Earning Points

Customers who choose not to redeem points on the current order will **earn** points based on their purchase value. They will have to **proceed with the standard payment process**.

> The points earned from a transaction will only be added to the points balance once the order is completed.


---

# 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.bossithq.com/points/points-in-the-kiosk.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.
