Skip to main content

How the QR API works with personal QR

View as Markdown (opens in a new tab)
Install AI tools

Give your assistant up-to-date guidance for our APIs, with our plugin or without it.

The plugin is still under development. See the AI tools page for details.

Run both commands, in order.

claude plugin marketplace add vippsas/agent-toolkit
claude plugin install vipps-developer@agent-toolkit

For troubleshooting, see the full instructions.

Enable fast, contactless in-store payments by scanning your customer's personal QR code from their Vipps or MobilePay app. This allows you to identify customers and send payment requests without asking for their phone number.

Personal QR payment flow diagram

Flow diagram: 6-step in-store payment process. (1) Identify the customer (scan their personal QR). (2) Add the products to be purchased. (3) Send payment request. (4) Customer authorizes the payment. (5) Register the purchase and send a receipt. (6) Customer gets the receipt in the app.

1. Customer shows their personal QR code​

Every Vipps and MobilePay user has a personal QR code available in their app. The customer opens their app and displays their personal QR code.

Vipps personal QR

Screenshot: Personal QR code screen in the app (Vipps or MobilePay), showing the customer's unique QR code ready to be scanned at checkout.

2. Merchant scans the QR code​

The cashier or the customer uses a QR scanner to scan the personal QR code. This can be done with:

  • Customer-facing scanner - A permanent scanner positioned for self-service
  • Cashier scanner - A handheld or wired scanner operated by store staff

POS hand scanner with Vipps button

Screenshot: A hand scanner at a point-of-sale terminal used to scan a customer's personal QR code from the app (Vipps or MobilePay).

3. Merchant creates payment request​

The scanner reads the QR code as text: a URL that starts with https://qr.vipps.no/. The merchant's system sends this URL straight to the ePayment API, with no need to look up the customer's phone number first. The payment request has:

  • userFlow set to PUSH_MESSAGE to send the payment directly to the customer's app
  • customer.personalQr set to the scanned URL, unchanged
  • customerInteraction set to CUSTOMER_PRESENT (required for regulatory compliance)
  • Optional receipt.orderLines to display purchase details

See Personal QR feature for complete implementation details.

Need the phone number?

If you need the customer's phone number for something else, such as a loyalty program, call the Personal QR exchange endpoint. The scanned QR code contains a tokenized string (in Denmark and Finland) or a clear-text phone number (currently in Norway), so use the endpoint rather than reading the number from the code.

4. Customer receives and approves payment​

The payment request appears as a push notification on the customer's phone. They open their Vipps or MobilePay app and see the payment details, including any order line items sent by the merchant.

The customer reviews and approves the payment in their app.

5. Merchant completes the transaction​

After the customer approves the payment:

  • The merchant receives confirmation via webhook or by polling the payment status
  • The merchant captures the payment to complete the transaction
  • The customer receives their receipt

Technical implementation​

For detailed API specifications and code examples:

Last updated on