Login from desktop
Let your customers log in to your website without the need for usernames and passwords.
- Vipps
- MobilePay
First-time login flow​
1. User selects to log in with Vipps or MobilePay​
The user selects the button to log in with Vipps or MobilePay on the merchant's website. The merchant initiates a login request through the authorization endpoint.
2. User enters phone number on landing page​
When the login is initiated from a desktop device, the user is directed to the landing page.
If the user is not remembered in the browser from a previous session, they enter their phone number. They can choose to be remembered in the browser for a quicker login next time. The Remember me in browser option is deselected by default and applies to the browser, independent of merchants.
The user is then prompted to open their Vipps or MobilePay app and follow the instructions there.
If the user is already remembered in the browser, they proceed directly to the app without entering their phone number.
3. User confirms login in the app​
The user opens their Vipps or MobilePay app and verifies the login by selecting the correct number from three displayed challenges. This number appears in a circle on the landing page in the browser, and the user must match it in the app to confirm their identity.
4. User gives consent to share information​
If the merchant has requested profile information (such as name, email, phone number, or address), the user is asked to consent to sharing this information with the merchant.
The user must either accept or decline the full set of requested information—they cannot select individual items.
One-time consent: The user only needs to give consent once per merchant sales unit (identified by the Merchant Serial Number). After this initial consent, it applies across all login scenarios for that sales unit. If the user has previously consented to share information with the merchant's sales unit, this step is automatically skipped.
5. Marketing consents (optional)​
The merchant may choose to collect additional marketing consents from the user using Custom Flow or legacy Marketing Consents.
If configured, the user will be asked to give consents according to the merchant's specifications. This step is most suitable for registration flows, such as joining a customer club or loyalty program.
Merchants can customize the consent collection experience through the business portal. For details, see Collecting consents.
6. User is logged in​
The user is now logged in on the merchant's page.
The merchant may provide the user with the opportunity to edit or add additional information that is not present in their Vipps or MobilePay profile, such as preferences or additional contact details.
Alternative login flows​
After the first login, users may encounter simplified flows depending on their previous choices and preferences.
Returning user with browser memory​
If the user chose to be remembered in their browser during a previous login, they can skip entering their phone number. They're taken directly to the app to confirm the login, making the process significantly faster.
- Vipps
- MobilePay
Instant login for returning users​
When the user is remembered in the browser and has already given consent to share their information with the merchant, the login becomes nearly instant. The user simply confirms in the app, and they're immediately logged in—no phone number entry, no consent screens required.
- Vipps
- MobilePay
Email verification​
If the merchant has requested the user's email address using the email scope, the user must verify their email address in the app when:
- They use Vipps MobilePay Login for the first time
- They change their email address
When email verification is required, the verification screen appears at the beginning of the login flow in the Vipps or MobilePay app:
- Vipps
- MobilePay
See also​
For technical implementation details, see: