> 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/pos/order-creation/checkout/payments/payment-types/cash-payment.md).

# Cash Payment

When cash is selected as the payment method, the **amount due is automatically entered by default**, and the **change is shown as** €**0.00**. If the customer provides a different amount, you can manually enter the **amount received**, and the POS will calculate and display the change accordingly.

The **cash drawer can be opened**, allowing you to store the cash and issue the correct change.

{% hint style="warning" %}
Only users with the permission **“User can open cash drawer on POS”** enabled will be able to open the drawer.
{% endhint %}

> It is possible to configure the POS so that the **cash drawer opens automatically** when a cash payment is made. This setup is not accessible to users and must be configured by the appropriate support team upon request.


---

# 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/pos/order-creation/checkout/payments/payment-types/cash-payment.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.
