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

# Dintero Payment

Send customers a Dintero payment link so they pay on their own phone.

## What is this?

Dintero is a PSP (Payment Service Provider). With it, your customer gets a payment link and pays on their own phone, choosing from the payment methods you have enabled in the Dintero backoffice. Depending on your Dintero setup, these can include:

* Vipps (Norway)
* Vipps MobilePay (Denmark)
* Visa (both EU consumer cards and non-EU consumer cards)
* Mastercard (both EU consumer cards and non-EU consumer cards)
* Klarna
* Swish (Sweden)
* Apple Pay
* Google Pay
* Walley
* Billie

It works for customers in the store, by phone or by chat, and as a fallback if your card terminals stop working.

Flow Retail has two Dintero payment methods: **Dintero**, the payment link described here, and **Dintero terminal**, for card terminals.

## How does it work?

Create a sale as normal, choose **Dintero** as the payment method, and enter the customer's mobile number. The customer gets an SMS with a link, pays on the Dintero page, and the order completes on its own. Add an email address too, and the link is sent both ways.

{% hint style="warning" %}
You cannot send a Dintero payment link and leave the sale. **The till waits until the customer completes the payment, or until you cancel it.**
{% endhint %}

Other limitations:

* **A mobile number is required.** Email alone will not start the payment.
* **Norwegian mobile numbers only** — 8 digits starting with 2–9, optionally prefixed `+47` or `47`.
* **The SMS and email are in Norwegian.**

To refund, use **Dintero**, the same method the customer paid with, not **Dintero terminal**.

[Payment links](/docs/day-to-day-operations/selling/payments/payment-methods/payment-links.md) walks through the till step by step.

## How do I get started?

1. Sign up with Dintero on their website. Choose Flow Retail as your partner, so that we automatically get access to do the configuration.
2. Make sure the SMS extension is active on your account. Dintero cannot be set up without it.
3. Contact our support and tell us which store(s) you want Dintero on. This normally takes 1–2 days, and we will need access to your Dintero account.
   1. We create the API key and add it to the Dintero extension
   2. We configure it on the relevant store(s)
   3. We do one test sale to confirm everything works. Do at least one real sale yourself to double-check

## What about accounting?

Dintero handles every payment that goes through it, so you get one payout from Dintero whether your customers paid by Vipps, Klarna or card.

Dintero has its own payment method in Flow Retail, which can be given an accounting number, so payments and payouts are easy to balance. Contact Dintero about payouts or reports, and us about the accounting number setup.

*Last updated 24.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/dintero-payment.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.