URLs and environments

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:
EnvironmentPurposeAuthentication
SandboxIntegration 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).
ProductionLive access to real customer accounts and payments.mTLS with a valid eIDAS QWAC issued by an accepted QTSP.

Base URLs

Coming soon
EnvironmentBase URL
Sandboxhttps://xs2a-api.banking.playground.klarna.com
ProductionTo be confirmed before GA
Once you have the base URL for your environment, every request is {{base-url}} + the endpoint path listed in Endpoint paths.

Endpoint paths

All endpoints live under the /v2 path. The two services are:
OperationPath
Create / manage consent/v2/consents/account-access, /v2/consents/account-access/{consentId}
List accounts/v2/accounts
Account details/v2/accounts/{account-id}
Balances/v2/accounts/{account-id}/balances
Transactions/v2/accounts/{account-id}/transactions

Payment Initiation (PIS) — interface v2.3

OperationPath
Initiate payment/v2/payments/{payment-product}
Payment status/v2/{payment-service}/{payment-product}/{paymentId}/status
Retrieve payment/v2/{payment-service}/{payment-product}/{paymentId}

Sandbox test data

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.

Relationship to the legacy XS2A API

This is the new Berlin Group openFinance API and is hosted independently of Klarna's legacy XS2A API. If you are moving over, see Migrating from the legacy API.
Support
Partner support•Service Status
Cookies|Terms & Conditions|Copyright Klarna AB 2026
Jump to section...