Adyen
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Adyen N.V. · www.adyen.com
Compare with Stripe → 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.
Adyen at a glance
- Vendor
- Adyen N.V.
- Headquarters
- Incorporated in the Netherlands source, captured 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 AI panel rates Adyen 3/5, the mean of 6 judges. Adyen N.V. 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
Adyen N.V. is a Dutch payment platform, licensed as a bank by De Nederlandsche Bank, and it scored highest on checkout and SCA, 7 to 8, and settlement and reconciliation, 7, and lowest on sovereignty, 3 to 4. The strengths are concrete: an Authentication Engine documented to handle PSD2 SCA and exemptions with the liability shift written down in both directions, and batch- and transaction-level reconciliation against bank statements with a stated settlement delay of 2 days. Sovereignty is proven at the entity layer only: data residency, hosting options and a data processing agreement are listed as unknown, and the privacy policy covers processing where Adyen acts as data controller. Licence and account terms at 5 to 6 are thinned by the MPL Reserve, continuously determined by Adyen with no stated limits or release timeline. Pricing transparency at 6 to 7 publishes per-method fees such as iDEAL at €0.11 + € 0.22 with no setup or monthly fees, though the captured pages give different figures for the SEPA Direct Debit fee. The judges did not meaningfully diverge.
Speaks for it
- Checkout and SCA scored 7 to 8, with the Authentication Engine handling PSD2 SCA and exemptions and the liability shift documented in both directions
- Settlement and reconciliation scored 7, with batch- and transaction-level reconciliation against bank statements, merchant-chosen payout timing and currency, and a stated settlement delay of 2 days
- The licence chain is public: Adyen N.V., Chamber of Commerce number 34259528, authorised as a credit institution by De Nederlandsche Bank with CRD IV passporting across the EEA
- Recurring billing scored 6 to 7, with card-on-file, subscription and unscheduled card-on-file models, SEPA Core mandates with pre-notification, and Auto Rescue retries with published recovery results such as a 4% improvement on retried transactions at Pinterest
- Per-method fees are published by name — iDEAL at €0.11 + € 0.22, Visa and Mastercard at €0.11 + Interchange+ + 0.60% — with no setup or monthly fees
Held against it
- Sovereignty scored 3 to 4, with data residency, hosting options and a data processing agreement listed as unknown
- The MPL Reserve is continuously determined by Adyen with no stated limits or release timeline, and set-off from settlements is permitted at any time — licence and account terms scored 5 to 6
- We found no public information on trials, proration or plan-change logic, or on a process for exporting payment tokens to another provider
- Klarna and American Express carry only a see-more-information pointer rather than a price, and the captured pages give different figures for the SEPA Direct Debit method fee
- We found no public information on a published chargeback fee, currency-conversion fees or contract term
Best for
- You collect recurring SEPA Direct Debit across the EU and want mandates, pre-notification and refund rules documented down to a configurable creditor identifier
- Your finance team reconciles payouts to bank statements in-house and wants payout timing and currency under its own control
- You build checkout yourself and want PSD2 SCA handled for you — automatic exemptions, Dynamic 3D Secure rules and per-transaction preference from Checkout API v69
- You need a banking licence with EEA passporting for compliance procurement, publicly documented at register level
Avoid if
- You need subscription billing logic such as trials, proration or plan changes — Adyen points to third-party subscription billing partners for that service
- You cannot accept chargebacks that cannot be defended — the documentation states SEPA chargebacks always result in the shopper receiving a refund
- You need processing or settlement in a currency other than EUR — the captured pages document both settlement and processing currency as EUR
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 3 of 5 |
| Checkout, SCA & fraud | 3.5 of 5 |
| Subscriptions & recurring payments | 3.5 of 5 |
| Settlement, reconciliation & API | 3.5 of 5 |
| Licence, risk & account terms | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 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, wallets, SEPA Direct Debit and named local methods such as iDEAL, Klarna and Swish are published with the countries each serves, 200+ methods are browsable, and local acquiring in 27+ markets is stated. But refund and recurring support is documented per method only for SEPA Direct Debit and a handful of combinable methods, currencies are stated only as EUR processing and settlement on the captured pages, and the coverage is not laid out as a matrix a merchant can plan against. 2 6 7 10
The E-Commerce Lead
The captured pages name cards, wallets, SEPA Direct Debit and real local methods with the countries each serves — iDEAL for the Netherlands, Klarna across eight markets, Bancontact and EPS for recurring — with settlement in EUR and a stated settlement delay, which is what I plan merchandising against. Beyond that the pages give counts ("100+", "200+") rather than lists, mark giropay and Sofort as no longer available, and we found no public information on BLIK, TWINT, Przelewy24 or Wero, so my Polish and Swiss markets stay unplanned. Refund and recurring support are documented for SEPA and a handful of methods rather than as a per-method matrix. 2 6 6 2
The SaaS Founder
Cards and wallets plus SEPA Direct Debit and named local methods such as iDEAL, Klarna, Bancontact and EPS are listed with per-country availability and prices, and the payment explorer advertises 200+ methods with local acquiring in 27+ markets — comfortably past the mid bar. But settlement currency and refund or recurring support are documented only for SEPA Direct Debit, and I found no listing for methods like BLIK, TWINT or Wero in the captured pages, so a merchant still cannot plan country-by-country coverage from what is published here. 2 6 10 2 6 6 2
The Payments Engineer
Cards and wallets, SEPA Direct Debit, and named local methods including iDEAL, Bancontact, EPS and Klarna with per-method country lists, plus local acquiring in 27+ markets, is a genuinely European acceptance story. I found no public information on BLIK, TWINT, Przelewy24 or Wero, settlement currency is documented only as EUR, and refund and recurring support is documented per method only partially — SEPA refunds and recurring combined with iDEAL, Sofort, EPS and Bancontact. 2 6 10 2 6
The Compliance Officer
SEPA Direct Debit is documented in depth for EU-wide use with the Core-scheme mandate flow, refunds and recurring support, and the captured pages name iDEAL, Bancontact, EPS, Klarna, cards and wallets by name, with a browser of 200+ methods and country lists per method on the pricing pages. What the evidence does not show is a full per-country matrix with refund and recurring support stated per method, and we found no public information on methods such as BLIK, TWINT, Przelewy24 or Wero on the captured pages. 2 2 6 7 10
The Skeptic
The pricing pages name methods with the countries they serve — iDEAL Netherlands, SEPA Direct Debit across Portugal, France, Belgium, Austria, Spain, Netherlands, Italy and Finland, Swish Sweden, BACS Direct Debit UK — and an explorer advertises 200+ methods with local acquiring in 27+ markets. But refund and recurring support is documented only for SEPA Direct Debit and a short combinable list (iDEAL, EPS, Bancontact), we found no public information on BLIK, TWINT, Przelewy24 or Wero on the captured pages, and the captured pages give different pictures of Sofort — listed as combinable with recurring in one place, "no longer available" on the pricing page. 2 2 6 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 authentication engine is documented as handling PSD2 SCA and requesting exemptions automatically, with Dynamic 3-D Secure rules, per-transaction API overrides, and exemption liability spelled out — it stays with the merchant when they request the exemption and shifts to the issuer when the issuer applies it. Pre-built and API-only checkout paths exist and fraud rules are configurable in the Customer Area. We found no public information on PCI scope per integration type, merchant-exposed risk scores, or authorisation-rate reporting by method and issuer country. 9 10 5 7
The E-Commerce Lead
The authentication engine is documented doing exactly what conversion needs: 3-D Secure is not triggered for out-of-scope transactions or when the issuer does not enforce it, exemptions are requested automatically with liability shift per flow explained, and Dynamic 3-D Secure rules plus per-transaction API settings let me tune when a shopper is challenged. Pre-built UI components for web and apps and an API-only path give checkout options, with network tokens, an account updater and fraud rules adjustable in the Customer Area. We found no public information on the PCI scope of each integration type or on risk scores exposed to the merchant, so I hold just below the top level. 5 7 9 10 11
The SaaS Founder
The Authentication Engine handles PSD2 SCA and exemptions automatically, Dynamic 3D Secure rules are configurable per condition, exemption liability is written down (merchant when requested, issuer when applied by the issuer), and network tokenization and the account updater are documented alongside pre-built UIs for web and mobile. I found no public information on risk scores exposed to the merchant, PCI DSS scope per integration type, or authorisation-rate reporting, which keeps it a step below the top. 5 7 8 9 10 11
The Payments Engineer
Pre-built UIs for web and mobile, an API-only path and Pay by Link, 3-D Secure 1 and 2, an Authentication Engine that applies PSD2 exemptions automatically and documents the liability shift for exemptions, Dynamic 3-D Secure rules, managed network tokens and an account updater — this is a checkout I could integrate against. What holds it back: PCI DSS is stated as overall compliance rather than scope per integration type, and I found no public information on risk scores exposed to the merchant or authorisation-rate reporting by method and issuer. 5 7 8 9 10 11
The Compliance Officer
The Authentication Engine is documented to handle PSD2 SCA end to end — exemptions requested where applicable, Dynamic 3D Secure rules, per-transaction API preference from Checkout API v69 — and exemption liability is written down in both directions. Hosted pre-built UI, API-only and Pay by Link integration options, preset adjustable fraud rules, network tokenisation and account updater are documented; we found no public information on PCI DSS scope per integration type, risk scores exposed to the merchant, or authorisation-rate reporting by method and issuer country. 9 8 5 7 10
The Skeptic
This is the strongest part of the file: the Authentication Engine is documented to handle PSD2 SCA and request exemptions where applicable, Dynamic 3-D Secure rules and per-request API overrides exist, and the liability shift is spelled out — a merchant-requested exemption keeps the liability with the merchant, an issuer-applied one shifts it to the issuer. Managed network tokenization, a real-time and a batch account updater, adjustable fraud rules in the Customer Area and PCI DSS compliance are all on the record. We found no public information on the PCI DSS scope per integration type, on risk scores exposed to the merchant, or on authorisation-rate reporting by issuer country. 8 9 10 11 5
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
Recurring is engineered, not bolted on: tokenisation with CardOnFile, Subscription and UnscheduledCardOnFile models, SEPA mandates with pre-notification at least one day before debit, an account updater covering Visa and Mastercard, and Auto Rescue smart retries with named merchants reporting recovery results. We found no public information on trials, proration or plan changes — subscriptions are described as fixed amount, fixed schedule — and no public information on a documented process for exporting payment tokens to another provider. 10 11 7
The E-Commerce Lead
The recurring plumbing is strong: tokens that never expire, SEPA mandates signed in the flow with the required pre-notification, merchant-initiated models covering fixed subscriptions and unscheduled usage-based charges, an account updater for Visa and Mastercard, and Auto Rescue retrying refused renewals with published recovery results from named merchants. What we did not find is subscription logic — trials, proration, plan changes — or any documented process for exporting payment tokens to another provider, and Adyen itself points to third-party partners if you want a subscription billing service. Payment infrastructure, not a billing product. 10 11 7
The SaaS Founder
For a subscription business this is the serious version: card-on-file, subscription and unscheduled card-on-file processing models, SEPA mandates with pre-notification and a configurable creditor ID, an account updater, and Auto Rescue whose recovery is measured in public case results such as a 4% improvement on retried transactions. What I found no public information on is proration, trials and plan changes — Adyen points to third-party subscription billing partners for that — and on any process for exporting stored payment tokens to another provider, which is the exit a merchant like me cares about most. 7 10 11 7 6
The Payments Engineer
Card-on-file, subscription and unscheduled card-on-file processing models, tokens that never expire, SEPA Core mandates signed in the payment flow with pre-notification requirements, an account updater, and Auto Rescue with published recovery results (a 4% improvement on retried transactions at Pinterest) make recurring a first-class concern. I found no public information on trials, proration or plan changes, and no documented process for exporting tokens to another provider — only deletion of stored details via API or the Customer Area. 7 10 11 7 6
The Compliance Officer
Tokenisation with CardOnFile, Subscription and UnscheduledCardOnFile models, SEPA Core mandates with pre-notification at least one day before each debit, Auto Rescue retries and account updater are documented, with case evidence of a merchant replacing manual dunning. We found no public information on trials, proration or plan-change logic, or on a process and timeline for exporting payment tokens to another provider. 11 10 7 6 7
The Skeptic
Tokenization with CardOnFile, Subscription and UnscheduledCardOnFile models, SEPA Core mandates implicitly signed in the payment flow, pre-notification at least one day before every debit, a configurable own creditor identifier, Auto Rescue retries (a named customer reports a 4% recovery improvement on retried transactions) and account updaters are all documented. But we found no public information on trials, proration or plan changes, and — the part I always read for — no documented process for exporting payment tokens to another provider: the captured pages show tokens never expire and can be disabled, nothing about taking them with you. 10 11 7 7 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
This is close to what I need to close a month: payout batches matched to the bank statement, bank/card commission and DCC markup broken out per entry, net credit defined as gross minus those, and a transaction-level report carrying the cost of each payment, refund and chargeback in the batch. Payout timing and currency are the merchant's choice, with a stated settlement delay of 2 days and sales-day payout, and the API is versioned with webhooks and a test account. We found no public information on idempotency, published rate limits, a status page with incident history, or named accounting integrations. 12 13 2 6 11 9
The E-Commerce Lead
Batch-level reconciliation matches payout batches to the bank statement with gross, bank/card commission and DCC markup columns and a worked example, transaction-level reports carry each payment, refund and chargeback with its costs, and there is guidance for invoice reconciliation and closing the fiscal period — close-the-month material. Payout timing and currency are mine to choose, the settlement delay is stated as two days with sales day payout available, and the API comes with webhooks and a test account. We found no public information on idempotency, published rate limits or a public status page. 11 12 13 6
The SaaS Founder
Batch-level reconciliation matches payout batches to bank statements with bank/card commission and DCC markup broken out per entry, transaction-level reports show each payment, refund and chargeback with per-transaction costs, and there are guides for invoice reconciliation and closing the fiscal period. Payout timing and currency are merchant-chosen, webhooks carry HMAC validation, and a test account is available; I found no public information on idempotency, published rate limits, a status page with incident history, or named accounting integrations. 5 11 12 13 2 6
The Payments Engineer
Batch-level and transaction-level reconciliation matching payouts to bank statements with bank/card commission and DCC markup columns, a 2-day settlement delay, merchant-chosen payout timing and currency, and an API whose versioning shows in the changed field behaviour between Checkout API v68 and v69, with webhooks and HMAC validation. The test account is requested through the team rather than a documented self-serve mode, and I found no public information on idempotency keys, published rate limits, or a status page with incident history. 5 9 11 12 13 2 6 6
The Compliance Officer
Batch-level reconciliation against the bank statement via the Aggregate Settlement Details Report, per-transaction costs, invoice reconciliation and fiscal-period closing guides are documented, payouts are configurable in timing and currency, and the API is versioned with webhooks and a test account. We found no public information on a public status page with incident history, idempotency, or published rate limits. 12 13 6 11 9
The Skeptic
Batch-level reconciliation matched to bank statements with Bank/Card Commission and DCC Markup columns down to Net Credit (a worked batch of EUR 5,847.53 net with EUR 114.27 commission on 31 transactions), transaction-level costs per payout, sales day payout, a 2-day settlement delay, merchant-chosen payout timing and currency, and an API with webhooks and a test account. We found no public information on idempotency and published rate limits, a public status page with incident history, or named accounting integrations — the fiscal-period guides are referenced but nothing is named. 12 13 6 2 11
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 licence chain is public and strong: Adyen N.V. registered with the Dutch Chamber of Commerce under number 34259528, authorised as a credit institution by De Nederlandsche Bank, passporting acquiring and payment services across the EEA, with UK branch permissions and other licences listed. The risk terms are what thin it out — the MPL Reserve is written into the contract but its level is continuously determined by Adyen with no stated limit or release timeline, set-off from settlements is permitted at any time, and we found no public information on ordinary termination notice, an appeal route, safeguarding, or a published chargeback fee. 15 5 7
The E-Commerce Lead
The licence layer is transparent: Adyen N.V. is a credit institution supervised by De Nederlandsche Bank with CRD IV passporting across the EEA, a published Chamber of Commerce number, named UK and UAE authorisations, and SEPA chargeback windows and reasons documented. The bad-day terms are thinner: the reserve is variable and "as continuously determined by Adyen" with no limits or release timeline stated, set-off is permitted at any time, and we found no public information on a chargeback fee, a termination notice period or an appeal route. 5 15 7
The SaaS Founder
The licence chain is unusually open: Adyen N.V. is a credit institution supervised by De Nederlandsche Bank with EEA passporting, a published register number, UK branch permissions and UAE licences all stated. The bad-day terms are thinner — the reserve is described as variable and continuously determined by Adyen with no limits or release timeline, set-off from settlements is permitted at any time, and I found no public information on a chargeback fee, termination notice period or appeal route. 3 5 14 15 7 2
The Payments Engineer
Adyen N.V. is named as a credit institution supervised by De Nederlandsche Bank with Chamber of Commerce number 34259528, CRD IV passporting across the EEA, a UK Part 4A permission and other named licences, and SEPA chargeback handling is documented down to the eight-week and thirteen-month windows. The MPL Reserve is retained "as continuously determined by Adyen" with no stated limits or release timeline, set-off applies to any amounts at any time, and I found no public information on a published chargeback fee, safeguarding, a termination notice period or an appeal route. 5 7 14 15 7
The Compliance Officer
This is my ground: Adyen N.V. is named with Chamber of Commerce number 34259528, authorised as a credit institution by De Nederlandsche Bank, with CRD IV passporting across the EEA and separately documented UK and UAE permissions — register-level naming, exactly as it should be. The MPL Reserve and set-off rights are defined but without limits or release timelines, the chargeback fee is not published, and we found no public information on safeguarding statements, an appeal route against freezes, or the PCI DSS level rather than bare compliance. 5 15 7 4 3
The Skeptic
The licence layer is real: Adyen N.V., Dutch Chamber of Commerce number 34259528, authorised as a credit institution by De Nederlandsche Bank with CRD IV passporting across the EEA, a UK branch with Part 4A permission under the PRA and FCA, a UAE licence with its number, and PCI DSS compliance stated. The bad-day terms are the weak leg: the MPL Reserve is "continuously determined by Adyen" with no limits or release timeline, set-off is permitted at any time across currencies even in insolvency, SEPA chargebacks cannot be defended at all, and we found no public information on a chargeback fee, safeguarding terms, an ordinary termination notice period or a route to appeal. 15 5 7 4 14
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
The contracting and regulated entity is European and proven: Adyen N.V. in Amsterdam, licensed by De Nederlandsche Bank, with a published privacy policy and a complaints route to the data protection authority. We found no public information on where payment and cardholder data are processed or stored, and no public information on a subprocessor list or a data processing agreement, so the data side of sovereignty rests unproven rather than European. 4 15 3
The E-Commerce Lead
The contracting and regulated entity is Dutch — a bank licensed by De Nederlandsche Bank with its seat in Amsterdam, publishing a versioned privacy policy and a complaint route to the data protection authority. Where payment and cardholder data are processed and stored is not stated on the captured pages, and we found no public information on hosting locations, a subprocessor list or a data processing agreement, so sovereignty is proven at the entity layer only. 3 4 15
The SaaS Founder
The contracting and regulated entity is Dutch, licensed by De Nederlandsche Bank, and a privacy policy with a route to complain to a supervisory authority is published. But the captured pages state nothing on where payment or cardholder data is processed or stored, publish no subprocessor list, and offer no data processing agreement that I could find — the privacy policy even describes Adyen acting as data controller for certain processing — so I can only credit part of the way. 3 4 5 15
The Payments Engineer
The contracting and regulated entity is Adyen N.V. in Amsterdam, licensed as a bank by De Nederlandsche Bank, and European rails such as SEPA Direct Debit are offered. The captured pages do not state where payment and cardholder data are processed or stored, and I found no public information on a subprocessor list or a data processing agreement; the privacy policy names Adyen as controller for part of its processing. 3 4 6 15
The Compliance Officer
The contracting and regulated entity is Dutch with an EU banking licence, but that is where the proof ends: the privacy policy covers processing where Adyen acts as data controller, and we found no public information on where transaction and cardholder data are processed or stored, on subprocessors and their locations, or on a data processing agreement for the processor role. A published privacy policy with a route to the data protection authority leaves the data-location question open rather than answered. 4 15 5 3
The Skeptic
The contracting entity Adyen N.V. sits at Simon Carmiggeltstraat in Amsterdam under a Dutch banking licence, with a privacy policy that names a complaint route to the data protection authority — the entity dimension is proven. The data dimension is not: the processing location of payment data is stated nowhere on the captured pages, and we found no public information on a data processing agreement, a subprocessor list or hosting locations. 4 15 3 5
Pricing transparency
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 fee architecture is public and plainly modelled: a fixed processing fee of €0.11 per submitted transaction regardless of outcome, plus per-method fees with countries named — iDEAL €0.11 + €0.22, SEPA Direct Debit €0.11 + €0.27, cards at €0.11 + Interchange+ + 0.60% — with no setup or monthly fees and the blended versus interchange++ choice defined in the terms. American Express and Klarna are marked "Mehr Informationen" rather than priced, PayPal and PIX run on direct contracts, and we found no public information on chargeback or currency conversion fees or a contract term. The captured pages also give different figures for the SEPA method fee — one shows $0.13 + € 0.27, another €0.11 + € 0.27 — and I am not choosing between them. 2 2 5 6 6 2
The E-Commerce Lead
Most of my mix is computable from public pages: per-method rates with the countries each applies to, a stated no-setup and no-monthly-fee position, and terms that define the Blend and Interchange++ models plainly. Klarna and Amex are "more information", PayPal and Swish point to direct contracts, and we found no public information on chargeback, refund or payout fees or on currency conversion and cross-border markups, so the effective rate for my full country mix is not fully derivable. The different captures of the pricing page also give different figures for the fixed per-transaction fee. 2 5 2 2
The SaaS Founder
Most methods carry public per-country prices with a stated fixed fee and no setup or monthly fee, and the interchange++ and blend models are defined plainly in the terms — more than most providers show. Still, Klarna and American Express are 'see more information', PayPal and PIX are direct contracts plus an unquantified administration fee, and I found no published chargeback, payout or currency-conversion fees; the captured pricing pages also give different figures for the fixed processing fee, so a single effective rate is not computable from them. 2 5 2 2 2
The Payments Engineer
Per-method rates are public — a fixed processing fee plus a method fee, iDEAL and SEPA Direct Debit quoted exactly, Visa and Mastercard at "Interchange+ + 0.60%", no setup or monthly fees — and the blend versus interchange++ models are defined in the terms. Klarna and American Express defer to "Mehr Informationen", PayPal and Swish to direct contracts, I found no public information on a chargeback or payout fee, and the captured pages give different figures for the SEPA method fee. 2 5 2 2 2
The Compliance Officer
The pricing pages publish per-method fees by name — iDEAL "€0.11 + € 0.22", SEPA Direct Debit "€0.11 + € 0.27", Visa and Mastercard "€0.11 + Interchange+ + 0.60%" — state plainly that both Blend and Interchange++ models exist, and confirm no setup or monthly fees. Klarna and American Express point only to "more information" and PayPal to a direct contract, we found no public information on chargeback, payout or currency-conversion fees, and the captured pages give different figures for the fixed fee ("€0.11" on some captures, "$0.13 + € 0.27" for the same method on others). 2 2 2 2 5
The Skeptic
A fixed processing fee of €0.11 per transaction plus per-method fees published country by country — iDEAL Netherlands €0.11 + € 0.22, SEPA Direct Debit $0.13 + € 0.27, cards plainly as Interchange+ + 0.60% — with the Blend and Interchange++ models defined in the terms and no setup or monthly fees charged. But American Express and Klarna read only "€0.11 + Mehr Informationen", PayPal and PIX require a direct contract, and we found no public information on the currency conversion markup rate, the chargeback fee, a payout fee or the contract term — so the effective rate for a real card mix stays a conversation with the sales team. 2 2 2 2 5
European sovereignty — proven facts
1 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 NL | 2/2 pts | 4 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 Adyen
Is Adyen European?
Yes. whats-best.ai classifies Adyen as EU-Made. Its vendor, Adyen N.V., is incorporated in the Netherlands, per the vendor’s page captured 16 Nov 2026.
Where does Adyen store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Adyen have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Adyen?
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: Adyen 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.
- 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.
- 24 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 pricing 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 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
- 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (16)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.adyen.com Checked 16 Nov 2026 Details →
- 2 Pricing page www.adyen.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 26 Oct 2026, 22 Sep 2026 Details →
- 3 Privacy policy www.adyen.com Checked 16 Nov 2026 Details →
- 4 Legal notice www.adyen.com Checked 16 Nov 2026 Details →
- 5 Terms of service www.adyen.com Checked 16 Nov 2026 Details →
- 6 Payment methods & local coverage — found from sitemap www.adyen.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 19 Oct 2026 Details →
- 7 Payment methods & local coverage — found from sitemap docs.adyen.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 8 Checkout, SCA & fraud — found from sitemap docs.adyen.com Checked 16 Nov 2026 Details →
- 9 Checkout, SCA & fraud — found from sitemap docs.adyen.com Checked 16 Nov 2026 Details →
- 10 Subscriptions & recurring payments — found from sitemap www.adyen.com Checked 16 Nov 2026 Details →
- 11 Subscriptions & recurring payments — found from sitemap www.adyen.com Checked 16 Nov 2026 Details →
- 12 Settlement, reconciliation & API — found from sitemap docs.adyen.com Checked 16 Nov 2026 Details →
- 13 Settlement, reconciliation & API — found from sitemap docs.adyen.com Checked 16 Nov 2026 Details →
- 14 Licence, risk & account terms — found from sitemap www.adyen.com Checked 16 Nov 2026 Details →
- 15 Licence, risk & account terms — found from sitemap www.adyen.com Checked 16 Nov 2026 Details →
- 16 Structured-data backfill: markup only, no text or screenshot www.adyen.com Checked 8 Nov 2026 Details →