Skip to main content
View as Markdown (opens in a new tab)

Technical update October 2026

Highlights since the June update:

MobilePay becomes Vipps​

Following the announcement on October 6, MobilePay will become Vipps on January 12, 2027.

Prepare for branding changes​

If you offer MobilePay, update the MobilePay name and logo in your customer-facing material to the new approved Vipps assets. You can prepare in advance, but switch on January 12, 2027, not before. You don't need to rebuild your integration, and existing MobilePay numbers and QR codes continue to work. See the Merchant and partner guide for details.

Prepare for landing page domain changes​

If you offer MobilePay, the payment landing page domains will change. On January 12, 2027, we plan to replace pay.mobilepay.dk with pay.vipps.dk, and pay.mobilepay.fi with pay.vipps.fi. The test domains may change earlier. See Payment landing page for all domains, and for the new test domains when they are ready.

Do you validate our domains?

Most integrations keep working without changes. If you allowlist or validate our domains, for example in a firewall or a Content Security Policy, add the new domains before January 12, 2027. Also review redirects in an iframe or webview, and any check for whether the MobilePay app is installed.

ePayment API​

Merchant terms​

Customers can now review and accept your terms of sale and privacy policy in the app before they pay. Add the optional merchantLegalLinks object, with termsOfSaleUrl, privacyPolicyUrl, or both, when you create a payment. See Merchant terms for details.

Capture guarantees and error codes​

You can now see exactly how long a capture is guaranteed for each payment, in the new captureGuaranteedUntil field. For some payment methods, this is earlier than the general Capture attempt deadlines. If a capture fails because of timing, new error codes tell you why, so you know whether to retry.

Express order details​

Order details for Express payments now keep up with the customer's shipping choice. If you create the payment with order details, we set the shipping order line to the shipping method the customer selects in the app, and update it if they change their mind. The order details then match what the customer chose, with no extra work on your side.

Recurring API​

  • Deleted profiles: When a user deletes their profile, their active agreements are now stopped automatically, with actor set to ADMIN in the recurring.agreement-stopped.v1 webhook. We are also stopping agreements that belong to previously deleted profiles, so you may receive a burst of these webhooks.
  • Safe retries: Stopping an agreement that is already STOPPED now returns 204 No Content instead of an error, so you can safely retry a stop.
  • Agreement history: Fetch agreement and List agreements now return history, an oldest-first array of lifecycle events, each with its actor.
  • Removed field: The explanation field has been removed from the campaign object.

See the Recurring API changelog for full details.

Login API​

With In-app confirmation, "remember me in browser" is disabled, so the user must always confirm the login in the app. This feature is available to merchants on the advanced pricing tier.

Webhooks API​

PSPs can now register and manage webhooks, the same way partners do. See Partner/PSP webhooks.

Donations API​

Merchants can now add more than one merchant-level API client and delete clients they no longer need. See How to get the API keys.

To ask a donor to change the amount of an active agreement, for example during an upgrade campaign, merchants and partners can send an amount change request. The donor approves or declines the requested amount in the app. See the Donations API changelog for details.

AI plugin​

We have created the vipps-developer plugin, which you can add to Claude Code, Cursor, or Codex. If you use one of these tools, the plugin can help you build your integration. It now has skills for most of our APIs, so your coding assistant gets current guidance on picking an API, implementing it, and getting ready to go live, rather than working from memory.

The skills cover:

  • Payments: ePayment, Recurring, QR, Donations, and the Widget SDK
  • PSPs: the PSP ePayment API and the PSP Recurring API
  • Login and user data: Login and Userinfo
  • After the payment: Order Management, Webhooks, Report, Sales, and settlement
  • Merchants: Management API
  • Getting started: access tokens, choosing an API, and testing and going live

The plugin's source is in the public agent-toolkit repository on GitHub. To install it, see AI plugin.

Last updated on