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

# Stripe

Take card payments on a Stripe terminal at the till.

## What is this?

The Stripe extension lets you take card payments on a Stripe terminal connected to a till. The cashier sees it as **Stripe terminal**, in both Flow Client and Flow Assistant.

## How does it work?

Each till is paired with one terminal, and a till can only carry one terminal brand at a time.

Register the sale as normal and choose **Stripe terminal**. Flow Retail sends the amount to the paired terminal, the customer pays there, and the till shows the terminal's status messages as the payment runs.

{% hint style="info" %}
A Stripe refund must point at the original transaction. Refund from the order the customer paid on, and the money goes back to the card that paid — no card needed at the till.
{% endhint %}

## How do we get started?

Ask us to switch on the Stripe extension for your organization. Everything after that is yours to do.

Add the Stripe payment method under **Admin → Settings → Payment Methods**.

Then, for each store: add the extension under **Admin → Stores → \[store] → Extensions** and fill in the **Account ID** from your Stripe account, activate the payment method under **Payment Methods**, and open each till under **Tills** to set **Payment Terminal** to <kbd>Stripe</kbd> and enter the **Stripe Terminal ID**.

The payment method stays hidden on a till until both the terminal type and the terminal ID are set.

*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/stripe.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.