whats-best.ai
Search Sign in

Payment · head-to-head

PAYONE vs Unzer

PAYONE

EU-Made

Panel rating

Sovereignty: 1 of 4 dimensions proven

Full evaluation →

Unzer

EU origin, foreign-owned

Panel rating

Sovereignty: 1 of 4 dimensions proven

Full evaluation →

The written short answer is being updated after a re-evaluation. The scores below are current.

Read this comparison as one judge. Each weighs the same scores by what they care about.

The Compliance Officer

Handles data protection and outsourcing risk, and wants the regulated entity named with its supervisor and register number, not "licensed in Europe". Asks where transaction and cardholder data are processed, who the subprocessors are, and where the provider acts as controller rather than processor.

PAYONE

This judge's pick

Unzer

Criterion by criterion

Payment methods & local coverage

PAYONE

The homepage promises "alle gängigen Bezahlverfahren" without naming them, while the developer documentation names Klarna's variants with twelve countries and seven currencies, and SEPA Direct Debit with its own country list; girocard participation terms exist as a download, which hints at German debit coverage. We found no public information on Apple Pay, Google Pay, iDEAL, Bancontact, BLIK or TWINT with the countries they cover, so a merchant cannot plan per-market coverage from these pages.

Unzer

The captured pages name no payment method at all: the pricing page says merchants can "wähle flexibel, welche Zahlungsmethoden Du anbieten möchtest" without naming a single one, and we found no public information on which cards, wallets, SEPA Direct Debit or local methods are covered in which countries. Judged as not evidenced.

Checkout, SCA & fraud

PAYONE

The Exemption Engine is documented in unusual depth — low-value exemptions below 30 €, acquirer transaction risk analysis, automatic soft-decline recovery and merchant liability for fraudulent exemptions are all stated — and hosted checkout plus server-to-server with a test environment, webhooks and documented test cases are available. Card-on-file transactions are explicitly out of the engine's scope, and we found no public information on an embedded checkout at reduced PCI scope, network tokens, an account updater or authorisation-rate reporting.

Unzer

PSD2 strong customer authentication and PCI DSS appear as a single line on the pricing page, and fraud protection in online trade is raised as an FAQ question, but we found no public information on checkout integration types, 3-D Secure handling, SCA exemptions or declined-payment flows. A mention of the regulatory layer without any engineered detail is worth little more than nothing here.

Subscriptions & recurring payments

PAYONE

SEPA mandate handling is first-class: mandate creation via three API paths, a dedicated revocation endpoint, a 36-month mandate lifecycle, recurring validity for an indefinite number of subsequent transactions, and reuse of existing mandates including card-on-file, with an eight-week contestation period for valid mandates. We found no public information on subscription plan logic such as trials or proration, on dunning and smart retries, or on exporting stored payment credentials to another provider, so recurring support stops at the mandate layer.

Unzer

We found no public information on stored payment methods, merchant-initiated transactions, SEPA mandate handling, subscription plans or dunning anywhere on the captured pages; even the included-services list on the pricing page is silent on repeat charges. Every element of this capability is unevidenced.

Settlement, reconciliation & API

PAYONE

The developer platform documents an API with webhooks and a test environment, and the help centre addresses payout timing, changing the payout cycle, and payout limits and fees as topics, but the captured pages state no actual payout frequency, delay or fee values. We found no public information on per-transaction fee breakdowns, reports linking payouts to their transactions, or reconciliation exports that match bank lines.

Unzer

Developer documentation and a platform status page are named as resources, which is the only signal an API exists, but we found no public information on payout schedules or currencies, per-transaction fee breakdowns, or reports linking payouts to their transactions. A finance team cannot plan on any of this.

Licence, risk & account terms

PAYONE

The imprint does what I always ask for: PAYONE GmbH is named as an E-Geld-Institut admitted and supervised by BaFin, with commercial register entry HRB 116860 at Amtsgericht Frankfurt am Main and ownership stated as Worldline and the DSV-Gruppe. We found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, termination notice periods or chargeback fees — only FAQ topics on handling chargebacks, a downloadable PCI DSS page without a stated level, and an online cancellation link.

Unzer

The legal notice names Unzer E-Com GmbH as a payment institution under ZAG supervised by BaFin with register number 122914, and Unzer S.A. as CSSF-registered in Luxembourg under number Z00000009, with registry entries for each group company and complaint addresses for both supervisors — exactly the identification I insist on. The bad-day side is absent: we found no public information on reserves, fund freezes, termination notice, safeguarding of merchant funds or chargeback fees on the captured pages.

European sovereignty

PAYONE

The contracting and regulated entity is German with a BaFin e-money licence, the parent Worldline is seated in Paris, and the privacy policy states that all group companies are seated within the EU/EWR, with standard contractual clauses and adequacy decisions cited for third-country recipients. What matters most for my file is missing: we found no public information on where transaction and cardholder data are processed or stored, and the published recipient list covers website analytics and hosting rather than the payment-processing chain, so the payment subprocessors remain unnamed.

Unzer

The contracting and regulated entities are German and Luxembourgish with EU supervisors, but we found no public information on where transaction and cardholder data are processed or stored, and no subprocessor list for the payment chain; the privacy policy names only the website's own host, Netlify Inc. of San Francisco, alongside Google, Facebook and Microsoft analytics tools, with a notice that the USA is not a safe third country. The group is also recorded as majority-owned by US private equity firm KKR, so I see no statement of European control anywhere in the payment chain.

Pricing transparency

PAYONE

Packages are priced publicly — 49,00 € setup for Starter, 99,00 € setup and 19,00 € monthly for Pro, with transaction fees of 0,99 € + Disagio and ab 0,09 € + Disagio — but the Disagio itself, per-method rates, cross-border and currency conversion markups and chargeback fees are not stated on the captured pages. Downloadable price and service schedules exist for the POS tariffs, though their contents are not shown, so a merchant cannot compute an effective fee from what is visible.

Unzer

There are no public prices at all: the pricing page offers an "unkomplizierten All-in-One-Preis" or an individually tailored quote via contact form and lists what is always included, but no rate, fee or contract term appears on the captured pages. A merchant cannot compute any effective fee from what is published.

Sovereignty, side by side

Dimension PAYONE Unzer
Legal entity Not determined Incorporated in DE
Ownership Not determined Not determined
Data residency Not determined Not determined
Subprocessors US CLOUD Act reach Not determined