Skip to main content

Authentication, Management and Test


On our new platform we will have a shared authentication solution that can be used across all APIs. Therefore, you only need to implement one solution for all APIs.

There are two options for keys:

  • API keys: These are specific for each sales unit. Therefore, one merchant can have multiple set of keys. These keys are found in the portal. You can get both test keys and productions keys in the portal.

  • Partner keys: As a Partner Plus or Partner Premium partner you can manage sales units and make transactions for your merchants. These credentials allow you to make API requests on behalf of the sales units connected to you as a partner. Partner keys are not available in test, instead you will receive a set of API keys to perform test. Production keys are supplied by our partner management team when your solution has been approved. Note that you must keep these keys secret from your merchants. As a partner it is a requirement that you use the Management API to manage your merchants.


If you didn't make the integration yourself, talk with your partner.

Existing MobilePay credentials

As long as you use the MobilePay facades (Subscriptions, App Payments and Online), you can continue to use your existing MobilePay credentials. For the Subscriptions and App Payments facade, you need to switch to the new authentication solution when you need to onboard new merchants. But for existing merchants, you can continue to use your existing MobilePay credentials. When integrating any of the new solutions on our joint Vipps MobilePay platform, you need to switch to the new authentication solution.

You can use your existing MobilePay credentials and your new Vipps MobilePay credentials at the same time. For example, if you are using one of the facade you can use the existing MobilePay credentials for existing merchants and new Vipps MobilePay credentials for new merchants.


With the Management API you can retrieve merchant data, such as sales unit ID (MSN), and as a partner you can prefill product orders. Note that a merchant can have multiple sales units.

Merchant: Basic information and sales unit data can be retrieved.

MSN: The sales unit ID known as MSN is a key part when using the API. It must be supplied to initiate payments etc. We will migrate all the existing MobilePay merchant data so that it is available on the new platform. So that all existing merchant agreements and payment points are ready for the launch.

Prefill product orders: Available for partners. This endpoint is used to ensure that all the data in the product order form is correctly filled in. As a partner you can also choose to "lock" parameters that are normally selectable. This is especially relevant when selecting price packages. Product orders that have been prefilled this way are processed faster, since they are correct and contain all the required information. Using the prefill option also ensures that your merchants are connected to you as partner. Once an order is prefilled the merchants just needs to approve it in the portal. The Report API has a slightly different partner key setup, please read more in the Reporting migration guide.


  1. How does the mapping work? If you are already a MobilePay integrator, we handle the mapping on our side for your existing merchants. However, New merchants should actively choose a new partner in the Merchant Portal


The test environment is called Merchant Test (MT) and is now open for test. MT currently only allows Norwegian phone numbers, currency and merchants, but you can test the API and payment flow. Please see the details of limitations of the test environment.


Management API and Report API is not available in MT and can only be tested in production.

In order to request access to the test environment, please use the following links:

We will e-mail you with the information you need to get started. This is also needed even though you are an existing MobilePay integrator or merchant, since we need your information registered on our new joint platform.

Help us improve our documentation

Did you find what you were looking for?