Deviations from Berlin Group v2
A consolidated reference of where Klarna's XS2A v2 PSD2 API differs from the Berlin Group openFinance 2.x standard — authentication, consent and AIS, and PIS deviations in one place.
4 min read
Klarna's XS2A v2 API implements the Berlin Group openFinance 2.x standard (AIS interface version 2.1 and PIS interface version 2.3). If you have integrated against another Berlin Group ASPSP, the vast majority of your integration carries over unchanged.
This page is the single reference for every place Klarna deviates from the vanilla standard — features that are restricted, not supported, or implemented in a specific way. Each service page repeats the relevant items inline; this page collects them so you can assess compatibility at a glance.
Conventions
Not supported means the element exists in the Berlin Group standard but is rejected by Klarna. Restricted means it is supported only for a subset of the standard's values.
Authentication and security
| Area | Berlin Group standard | Klarna |
|---|---|---|
| Transport security | mTLS with an eIDAS certificate | As standard — mTLS on every request (see Authentication). |
| Certificate model | QWAC for transport, QSEAL for message signing | 1‑QWAC model. The QWAC is the TLS client certificate; QSEAL is not currently required. Message-level signing is therefore not mandated today. |
| QWAC validity | CA/Browser Forum maximum-validity schedule | Planned — QWACs exceeding the maximum validity for their issuance date will be rejected; this is not enforced yet (see the schedule). |
| Accepted QTSPs | Any QTSP on the EU Trusted List | At launch, a defined set of QTSPs is pre-configured; others can be added on request. |
Consent and account information (AIS)
| Area | Berlin Group standard | Klarna |
|---|---|---|
| Account product buckets | payments, cards, cardAccounts, savings, loans, securities | Restricted to payments (current accounts). Other buckets are rejected with 400 PARAMETER_. |
| Consent types | detailed, global, accountList, aspspManaged | Restricted to detailed and global. accountList and aspspManaged are rejected with 400 CONSENT_. |
| Card / securities / loans data | Dedicated endpoints | Not supported (follows from the payments-only restriction). |
| SCA method | Redirect, OAuth, decoupled or embedded, depending on the ASPSP | PUSH_ only, decoupled, through the Klarna app. PSU-ID must be the customer's email address (see SCA). |
PSU-IP-Address | Conditional | Mandatory on consent creation, payment initiation and whenever PSU-ID is sent. |
| Consent validity | validTo chosen by the TPP | Capped at 180 days from today for every consent. |
| One-off consents | Single access | Attended only (PSU-IP-Address present) and valid for one hour after creation. |
| Transaction history | History as requested by the TPP | Full history within the first hour after the consent is created, then limited to the last 90 days. |
| Transaction history parameters | bookingStatus, deltaList and cardBrand | bookingStatus=information is rejected with 400 PARAMETER_; deltaList and cardBrand are accepted but ignored. Pages hold up to 50 transactions. |
| Authorization sub-resources | authorisations and cancellation-authorisations | authorisations only; cancellation-authorisations is rejected with 400 SERVICE_. |
See Consent and account information (AIS) for the full consent model and supported account data.
Payment Initiation (PIS)
| Area | Berlin Group standard | Klarna |
|---|---|---|
| Request encoding | JSON and pain. XML (ISO 20022) | JSON only. pain. products / XML payloads are not supported. |
| Payment services | payments, bulk-payments, periodic-payments | Single payments only (payments). Bulk payments and periodic payments / standing orders cannot be initiated. |
| Payment products | SEPA-family plus ASPSP-defined proprietary products | Three JSON products — sepa-credit-transfers, instant-sepa-credit-transfers and se-domestic-credit-transfers (SEK, accounts identified by bban). Any other product returns 404 PRODUCT_ on initiation, status and retrieve, and 400 SERVICE_ on the authorization endpoints. |
| Debtor account | debtorAccount required | Optional. If omitted it is resolved after authorization, but only when the customer has exactly one eligible account; send debtorAccount whenever the customer may hold more than one account. |
| Remittance information | remittanceInformationUnstructured array | One entry (maxItems: 1). |
| Payment cancellation | DELETE on a payment resource | Not supported — there is no cancellation operation. |
See Payment Initiation (PIS) for the supported products, request structure and status model.
Reporting a gap
If your integration relies on a Berlin Group feature listed here as not supported, let us know at
support. — it helps us prioritize the roadmap. Changes to this list are announced in the change log.Jump to section...