Skip to main content

Recurring and ePayments for PSP

Proof of concept

This documentation is a proof of concept and is subject to change. The feature is currently in the design phase and not yet available.

We are adding card passthrough support to ePayment API and Recurring API to allow Payment Service Providers to process card payments in all markets. This will allow PSP partners to get access to the same product portfolio as direct merchants. The ePayment API will eventually replace the PSP_v3 API and MobilePay Online API for one-time payments, whereas the Recurring API adds new functionality for PSP partners.

Goals of the project​

  • Full product access: Enable PSPs to offer all current and future Vipps MobilePay products to their merchants.
  • Cross-border payments: Process card payments across Norway, Denmark, and Finland.
  • One integration: Support both Vipps and MobilePay with a single API integration.
  • Simpler setup: Streamlined technical and commercial onboarding.
  • Timeline: We aim to release ePayment API with card passthrough and PSP support at the end of Q1/start of Q2 2026 and the Recurring API following closely after.

Migration and commercial​

Currently, there is no EOL to the PSP_v3 API and the MobilePay API, but the goal is to get everyone over to the new APIs eventually. The first step is to create the card passthrough support in ePayments, and the migration will follow later, from Q2/Q3 in 2026 and beyond. Migration will be slightly different for every current integrator, depending on which pricing agreements and APIs they are connected to already. Also note that the undertaking agreements for the PSPs that have them will still be respected.

Separate commercial terms will apply for PSP partners who wish to offer Recurring payments. A dedicated commercial agreement must be established before recurring functionality and/or other functionality is enabled. Details on pricing and terms will be announced at a later stage. If you have questions about commercial conditions or need preliminary information before launch, please reach out to your PSP Partner Manager.

Summary of plans​

We will add card passthrough to support both the ePayment API and Recurring API.

PSP partners will be required to use card passthrough functionality, there will be no account payments or payfac setup available at this time. This section contains an outline of how the APIs will look and behave, and feedback is welcome.

  • We will add support for PSP keys to the APIs
    • The PSP keys and authentication will be similar to the existing PSP_v3 API.
    • The same keys and merchants will work on both ePayments and Recurring API.
  • A cardPassthrough field will be added to both APIs, to specify where the card callback should go
  • Cross-border and cross-market will be supported
    • The same merchant can be used in all markets

What to implement​

Implement the PSP-specific sections of the ePayment and Recurring APIs:

You will also need to handle card callbacks. Vipps MobilePay sends a POST to your cardCallbackUrl when the user confirms a request and selects their card:

Last updated on