Vipps MobilePay

JWT/Token example

Test users

To test Vipps MobilePay, you need to install the Vipps app in a test version on your device. Follow the Vipps guide with instructions on how to set up test apps.

Available data / scopes

Username is always made available.

For applications configured to use a static scope strategy, address, email, phone and birthdate are always made available. You can also configure your tenant so it requests SSN as well.

For applications configured to use a dynamic scope strategy, the following scope tokens can be supplied: address, email, phone, birthdate, gender and ssn (scope=openid phone email...).

The gender scope returns a gender claim. It is a user-chosen value and is only made available when the user has registered a gender with Vipps MobilePay. The possible values are male, female, other and prefer not to say.

Example (partial) authorize request with scopes

https://YOUR_SUBDOMAIN.idura.broker/oauth2/authorize?scope=openid phone ssn&...

Alternatively, you can send them in the login_hint

https://YOUR_SUBDOMAIN.idura.broker/oauth2/authorize?...&login_hint=scope:phone scope:ssn&...

which can be a useful if you are working with technology that does not let you control the scope value.

Branding

Vipps MobilePay has two brandings: Vipps (used in Norway and Sweden) and MobilePay (used in Denmark and Finland). By default, users are shown the Vipps branding.

You can select which branding a user is shown for a given request by passing a market token in the login_hint, using a country code:

https://YOUR_SUBDOMAIN.idura.broker/oauth2/authorize?...&login_hint=market:DK&...

If the market token is omitted or the value is not one of the supported markets, the default Vipps branding is shown.

You can try this out in the Authorize URL Builder by selecting Vipps MobilePay and picking a market.

Ordering Vipps MobilePay

To start accepting real user logins, you must register with Vipps MobilePay as a merchant and receive a set of secret keys (client credentials).

Prerequisites for merchant registration

You must meet the following requirements to be registered as a merchant.

• Your company must be registered in your national business registry (Brønnøysundregistrene in Norway, Virk in Denmark, PRH in Finland).
• You must have a bank account in the country of registration associated with your company’s organization number.
• The person signing the merchant agreement must possess a valid local eID (BankID in Norway/Sweden, MitID in Denmark, FTN in Finland).
• Before you can order the client credentials from Vipps, you will need to have created a production domain in Idura Verify as described in the Getting ready for production guide. Once you have set up the production domain, go to the Vipps MobilePay eID provider screen and take note of the URL displayed. It must be supplied during merchant registration.

Signing a merchant agreement

You can register as a merchant by signing an agreement with Vipps MobilePay. Use the links below to start registration via Idura’s partner setup.

• Vipps MobilePay Login for Customer Service: Use this option if you want to authenticate callers when they contact your customer service.

• Vipps MobilePay Login for Online Web: Use this option if you want to use Vipps MobilePay Login on your webpages to pre-fill user information.

Next steps

After you request client credentials by filling out the online agreement, your application is processed by Vipps. If you are approved, the designated contact person will receive the credentials.

Once you have received the client credentials, enter them into the Idura Verify management UI to configure your Vipps MobilePay integration.