Skip to main content

Test environment

Vipps This is available for Vipps.

MobilePay This is available for MobilePay, with the limitations below.

All customers with access to the APIs have access to the Merchant Test (MT) environment.

The test environment is suitable for testing most of the API functionality, but some functionality in the production environment is not available in MT. In general, MT does not contain functionality that requires integration with third parties.

The test and production environments are completely separate and use different API keys.

Limitations of the test environment

Regional limitations

These limitations will be fixed, but we don't yet have a time estimation. For now:

  1. The test app has the orange Vipps color scheme and not the blue MobilePay color scheme.
  2. Only Norwegian phone numbers are supported.
  3. All test merchants appear as Norwegian merchants in the app.
  4. Currency: Limited support, please test with NOK.

Other limitations

info

There is no SLA or uptime guarantee for the test environment. We will not make any fixes, etc. outside typical Norwegian office hours. See the Status page for automatically updated status information.

Functionality that is not available in the test environment, a non-exhaustive list:

  1. Unscheduled maintenance may occur. We will do our best to inform you with Status page.
  2. Freestanding card payments (in the ePayment API) do not work in the test environment.
  3. Push alerts may be unavailable or unstable. To see payment requests: Click the "Payments" button at the bottom, and then "pull to refresh" on the Payments screen.
  4. Email verification has some quirks, see Email address.
  5. Partner functionality, like the relationship between an MSN and a partner, and the use of partner keys, does not work as in the production environment. In general, partner functionality is not available. See Partners.
  6. The Management API is not available in the test environment.
  7. There is no equivalent to portal.vippsmobilepay.com for the test environment. Payments must be checked with the API.
  8. There are no settlements in the test environment, and therefore no settlement reports, no SFTP service, and no Report API. The only way to test the complete settlement flow is in the production environment.
  9. The user's email address can not be verified in the normal way. See: Email address.
  10. Payment of invoices is unavailable.
  11. We allow 10,000 incorrect PIN attempts before locking the user's account.

To test functionality that is not available in MT, you will have to use the production environment in a controlled manner, using a real user and a real merchant.

Start testing in the test environment

You will need the following:

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

  2. API keys.

    Log-in to the portal.vippsmobilepay.com and get your test API keys, as described in get your API keys.

    To learn more about API keys, see About 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 you will use is listed on the test servers page.

Access to the test environment

Merchants

All merchants with API access have access to the test environment.

A test sales unit is automatically created when the merchant submits an order for a Vipps MobilePay product that includes an API. The details can then be found on the Developer section on portal.vippsmobilepay.com. See the Merchant portal section for details about logging in.

Portal test sales unit

See:

Partners

Partners can get access to the test environment by ordering the Login API. See Partner: How to get access to your sales units on the merchant portal.

Test server

The test and production environments are separate and require different API credentials:

The servers are accessible around the world. Vipps MobilePay only relies on the API keys, and no requests to our servers are blocked on our side by IP addresses or similar.

See Servers for more information.

Test merchants

The test environment and production environments are completely separate. You will, therefore, need to use a different set of API keys for the test environment.

Test merchants have access to all the common APIs on the API platform.

All Vipps MobilePay customers can create as many sales units ("merchants") as they need in the test environment. Sale units in the test environment can not be changed.

See: Developer resources: Merchant portal: How to create a test sales unit.

note

Sales units in the production environment must follow strict rules (regulatory and other), so you may not be able to get the same sales unit configuration there, even though you have it in the test environment.

Test users

A welcome email is automatically sent to all new customers. This email contains information about your test user.
Please search your mail, including the spam/junk folder, if you do not find it.

You can also find the same test users by logging in to portal.vippsmobilepay.com, going to the Developer section, and selecting the Test users tab.

On this page it is also possible to create additional test users.

Portal test users

note
  • Test users must only be used in the test apps.
  • You must log in (not register) as the test user in the test app, before you can complete payments or logins as that user.
  • You may use the same test user on multiple devices.
  • Test users are not connected to any merchant, they can be used with any merchant and sales unit in the test environment.
  • We can not create test users with specific attributes (phone number, name, numbers, age, etc.).
  • There is no way to get a test user in the production environment. The production environment only contains real users and data.

