Get ready for migration
Are you ready to switch from the MobilePay facade and take advantage of our new common platform and all the features and possibilities our new joint Vipps MobilePay can offer? Then you have come to the right place! Switching to the Vipps MobilePay APIs means that you can utilize the entire platform and combine the APIs to suite your use in the best way possible. Check out our recommended flows for inspiration and best practice.
Getting started
In order to start the migration, you must first get access to the test environment to try out the new solution.
- Partners
- Merchants
- All partners must register again, even though you already had a partner agreement for MobilePay. Please visit the partner page for details or contact your partner manager.
- Once you have registered you will receive test access in order to start testing. Check out the test environment documentation for details on how to start testing.
- Use the migration guide for either App Payments or Subscriptions to map your existing integration to your new integration.
- Once you are satisfied with your test you must send us a checklist to verify your solution.
- When we have approved your solution you will receive production keys and can start using the new solution for your merchants. Note that all merchants must be linked to you as partner.
- Check out the test environment documentation for details on how to get access and start testing.
- Use the migration guide for either App Payments or Subscriptions to map your existing integration to your new integration.
- Once you are satisfied with your test you can go live with your solution. Fetch your production keys in the merchant portal.
Make sure to stay updated by signing up for our technical updates and follow the operational status page.
Authentication
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:
-
Merchant API keys: These are specific for each sales unit. A merchant can have multiple sales units, and 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 API keys: As a partner you can manage sales units and make transactions for your merchants using partner API keys. 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 merchant API keys to perform test. But don't worry, the flows are the same regardless of the type of keys. 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.
Management
With the Management API you can retrieve merchant data, such as sales unit ID (MSN), and as a partner you can prefill product orders.
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 have migrated all the existing MobilePay merchant data so that it is available on the new platform.
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.
FAQ
How does the mapping between partner and merchant work?
If you are already a MobilePay partner, we handle the mapping on our side for your existing merchants. However, New merchants should actively choose you as their partner in the Merchant Portal to establish the link. If merchants have existing sales units they want to link to you as partner please contact partner@vippsmobilepay.com to request to be registered as their partner.
Can we use our existing MobilePay credentials?
As long as you use the MobilePay facades (Subscriptions and App Payments), you can continue to use your existing MobilePay credentials in production. But you must 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 facades you can use the existing MobilePay credentials for existing merchants and new Vipps MobilePay credentials for new merchants.
Must the new integration be verified?
All new integrations must be verified, this includes migration solutions as well. For partners, we will do the verification, and merchants can do a self verification. The verification consist of a checklist which must be completed before you can go live with the new solution.
- Subscriptions facade must complete the Recurring Checklist
- App Payments facade must complete the ePayment Checklist