Skip to main content

Technical update June 2026

Highlights since the February update:

PSP API solutions​

New PSP APIs are now available, enabling payment service providers to offer Vipps and MobilePay directly to their merchants. PSPs can distribute additional Vipps MobilePay products through their existing integrations, reducing onboarding effort for merchants and broadening payment availability across the Nordic market.

ePayment PSP API: Launched​

PSPs can now integrate directly with the ePayment PSP API, with full access to cross-border payments in multiple currencies and card passthrough.

Key highlights:

  • Full access to ePayment API features, including online single payments and express payments
  • Cross-border support — process payments in any currency covered by your commercial agreement
  • New PSP agreements include all currencies by default

To get access, contact your PSP Partner Manager.

PSP Recurring API: Available in the test environment​

The Recurring PSP API has initial PSP support live in the Merchant Test (MT) environment. PSPs can test the full card passthrough flow — including agreement sign-up and recurring charges — ahead of the production rollout.

There are no platform-level currency restrictions. PSPs can process recurring payments in any currency supported by the Recurring API, including three newly added currencies: GBP, USD, and SEK.

Production rollout is planned for Q3 2026. Reach out to your PSP Partner Manager to get started.

Checkout API: Moving to Kustom​

We have completed the sale of our Checkout solution to Kustom.

Going forward, Vipps MobilePay Checkout becomes Kustom Checkout — delivered and developed by Kustom. For you and your merchants, nothing changes right away. The setup works as before, and we remain responsible for the payment experience during the transition. Any steps that require action on your part will be communicated clearly in good time.

FAQ for Kustom

Donations API​

Stop agreements​

Donation agreements can be stopped using the Donations API, through the new POST:/donations/v1/agreements/{agreementId}/stop endpoint. This means that integrators can stop agreements on behalf of users through customer support, instead of having to guide the user to do so in the app.

Partner authentication​

Partners can now call the Donations API and register Donations webhooks with their partner keys. This means that, instead of retrieving merchant keys from each individual sales unit, the partner can use their own single set of keys to get data from the Donations solution.

See Partner-specific behavior for details.

ePayment API​

The shipping object on the create payment endpoint supports a new allowedCountries field. Pass a list of ISO 3166-1 alpha-2 country codes to limit which countries are available for the user to ship to in an Express payment.

Recurring API​

Campaign explanation field deprecated

The explanation field in the campaign object returned by the Get agreement endpoint is deprecated and will be removed on September 1, 2026. It currently returns an empty string.

This change follows improvements to how campaigns are displayed in the app, making the field redundant. Update your integration to stop reading it before September 1.

Several improvements to the Recurring API have shipped recently, including:

  • Get payment info: A new GET /recurring/v4/.../{chargeId}/paymentInfo endpoint returns payment info for DUE scheduled charges, so card data is fetched on demand rather than stored.
  • Retryable failures: Transient failures (for example, processing_timeout) are now returned in a separate retryableCharges array and can be retried with the same agreementId + chargeId pair.
  • Clearer error responses: Capture, cancel, and refund endpoints now include the current charge status in the detail field when the charge is in an invalid state.

See the Recurring API changelog for full details.

Report API​

Donations organizations using merchant-level keys can access their data through the Report API.

Sales API​

Accounting partners can now access order-level sales context through the Sales API — what was sold, settlement timing, VAT rates per item, and buyer details where permitted — alongside the settlement data already available in the Report API.

Every sale is captured automatically, with no manual recording or data exports needed. Where the Report API answers "what happened to the money", the Sales API answers "what was sold". The two are designed to be used together, joined on the shared reference and pspReference fields.

Access requires an accounting partner agreement with Vipps MobilePay.

Become an accounting partner

Webhooks API​

The Webhooks API is introducing automatic cleanup of failed endpoints.

Webhook registrations that have failed to receive deliveries consistently for two weeks are automatically removed. This keeps the registry healthier, reduces clutter, and makes it easier to spot endpoints that need attention.

See Webhooks API guide: Faulty webhook servers for details.

Legacy MobilePay APIs migration complete​

The legacy MobilePay Subscriptions API and MobilePay App Payments API are closed in both the test environment and production. API traffic to these products is no longer accepted.

For new subscriptions and payments, use the Recurring API and ePayment API.

Partner terms and conditions updated​

Version 1.3 of the partner terms and conditions applies to all new partners from June 1, 2026.

Agentic commerce (coming soon)​

We are building support for agentic and conversational commerce — where AI assistants or other agents act on behalf of the user. Vipps MobilePay will support this through the Universal Commerce Protocol (UCP) and the Vipps MobilePay Payment Handler, making it possible to accept payments inside chat interfaces and AI-driven checkout flows.

The documentation is available in early form and under active development. Feedback is welcome.

Last updated on