PAYONE vs Unzer

PAYONE

The homepage sells "alle gängigen Bezahlverfahren" without naming anything, while the developer pages do better: Klarna's methods come with a twelve-country list and seven currencies, and SEPA Direct Debit with its scheme countries and mandate flow. We found no public information on wallets such as Apple Pay or Google Pay, on iDEAL, Bancontact or EPS, or on refund and recurring support stated per method beyond Klarna and SEPA.

Unzer

We found no public information naming any payment method, let alone which countries and currencies each one covers — the pricing page says only that a POS merchant can 'flexibel' choose which payment methods to offer. A merchant could plan acceptance in no market from these pages.

PAYONE

The exemption documentation is the best part of this file: low-value thresholds, acquirer transaction risk analysis, soft-decline recovery and who is liable when an exemption turns fraudulent are all written down, with hosted and server-to-server integration modes and a low-PCI claim. We found no public information on network tokens, an account updater, authorisation-rate reporting, or fraud rules and risk scores exposed to the merchant — the fraud modules are only named.

Unzer

The pricing page carries PSD2 strong customer authentication and PCI DSS compliance claims and an FAQ question on fraud protection in online trade, but we found no public information on hosted or embedded checkout options, 3-D Secure handling, SCA exemptions or how the fraud screening actually works. That is a compliance badge, not a documented authorisation path.

PAYONE

SEPA mandates are handled as a first-class product — creation, reuse, a dedicated revocation endpoint, a 36-month lifecycle and recurring charges for an indefinite number of transactions are all documented, plus an 8-week contestation window on valid mandates. But that is where it ends: we found no public information on subscription plans with scheduled charges, dunning or retries, an account updater, or any process for exporting stored credentials to another provider.

Unzer

We found no public information on stored cards, SEPA Direct Debit mandates, subscription logic, dunning or whether payment tokens can ever be exported to another provider. Nothing on the homepage or pricing page addresses charging the same customer twice.

PAYONE

The payouts help pages read as a list of unanswered questions — viewing payouts, timing, changing the cycle, limits and fees — with no payout cadence, delay or figures stated anywhere I could find, and nothing on per-transaction fee itemisation or reports linking a payout to its transactions. The developer API with webhooks, documented status codes and a real test environment is what lifts this above the bare minimum.

Unzer

Payout schedule, settlement currencies and any per-transaction fee breakdown are absent from the public pages, so there is nothing to reconcile against a bank statement. The only finance-relevant signal is that a developer documentation set and a platform status page are named among support resources.

PAYONE

The imprint names PAYONE GmbH in Frankfurt as a BaFin-supervised e-money institution with a commercial register entry, and the terms page carries the full AGB set including girocard and factoring conditions plus an online cancellation route. What I cannot find is what matters on a bad day: safeguarding of merchant funds, chargeback fee figures and a dispute process, notice periods for termination, and any reserve or rolling-hold conditions with limits.

Unzer

The legal notice is unusually complete on entities: Unzer E-Com GmbH as a BaFin-supervised payment institution under register number 122914, a Luxembourg payment institution CSSF-listed as Z00000009, a Danish registration with FSA number 22006, and published complaint addresses for BaFin and CSSF. But we found no public information on safeguarding of merchant funds, reserve or rolling-hold limits, chargeback fees or termination notice periods — the bad-day terms are exactly what is missing.

PAYONE

A German contracting entity with a BaFin e-money licence is on the imprint, and the privacy page states all group companies sit within the EU and EEA, with standard contractual clauses or adequacy decisions covering the third-country recipients — which the page says are website analytics, marketing and hosting only. The silence is on the core question: we found no public information on where payment and cardholder data are processed and stored.

Unzer

The group and its regulated entities are German, Luxembourg, Austrian and Danish, yet the privacy policy shows the website hosted by Netlify in San Francisco with Google, Facebook, LinkedIn and Microsoft analytics attached and a warning that the US is not a safe third country. There is no statement of where payment and cardholder data are processed and no subprocessor list for the payment chain.

PAYONE

Setup and monthly fees are published plainly — "49,00 € einmalige Einrichtungsgebühr" with "0,99 € + Disagio" per transaction at Starter, "99,00 €" once and "19,00 € monatliche Grundgebühr" with "ab 0,09 € + Disagio" at Pro — but the Disagio itself is never quantified, the top package is "individuell" throughout, and the captured pages give no figures for payout limits and fees, chargebacks or currency conversion. I cannot compute an effective fee for any card or country mix from what is public.

Unzer

The pricing page publishes no figures at all: an 'All-in-One' price and a custom offer both route to an individual quote via contact form, so every rate is a sales conversation. A finance lead cannot compute an effective fee for any card, country or method mix from public pages.