> 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-links.md).

# Payment links

Send your customer a link so they can pay on their own phone.

**Your customer can pay on their own phone. Dintero sends them a link by SMS; Vipps pushes a request into their app.**

Useful when the customer has no card with them, orders by phone or chat, or when a card terminal fails.

{% hint style="info" %}

#### What you need

**Dintero** set up on the store with a Payment Profile, or **Vipps** for the app variant. The **SMS** extension must be active, and the payment method must exist under **Admin → Settings → Payment Methods**.
{% endhint %}

|                            | Dintero payment link                 | Vipps                      |
| -------------------------- | ------------------------------------ | -------------------------- |
| Customer gets              | An SMS with a link                   | A request in the Vipps app |
| Customer needs             | A Norwegian mobile number            | The Vipps app              |
| Customer pays with         | Anything your Dintero profile offers | Vipps only                 |
| Cashier can leave the till | No                                   | No                         |

***

## How does it work?

Register the sale as normal, choose the payment method, and enter the customer's mobile number. Flow Retail sends the link, and the till waits until the customer pays.

{% stepper %}
{% step %}

#### Create the sale

Add the products as you would for any other sale.
{% endstep %}

{% step %}

#### Choose Dintero

On **Choose payment method**, pick Dintero.
{% endstep %}

{% step %}

#### Enter the customer's details

A mobile number is required, and fills in automatically if the order has a customer. Add an email address too, and the customer gets the link both ways.
{% endstep %}

{% step %}

#### Send it

Select **Pay**. The screen shows **Payment link sent to customer on SMS**, with the number.
{% endstep %}

{% step %}

#### Wait for the customer

The till shows **Waiting for payment confirmation from customer** and checks every few seconds. When the customer confirms, the order completes on its own.
{% endstep %}
{% endstepper %}

The customer opens the link on their phone, picks how to pay on the Dintero page, and confirms.

***

## Can I send the link and serve the next customer?

No. The payment screen stays open until the customer pays, and you cannot use that till until then.

<kbd>Escape</kbd>, the back button and the close button are all blocked. The only way out is **Cancel**, which cancels the payment and stops the link working.

{% hint style="warning" %}
If the customer leaves to find their phone, that till stays tied up until they return or you cancel.
{% endhint %}

If the till crashes or restarts, nothing is lost. Reopen the order and the payment screen continues where it stopped.

***

## What are the limitations?

There are three:

* **A mobile number is required.** Email alone will not start the sale.
* **Norwegian numbers only.** 8 digits starting with 2–9, optionally prefixed `+47`. Stores outside Norway cannot use this yet.
* **The message is in Norwegian**, whatever language you and your customer use elsewhere.

The customer chooses how to pay, from whatever your Dintero payment profile offers — typically Vipps, card and Klarna. You manage that list in the Dintero backoffice, not in Flow Retail.

***

## How do I refund a payment link?

Use Dintero, the same method the customer paid with. Choose Dintero terminal instead, and Flow Retail blocks the refund:

> This order was paid with Dintero payment link. Use Dintero (payment link), not Dintero card, to refund.

***

## Can I use Vipps instead?

You can, but it is not a payment link. You enter the mobile number and Vipps pushes a request into the customer's Vipps app — no link, no SMS, no choice of payment method. The customer needs the Vipps app, and it ties up the till the same way.

{% hint style="info" %}
Dintero can offer Vipps as one option on its payment page. That is the route if you want Vipps through a link.
{% endhint %}

***

## Which other providers support payment links?

None. Dintero is the only one. Adyen, for example, works only as a card terminal in Flow Retail. Some providers offer payment links in their own products, but we have not built those integrations.

***

## What's next?

[Dintero Payment](/docs/day-to-day-operations/selling/payments/payment-methods/dintero-payment.md) covers pricing, sign-up, and how to get it switched on for your store.

***

*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-links.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.
