Skip to main content


Technical information for partners.

How to become a partner

If you and your merchants have a good volume and great potential, we would like to have you on the team as a partner. The goal of the partner program is to find areas where we can work closely together and experience good growth - together. The collaboration will give you good exposure and opportunities for even better solutions for our customers.

Partner types

Vipps MobilePay has four types of partners:

Platform partner

Platform partners provide a closed, ready-to-use platform for their merchants. They do all integration with the API platform, do all development and maintenance on their platform, and also provide all support for the merchants.

Partners with Partner Plus and Partner Premium can and should use partner keys. Platform partners on these partner levels use the API platform on behalf of merchants. This means that they can initiate payments, captures, refunds, and other relevant transactions.

Merchants that use a platform partner with Partner Plus and Partner Premium never need to see their API keys, since the partner uses partner keys.

Partner keys can be used with the Management API.

Reseller partner

Assist merchants in development of the merchants' integration. Typically, a consultancy firm doing development for the merchant. A reseller partner does not use the API platform on behalf of the merchant.

Merchants that use a reseller partner must provide the API keys to the integration partner. See Common topics: API Keys.

If the reseller partner continues to run, manage, and develop everything related to the Vipps MobilePay integration after it has been developed, and also manage the API credentials on behalf of the merchant, the partner is similar to a platform partner and should use partner keys.

Plugin supplier

Develops Vipps MobilePay official open source plugins on contract for Vipps MobilePay.

If a partner uses official Vipps MobilePay plugins to implement a integration for a merchant, the API credentials for the merchant must be used, and the partner uses the API platform on behalf of the merchant.

PSP partner

Uses the PSP API to offer Vipps MobilePay to its merchants.

Information for PSP (Payment Service Providers) is here: PSP API, including PSP Signup API.

More about partner types

A partner may act as a different type of partner in different situations. It is possible for a partner to both develop an official Vipps MobilePay plugin and to be a platform partner.

This document is mainly for platform partners that act on behalf of merchants, using one set of API keys for all merchants: Partner keys. Other partners must rely on each merchant's individual API keys.

Partner levels

See: Partner levels.

Apply on

Please visit the partner page at, read through our FAQ, and fill out the form.

Integrate with the API platform

See developer documentation for information about how to get started.

When your application is approved, you will receive an email with details about access to the test environment.

If you already have a pilot merchant that has access to the API platform, you can also use the merchant's API keys for the test environment for development.

Please note: Access to the production environment requires thorough checks required by law. For most partners this is not relevant, as it is the partner's merchants that will need production access. The partner only needs access to the test environment to complete an integration.

Finishing the integration and going live

An integration is considered complete when all the elements of the relevant API checklists are done. See the checklists:

Important: Please make sure to read and understand the checklist. You must provide the required information, such as reference, paymentDescription and HTTP headers. If you simply send a copy of the checklist with "OK" for each item, we will have to ask you again to complete the checklist.

In addition to the checklists mentioned above, all partners are required to complete the following:

Required to become a partner
As a partner, you accept the Partner terms and conditions
Provide technical documentation for merchants regarding:
- How to apply for products (a URL, plain text or PDF is preferred)
- How to configure and use the solution (a URL, plain text or PDF is preferred)
- Frequently Asked Questions (FAQs) for merchants (a URL, plain text or PDF is preferred)
Provide one pilot customer to verify the integration in the production environment (send organization number and name)
Describe how your integration has been set up, with a link to a demo, or provide screenshots (PDF is preferred).