Phone number

The test user has everything required to complete a payment. The test user's mobile number works on all phones and on all networks.

info

Do not use the test phone number in the production environment, because the test number may be a phone number for a real Vipps or MobilePay user.

You will get your test phone number in the welcome email. If you did not receive this, contact your partner contact (if you have one) or customer service.

Payment card

The test user is registered with a payment card, and it is not possible to add new cards in the test app.

Email address

You can add a real email address on a test user from the Profile -> Personal information -> Email section in the app.

note

In the test environment verification of emails can only be triggered in a Login flow (if the merchant requests the email scope), or from clicking “send email” from the email address section under the profile page. After updating the email address you will need to close and reopen the app for this option to be available.

Just updating the email and saving it will not trigger an email to be sent for verification. The indication on the profile page that the email is not verified can be ignored.

Other data

The test user's name, birthdate, etc. are randomly generated when the test user is created and cannot be changed.

Test amounts

Vipps MobilePay supports using special amounts in the test app. Use these amounts to always get the same result.

AmountError
1.51Insufficient funds
1.82Refused by issuer
1.83Suspected fraud
1.84Withdrawal limit exceeded
1.86Expired Card
1.87Invalid card
1.973D Secure denied
2.01Unknown result for 1 hour
2.02SCA required
note

The force approve endpoint does not support this functionality.

Test apps

The test apps for iOS and Android are identical to the production apps, but connect to the Merchant test environment (MT) instead of the production environment.

The test apps can be installed on the same device as the production apps without conflicts. The test apps use the vippsMT:// URL scheme, and the production apps use vipps://.

Only test users, with random "fake" phone numbers, are available in the test environment. Normal (real) users are not available, so you cannot use your own phone number with the test apps.

info

Do not use the test phone number in the production environment, as the test number may be a phone number for a real Vipps or MobilePay user.

Install MT on iOS

The iOS test app is available for everyone in Apple TestFlight. You do not need an invitation or an activation code.

note

You only need to log in with your test user, not register.

  1. Open the TestFlight link on your iOS phone (it will not work on macOS, and you cannot search for Vipps in TestFlight)
  2. Install the "Vipps MT" app
  3. Open the "Vipps MT" app
  4. Enter the test phone number, that was sent in the welcome email to the email address used in the registration (please double-check before asking for a new test phone number). Your normal Vipps or MobilePay user is not available in the test environment.
  5. On the "Verify your number" screen: Use PIN 1236.
  6. On the "Enter your code" screen: Use PIN 1236.
  7. Enable Face ID (or Touch ID) and confirm with PIN 1236.
  8. Accept push notifications.

You are now ready to use the iOS test app connected to the test environment.

Install MT on Android

The Android test app is available for everyone in App Center. You do not need an invitation or an activation code.

note

You only need to log in with your test user, not register.

  1. Open the App Center link on your Android phone (it will not work on a PC/Mac). If you get a push message prompting to whitelist the source, you should be able to do this via the "Settings" button.
  2. Install the "Vipps Android" app
  3. Open the "Vipps Android" app
  4. Enter the test phone number, that was sent in the welcome email to the email address used in the registration (please double-check before asking for a new test phone number). Your normal Vipps or MobilePay user is not available in the test environment.
  5. On the "Verify your number" screen: Use PIN 1236.
  6. On the "Enter your code" screen: Use PIN 1236.
  7. Enable touch ID and confirm with PIN 1236.
  8. Accept push notifications.

You are now ready to use the Android test app connected to the test environment.

Other versions of the test app

It may sometimes be necessary to use specific app versions in MT. This happens when the production apps and the production environment are not quite in sync with the test environment. When this happens, we update the Status page for the test environment with details.

Using an emulator

If you use an app emulator, and not the native apps installed on a real phone, you may experience problems - including having to log in "from scratch" every time you start the app in the emulator.

Next steps

If you aren't sure what to do next, see the Getting started page.

Help us improve our documentation

Did you find what you were looking for?