> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/selling/payments/payment-methods/cash.md). # Cash Take payment in notes and coins at the till. ## What is this? Cash lets you take payment in notes and coins. It is there from day one: every new store gets it, switched on and ready. *** ## How does it work? Pick **Cash** on **Choose payment method** and enter what the customer hands over. Flow Retail rounds the amount to your country's smallest coin and gives you the change to hand back. A cash sale can be refunded without the original sale to point at, so a customer with no receipt is not a problem. {% hint style="warning" %} Norwegian law caps a single cash payment. Go over it and the till stops you with **Maximum allowed amount: 39.999**. {% endhint %} When you close the till, enter the **Counted amount**. The **Till report** then shows **Cash revenue**, **Cash counted** and the **Difference** between them. *** ## How do we get started? Nothing to do. Cash needs no extension and no setup, and it is enabled on every store the moment the store is created. You can still turn it off for a store that never takes cash, on that store's **Payment Methods** tab in Flow Admin. *** *Last updated 17.09.2026* --- # 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.flowretail.com/docs/day-to-day-operations/selling/payments/payment-methods/cash.md?ask=&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.