Panel 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? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Klarna at a glance
- Vendor
- Klarna Bank AB
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The captured record defines this product by its channel: the only confirmed fact states the documentation is for payment providers (e.g. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
The captured record defines this product by its channel: the only confirmed fact states the documentation is for payment providers (e.g. Stripe or Adyen) that process payments and distribute Klarna. Scoring is strongest on checkout and SCA, where documented hosted checkout pages, embedded elements and a customer-initiated transaction flow draw 4 from the payments engineer, compliance officer and e-commerce lead. Recurring billing holds at 3 among the judges who rated it, on a documented flow for charging a subscription from tokenized payments. Payment methods scored a flat 2 — Klarna is the only method the evidence names. The skeptic found too little public information to rate anything beyond payment methods. Settlement and reconciliation run 2 to 4 among rated judges: the e-commerce lead credits documented settlement reporting, while the finance lead and payments engineer find no payout schedules, settlement currencies or fee itemisation. Licence and account terms, sovereignty and pricing each scored 0 — we found no public information on the regulated entity, licence, safeguarding of merchant funds, data residency or any rate.
Speaks for it
- Hosted checkout pages and embedded elements are documented for payment presentation and customer-initiated transactions
- Charging a subscription from tokenized payments is documented, alongside a subscriptions-and-on-demand use case
- Settlement reconciliation and settlement reports are documented for distribution partners
- Checkout and SCA draw the panel's top marks, 4 from the payments engineer, compliance officer and e-commerce lead
Held against it
- The captured documentation is written for payment providers that distribute Klarna, not for merchants
- We found no public information naming payment methods, countries or currencies beyond Klarna itself
- We found no public information on 3-D Secure handling, SCA exemptions, fraud screening or PCI scope
- We found no public information on dunning, smart retries, SEPA mandates or exporting stored tokens to another provider
- We found no public information on the regulated entity, licence, safeguarding of merchant funds, data residency or prices
Best for
- You are a payment provider integrating Klarna distribution and need a documented path to hosted checkout pages and embedded elements
- You run a subscription model and need a documented flow for charging stored payment tokens again
- You are a distribution partner who wants documented settlement reporting alongside payouts
Avoid if
- You are a merchant planning a per-market payment mix — the captured pages are written for payment providers and name no methods, countries or currencies beyond Klarna itself
- You need PSD2-grade checkout assurance before launch — ask the vendor: the public pages we read do not show it
- Your procurement requires a named regulator, licence, safeguarding terms or data residency on record — each of these is marked unknown
- You depend on moving subscribers to another provider later — ask the vendor: the public pages we read do not show it
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 — Not a payment acceptance product; customers cannot pay through it.
3 — Card payments with the major schemes, plus wallets such as Apple Pay or Google Pay.
5 — Cards and wallets plus SEPA Direct Debit and several European local methods (for example iDEAL or Wero, Bancontact, Klarna, EPS) listed by name.
8 — Broad EU coverage named per country with the countries and currencies each method serves — 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 only confirmed fact describes the product's audience as payment providers such as Stripe or Adyen that process payments and distribute Klarna, and the remaining captured pages are partner-facing integration guides. No per-market method catalogue, card scheme list or SEPA detail was captured, so I can verify that Klarna itself is the method being distributed but not which methods European customers could actually pay with. 1 2
The E-Commerce Lead
Klarna itself is the only payment method the evidence names — a method that payment providers such as Stripe or Adyen process and distribute, with documentation on grouping payment methods — and no country-by-country list, currency or local method appears in what was captured. For eight EU markets I need methods named per market, and there is nothing here to plan a checkout mix against. 1 2
The SaaS Founder
The captured pages are written for payment providers that distribute Klarna rather than for merchants, and the payment-method grouping page names no individual method, country or currency in the captured material — neither SEPA Direct Debit nor any local scheme appears by name. I cannot judge local conversion coverage from documentation that stops at the grouping concept. 1 2
The Payments Engineer
What the captures establish is distribution rather than a merchant-facing method catalogue: Klarna reaches consumers through payment providers such as Stripe or Adyen, and the documentation includes a page grouping payment methods for acquirers. No method names, countries, currencies, or per-method refund and recurring support appear in the captures, so I cannot place this above the entry level. 1 2
The Compliance Officer
Klarna is documented as a payment method that shoppers pay with through distributing payment providers such as Stripe or Adyen, and a page on payment method grouping exists. We found no public information naming methods per country, the currencies each serves, or refund and recurring support per method, so coverage cannot be planned against from these pages. 1 2
The Skeptic
The only confirmed fact defines this product by its buyer, not by its coverage: "For payment providers (e.g. Stripe or Adyen) that process payments and distribute Klarna." We found no public information naming methods, countries or currencies a customer can pay with; a payment-method-grouping page sits in the captured set, but nothing from its content is confirmed. 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 — No checkout or payment form; the product does not take a payment to authorisation itself.
3 — A hosted payment page or payment links with 3-D Secure.
5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, and fraud screening with configurable rules.
8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, the PCI DSS scope of each integration type stated, 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
The captured integration guides cover hosted checkout pages and embedded elements, plus a customer-initiated transaction flow under payment authorisation, so a checkout path to authorisation is documented. We found no public information on 3-D Secure handling, SCA exemptions, PCI scope or fraud screening, so this stays at the entry level. 3 4
The E-Commerce Lead
The integration documentation is titled for hosted checkout pages and embedded elements, for both the payment presentation and customer-initiated transactions, so an embedded checkout on my own page is a documented integration option. We found no public information in the captured pages on 3-D Secure behaviour, SCA exemptions, fraud screening or PCI scope, so I cannot tell how often a legitimate customer would be challenged. 3 4
The SaaS Founder
Hosted checkout pages and embedded elements are documented, alongside a customer-initiated authorisation flow, so the checkout surface itself is real. But we found no public information on 3-D Secure handling, SCA exemptions or fraud screening in the captured pages, so the documented path ends at getting a basket in front of the customer. 3 4
The Payments Engineer
The documentation describes a payment presentation integration built for hosted checkout pages and embedded elements, together with a customer-initiated transaction authorization flow — the right integration shape. I found no public information on 3-D Secure, SCA exemptions, fraud screening or PCI scope in these captures, which holds it below the level where I would trust it for PSD2 flows. 4 3
The Compliance Officer
Payment presentation is documented both for hosted checkout pages and for embedded elements, and customer-initiated transaction authorisation is documented as its own flow, which goes beyond a single hosted page. We found no public information on 3-D Secure or SCA exemption handling, the PCI DSS scope of each integration type, fraud screening, or liability shift. 3 4 3
The Skeptic not rated — no public information
We found no public information on checkout options, 3-D Secure, SCA exemption handling or fraud screening. The captured pages include addresses pointing at payment presentation for hosted checkout pages and embedded elements and at customer-initiated transactions, but no confirmed fact describes what any of that does. 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 — One-off payments only; the product stores no payment method for a later charge.
3 — Saved cards (card-on-file) charged again for repeat or recurring payments.
5 — Stored cards and SEPA Direct Debit mandates for recurring charges, merchant-initiated transactions, and subscriptions or scheduled payments with notification of failed payments.
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
The documentation includes a guide to charging a subscription from tokenized payments and subscriptions-and-on-demand use cases for Sign in with Klarna, so stored payment credentials charged again for recurring billing are documented. Nothing was captured on SEPA mandate management, dunning, retries or moving tokens to another provider. 5 6
The E-Commerce Lead
Tokenized payments can be charged for a subscription, and the sign-in product documents subscriptions and on-demand use cases, which is a stored payment credential charged again — enough for card-on-file style recurring. We found no public information in the captures on SEPA mandates, smart retries and dunning, or exporting the stored tokens to another provider. 5 6
The SaaS Founder
Charging a subscription from stored payment tokens is documented, and a subscriptions-and-on-demand use case appears in the sign-in material, so the card-on-file primitive is there. But we found no public information on SEPA mandates, dunning, retries, proration or any documented process for exporting payment tokens to another provider — and for a subscription business, that export path is what decides whether the customer base is mine to keep. 5 6
The Payments Engineer
There is a documented tokenized-payments flow for charging a subscription under the acquirer integration, plus a sign-in use case covering subscriptions and on-demand — stored tokens charged again, which is the basic recurring capability. I found no public information on SEPA mandates, dunning, smart retries or exporting tokens to another provider in these captures. 5 6
The Compliance Officer
Charging a subscription from tokenized payments is documented, which evidences stored credentials charged again, and a subscriptions and on-demand use case is described alongside sign-in. We found no public information on SEPA mandates, smart retries and dunning, an account updater, or a process for exporting payment tokens to another provider. 5 6
The Skeptic not rated — no public information
We found no public information on stored cards, merchant-initiated transactions, SEPA mandates, subscription logic, dunning or token export. Captured addresses point at charging a subscription under tokenized payments and a subscriptions use case for sign-in with Klarna, and I cannot confirm a word of their content. 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 — No merchant reporting: the product is a payment button or link with no dashboard, report or API.
3 — A dashboard of transactions and payouts, a stated payout schedule, and CSV export.
5 — The payout schedule stated, reports or exports that link each payout to its transactions and fees, and a documented API with webhooks and a test mode.
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
The partner documentation includes settlement reconciliation and settlement report pages, so some payout reporting is documented. We found no public information on payout cadence, settlement currencies, fee itemisation per transaction, or reports that tie payouts to bank statement lines, which is exactly what I need to close a month. 7 8
The E-Commerce Lead
Captured documentation covers settlements reconciliation and settlement reports, so payouts with reporting are part of the product. We found no public information in the captures on payout schedules and settlement currencies, fee itemisation per transaction, or an API with webhooks and a test mode to build finance processes on. 7 8
The SaaS Founder
Captured pages on settlements reconciliation and settlement reports show that payout reporting exists in some form. We found no public information on payout schedules, settlement currencies, fee itemisation, or an API with webhooks and a test mode, so I cannot tell whether these reports would let a finance team close a month. 7 8
The Payments Engineer
The partner documentation includes pages on settlements reconciliation and settlement reports, so payout reporting exists on paper for distribution partners. I found no public information on payout cadence, fee itemisation, a versioned API with idempotency and webhooks, a test mode, or a status page in these captures — and when webhooks go quiet I need that last one documented, not inferred. 8 7
The Compliance Officer
Settlement reconciliation and settlement reports are documented for partners, indicating reporting that ties payouts back to transactions. We found no public information on payout cadence and settlement currencies, fee itemisation per transaction, accounting exports, or an API with webhooks and a test mode. 7 8
The Skeptic not rated — no public information
We found no public information on payout cadence, settlement currencies, fee itemisation, reconciliation reports or API and webhook access. The captured set contains pages addressed to settlements reconciliation and settlement reports for distribution partners, with nothing confirmed from their content. 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 — The terms let the provider freeze funds or close the account at any time with no notice, reason or timeline.
3 — The regulated entity or the licensed partner behind the payments named, and a chargeback or dispute process described.
5 — The regulated entity named with its supervisor or licence type, the dispute process and chargeback fee published, and either safeguarding of merchant funds or a notice period for ordinary termination stated.
8 — Entity, supervisor, register number and passporting stated per country; safeguarding stated; 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 not rated — no public information
We found no public information on the licensed entity behind the payments, safeguarding of merchant funds, reserve or rolling-hold conditions, termination notice, or the dispute and chargeback process. The captured pages are integration and settlement documentation for distribution partners, with no terms or imprint pages among them. 2 8
The E-Commerce Lead not rated — no public information
We found no public information on the regulated entity and licence behind the payments, safeguarding of merchant funds, reserve or freeze conditions, termination notice, or the chargeback and dispute process. The captured pages are technical integration documentation carrying no account terms, so this is reported as unevaluated rather than scored. 1 2 3 4 5 6 7 8
The SaaS Founder not rated — no public information
We found no public information on the regulated entities behind the payments, their licences or supervisors, safeguarding of merchant funds, reserves, or account and termination terms in the captured pages — the only captured text describes the documentation's intended audience. This criterion stays open rather than counted. 2
The Payments Engineer not rated — no public information
I found no public information on licence or account terms in these captures: the pages are developer integration guides for distribution partners, and none of them touches on a regulator, licence type, safeguarding, disputes, reserves or termination. 1 2
The Compliance Officer not rated — no public information
We found no public information on the regulated entity behind the payments, its supervisor or register number, safeguarding of merchant funds, reserves, or freeze, termination and dispute terms. The pages read address distribution partners and integration, not account terms. 2 8
The Skeptic not rated — no public information
We found no public information on the regulated entity behind the money, its supervisor, licence or register number, safeguarding of merchant funds, reserve and rolling-hold rules, freeze and termination terms, or the chargeback process. I read an unstated licence number as an answer, and none is stated in what was captured. 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 — Contracting entity and processing of payment data both shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; the processing location of payment data not stated or partly outside the EU.
5 — An EU contracting or regulated entity, with EU processing of core payment data stated or a subprocessor list published, and a data processing agreement offered.
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 not rated — no public information
We found no public information on the contracting entity's jurisdiction, where transaction and cardholder data are processed, subprocessor locations, or a data processing agreement. Nothing in the captured pages speaks to who controls the payment data, so I have nothing to assess on the European control question. 2 3
The E-Commerce Lead not rated — no public information
The contracting entity, data residency, processing locations and data processing agreement are all marked unknown, and nothing in the captured pages states where transaction or cardholder data is processed. We found no public information to establish European data handling either way, so this is reported as unevaluated rather than scored. 1 2 3 4 5 6 7 8
The SaaS Founder not rated — no public information
We found no public information on where the contracting entity sits or on where transaction and cardholder data are processed and stored; every sovereignty question came back unrecorded from the captured pages. Unknown is not a verdict against the vendor, but it is nothing I can plan a European deployment on. 2
The Payments Engineer not rated — no public information
The sovereignty dimensions are all marked unknown, and I found no public information on where the contracting entity sits or where payment and cardholder data are processed and stored in these captures. 1 2
The Compliance Officer not rated — no public information
We found no public information on the contracting entity's jurisdiction, where transaction and cardholder data are processed and stored, the subprocessors involved, or a data processing agreement distinguishing the provider's role as controller versus processor. The processing the vendor controls is therefore unknown from these pages. 2 7
The Skeptic not rated — no public information
Every sovereignty dimension on record — contracting entity, data residency, hosting, data processing agreement — is unknown, and the captured pages confirm no processing location for payment data. Unknown is not the same as outside Europe; it simply means nothing is proved either way. 2
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 rate published for one method or card type, or a "from" percentage.
5 — Rates published per main method with domestic and international cards distinguished, and any monthly or plan fee stated with its billing period; ancillary fees (currency conversion, chargeback, payout) may still be 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 not rated — no public information
We found no public information on pricing: no transaction rates, monthly or plan fees, currency conversion markups, or chargeback and payout fees were captured. The one confirmed fact describes a product distributed through payment providers, and no public rate page appears among the captured pages. 2
The E-Commerce Lead not rated — no public information
We found no public information on pricing in the captured pages — no rate per method or card type, no monthly fee with its billing period, and no chargeback, refund or payout fees. A merchant cannot compute an effective fee for their own country and method mix from what was captured. 1 2 3 4 5 6 7 8
The SaaS Founder not rated — no public information
We found no public information on pricing — no per-method rate, monthly or plan fee, conversion markup, or chargeback fee appears in the captured pages, which are integration documentation for distribution partners. Without a published rate I cannot compute the effective fee for my own mix of cards, countries and renewal volume. 2 7
The Payments Engineer not rated — no public information
I found no public information on pricing in these captures: no rate, plan fee, currency conversion markup, chargeback fee or payout fee appears on any of the pages. 1 2
The Compliance Officer not rated — no public information
We found no public prices on the captured pages — no per-method rates, monthly or plan fees, or chargeback and payout fees. The pages are integration and settlement documentation aimed at payment providers. 2 7
The Skeptic not rated — no public information
We found no public information on prices: not a headline rate, a per-method rate, a currency-conversion markup, a chargeback or payout fee, or a monthly fee is confirmed in the captured pages. With the documentation addressed to payment providers distributing Klarna, there is nothing here a merchant could compute a fee from. 2
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Klarna
Is Klarna European?
Not determined: the vendor’s pages as captured do not say where Klarna is based.
Where does Klarna store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Klarna have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Klarna?
As of 18 Nov 2026, the panel rates Novalnet (3.5/5), PayPal (3.5/5) and Mollie (3/5) highest among the other 45 Payment products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Novalnet (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Klarna alternatives.
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 could not confirm any compliance 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
- 310 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
- 35 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
- 5 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
- 2 hosting 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 legal 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
- 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 16 Nov 2026 Details →
- 2 Payment methods & local coverage — found from sitemap docs.klarna.com Checked 16 Nov 2026 Details →
- 3 Checkout, SCA & fraud — found from sitemap docs.klarna.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 1 Oct 2026 Details →
- 4 Checkout, SCA & fraud — found from sitemap docs.klarna.com Checked 16 Nov 2026 Details →
- 5 Subscriptions & recurring payments — found from sitemap docs.klarna.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 6 Subscriptions & recurring payments — found from sitemap docs.klarna.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
- 7 Settlement, reconciliation & API — found from sitemap docs.klarna.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
- 8 Settlement, reconciliation & API — found from sitemap docs.klarna.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →