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 Payments Engineer
Integrates the provider and gets paged when webhooks stop arriving. Wants a versioned API with idempotency keys, a test mode that behaves like production, the PCI scope of each integration stated, and a status page that admits incidents rather than a green dot.
PAYONE
This judge's pick
Unzer
Criterion by criterion
Payment methods & local coverage
PAYONE
Cards (Visa, Mastercard, Amex), SEPA Direct Debit with full mandate handling, girocard participation conditions, and Klarna's Pay Now, Pay Later and instalment variants are each documented by name, and the developer pages list the twelve countries and seven currencies Klarna serves plus its refund and cancellation behaviour. What holds this below the top of the scale: we found no public information naming methods such as iDEAL, EPS, BLIK, TWINT or Wero, settlement currencies per method are not stated, and the homepage positions the offer around Germany and Austria.
Unzer
The help centre lists card-based methods, digital wallets, direct transfers, purchase on account and instalments, SEPA Direct Debit and prepayment, and the recurring-payments pages confirm tokenisation of local and international payment methods. Almost nothing is named per market though — Unzer Instalment is the only named method family — and we found no public information on the countries and currencies each method serves or on per-method refund and recurring support.
Checkout, SCA & fraud
PAYONE
The Exemption Engine documentation is what I wish everyone shipped: low-value exemptions for transactions below 30 € with the 100 € single-transaction and five-consecutive limits, acquirer transaction risk analysis, which card methods qualify, who is liable when an exemption turns out fraudulent, and automatic recovery via soft decline when the issuer rejects frictionless; SCA exclusions like MOTO are auto-detected and issuer liability under 3-D Secure is stated plainly. Hosted checkout, hosted tokenization, server-to-server and mobile integration modes are documented with a test environment and written test cases. We found no public information stating the PCI DSS scope per integration type, on an account updater or network tokens, or on authorisation-rate reporting by method and issuer country.
Unzer
The SCA documentation is the deepest part of this evidence: EMV 3DS 2.x decoupled authentication, a single-use SCA reference with a 90-day linkage window, partial-capture rules, card-on-file setup with merchant-initiated transaction flagging, issuer risk-based re-challenge, and documented behaviour when an authorisation is declined. PCI DSS Level 1 and 24/7 AI-backed fraud monitoring are published, but the fraud tooling runs entirely provider-side with no merchant-facing rules, and we found no public information on hosted or embedded checkout form options, low-value or transaction-risk-analysis exemptions, or liability shift.
Subscriptions & recurring payments
PAYONE
SEPA mandates are engineered properly: separate mandate creation and revocation endpoints, reuse of an existing mandate across transactions, recurring validity for an indefinite number of subsequent charges, a creditor-ID service, and webhook status codes that tell you a debit was declined. Card-on-file flows appear through the challenge-indicator handling. We found no public information on subscription logic such as trials, proration or plan changes, smart retries or dunning, a card account updater, or a documented process for exporting payment tokens to another provider.
Unzer
Stored-card tokenisation with a single customer authorisation for regular debits, a one-time buyer mandate collection, merchant-initiated transaction flagging under SCA, and a subscription module with master data, over- and underpayment tracking and adjustable debit intervals are all documented. We found no public information on trials, proration, dunning or smart retries, an account updater, or a process for exporting payment tokens to another provider.
Settlement, reconciliation & API
PAYONE
The developer platform documents webhooks, polling via GetPaymentDetails and GetHostedCheckout, status-code transitions with a five-day finality rule, and a test environment — the pieces I actually build against — but we found no public information on a versioned API with idempotency keys, published rate limits, or a status page with incident history. Payouts appear as FAQ topics (viewing payouts, timing, changing the payout cycle, limits and fees) with no figures stated on the captured pages, and fee itemisation per transaction or reconciliation exports linking payouts to bank lines are not evidenced.
Unzer
Transaction lists, payment-method and VAT reports, monthly exports emailed to a tax advisor, a bulk accounting export to DATEV, Excel or CSV, and GoBD-compliant posting accounts are documented, with a platform status page and developer documentation linked. We found no public information on payout schedules or settlement currencies, fee itemisation, webhooks, a test mode, API versioning or idempotency — nothing here lets me build finance processes on the API.
Licence, risk & account terms
PAYONE
The imprint names PAYONE GmbH with its Frankfurt registry entry (HRB 116860) and states it is licensed and supervised by BaFin as an e-money institution, and chargeback handling is described in the billing FAQs. We found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, a published chargeback fee, or notice periods for termination — only that cancellation is available online through the service area.
Unzer
Entity and licence disclosure is strong: Unzer E-Com GmbH is named as a ZAG payment institution under BaFin register number 122914, Unzer Luxembourg is listed with the CSSF (Z00000009), a Danish licence and Clearhaus registration are given, PCI DSS Level 1 is published, and complaint routes to BaFin and the CSSF plus the EU ODR platform are stated. The bad-day contract is not shown: we found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, freeze and termination terms, or chargeback fees.
European sovereignty
PAYONE
The operating entity is German with a BaFin licence, the parent Worldline is seated in Paris with ownership shared with the German DSV group, and the privacy policy states all group companies sit within the EU/EEA, with standard contractual clauses and adequacy decisions named for third-country transfers. The processing location of payment data itself is not stated and a data processing agreement for payment processing is not evidenced; the published processor lists cover website analytics and media tools.
Unzer
European regulated entities and payment institution licences are evidenced across Germany, Luxembourg and Denmark, and the security page states full GDPR applicability as a European payment provider. The only data-location statement captured is a marketing-website hoster in San Francisco; we found no public information on where the payment platform's transaction and cardholder data is processed, no subprocessor list, and no processor data processing agreement offered to merchants, with ownership majority held by US private equity firm KKR.
Pricing transparency
PAYONE
Package prices are public and exact — Starter at a 49,00 € one-off setup with 0,00 € monthly and 0,99 € + Disagio per transaction, Pro from 19,00 € per month with 99,00 € setup and ab 0,09 € + Disagio, Individual quoted individually — and downloadable price lists exist for the card and terminal products. The Disagio carries no figure on the captured pages, and we found no public information distinguishing domestic from international cards or stating currency-conversion markups or chargeback fees; payout fees appear only as an FAQ topic with no values stated on the page.
Unzer
The captured pricing pages show no concrete rates at all: an All-in-One offer versus an individually quoted offer via a contact form, with personal consulting, fast onboarding and integration always included. Every rate is a sales conversation — we found no public information with a headline rate, per-method rates, or chargeback, payout and currency conversion fees.
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.