Skip to main content

QR to site (product selection)

Also covered in In-person payments

This flow is also documented in In-person payments → Static QR → Merchant Redirect QR, which covers unmanned location scenarios where customers select products through your website.

Customer scans a static QR code posted on the vending machine, is redirected to your website where they select products and pay with Vipps MobilePay.

User scans QR, pays, and gets receipt

Flow diagram: 5-step QR-to-merchant-site product-selection process. (1) Customer scans a QR sticker and merchant website opens. (2) From the website, customer selects the items. (3) From the website, customer selects to pay with Vipps. (4) The payment appears in their app and they authorize it. (5) The payment is confirmed.

  1. Customer scans QR - Customer scans the merchant redirect QR code posted on the vending machine.
  2. Redirect to website - Customer lands on your website linked to that specific vending machine.
  3. Customer selects products - Customer browses and selects products through your web interface.
  4. Initiate payment - Create payment request with selected products using userFlow: "WEB_REDIRECT".
  5. Customer authorizes - Customer approves payment in their app.
  6. Capture payment - Confirm the transaction is complete.
Use when you want product selection on your website

This flow works when you don't have a customer-facing screen and want to offer product selection through your own web interface instead of the vending machine.

Regulatory requirement

Per regulations, specify "customerInteraction": "CUSTOMER_PRESENT".

View sequence diagram

QR to site (product selection) and payment

  1. Customer selects products on the merchant site.
  2. Merchant adds the products to the sale.
  3. Customer selects to pay with Vipps MobilePay.
  4. Merchant initiates a payment request with order details via the ePayment API.
  5. ePayment API requests payment from the customer.
  6. Customer confirms the payment.
  7. Webhooks API sends the merchant a webhook with the payment authorization status.
  8. Merchant captures the payment via the ePayment API.
  9. ePayment API returns the status of the capture.
  10. Merchant verifies that the POS status matches the capture.

Technical details​

Last updated on