Technical update June 2026
Here is what has changed since the February update — a completed product transition, new PSP capabilities, upcoming APIs, and the close of a long-running migration.
Highlights this month:
- Vipps Checkout to Kustom — transfer complete
- PSP ePayment API — card passthrough available for PSPs
- Recurring PSP API — live in the test environment
- Donations API — stop agreements and partner authentication
- Sales API — coming soon: order-level accounting data for partners
Checkout product: partnering with Kustom​
Vipps MobilePay has completed the sale of its 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 Vipps remains 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
PSP API solutions​
ePayment PSP API: launched​
PSPs can integrate directly with the ePayment PSP API — unlocking the full feature set, including cross-border payments in multiple currencies and card acquiring after receiving card details in a callback.
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.
Recurring PSP 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 will be enabled once the first PSPs have a validated and tested integration ready. Reach out to your PSP Partner Manager to get started.
Donations API​
Stop agreements​
Donation agreements can be programmatically stopped using the Donations API, through the new POST:/donations/v1/agreements/{agreementId}/stop endpoint. This means that donors no longer have to cancel agreements themselves in the app.
Partner authentication​
Partners will soon be able to call the Donations API and register Donations webhooks with their own 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 trigger a Donations request.
See Partner-specific behavior for details.
Updated partner terms and conditions​
Version 1.3 of the partner terms and conditions applies to all new partners from June 1, 2026. Key changes from v1.2:
- Commission withholding removed as an enforcement option for high API error-rates — only deactivation applies
- Branding obligations consolidated under a new "Vipps MobilePay Branding" definition
- Clarified that the Partner does not provide services to Vipps MobilePay; obligations govern safe API use only
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.
To refund an eligible transaction that originated from one of these APIs, complete the refund in the business portal. See How do I make a refund through the portal?.
For new subscriptions and payments, use the Recurring API and ePayment API.
Coming soon​
Sales API​
The Sales API provides access to order-level sales context — 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.
The API is under development. Documentation is available and feedback is welcome.
Agentic commerce​
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.
More updates​
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.
Report API: Donations organizations support​
Donations organizations using merchant-level keys can access their data through the Report API.
ePayment API: restrict shipping countries for Express​
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.
Webhooks API: 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.
Stay up to date​
We keep releasing new features and improvements — stay tuned for updates in the coming months.
