> 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/santander.md). # Santander Record a sale paid through Santander by entering the reference number at the till. ## What is this? Santander is a way of recording that a sale was paid through Santander. Flow Retail does not talk to Santander — nothing is authorised, captured or refunded through the platform. The operator types in the reference from Santander's own flow, and the sale is filed against it. Unless you rename it, it appears in the payment list as **Santander terminal**, although Flow Retail does not connect to one. *** ## How does it work? Pick Santander on **Choose payment method** and enter the **Reference**. The field accepts digits only and checks them against a modulus-10 checksum, so a mistyped number is caught before the sale goes through: > Incorrect format, checksum does not match. That is the whole flow. There is no waiting screen, no approval and no message back — the sale completes as soon as the reference validates. Refunds are not tied to the original payment. A return can be settled to Santander without pointing at what was paid, and the reference is entered the same way. Cashback is not available, and Santander cannot be used to pay off an existing invoice. *** ## How do we get started? Santander is a standard payment method. There is no extension and nothing to authenticate. Add it under **Admin → Settings → Payment Methods**, enable it in the stores that should offer it, and give it a ledger number per store so the amounts post where you expect. Everything else — the agreement, what the reference is, and how the money reaches you — sits with Santander, outside Flow Retail. *** *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/santander.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.