> 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/swish.md).
# Swish
Your customer pays for the sale from the Swish app on their own phone.
## What is this?
Swish lets your customer pay from the Swish app on their own phone. You enter their mobile number and the payment request lands in their app.
Swish is for Swedish stores. The account has to be registered in Sweden, and the sale has to be in Swedish kronor.
***
## How does it work?
On **Choose payment method**, pick Swish and enter the customer's **Mobile number**. It fills in by itself when the sale has a customer with a mobile number on file.
The number must be 11 digits starting with 46 — the Swedish country code without the plus. Anything else is turned away with **Invalid phone number '…'. Phone number must contain 11 digits. 46XXXXXXXXX**.
The till shows Swish payment started and stays there until the customer pays or you cancel, so you cannot serve the next customer from that till in the meantime. When the customer pays, the sale completes on its own. If they decline, or Swish reports an error, the payment fails and you can pick another method.
A refund is sent back to the original Swish payment.
{% hint style="warning" %}
A Swish payment can only be refunded within 13 months of the sale.
{% endhint %}
***
## How do we get started?
Swish needs a merchant certificate, its password and the matching CA certificate from your Swish agreement. Send those to us and we register them on your account.
Then enable the Swish payment method in the stores where you want it.
***
*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/swish.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.