Skip to main content

ePayment & Recurring PSP

Recurring API not yet available

ePayment API card passthrough for PSPs is now available. Recurring API card passthrough is in development — see timelines for details.

Card passthrough support for Payment Service Providers is being rolled out across the ePayment API and Recurring API, enabling PSPs to process card payments in all markets. This gives PSP partners access to the same product portfolio as direct merchants. The ePayment API replaces the Vipps PSP API and MobilePay Online API for one-time payments; the Recurring API adds new functionality for PSP partners.

PSPs must use card passthrough — account payments and payfac setup are not available.

Goals:

  • 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: ePayment API with PSP card passthrough is available now. Recurring API support is targeted for Q2/Q3 2026.

Migration and pricing​

The Vipps PSP API and MobilePay Online API have no announced end-of-life date, but the long-term goal is for all integrators to migrate to the new APIs. Migration paths will vary by integrator based on existing pricing agreements and API connections. Existing PSP undertaking agreements will be honored.

Recurring payments require a separate commercial agreement before the functionality can be enabled. Pricing and terms will be announced closer to launch. For questions, contact your PSP Partner Manager.

API overview​

The ePayment API card passthrough is available now. Recurring API card passthrough is in development.

When both are available:

  • PSP keys work on both APIs — authentication follows the same pattern as the existing PSP_v3 API, and the same keys and merchants work across both
  • Both APIs use a cardPassthrough object to specify where the card callback should go
  • Cross-market support is included — the same merchant can be used in all markets

API guides​

  • ePayment API PSP — one-time payments using CARD_PASSTHROUGH (available now)
  • Recurring API PSP — agreements, charges, and payment source updates (in development)
  • Card callback — synchronous callback required for CIT-based flows
Last updated on