Skip to main content


Here are the QR API Frequently Asked Questions (FAQ). See the QR API guide for all the technical details. For general information and questions, please check in the Knowledge base.

API version: 1.1.1.

Can we make our own QRs for payment and redirects?

Technically, yes. Is it a good idea, and will it work? No.

Firstly, we have a security aspect. We only allow QRs on the domain to be scanned within the Vipps or MobilePay app, to ensure that we have control of everything that is scanned. For payment QRs, using our own domain also means we have full control over universal linking. These two aspect forces us to only allow our own QR codes for payments.

Addition: Our brands have a very high level of trust from users. Properly branded QR codes will look familiar to users resulting in a higher completion rate. The QR codes also contain very little data, have good contrast and are very reliable to scan.

Why are there extra API calls to retrieve the QR code?

The QR API is an addition to the eCom API. Merchants can integrate with the eCom API for many use cases. The QR API adds "just" the QR code functionality.

Yes, there is one extra API call, but the overhead is minimal. With current HTTP technology, the user will not notice any delay.

What happens with the user after the payment?

In the One-Time Payment QR flow, the user will be sent to the receipt view in the Vipps app once the payment is complete. The Merchant Redirect flow will redirect the user to the URL that you specify.

Why do I get the error "Can't connect to store. Try to scan the again or pay in another way" in the app?

When using Merchant Callback QR you need to subscribe to the user.checked-in.v1 Webhook. If this event is missing or we do not receive a successful response to the webhook the user will see the error "Can't connect to store. Try to scan the again or pay in another way" in the app.

Help us improve our documentation

Did you find what you were looking for?