> 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/payment-gateway.md).
# Payment gateway
Record a payment an external checkout has already authorised, and capture it when you deliver.
## What is this?
Payment gateway records a payment that was authorised somewhere else — typically a webshop checkout that ran the card payment with its own payment service provider. The order and the payment arrive together through the order import API, and Flow Retail captures the money when you deliver.
{% hint style="info" %}
This one is not for the till. It cannot be chosen in Flow Client, and it only reaches Flow Retail through an imported order.
{% endhint %}
***
## How does it work?
An imported gateway payment arrives as Authorized: the money is reserved with the provider, but not yet taken. It must carry the provider's own payment reference, or Flow Retail rejects it with **External payment reference is missing**.
Flow Retail captures the authorisation when the order receipt is completed and the products are delivered. If you have given us a URL to call, we post the capture there; otherwise it is only recorded on the order.
While a payment is still authorised, you can cancel it in Flow Retail. Releasing the reservation with the provider is your side of that. Once the payment is captured, it stays captured.
{% hint style="warning" %}
A gateway payment cannot be refunded. Flow Retail refuses it with **Refunds for payment gateway settlements are not supported yet.** An authorisation can be captured or cancelled, never sent back through the gateway.
{% endhint %}
***
## How do we get started?
Ask us to switch on the Payment gateway extension for you. If your provider needs a capture call, give us the URL and we set it up at the same time.
Your webshop or middleware then imports orders with the payment attached. Alongside gateway payments, imported orders also accept invoice, rounding, and your own custom payment methods.
***
*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/payment-gateway.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.