When the integration checklist is completed, notify Vipps MobilePay Integration Service ( as described in the checklist, with reference examples from the test environment, pilot customer info, and a description of the implemented solution.

Vipps MobilePay Integration Service will verify the integration and contact you.

After the checklist is approved, you will receive all necessary information from

We then add you to the partner page(s) on, and in the signup forms on where the merchants can sign up and select you as their partner.

Technical information for partners

Partner keys

As a partner, you manage transactions on behalf of Vipps MobilePay merchants. We provide you with partner keys, which allow you to use your own API credentials to make API calls on behalf of your merchants (i.e., the sales units that are connected to you as a partner).

This means that you don't need to use the merchant's own API keys.

See: Partner keys.

Please note: Partner keys are only available for Partner Plus and Partner Premium.

Plugin development

All official plugins are open source, free to use, and available in our plugin section, as well as on the platforms they are designed for.

We encourage submitting issues and pull requests to improve the plugins.

If you have developed, or plan to develop, a plugin for Vipps MobilePay, and you think it may be a candidate for becoming an official plugin: See How to become a partner and let us know what your plans are.

How to get access to

Partners that have a Norwegian organization number and Norwegian BankID can order Login on The requirements for compliance are simpler than other products, since Login API does not allow for payments.

Please note:

  • The partner must have a website.
  • The partner's Norwegian organization number must be clearly visible on the website.
  • The partner must mention in the application that the application is for a partner and that it's for access to the API for development.

When the partner's order for Login is approved, the partner can log in on and manage their own sales units in the test environment.

For information about the test environment, see: Developer resources: Test environment.

Please note: Partners can also ask the merchant to create a user for them, so they get access to the merchant's MSN on as described in detail with screenshots here. The user permissions are described (in Norwegian) here.

See: Developer resources: Vipps Portal: Permissions and users.

How to sign up new merchants

The information below is for platform partners.

All merchants must have a customer relationship with Vipps MobilePay, in addition to the one with the partner.

A merchant that already has a customer relationship with us still needs to apply for a new product (sales unit) to use with a new partner. See: How to change partners for a merchant.

Merchants that do not use a platform partner must sign up on their own on

Management API

The Management API enables a partner to "pre-fill" the product order form on on behalf of a merchant, so the merchant can log in, check the data, and submit the product order.

See: Pre-fill a product order

Please note: A partner that only rarely needs to onboard a new merchant can have the merchant order a product on instead of using the Management API's "pre-fill" functionality. The partner may also log in on and manually fill in the form, which will be similar to using the Management API's "pre-fill" functionality.

Manual signup

See: Manual signup.

Typical reasons for delays

The application solution on contains a lot of help and tips, as well as links to more information.

There are still some common problems that cause delays:

  • The merchant has signed a merchant agreement, but has not ordered any Vipps MobilePay products.
  • The application is not signed by a person that has signatory rights. Merchants can check who can sign at Brønnøysundregistrene.
  • The merchant's website does not have the legally required terms and conditions.
  • The merchant's website does not have the organization number clearly visible.
  • The merchant has not provided enough information about what they want to use Vipps MobilePay for (Spesifiser kort hvilke varer/tjenester dere selger, in English: Briefly specify which goods/services you sell).
  • If the merchant website is not the distribution channel, the requirements outlined above shall also apply to the partner platform.
  • Vipps MobilePay has sent an email requesting additional information, but has not received a reply. Merchants should check their "spam" and try to search their email for "vipps".
  • The application has been declined. Vipps MobilePay only informs the merchant about this, not the partner. The reason for declining may be related to risk and compliance, and thus sensitive.

How to check if a merchant is signed up with the partner as partner

Important: For partners: Vipps MobilePay has limited capacity to handle partners' requests to "just check something", even though it may be trivial. We therefore recommend the following priority:

  1. Integrate with the Management API, so the functionality is made available in the partner's own admin interface.
  2. Use the Management API manually with the Postman collection.
  3. Ask the merchant to create a user for the partner on, so the partner can check on behalf of the merchant: How to add a user on
  4. See the FAQ for how to check if a sales unit has skipLandingPage enabled or which capture type it has direct capture turned off.

Please note: Vipps MobilePay cannot share information about the status of a merchant's agreement or product orders. This is because we need explicit consent from the merchant to share the information with the partner, and the consent must also be possible to withdraw. We have not been able to prioritize implementing this consent management. Also: Some applications may be declined due to too high risk, suspicion of fraud, etc. We can not "leak" this information about the merchant. The partner must always check with the merchant.

The merchant can check the status on any time.

When a new merchant gets their Vipps MobilePay application approved, an email is sent to both the merchant and the partner with information about:

  • The merchant's organization number
  • The merchant's name
  • The sales unit's MSN
  • The sales unit's name

The Management API enables a partner to look up merchant serial numbers based on the merchant's organization number, and also retrieve details of a specific sales unit based on the sales unit's MSN.

How to change partners for a merchant

See: How to change partners.

The deprecated Signup API

The deprecated legacy Signup API, also called "partial signup", is no longer available, and partners should use the more efficient partner keys (and the Management API when possible).

FAQ for partners

You may find answers to your questions on our FAQ section on the bottom of the partner page on


Please contact your partner manager. If you do not have a partner manager, please contact

We're always happy to help with code or other questions you might have! Please create an issue, a pull request, or contact us by email: