Base URLs, environments and endpoint paths for Klarna's XS2A v2 (Berlin Group openFinance) PSD2 API, and how mutual TLS applies in each environment.
3 min read
The XS2A v2 API is served over HTTPS with mutual TLS (mTLS) in every environment. You reach an endpoint by combining the base URL of the target environment with the API path (for example /v2/consents/account-access).
Environments
Klarna offers two TPP-facing environments:
Environment
Purpose
Authentication
Sandbox
Integration testing against the AIS and PIS API with static test data. SCA is resolved automatically from the PSU email, see Sandbox test data.
mTLS — use your production QWAC, or a Klarna-provided test certificate (see Sandbox access).
Production
Live access to real customer accounts and payments.
mTLS with a valid eIDAS QWAC issued by an accepted QTSP.
Base URLs
Coming soon
The public Sandbox and Production base URLs will be published here before general availability and are shared with you during onboarding. If you need them ahead of time, contact support.xs2a.banking@klarna.com.
The Sandbox is pre-loaded with a fixed set of test PSUs (customers), accounts, and transaction history so you can exercise AIS and PIS flows without a real Klarna account. See Sandbox test data for the full list of test PSUs, their IBANs, and their transaction data.
Authentication applies everywhere
There is no separate token endpoint or API key. You present your certificate on the mTLS connection for every request, in both environments — the Sandbox uses the same mechanism as Production. See Authentication for the certificate requirements and Strong Customer Authentication for how the customer authorizes consents and payments.