> 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/vipps-mobilepay.md).
# Vipps MobilePay
Your customer pays for the sale from the Vipps app on their own phone.
## What is this?
Vipps lets your customer pay from the Vipps app on their own phone. No card, no terminal — you enter their mobile number and the payment request lands in their app.
Vipps is the payment method Flow Retail integrates with. MobilePay is not offered as a separate payment method.
***
## How does it work?
On **Choose payment method**, pick Vipps 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 request goes straight into the customer's Vipps app — there is no landing page and no choice of payment method. The till shows Processing payment... and stays there until the customer confirms or you cancel, so you cannot serve the next customer from that till in the meantime.
When the customer approves, Flow Retail captures the amount and the sale completes on its own.
A refund is sent back to the original Vipps payment.
{% hint style="info" %}
To send the customer a link and let them choose how to pay, see [Payment links](/docs/day-to-day-operations/selling/payments/payment-methods/payment-links.md). The Vipps option described there is this same payment method.
{% endhint %}
***
## How do we get started?
Ask us to switch Vipps on for your account.
Then add Vipps to each store under **Admin → Stores → Extensions**, with that store's Vipps merchant serial number, and enable the Vipps 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/vipps-mobilepay.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.