Announcing breaking change:

• The existing Payment Method Type: "MobilePaySubscriptions" will be replaced by: "VippsMobilePayRecurring"
• The existing Payment Gateway Provider: "MobilePay" will be replaced by: "VippsMobilePay"

Integrators are encouraged to account for both existing and replacing Payment Method Types and Payment Gateway Provider.

---

Background

When Norwegian Vipps and Danish MobilePay merged in March 2024 we chose to extend our existing “Payment Gateway Engine” (a micro service) as the fastest way to support the new VippsMobilePay API without any chances to our Payment API, allowing a smooth transition.

As OnlineFundraising remained in Denmark we kept the Payment Method Type: "MobilePaySubscriptions" as it were.

Today OnlineFundraising manages ~600.000 MobilePay Subscriptions, and as we become increasingly relevant for Norwegian organisations we have identified a need to both enhance our ability to scale and incorporate the Norwegian brand: “Vipps”.

We have therefore been working on a new micro service with a fresh implementation of the VippsMobilePay Recurring API which among other things allows synchronisation of Agreement details, such as plan, description, amount and frequency in the app.

Migration

Implementation of the new micro service will involve a migration of existing Subscriptions and Payments from one micro service to another which includes replacing the Payment Method Type and Payment Gateway Provider per entity in the Payment API.

We expect the migration to start in April and last until July October 2026, one merchant at a time, in a prioritised timetable, and as coordinated with each CRM integrator as possible.

During the migration updated webhook events will be sent for:

• Recurring MobilePay Payments in 2026
• All MobilePay Payment Methods
• All MobilePay Subscriptions

NB: Your integrator may request a migration without webhooks.

Integration

If your integration is creating new Subscriptions with the Payment Session Handler API you may continue to use the Payment Method Type: “MobilePaySubscriptions” until the end of 2026, as we will convert it to “VippsMobilePayRecurring“.

If your integration relies on Payment Method Type for reporting or similar, please be prepared to receive new Subscriptions and new Recurring Payments with “VippsMobilePayRecurring” sometime in the above mentioned timeline.

Payment and Payment Method

Once migrated Payments and Payment Methods will include:

{
    "paymentMethodType": "VippsMobilePayRecurring",
    "paymentGatewayProvider": "VippsMobilePay"
}

Subscription

Once migrated Subscriptions will include:

{
    "paymentMethodType": "VippsMobilePayRecurring"
}

Future transitions

Please note that this release and migration only involve Subscriptions and their Recurring Payments. Single and External Payments are not included at this stage, but these will be transitioned as the integration progresses.

Support of	Existing Payment Method Type	Replaced by
Single Payments (currently via PSP)	MobilePayOnline	VippsMobilePaySingle (later)
Recurring API	MobilePaySubscriptions	VippsMobilePayRecurring
Report API, Donations API	MobilePayExternal	VippsMobilePayExternal (later)