Payment
Klarna
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: not determined
by Klarna Bank AB · klarna.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Klarna Bank AB reaches this bench as a payment product whose captured documentation is addressed to payment providers (e.g. Stripe or Adyen) that distribute Klarna, not to merchants choosing payment methods. Payment methods spans 0 to 2, with no method named alongside its countries and currencies, so a buyer can plan nothing per market. Settlement and reconciliation sits at 2, with no public information on payout cadence, per-transaction fee breakdown or an API with webhooks. The evidence is strongest on recurring billing, spanning 2 to 4, on a documented tokenized subscription charge flow and a subscriptions use case, and on checkout, clustering at 2, for hosted checkout pages and embedded elements covering payment presentation and customer-initiated authorisation. The recurring spread is real: judges who credit documented topic pages score 3 to 4, while the skeptic holds at 2, declining to credit capabilities whose pages were captured only as titles. Sovereignty sits at 1 with no attributes on record, licence and account terms runs 1 to 2, and no prices appear in anything captured — this vendor publishes none.
Speaks for it
- A documented tokenized subscription charge flow plus a subscriptions-and-on-demand use case puts recurring billing at 2 to 4, this vendor's highest scores
- Hosted checkout pages and embedded elements are both documented for payment presentation and customer-initiated authorisation, with checkout clustering at 2
- Dedicated settlement reconciliation and settlement report pages exist, which is more than an on-screen list
- The vendor is named as Klarna Bank AB, which reads like a regulated entity
Held against it
- The captured documentation is written for payment providers (e.g. Stripe or Adyen) that distribute Klarna, not for merchants choosing methods
- We found no public information naming which payment methods serve which countries and currencies; scores span 0 to 2
- We found no public information on 3-D Secure, SCA exemptions, fraud screening or PCI scope for any integration type
- We found no public information on payout cadence, per-transaction fee itemisation, or an API with webhooks and test mode
- We found no public information on a supervisor, register number, safeguarding of merchant funds, reserves, chargeback fees or termination notice; licence scores run 1 to 2
Best for
- You are a payment provider or acquiring partner that processes payments and wants to distribute Klarna — the captured documentation is written for that audience
- You need repeat charging on stored tokens for subscriptions or on-demand billing, the area where scores are highest (recurring billing 2 to 4)
- You are integrating payment presentation across hosted checkout pages and embedded elements and will take the 3-D Secure, SCA and PCI questions to the vendor directly
Avoid if
- You need a named list of payment methods with their countries and currencies to plan acceptance market by market — none is named and scores span 0 to 2
- Your finance team must close a month against payout cadence, per-transaction fee itemisation and an API with webhooks — we found no public information on any of these
- You must see a supervisor, register number, safeguarding statement or reserve and termination terms before signing — only the entity name appears, and licence and account terms scores run 1 to 2
- You need documented 3-D Secure, SCA-exemption and fraud-screening behaviour to keep legitimate payments from failing — we found no public information on these
The scores
Too little public evidence to rate — fewer than 1 captured source or 3 proven facts — so no star rating is shown. The panel's reasoning is below.
Payment methods & local coverage
Show reasoningHide reasoning
How this is scored
Which methods a European customer can actually pay with — cards and wallets, SEPA Direct Debit, and the local methods that decide conversion per country — judged on the named list per market rather than on a method count.
0 — Cards only, or a method list with no statement of which countries and currencies each one covers.
3 — Major cards and wallets plus one or two European methods, with local coverage stated vaguely ("many local methods") and no SEPA Direct Debit.
5 — Cards, Apple Pay and Google Pay, SEPA Direct Debit, and the main local methods for DACH and Benelux (iDEAL or Wero, Bancontact, Klarna or invoice) listed by name with the countries they serve.
8 — Broad EU coverage named per country — including methods such as BLIK, TWINT, Przelewy24, EPS and Wero — multi-currency acceptance with settlement currencies stated, and which methods support refunds and recurring charges documented per method.
10 — Coverage is documented as a matrix a merchant can plan against: every method with its countries, currencies, refund, partial-capture and recurring support, and the provider's own acquiring versus third-party routing stated per method.
The Finance Lead
The captured documentation is written for payment providers distributing Klarna rather than a merchant choosing methods, and I found no public information on which payment methods, countries or currencies are covered, nor on SEPA Direct Debit. A method-grouping resource exists, but without a named list I cannot plan acceptance for any single market. 1 2
The E-Commerce Lead
A payment-method-grouping page exists, but the only substantive captured statement is that the documentation serves payment providers that distribute Klarna rather than merchants. No method is named with the countries and currencies it covers, so I found no public information to plan my eight markets against — not even a count, let alone a per-country list. 1 2
The SaaS Founder
The one captured fact tells me this documentation is written for payment providers distributing Klarna, not for a merchant like me choosing methods per market, and I found no public information on which payment methods, countries or currencies are covered — no SEPA Direct Debit, no iDEAL or Bancontact, nothing named with its coverage. 1 2
The Payments Engineer
The captured documentation includes a payment-method grouping resource and a distribution overview, but no named list of methods with the countries and currencies each covers appears anywhere; we found no public information on SEPA Direct Debit or per-country local methods in the evidence. 1 2
The Compliance Officer
The only confirmed statement positions the documented offering for acquiring partners such as Stripe or Adyen that distribute Klarna, and one captured page is devoted to payment method grouping. We found no public information naming which methods serve which countries and currencies, on SEPA Direct Debit coverage, or on refund and recurring support per method. 1 2
The Skeptic
The only confirmed statement on these pages is aimed at payment providers that distribute Klarna, not at a merchant choosing methods, and the capture of the payment method grouping page yields no list of methods with the countries and currencies they serve. We found no public information on SEPA Direct Debit or on any local method's coverage. A buyer can plan nothing against this. 1 2
Checkout, SCA & fraud
Show reasoningHide reasoning
How this is scored
The path from basket to authorised payment under PSD2: hosted and embedded checkout options, 3-D Secure and SCA exemption handling, fraud screening, and what the provider documents about keeping legitimate payments from failing.
0 — A single redirect page with no statement on 3-D Secure, SCA or fraud screening.
3 — Hosted checkout with 3-D Secure 2 mentioned, fraud screening as an unexplained add-on, and no word on exemptions or declined-payment handling.
5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, configurable fraud rules, and the resulting PCI DSS scope for each integration type stated.
8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, fraud tooling with rules and risk scores exposed to the merchant, network tokens or account updater, and liability shift explained per flow.
10 — Authorisation is engineered and shown: exemption strategy documented, soft-decline retry handled, authorisation-rate reporting by method and issuer country, and a checkout the merchant can run in their own domain while staying at the lowest PCI scope.
The Finance Lead
Integration guides exist for hosted checkout pages and for embedded elements, with a documented customer-initiated authorisation flow, so both checkout shapes are real. We found no public information on 3-D Secure handling, SCA exemptions, fraud screening or PCI scope, which is most of what this question asks. 3 4
The E-Commerce Lead
Hosted checkout pages and embedded elements are documented, with customer-initiated transactions covered for both, which is a real start on the basket-to-authorisation path. I found no public information on 3-D Secure, SCA exemption handling, fraud screening, or running the checkout on my own domain. 3 4
The SaaS Founder
Hosted checkout pages and embedded elements are documented, along with a customer-initiated authorisation flow, but I found no public information on 3-D Secure, SCA exemptions, fraud screening or the resulting PCI scope — so I cannot judge whether legitimate payments are kept from failing. 3 4
The Payments Engineer
Captured pages for payment presentation and customer-initiated authorisation cover both hosted checkout pages and embedded elements, which is a real integration choice; we found no public information on 3-D Secure handling, SCA exemptions, fraud screening, or the PCI scope of each integration option. 3 4
The Compliance Officer
The captured documentation addresses payment presentation for hosted checkout pages and embedded elements and a customer-initiated transaction authorisation flow, which is more than a bare redirect. We found no public information on 3-D Secure, SCA exemption handling, fraud screening, or the PCI DSS scope of any integration type. 3 4
The Skeptic
The captured pages show integration topics for hosted checkout pages and embedded elements and for customer-initiated transaction authorisation, which is more than a bare redirect. Beyond those titles we found no public information on 3-D Secure, SCA exemptions, fraud screening, declined-payment handling or PCI scope. Nothing captured says a word about keeping legitimate payments from failing. 3 4
Subscriptions & recurring payments
Show reasoningHide reasoning
How this is scored
Charging the same customer again: card-on-file and merchant-initiated transactions, SEPA mandates, subscription logic and dunning — and whether the stored payment credentials can leave with the merchant.
0 — No stored payment methods; every charge needs the customer to pay again.
3 — Card-on-file tokens for repeat charges, but no SEPA mandate handling, no subscription logic, and failed-payment handling left entirely to the merchant.
5 — Stored cards and SEPA Direct Debit mandates, merchant-initiated transactions documented, and basic subscription plans with scheduled charges and failed-payment notifications.
8 — Subscription billing with trials, proration and plan changes, smart retries and dunning, card account updater, mandate management with pre-notification, and a documented process for exporting payment tokens to another provider.
10 — Recurring revenue is a first-class product: usage-based and invoice-based billing, dunning with measurable recovery, token migration in and out documented with a stated timeline and format, and recurring support stated for every local method that allows it.
The Finance Lead
Documented guidance covers charging a subscription on tokenised payments, and a subscription use case is spelled out for the sign-in product, so repeat charging is more than an afterthought. We found no public information on SEPA mandate handling, smart retries and dunning, or taking stored tokens to another provider. 5 6
The E-Commerce Lead
Tokenized payments come with a documented subscription charge flow, and sign-in has a subscriptions use case, so repeat charges on stored credentials are evidenced. I found no public information on SEPA mandate handling, retries and dunning, or exporting stored credentials to another provider. 5 6
The SaaS Founder
Tokenized payments with a documented flow to charge a subscription, plus a subscriptions use case, are the only recurring evidence here; I found no public information on SEPA mandate handling, dunning or smart retries, and — the part that decides my score — nothing on whether stored payment tokens can be exported to another provider. 5 6
The Payments Engineer
There is a documented flow to charge a subscription from tokenized payments, plus subscription and on-demand use cases for the sign-in product, so repeat charging exists on paper; we found no public information on SEPA mandate handling, smart retries and dunning, or a process for exporting stored tokens to another provider. 5 6
The Compliance Officer
Captured pages document charging a subscription from tokenized payments and subscription and on-demand use cases for Sign in with Klarna, which evidences stored-credential repeat charging as a topic. We found no public information on SEPA mandate management, retries and dunning, account updater, or a process for exporting stored credentials to another provider. 5 6
The Skeptic
Captures point to a tokenized-payments page for charging a subscription and a subscriptions-and-on-demand use case, so repeat charging is at least a documented topic. We found no public information on SEPA mandate handling, smart retries, dunning, an account updater, or whether stored payment credentials can be exported to another provider. I will not credit capabilities whose pages were captured only as titles. 5 6
Settlement, reconciliation & API
Show reasoningHide reasoning
How this is scored
Getting the money and knowing what it was: payout cadence and currencies, fee itemisation per transaction, reports that match a bank statement, and an API and webhooks a team can build finance processes on.
0 — Payouts on an unstated schedule, one net amount per payout, and no API or report beyond an on-screen list.
3 — A stated payout schedule and CSV exports, but fees netted invisibly into payouts and an API with thin documentation.
5 — Payout frequency and delay stated, per-transaction fee breakdown in reports, a documented REST API with webhooks and a test mode, and exports that link each payout to its transactions.
8 — Configurable payout schedules and settlement currencies, reconciliation reports that match bank lines, accounting integrations or exports named, a versioned API with idempotency and published rate limits, and a public status page with incident history.
10 — Finance can close the month from the provider's data: interchange and scheme fees itemised per transaction, automated reconciliation to the ledger, a deprecation policy for the API, and full historical data exportable after the contract ends.
The Finance Lead
Dedicated resources exist for settlements reconciliation and for settlement reports, so reporting is a documented topic, but we found no public information on payout cadence, per-transaction fee itemisation, or API, webhook and test-mode capability. Without a fee breakdown I cannot tell whether a payout would reconcile to a bank line. 7 8
The E-Commerce Lead
There are dedicated pages for settlement reconciliation and settlement reports, which is more than an on-screen list. I found no public information on payout cadence and currencies, per-transaction fee breakdown, or the API and webhooks my finance team would build on. 7 8
The SaaS Founder
Settlement and settlement-report documentation exists for the distribution network, but I found no public information on payout cadence, per-transaction fee breakdown, or a documented API with webhooks and a test mode, so a finance team cannot close a month from this. 7 8
The Payments Engineer
Captures include settlement reconciliation and settlement report pages aimed at distribution partners, so some reporting exists; we found no public information on payout cadence and currencies, per-transaction fee itemisation, a versioned API with idempotency, or a public status page with incident history. 7 8
The Compliance Officer
Captured pages address settlement reconciliation and settlement reports, so payout reporting exists as a documented subject. We found no public information on payout cadence or settlement currencies, per-transaction fee breakdowns, or an API with webhooks and a test mode. 7 8
The Skeptic
Two captured pages cover settlements reconciliation and settlement reports, but neither capture confirms a payout schedule or delay, a per-transaction fee breakdown, an API with webhooks, or any format tying payouts to their transactions. We found no public information on settlement currencies or reconciliation that matches a bank statement. Titles are not terms. 7 8
Licence, risk & account terms
Show reasoningHide reasoning
How this is scored
Who holds the merchant's money under which licence, and what the contract lets the provider do on a bad day: freezes, reserves, termination, chargebacks. Scored on what the terms and the imprint state, not on reputation.
0 — No regulated entity named; terms allow freezing funds and terminating the account at any time with no notice, reason or timeline.
3 — A licence mentioned without the entity, supervisor or register number, and terms that permit reserves and holds with no stated limits.
5 — The regulated entity named with its supervisor and licence type, safeguarding of merchant funds stated, chargeback fees and dispute process published, and a notice period for ordinary termination.
8 — Entity, supervisor, register number and passporting stated per country; reserve and rolling-hold conditions defined with limits and release timelines; freeze and termination terms with reasons and a route to appeal; PCI DSS level and attestation published.
10 — The bad day is written down: every regulated entity in the chain named with register links, reserve calculation disclosed, funds release timelines after termination committed, a documented complaint route to the supervisor, and exit terms that include handing back payment tokens and transaction history.
The Finance Lead
The only entity named anywhere in the captured material is the vendor, Klarna Bank AB. We found no public information on licence type, supervisor or register number, safeguarding of merchant funds, reserve or rolling-hold conditions with limits, freeze and termination terms, or chargeback fees — and a reserve I discover on a Tuesday is exactly what I refuse to sign. 2
The E-Commerce Lead
No licence, supervisor, register number, safeguarding statement or account terms appear in what was captured; the only confirmed statement concerns the documentation's audience of distribution partners. I found no public information on reserves, freezes, chargeback fees or termination notice. 2
The SaaS Founder
Klarna Bank AB is the only entity named, in the vendor line itself, and I found no public information on its supervisor or register number, safeguarding of merchant funds, chargeback fees, or reserve, freeze and termination terms in the captured pages. 2
The Payments Engineer
The vendor line names Klarna Bank AB, but the captured pages are distribution-partner documentation with no supervisor, licence type or register number stated, and we found no public information on reserves, holds, chargeback fees or termination notice. 2
The Compliance Officer
The vendor is named as Klarna Bank AB, but nothing captured states its supervisor, register number or licence type. We found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, freeze and termination terms with notice and appeal, or chargeback fees and the dispute process. 2
The Skeptic
The vendor line names Klarna Bank AB, which reads like a regulated entity, but nothing captured states a supervisor, licence type or register number, and we found no public information on safeguarding of merchant funds, chargeback fees, reserves, or termination notice. For a payments product, a missing licence number is an answer. 2
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting and regulated entity is, and where transaction and cardholder data are processed and stored. Independently sourced by the sovereignty pipeline. The card schemes are US-based for every provider, so the scheme layer is not held against any one vendor; the part the vendor controls is.
0 — Non-EU contracting entity, no statement on where payment data is processed, and subprocessors unnamed.
3 — An EU licensed entity contracts, but payment and customer data is processed outside the EU by default without an explained safeguard, or the subprocessor list is absent.
5 — EU contracting and regulated entity, EU processing stated for core payment data, but the group parent or significant parts of the chain (fraud scoring, support, analytics) are non-EU without a stated safeguard.
8 — EU entity and EU licence, payment and cardholder data processed and stored in the EU on named infrastructure, subprocessor list published with locations, and a DPA covering the processing the provider does as processor versus as controller.
10 — Sovereign end to end and evidenced: European ownership, EU entity and licence, every processing location and subprocessor European, European rails (SEPA, Wero or national schemes) offered alongside cards, and certifications published.
The Finance Lead
No sovereignty attributes are on record, and we found no public information on where transaction and cardholder data are processed or stored, on subprocessors, or on ownership. The vendor name appears without a stated jurisdiction or licence. 2
The E-Commerce Lead
Independent sourcing returned no sovereignty attributes on record, and I found no public information on where transaction and cardholder data is processed, on the contracting entity's licence, or on any subprocessor list. The captured pages speak to payment providers distributing Klarna and say nothing about data locations. 2
The SaaS Founder
There are no sovereignty attributes on record at all: I found no public information on where the contracting entity is established or licensed, where payment and cardholder data is processed, or which subprocessors are involved. 2
The Payments Engineer
The independently sourced sovereignty record shows no attributes at all for this vendor, and we found no public information on where payment and cardholder data are processed or which subprocessors are involved; the only quoted page describes distribution through other payment providers, leaving the data chain undocumented. 2
The Compliance Officer
No sovereignty attributes are on record, and we found no public information on where transaction and cardholder data are processed, who the subprocessors are, or where the provider acts as controller rather than processor. The contracting entity is named as Klarna Bank AB, but nothing captured confirms where it is licensed or that EU processing is stated for any part of the chain. 2
The Skeptic
The independence pipeline has no sovereignty attributes on record for this vendor and provenance is unknown. No captured page states where payment or cardholder data is processed or stored, and we found no public information on subprocessors or their locations. With contracting entity details and processing locations both unrecorded, only the bottom anchors apply. 2 3 7
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the effective fee for their own mix of cards, countries and methods — including cross-border and currency conversion markups, chargebacks, refunds, payouts and monthly fees — from public pages alone.
0 — No public prices at all; every rate is a sales conversation.
3 — A headline percentage exists, but it is unclear which cards and countries it covers, and cross-border, currency conversion or chargeback fees are unstated — the effective fee is unknowable.
5 — Rates published per main method with domestic and international cards distinguished, but at least one commonly incurred cost (currency conversion markup, chargeback fee, payout or monthly fee) is missing or "on request".
8 — Every method priced publicly, cross-border and currency conversion markups stated, chargeback, refund and payout fees listed, minimum monthly fees and contract term given, and whether the model is blended or interchange++ said plainly.
10 — Complete fee computability: the effective rate derivable for a given volume, card mix and country mix — interchange++ with the markup published or a blended rate with every exception listed — plus volume tiers, reserves and every ancillary fee on a public page.
The Finance Lead
We found no public information on pricing of any kind — no rate per method, no cross-border or currency-conversion markup, no chargeback, refund or payout fees, no monthly minimum or contract term. The captured pages speak to payment providers distributing Klarna and to settlement reporting; I could not build a fee model from them. 2 7 8
The E-Commerce Lead
Nothing in the captured pages carries a price: no rates, no currency-conversion or cross-border markups, no chargeback or payout fees, no monthly minimums. I found no public information that would let me estimate my effective fee for any card or country mix. 2
The SaaS Founder
No rate, fee, chargeback cost or monthly minimum appears anywhere I can see, and the one captured fact says these products are documented for payment providers distributing Klarna — so a merchant's effective fee for a given card and country mix is not computable from public pages alone. 2
The Payments Engineer
No captured page states a rate, fee or pricing model of any kind, and the quoted material concerns distribution to payment providers rather than merchant pricing; we found no public information from which a merchant could compute an effective fee for their card and country mix. 2
The Compliance Officer
We found no public information on any rate, fee, currency conversion markup, chargeback cost, payout fee or monthly charge in the captured material. The one confirmed statement frames the product for acquiring partners, and no pricing page appears among the captures. 2
The Skeptic
We found no public prices in anything captured — no rate, no currency conversion markup, no chargeback fee, no payout or monthly fee, no contract term. The one confirmed statement tells me the documentation is written for payment providers distributing Klarna rather than for merchants weighing rates. A merchant can compute nothing from these pages. 2 7 8
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We could not confirm any pricing information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- We found no public information on compliance on the pages we read (docs.klarna.com/acquirer/klarna/web-payments/additional-resources/payment-method-grouping, docs.klarna.com/klarna-network-distribution, docs.klarna.com/klarna-network-distribution/payment-presentation/integrate-payment-presentation/for-hosted-checkout-pages-and-embedded-elements, docs.klarna.com/klarna-network-distribution/payment-authorization/customer-initiated-transaction/for-hosted-checkout-pages-and-embedded-elements, docs.klarna.com/acquirer/klarna/web-payments/integrate-with-klarna-payments/tokenized-payments/charge-a-subscription, docs.klarna.com/acquirer/klarna/sign-in-with-klarna/integrate-sign-in-with-klarna/use-cases/subscriptions-and-on-demand and 2 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 119 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 13 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Payment methods & local coverage — found from sitemap docs.klarna.com Checked 1 Oct 2026 Details →
- 2 Payment methods & local coverage — found from sitemap docs.klarna.com Checked 1 Oct 2026 Details →
- 3 Checkout, SCA & fraud — found from sitemap docs.klarna.com Checked 1 Oct 2026 Details →
- 4 Checkout, SCA & fraud — found from sitemap docs.klarna.com Checked 1 Oct 2026 Details →
- 5 Subscriptions & recurring payments — found from sitemap docs.klarna.com Checked 1 Oct 2026 Details →
- 6 Subscriptions & recurring payments — found from sitemap docs.klarna.com Checked 1 Oct 2026 Details →
- 7 Settlement, reconciliation & API — found from sitemap docs.klarna.com Checked 1 Oct 2026 Details →
- 8 Settlement, reconciliation & API — found from sitemap docs.klarna.com Checked 1 Oct 2026 Details →