MobilePay migration guides

MobilePay and Vipps have merged to become one company with a joint platform. There is one app, branded locally as MobilePay in Denmark and Finland, and as Vipps in Norway and Sweden.

Are you currently using the MobilePay Facade APIs?

The MobilePay facade APIs are Subscriptions API or App Payments API.

If you are currently using the facade APIs for your payment integration, it's important to plan your migration to the Vipps MobilePay API platform as soon as possible. This platform provides a flexible and modern payment solution designed to meet your needs going forward.

To support your transition, we've prepared detailed migration guides that offer step-by-step instructions and best practices for integrating with the Vipps MobilePay APIs.

Please note that the facade APIs will be disabled in 2025, making migration essential. Starting the process now ensures sufficient time and support to complete the transition smoothly before the facade reaches end-of-life.

The timeline is as follows:

Important dates

31 May 2025 - Latest recommended go-live date

To avoid potential issues, extra fees, and to give yourself enough time to address any challenges, we strongly recommend planning your go-live date well before this deadline.

30 June 2025 - End of facade general availability

The facade APIs are no longer generally available. If you're a merchant or partner and want to keep using them, you'll need to make a specific agreement with us at Vipps MobilePay.

Heads up: After this date, using the facade APIs will come with extra fees. Only critical bugs and major issues will be fixed going forward.

Where to start?

First, take a look at the Get ready for migration section to explore the new shared authentication solution and see how you can automate merchant onboarding with the Management API.

Once you've checked that out, you're all set to dive into the migration guides:

• App Payments to ePayment migration guide
• Subscriptions to Recurring migration guide

Still seeing traffic on old APIs?

Even after migrating to ePayment or Recurring APIs, you may still see traffic to the Subscriptions or App Payments facade endpoints. This does not necessarily mean the migration failed – but it does indicate that the old setup is still being used somewhere in your environment.

Why this happens

Old API activity may occur if:

• Scheduled or queued processes run monthly, quarterly, or based on customer events
• Some parts of your system have not been updated (e.g., test systems or internal tools)
• Legacy monitoring or health-check scripts still hit deprecated endpoints
• Older customer support tools or dashboards still use the facade APIs
• Retry mechanisms are still processing delayed requests

What you should do

• Verify all active systems, jobs, and tools are updated to use the new API
• Monitor outgoing traffic to api.mobilepay.dk or api.sandbox.mobilepay.dk
• Work with your technical partner to ensure old endpoints are removed
• Use logging or proxy tools to detect any unexpected traffic

Reminder

Vipps MobilePay cannot guarantee that traffic to old endpoints will stop unless the integration is fully removed. Extra fees may apply after June 30, 2025, for use of deprecated APIs. ✅ It is your technical partner’s responsibility to disable the old API integration entirely.

Have questions?

If you didn't do the integration yourself, talk with your partner. They probably have everything under control.

For details about the app or pricing changes, go to vippsmobilepay.com.