Skip to main content


Here are the QR API Frequently Asked Questions (FAQ). See the QR API guide for all the technical details.

For more common questions, see:

API version: 1.1.1.

See the common FAQ

It contains answers to all(?) common questions about Vipps payments: Vipps FAQ.

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 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: Vipps is an extremely strong brand in Norway, with a very high level of trust. The Vipps-branded QR codes will look familiar to users, and in our experience result in a higher completion rate. The Vipps 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 Vipps QR API is an addition to the Vipps eCom API. Merchants can integrate with the Vipps eCom API for many use cases. The Vipps 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.