As of 18 Nov 2026, the panel rates PAYONE 2.5/5 and Unzer 2.5/5 in Payment. Weighted by what each judge cares about, 6 of the 6 judges pick PAYONE and 0 pick Unzer. PAYONE scores higher on 5 of 6 criteria (Payment methods & local coverage, Checkout, SCA & fraud, European sovereignty, plus 2 more). Unzer scores higher on 1 of 6 criteria (Licence, risk & account terms). Provenance — PAYONE: EU-Made, France; Unzer: EU origin, foreign-owned, Germany. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
The bench splits by criterion; there is no overall winner. PAYONE is ahead on payment methods (5.7 vs 4.0, 6 judges lean PAYONE), checkout and SCA (7.2 vs 5.7, 6 lean PAYONE) and sovereignty (4.0 vs 3.2, 5 lean PAYONE, 1 tie). Unzer is ahead on licence and account terms (5.7 vs 4.0, 6 lean Unzer). The benches genuinely divide on recurring billing (5.7 vs 5.2, 3 lean PAYONE, 3 tie) and settlement and reconciliation (4.2 vs 4.0, 1 lean PAYONE, 5 tie). Pricing transparency reads 4.0 vs 0.2, 6 judges lean PAYONE; Unzer publishes no prices — a B2B norm — and pricing is not weighted in its verdicts. PAYONE leads the five reported judge totals (4.6 vs 4.4, 5.2 vs 4.9, 5.1 vs 4.8, 4.7 vs 4.2, 4.5 vs 4.4). We found no verdict summary for Unzer here; PAYONE's data residency and hosting are recorded as unknown.
Choose PAYONE if
You need documented SCA exemption handling in checkout — 6 judges lean PAYONE there (7.2 vs 5.7), with the verdict recording low-value exemptions below 30 € with the five-transaction and 100 € caps, automatic soft-decline recovery and liability written down for both flows.
Your storefronts span the twelve countries and seven currencies of the named Klarna suite and you take SEPA Direct Debit — payment methods leans PAYONE with 6 judges (5.7 vs 4.0).
Your recurring revenue runs on SEPA Direct Debit mandates you want handled as first-class API objects — recurring billing leans PAYONE with 3 judges and ties for 3 (5.7 vs 5.2).
Your compliance scorecard weights the sovereignty criterion — 5 judges lean PAYONE there (4.0 vs 3.2), though PAYONE's data residency and hosting are recorded as unknown.
Choose Unzer if
Your contracts review weighs licence and account terms most heavily — that criterion leans Unzer with 6 judges (5.7 vs 4.0), the one place the table has Unzer ahead.
You need a German legal entity — Unzer's legal entity jurisdiction is recorded as DE.
Your architecture expects data residency outside the EU — Unzer's data residency is recorded as non-EU.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Finance Lead
Closes the month and owns the cash position. Wants payouts on a stated schedule, fees itemised per transaction rather than netted into a lump, reports that match the bank statement, and a rolling reserve written into the contract with a limit rather than discovered on a Tuesday.
PAYONE
This judge's pick
Unzer
Criterion by criterion
Payment methods & local coverage
PAYONE
The developer pages name the full Klarna suite — Pay Later, Pay in 3/4, Pay Now bank transfer and direct debit, Billie B2B, Fair Financing — with twelve supported countries and seven currencies, and SEPA Direct Debit is documented with its own country list, girocard participation terms exist, and cards appear as Visa, MasterCard and American Express. However, we found no public information on wallets or local methods such as iDEAL, Bancontact, BLIK or EPS, or on a per-country matrix stating settlement currencies.
Unzer
Cards, digital wallets, SEPA Direct Debit, prepayment and purchase on account or in instalments are listed as supported categories, with a secured instalment product of Unzer's own named. Beyond SEPA, though, we found no public information naming local methods such as iDEAL, Bancontact or EPS per country, and no settlement currencies or refund and recurring support stated per method.
Checkout, SCA & fraud
PAYONE
The Exemption Engine documentation is unusually concrete: low-value exemptions below €30 with the five-consecutive-or-€100 caps, acquirer transaction risk analysis, automatic soft-decline recovery when frictionless flow is refused, and the merchant's liability for fraudulent exemptions stated plainly. Integration modes include hosted checkout, hosted tokenization, server-to-server and mobile, with 3-D Secure steps covered automatically, SCA exclusions auto-detected, and the issuer covering fraud losses; we found no public information on authorisation-rate reporting, network tokens or an account updater.
Unzer
The decoupled SCA flow is documented to a level I can plan against: EMV 3DS 2.x, a single-use authentication reference with a 90-day authorisation window, partial captures, and card-on-file setup with follow-on merchant-initiated transactions flagged. PCI DSS Level 1 is published and fraud monitoring runs provider-side around the clock, but we found no public information on hosted versus embedded checkout options, configurable fraud rules exposed to the merchant, or authorisation-rate reporting.
Subscriptions & recurring payments
PAYONE
SEPA mandate handling is properly built out: a separate CreateMandate API, a RevokeMandate endpoint, a 36-month mandate lifecycle, an eight-week contestation period for valid mandates, recurring mandates valid for an indefinite run of charges, and webhook status codes that flag declines. But we found no public information on subscription logic such as trials, proration or plan changes, on smart retries and dunning beyond 1-cent transfer guidance for failed direct debits, or on exporting payment tokens to another provider.
Unzer
Stored-card tokenisation across local and international methods, one-time SEPA mandate collection, and a subscription module with adjustable debit intervals, terms, prices and over- and underpayment tracking are all documented, with recurring SCA and merchant-initiated transactions handled explicitly. We found no public information on dunning or smart retries, mandate pre-notification, an account updater, or any process for exporting payment tokens to another provider.
Settlement, reconciliation & API
PAYONE
Payouts are addressed only as an FAQ section — where to view them, when they arrive, how to change the cycle, and whether there are limits or fees, with no values stated on the page — so we found no public information on a stated payout schedule, fee itemisation per transaction, or reports that tie each payout to its transactions and charges. The developer platform does provide a documented API with webhooks and a test environment, which is the part a finance team could build on.
Unzer
The ledger side is real: transaction, payment-method, VAT and cash-closing reports with exports to DATEV, Excel and CSV, and receivable accounts separated per payment method under GoBD. The money side is thin though — we found no public information on payout cadence, settlement currencies, fee itemisation per transaction, or webhooks and a test mode for the API.
Licence, risk & account terms
PAYONE
The imprint names PAYONE GmbH with its Frankfurt commercial register number, its BaFin e-money institution licence, and ownership by Worldline and the DSV-Gruppe, and the terms library runs deep — girocard participation conditions, PAC & PPS conditions, factoring agreements — with online contract cancellation and chargeback FAQs. But we found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions with limits and release timelines, the chargeback fee, or a notice period for ordinary termination.
Unzer
Licensing disclosure is unusually complete: Unzer E-Com is a BaFin-supervised payment institution under the ZAG with register number 122914, with sister licences and register numbers in Luxembourg and Denmark, complaint routes to BaFin and the CSSF, PCI DSS Level 1 published, and the 2021 BaFin special audit and its October 2024 lifting disclosed on Unzer's own pages. What I cannot find is the bad-day contract: we found no public information on safeguarding of merchant funds, rolling reserves with limits and release timelines, freeze and termination terms, or a published chargeback fee.
European sovereignty
PAYONE
The contracting entity is German — PAYONE GmbH, registered at the Frankfurt local court and licensed by BaFin as an e-money institution — while the privacy policy places the parent Worldline group's seat in Paris and states that all group companies sit within the EU and EEA. We found no public information on where payment or cardholder data is processed or stored, on a data processing agreement, or on subprocessor locations; the published subprocessor list covers website tools such as Google Analytics and Facebook Pixel, with standard contractual clauses and adequacy decisions cited as transfer safeguards.
Unzer
The contracting entities are German and Luxembourg-based with EU payment-institution licences and GDPR is claimed throughout, so the entity layer is European. The only processing statement captured covers the marketing website and names Netlify in San Francisco as its host; we found no public information on where the payment platform's merchant and transaction data is processed or stored, nor a published subprocessor list or a data processing agreement covering that processing.
Pricing transparency
PAYONE
The e-commerce plans are published plainly: Starter with a 49,00 € one-off setup, 0,00 € monthly and a 0,99 € + Disagio transaction charge; Pro at 99,00 € once, 19,00 € per month and ab 0,09 € + Disagio; Individual priced individually; and POS price lists available as downloads. But the Disagio itself — the percentage a merchant actually pays — is never quantified, and we found no public information on chargeback, currency conversion or payout fees, so the effective rate cannot be computed from these pages.
Unzer
The pricing page presents an all-in-one offer and a custom offer and lists what is always included — personal consulting, onboarding, integration without programming — but shows no concrete prices, with rates available only as an individual quote through a contact form. From what is public I cannot compute an effective fee for any card mix, country mix or method.
Sovereignty, side by side
Dimension
PAYONE
Unzer
Legal entity
Incorporated in FR
Incorporated in DE
Hosting location
Not determined
Outside the EU
Hosting options
Not determined
Not determined
Open source
Not determined
Not determined
Data processing agreement
Not determined
Not determined
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
As of 18 Nov 2026, the panel rates both 2.5/5. Weighted by what each judge cares about, 6 of the 6 judges pick PAYONE and 0 pick Unzer. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is PAYONE or Unzer European?
PAYONE is European (EU-Made, France). Unzer is European (EU origin, foreign-owned, Germany). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Where do PAYONE and Unzer store customer data?
Per the vendors’ own pages as captured — PAYONE: its pages as captured do not say. Unzer: Outside the EU by default.