User data & privacy
For detailed information about who can use Vipps MobilePay, see Who can use Vipps MobilePay.
User anonymity in transactions​
Vipps MobilePay is anonymous by default. Users can pay without sharing personal data with the merchant.
Phone numbers entered on the landing page are only used for push notifications and are not passed to the merchant. If your POS integration allows cashiers to enter phone numbers, you may store them in compliance with GDPR.
User information and consent​
Merchants can request user information such as phone number, name, email address, and address, but only as part of a payment or login flow with user consent.
Available methods:
- ePayment API: Profile sharing during payment
- Login API: User info during authentication
- eCom API (legacy): Userinfo API after payment
Users must always give consent to sharing data with a merchant. There is no API to look up a user's address or retrieve purchases without consent.
Transaction overview: The merchant portal shows customer names for Vippsnummer and MobilePay-nummer payments, but shows payment IDs for online payments
User lookup and privacy protection​
Vipps MobilePay does not offer a lookup service to check if a phone number belongs to a user, as this would leak information. Payment initiation attempts with invalid phone numbers will fail with an error.
For privacy reasons, payment failures do not disclose which scenario applies:
- Not a Vipps MobilePay user
- User too young to pay businesses
- Deleted account
- Blocked account (temporary or permanent)
Users accept terms and conditions that allow merchant lookup when initiating payment with their phone number. However, users can pay without sharing their phone number with the merchant, and users with unlisted or secret numbers can still use Vipps MobilePay.
Customer presence requirements​
Customer present: For physical settings (POS, restaurants), specify "customerInteraction": "CUSTOMER_PRESENT" in the ePayment API request. Required for compliance and reporting. See Specify customer present.
Customer not present: Use online payment methods with Payment Integration. Order details required via:
- ePayment API:
receiptproperty - eCom API (legacy): Order Management API
An online sales log must be available as an alternative to digital receipts.