Skip to main content

Getting started

When your Merchant Agreement is approved and your product order is sent, you will receive an email with credentials for accessing the test environment:

  • Sales unit name
  • Merchant serial number
  • Credentials for logging into the Vipps test app

For information about applying for services, see the Applying for services FAQ.

Start testing in the test environment

You will need the following:

  1. A test user. All merchants automatically get a test user.

  2. Test keys.

    Log-in to and get your test API keys, as described in API keys.

  3. The test app.

    Download and install the Merchant Test (MT) app as described in the test apps section.

  4. The test server, See test servers for more information.

  5. A tool allowing you to test the API.

    • curl is a command line tool where you can enter API requests and get responses.

    • Postman has a Graphical User Interface which allows you to build your API requests and save them for later.

      Please note: Postman now only supports a cloud version. Many companies don't have permission to save keys in the cloud, as they are very secret and allow for transferring money.

      If you wish to use Postman, we have created collections for the APIs (e.g., ePayment). These can be used to quickly run through the requests after updating a few global variables in the Vipps MobilePay Global Postman environment.

The production environment

When your product order is approved, you will get an email stating that you can get access to the API in the production environment.

Log in to to get your production API keys.

Now, you can start making API requests to the production server (e.g., create a payment request that goes to a real user's Vipps app).

Best practices

It is very important that you check the return response of each API call. You will get information about potential problems that could cause the customers problems or might cause you to lose money.

We strongly recommend using the API Dashboard for detecting errors in the API use, in addition to normal monitoring.