Checkout.com
UK / wider Europe Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Checkout Ltd · www.checkout.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.
Checkout.com at a glance
- Vendor
- Checkout Ltd
- Headquarters
- Incorporated in the United Kingdom source, captured 16 Nov 2026
- Data hosting
- In the EU by default source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Checkout.com 3/5, the mean of 6 judges. Checkout.com scores in a steady upper-middle band: payment methods scores 6 across the bench, while checkout and SCA, settlement and reconciliation, and licence and account terms sit at 6 to 7. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Checkout.com scores in a steady upper-middle band: payment methods scores 6 across the bench, while checkout and SCA, settlement and reconciliation, and licence and account terms sit at 6 to 7. The licensing evidence is the strongest part — Checkout SAS is authorised by the French ACPR as an electronic money institution under licence 17208 and passported to all EEA member states, Checkout Ltd holds FCA licence 900816, and PCI DSS Level 1 Service Provider status is published with an attestation — matched by configurable daily, weekly, monthly or twice-monthly settlement on the 1st and/or 15th with automated reconciliation of fees and FX, and 3-D Secure 2.2 with SCA compliance stated for the EEA and UK. Recurring billing scores 5 to 6, with no public information on trials, proration, dunning or exporting stored payment tokens. Sovereignty draws the widest spread, 4 to 6: EEA merchants contract with the French-licensed entity and e-commerce infrastructure is stated to run in EU AWS regions, but subprocessor regions span the US, EEA and UK, and no public information appears on a data processing agreement.
Speaks for it
- Checkout SAS licensed by the French ACPR as an electronic money institution under number 17208, passported to all EEA member states
- PCI DSS Level 1 Service Provider status published with certificate and attestation of compliance
- Settlement configurable as daily, weekly, monthly or twice-monthly on the 1st and/or 15th, with automated reconciliation of fees and FX
- SEPA Direct Debit documented across 36 European countries with EUR processing and settlement, refunds, partial refunds and recurring support
- 3-D Secure 2.2 deployed with automatic upgrades to future versions and SCA compliance stated for the EEA and UK
Held against it
- We found no public information on subscription trials, proration, dunning, mandate pre-notification or exporting stored payment tokens to another provider
- Local payment methods beyond SEPA Direct Debit appear as names without documented countries, currencies or refund treatment
- We found no public information on API versioning, idempotency, published rate limits or a public status page with incident history
- Reserves defined as fixed or rolling without stated limits or release timelines, with the platform-merchant reserve rate set by the marketplace
- The pricing pages publish no rate, percentage or fee figure, with plans created by getting in touch with the team
Best for
- You are an EEA business that wants a locally regulated acquiring partner — EEA merchants contract with Checkout SAS, authorised by the French ACPR and passported across the EEA
- Your finance team wants control over payout timing, from daily settlement to monthly or twice-monthly on the 1st and/or 15th
- You sell mainly into euro markets where SEPA Direct Debit carries the volume, documented across 36 European countries with recurring support
- You need SCA-compliant checkout for EEA and UK customers, with 3-D Secure 2.2 and automatic upgrades to future versions stated
Avoid if
- You need to model your costs before talking to sales — the pricing pages publish no figures and plans are created by getting in touch with the team
- Your procurement requires that no customer data be processed outside the EU — ask the vendor: the public pages we read do not show it
- You are a platform merchant on a marketplace — your reserve rate is set by the marketplace rather than the provider
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 3 of 5 |
| Checkout, SCA & fraud | 3 of 5 |
| Subscriptions & recurring payments | 3 of 5 |
| Settlement, reconciliation & API | 3 of 5 |
| Licence, risk & account terms | 3.5 of 5 |
| European sovereignty | 3 of 5 |
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
Cards from the major schemes, wallets, and a genuinely European list by name — iDEAL, Bancontact, EPS, Multibanco, Przelewy24, Klarna — plus a SEPA Direct Debit page that states 36 countries, EUR processing and settlement, and refunds, partial refunds and recurring support. Beyond SEPA the captured pages give a method list without the countries and currencies each method serves, so I cannot plan per-market acceptance from them. 7 8 10 15
The E-Commerce Lead
The named list gives me the European basics I sell against — iDEAL, Bancontact, EPS, Multibanco, Przelewy24, Klarna and SEPA Direct Debit, which gets its own page with 36 countries, EUR processing and settlement, and refunds, partial refunds, disputes and recurring each marked. That per-method depth stops at SEPA: I found no public information on countries, currencies or refund and recurring support for the other named methods, and no public information on methods such as BLIK, TWINT or Wero. 7 8 10
The SaaS Founder
Cards, Apple Pay and Google Pay plus named European methods (iDEAL, Bancontact, EPS, Multibanco, Przelewy24, Klarna), and SEPA Direct Debit gets a genuinely merchant-plannable entry: 36 countries, EUR processing and settlement, refunds, partial refunds and recurring support all stated. That per-method documentation exists only for SEPA though, and I found no public information on BLIK, TWINT or Wero, so I cannot plan a full country matrix from these pages. 7 8 10
The Payments Engineer
Visa, Mastercard, Apple Pay, Google Pay and PayPal sit alongside named European local methods — iDEAL, Bancontact, EPS, Multibanco, Przelewy24, Klarna — and SEPA Direct Debit gets a proper per-method treatment across 36 European countries with EUR processing and settlement, refunds, partial refunds and recurring support all stated. But that country, currency, refund and recurring detail is documented for SEPA only; the other methods appear as names on a list, so a merchant still cannot plan a per-market rollout from the captured pages. 7 8 10 2
The Compliance Officer
The named list runs from cards and wallets to iDEAL, Bancontact, EPS, Multibanco, Przelewy24 and Klarna, and the SEPA Direct Debit page details 36 European countries, EUR processing and settlement, refunds, partial refunds and recurring support. Beyond SEPA the local methods are named without their countries, currencies or refund treatment, so a merchant cannot plan coverage against it market by market. 10 8 7 15
The Skeptic
Cards and wallets are named alongside iDEAL, Bancontact, EPS, Multibanco, Przelewy24 and Klarna, and the SEPA Direct Debit page is documented properly: 36 European countries, euro processing and settlement, refunds, partial refunds, recurring support and a full-service gateway-plus-collecting model. That per-method rigour appears only there — we found no public country or currency detail for the other local methods, and no information on BLIK, TWINT or Wero. One method documented to that standard lifts this above the middle; a named list for everything else holds it there. 7 8 10 15
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
A fully branded hosted checkout and payment links sit alongside embedded components, 3-D Secure 2.2 with future versions implemented automatically, SCA compliance stated for the EEA and UK, machine-learning fraud screening with custom rules, network tokens and a real-time account updater. I found no public information on SCA exemption handling, risk scores exposed to the merchant, or liability shift per flow. 7 9 10 11
The E-Commerce Lead
Hosted and embedded checkout are both documented — a fully branded hosted page plus Flow components with built-in validation — alongside 3-D Secure 2.2, SCA and PSD2 compliance for EEA and UK, and machine-learning fraud with custom rules and permission lists. Network tokens and a real-time account updater appear in the product list, and intelligent routing through 3-D Secure or Google authentication is pitched for acceptance rates. I found no public information on specific SCA exemptions (low value, transaction risk analysis, merchant-initiated), PCI scope per integration type, liability shift, or authorisation-rate reporting by issuer country. 9 10 11 5
The SaaS Founder
Hosted branded checkout and embeddable Flow components are documented, 3-D Secure 2.2 with SCA and PSD2 compliance in the EEA and UK is stated with intelligent routing to protect acceptance rates, and fraud detection with custom rules and permission lists is built in. The pages do not show SCA exemption strategy, liability shift per flow or authorisation-rate reporting by issuer country, so I stop short of the top band. 9 10 11 5
The Payments Engineer
There is a fully branded hosted checkout, a components integration, payment links, and 3-D Secure 2.2 with automatic upgrades to future versions and SCA compliance for the EEA and the UK, plus machine-learning fraud screening with custom rules, network tokens and a real-time account updater as named modules, and PCI DSS Level 1 Service Provider status with a published attestation. We found no public information on SCA exemption handling — low value, transaction risk analysis, merchant-initiated — on the PCI scope of each integration type, or on liability shift per flow, which is exactly what I need before putting a checkout in front of customers. 9 10 11 5
The Compliance Officer
Hosted and component-based checkout, 3-D Secure 2.2 with SCA for EEA and UK issuers, intelligent routing, configurable fraud rules, network tokens, a real-time account updater and PCI DSS Level 1 as service provider are all documented. We found no public information on SCA exemption handling — low-value, transaction risk analysis or merchant-initiated — or on liability shift per flow. 10 9 11 5
The Skeptic
Hosted page and customisable embedded components, 3-D Secure 2.2 with automatic upgrades to future versions, SCA compliance stated for the EEA and UK, and fraud screening with machine learning and custom-built rules. We found no public information on SCA exemption handling, liability shift per flow, or authorisation-rate reporting, and the PCI position is stated only as Level 1 Service Provider rather than per integration type. Network token support is the one documented item that carries it past the middle. 5 9 10 11
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
There is a dedicated subscription solution with per-stage subscription tracking and granular reporting, SEPA Direct Debit is documented as supporting recurring and one-click payments, and the product list includes Vault, Network Tokens and a Real-Time Account Updater alongside smart retry logic. Dunning, mandate pre-notification, and any process for exporting payment tokens to another provider are not documented on the captured pages. 7 8 11 13
The E-Commerce Lead
A dedicated subscription solution is documented — conversion insights and tracking of subscription payments at every stage — SEPA is marked yes for recurring with one-click and one-time support, and Vault, Network Tokens and a Real-Time Account Updater are listed products. I found no public information on merchant-initiated transactions, dunning, trials or plan changes, mandate pre-notification, failed-payment notifications, or a process for taking stored tokens to another provider. 8 11 6 9
The SaaS Founder
SEPA recurring is explicitly supported, the product list includes Vault, Network Tokens and a Real-Time Account Updater, and smart retry logic with webhooks gives me most of a renewal engine. But I found no public information on trials, proration or plan changes, on mandate pre-notification, on dunning with measurable recovery, or — the part that decides whether my customer base is mine — any documented process for exporting payment tokens to another provider. 8 6 13 11
The Payments Engineer
SEPA flexibly supports one-time, one-click and recurring payments with refunds documented, a Vault and a Real-Time Account Updater are product modules, and there is a subscription solution with granular reporting plus smart retry and "fail fast" logic. We found no public information on subscription mechanics such as trials, proration or dunning, on mandate pre-notification, or on any process for exporting payment tokens to another provider — portability is the part I always look for and it is undocumented here. 6 8 11 13
The Compliance Officer
A subscription product is documented alongside vault storage supporting PAN, tokens and network tokens, a real-time account updater, smart retries, and SEPA recurring with one-click, refunds and disputes. We found no public information on dunning, mandate pre-notification, trials and proration, or a documented process for exporting payment tokens to another provider. 11 7 9 8 13
The Skeptic
The subscription business is served: a dedicated subscription solution with conversion and pricing insights, granular reporting, a vault, network tokens and a real-time account updater, plus SEPA documented as supporting recurring and one-click payments, and smart retry logic to minimise failures. We found no public information on dunning or failed-payment recovery, trials, proration or plan changes, mandate pre-notification, or any process for exporting stored payment tokens to another provider. 6 8 11 13
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
Payout schedules are stated and configurable — daily, weekly, monthly or twice-monthly on the 1st and/or 15th, changed through the account manager — and the pages promise interchange++ fee granularity with automated reconciliation of fees and FX through a single documented API, webhooks, a test account and dashboard exports. I found no public information on accounting integrations, API versioning with idempotency, or a public status page with incident history. 2 8 11 12 13 13
The E-Commerce Lead
Payout cadence is configurable and stated — daily, weekly, monthly or twice-monthly settling on the 1st and/or 15th — and reconciliation is automated through the API with real-time financial data showing a clear breakdown of payment fees, plus a Dashboard with export, webhooks and a developer test account. I found no public information on reports that match bank lines, accounting integrations, API versioning, idempotency and rate limits, or a public status page. 11 12 13 13
The SaaS Founder
Settlement schedules are stated and configurable (daily, weekly, monthly or on the 1st and 15th), reconciliation of fees and FX is automated through the API with a fee breakdown, and webhooks plus a test account are documented. I found no public information on named accounting integrations, API versioning with idempotency and rate limits, or a public status page with incident history, which is what I need before wiring this into month-end close. 12 11 13
The Payments Engineer
Payout schedules are stated and configurable — daily, weekly, monthly or twice-monthly on the 1st and/or 15th — with reconciliation of fees and FX automatable through the API, a Dashboard to view, manage, export and share payment data, and one Unified Payments API with webhooks, an API reference and a test account. What the captured pages do not show is the engineering hygiene I build finance processes on: API versioning, idempotency, published rate limits, and a public status page with incident history — the trust centre covers certifications, not uptime. 11 12 13 13
The Compliance Officer
Daily, weekly, monthly and twice-monthly settlement schedules are stated with settlement on the 1st and/or 15th, deductions itemised including chargebacks, refunds and reserves, and a Unified Payments API with webhooks, a test account, dashboard export and automated reconciliation of fees is documented. We found no public information on API versioning and idempotency, published rate limits, a public status page or named accounting integrations. 12 15 11 13 7
The Skeptic
Payout cadence is genuinely configurable — daily, weekly, monthly or twice-monthly settlement on the 1st and/or 15th — with automated reconciliation of fees and FX through a unified API, a dashboard with view, manage, export and share, webhooks and a test account. We found no public information on accounting integrations, API versioning, idempotency or rate limits, or a public status page with incident history; interchange and scheme fees are promised in granular detail but never itemised in an example a merchant can check. 6 11 12 13
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
The EEA supplier is Checkout SAS, authorised by the ACPR as an electronic money institution under number 17208 with the register linked and passporting to every EEA state, and PCI DSS Level 1 service provider status is published with a 2026 attestation. The contract defines reserves as fixed or rolling amounts withheld from settlement as security, but the reserve rate is communicated by the marketplace, and we found no public information on reserve limits, release timelines, or safeguarding of merchant funds with the EEA entity. 4 5 6 15
The E-Commerce Lead
The licence chain is unusually transparent: Checkout SAS named for France and the EEA as an ACPR electronic money institution under number 17208 passported to all EEA member states with an online register, Checkout Ltd FCA-authorised under 900816, and PCI DSS Level 1 Service Provider with the attestation listed in resources. Reserves are defined as fixed or rolling amounts withheld from settlement, but without limits or release timelines. I found no published chargeback fee, no notice period for ordinary termination, and no freeze, appeal or exit terms on the captured pages. 5 6 15 4
The SaaS Founder
The licence disclosure is unusually complete: Checkout SAS is named with its ACPR licence number 17208 passported to all EEA member states, the register is viewable at regafi.fr, the UK entity carries FCA number 900816, and PCI DSS Level 1 is published with a certificate and AOC. Reserves are described as fixed or rolling withheld from settlement, but I found no public information on reserve limits and release timelines, a published chargeback fee, or an EEA complaint route to the supervisor, so the bad-day terms are only half written down. 6 15 4 5
The Payments Engineer
The licensing chain is well disclosed: Checkout SAS is an ACPR-authorised electronic money institution under number 17208 passported to all EEA states and listed on the ACPR register, Checkout Ltd holds FCA authorisation 900816, other group entities are named with register numbers, and PCI DSS Level 1 with a published AOC sits alongside a defined fixed or rolling Reserve Account. We found no public information on reserve limits or release timelines, on freeze and termination terms with reasons and a route to appeal, or on a published dispute process with a chargeback fee. 5 6 15 4
The Compliance Officer
The EEA supplier is Checkout SAS, authorised by the ACPR as an electronic money institution with licence number 17208, RCS number 841033970 and passporting to all EEA member states on the regafi.fr register, Checkout Ltd holds FCA number 900816 for the UK, PCI DSS Level 1 is published with certificate and AOC, and reserves are defined as fixed or rolling with the rate communicated. We found no public information on EEA safeguarding arrangements, reserve release timelines, or reasons and a route of appeal for freezes and termination. 15 6 4 4 5
The Skeptic
The licence trail is the strongest part: Checkout SAS holds French ACPR electronic money licence 17208 passported to all EEA member states and listed on a public register, Checkout Ltd holds FCA licence 900816, and PCI DSS Level 1 status carries a published attestation. The bad day is thinner: a fixed or rolling reserve is defined with no rate basis, limits or release timeline stated — and for platform merchants the reserve rate is set by the marketplace, not the provider — while we found no published chargeback fee, dispute process, or freeze, termination and appeal terms beyond changes deemed accepted unless the merchant objects. The Singapore terms state that customer funds are commingled in one customers' account and the interest is retained by the provider. 5 6 15 4
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
EEA merchants contract with Checkout SAS in Paris under an ACPR licence, the e-commerce infrastructure is stated to be hosted in EU regions of AWS, and a subprocessor list is published with locations, alongside SCC-based transfer safeguards and transfer impact assessments. AWS is listed covering US/EEA/UK with US merchant acquiring traffic processed via AWS in the US, and we found no public information on a data processing agreement. 3 4 5 15 5
The E-Commerce Lead
For EEA merchants the contracting entity is Checkout SAS in Paris under an ACPR electronic money licence, the e-commerce infrastructure is stated to be hosted in the EU regions of AWS, and a subprocessor list is published with regions, alongside EU Standard Contractual Clauses and transfer impact assessments. The same pages show acquiring traffic for US merchants processed via AWS in the US, and I found no public information on a data processing agreement or on hosting options. 3 5 15 5
The SaaS Founder
EEA merchants contract with the Paris entity licensed by the ACPR, the e-commerce infrastructure is hosted in AWS EU regions, and a subprocessor list is published with regions and a controller-versus-processor statement in the privacy notice. The subprocessor footprint includes the US (AWS US/EEA/UK, with US acquiring traffic processed in the US) and I found no public information on a data processing agreement being offered, which keeps this below the middle band. 15 5 3 5
The Payments Engineer
EEA merchants contract with the French ACPR-licensed entity, the e-commerce infrastructure runs in EU regions of AWS, a subprocessor list with locations is published, transfers outside adequacy rely on EU SCCs with transfer impact assessments, and the privacy notice distinguishes controller from processor roles. Two things hold it back: acquiring traffic for US merchants is processed via AWS in the US as well as the EU, and we found no public information on a data processing agreement being offered. 3 5 15 5
The Compliance Officer
EEA merchants contract with the French-regulated entity Checkout SAS, the e-commerce infrastructure is stated as hosted in EU regions of AWS, and a subprocessor list is published with locations — Checkout Technology Ltd (EEA/UK), Google Cloud Platform for BigQuery (EEA/UK) and AWS (US/EEA/UK) — while the privacy notice sets out controller versus processor roles and SCC-based transfer safeguards with transfer impact assessments. We found no public information on a data processing agreement, and the trust page states acquiring transaction traffic for US merchants is processed via AWS in the US and EU. 15 6 5 5 3
The Skeptic
EEA merchants contract with a French ACPR-licensed entity and the e-commerce infrastructure is stated to run in EU AWS regions, with a published subprocessor list carrying locations and standard contractual clauses plus transfer impact assessments for transfers out. The footprint is not clean: the group and its data protection officer are anchored on a London entity, subprocessor regions span the US, EEA and UK with US acquiring traffic processed in the US, and biometric information is shared with Snowflake with no location stated. We found no public information on a data processing agreement. 3 5 15 5
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
The pricing page names an interchange++ model with granular cost detail and a fully flat-rate model based on business profile and risk category, states there are no setup fees and no account maintenance fees, and offers free processing for registered charities. Not a single rate, percentage or "from" figure appears on the captured pages — pricing is tailored and created by getting in touch with the team — so I cannot compute an effective fee for our card and country mix. 2 14 15
The E-Commerce Lead
The pricing page names its models — "Fully flat-rate" and interchange++ with granular cost detail — and states "No setup fees", no account maintenance fees and free processing for registered charities, but publishes no rate, percentage or amount anywhere as captured; pricing is tailored by getting in touch with the team. For my card, country and method mix there is nothing on these pages to compute an effective fee from, not even a "from" rate, and a sponsored sub-merchant annual fee is mentioned without an amount. 2 14
The SaaS Founder
The pricing page names its models plainly — "Fully flat-rate" or "Simple interchange++ fees" — and states no setup fees and no account maintenance fees, with free processing for registered charities. Not one rate for any method or card type is published; pricing is a tailored quote from the sales team, and I found no public information on chargeback, refund or payout fees, so I cannot compute my effective cost from these pages at all. 2 14
The Payments Engineer
The pricing page names the models plainly — "Fully flat-rate" pricing by business profile and risk category, and "Simple interchange++ fees" with granular transaction cost detail — states there are no setup or account maintenance fees, and offers free processing for registered charities, but every actual rate is "tailored pricing" you create "by getting in touch with our team today". We found no public information on per-method rates, cross-border or currency conversion markups, or chargeback, refund and payout fees, so a merchant cannot compute an effective fee for their own mix from public pages alone. 2 14 15
The Compliance Officer
The pricing page describes a flat-rate model based on business profile and risk category, an interchange++ option with granular cost detail, no setup or account maintenance fees, and free processing for registered charities. We found no published rate, percentage, chargeback, payout or currency-conversion figure — pricing is a plan created by getting in touch with the team, and for marketplace merchants the fees are set by the marketplace. 2 13 15 14
The Skeptic
The pricing page names the model — interchange++ with granular cost detail, or a flat rate set by business profile and risk category, FX honoured from capture to settlement, no setup or account maintenance fees, and free processing for registered charities — and then gives no number at all: no rate, no percentage, no chargeback, refund or payout fee, with pricing only through getting in touch with the sales team. A merchant cannot compute an effective fee for any card or country mix from these pages, and a sponsored sub-merchant annual fee is mentioned without an amount. 2 14 13
European sovereignty — proven facts
2 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 |
Incorporated in GB
unverified
Why unverified?The country terms present Checkout Ltd as just the UK contracting entity among many regional Checkout entities, and no excerpt explicitly labels it the group parent, though the privacy notice anchors the Checkout.com group on Checkout Ltd. |
1/2 pts | 4 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?Trust page subprocessor entries list AWS covering 'US/EEA/UK' and note that acquiring transaction traffic for US merchants is processed via AWS in the US and EU, so some customer data is hosted outside the EU. |
2/4 pts | 5 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
Questions about Checkout.com
Is Checkout.com European?
Yes, though not from the EU. whats-best.ai classifies Checkout.com as UK / wider Europe. Its vendor, Checkout Ltd, is incorporated in the United Kingdom, per the vendor’s page captured 16 Nov 2026.
Where does Checkout.com store data?
Checkout.com stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026.
Does Checkout.com have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Checkout.com?
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: Checkout.com alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Transfer impact assessment, Open source. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The country terms present Checkout Ltd as just the UK contracting entity among many regional Checkout entities, and no excerpt explicitly labels it the group parent, though the privacy notice anchors the Checkout.com group on Checkout Ltd.
- Weak sourcing — Hosting location. Trust page subprocessor entries list AWS covering 'US/EEA/UK' and note that acquiring transaction traffic for US merchants is processed via AWS in the US and EU, so some customer data is hosted outside the EU.
- 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.
- 69 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
- 11 legal 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
- 7 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
- 4 compliance 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
- 4 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.checkout.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 2 Pricing page www.checkout.com Checked 16 Nov 2026 Details →
- 3 Privacy policy www.checkout.com Checked 16 Nov 2026 Details →
- 4 Terms of service www.checkout.com Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
- 5 Security / trust page trust.checkout.com Checked 16 Nov 2026 +2 earlier captures: 19 Oct 2026, 30 Sep 2026 Details →
- 6 Legal notice www.checkout.com Checked 16 Nov 2026 Details →
- 7 Payment methods & local coverage — found from sitemap www.checkout.com Checked 16 Nov 2026 Details →
- 8 Payment methods & local coverage — found from sitemap www.checkout.com Checked 16 Nov 2026 Details →
- 9 Checkout, SCA & fraud — found from sitemap www.checkout.com Checked 16 Nov 2026 Details →
- 10 Checkout, SCA & fraud — found from sitemap www.checkout.com Checked 16 Nov 2026 Details →
- 11 Subscriptions & recurring payments — found from sitemap www.checkout.com Checked 16 Nov 2026 Details →
- 12 Settlement, reconciliation & API — found from sitemap www.checkout.com Checked 16 Nov 2026 Details →
- 13 Settlement, reconciliation & API — found from sitemap www.checkout.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 14 Licence, risk & account terms — found from sitemap www.checkout.com Checked 16 Nov 2026 Details →
- 15 Licence, risk & account terms — found from sitemap www.checkout.com Checked 16 Nov 2026 Details →