> 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.md).

# Payments

Receiving payment in Flow Retail is both very easy to do, and flexible.

## A few important notes on payments

* You can **use an unlimited number of payment methods** on one settlement/order
  * E.g. on an order with a total amount of 1000, you can give your customer the option to pay 100 in cash, 500 one one card, 200 on another card, and the remaining 200 by gift card, to put it to the extreme
    * Note that combining multiple payment methods makes it more complex to do a refund, as especially card refunds must be refunded towards the exact same card
* We recommend to **have at least two modern paymet methods** (cash is not defined as modern) active, like card payment and one of the available mobile payment methods, like Dintero or Softpay, in case of technical issues


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flowretail.com/docs/day-to-day-operations/selling/payments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
