whats-best.ai
Search Sign in

Payment · head-to-head

Mollie vs PAYONE

Mollie

EU-Made

Panel rating

Sovereignty: not determined

Full evaluation →

PAYONE

EU-Made

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 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.

Mollie

PAYONE

This judge's pick

Criterion by criterion

Payment methods & local coverage

Mollie

The pricing page names the methods a European rollout needs — iDEAL and Wero, Bancontact, EPS, BLIK, Przelewy24, TWINT, Swish and SEPA Direct Debit — with Klarna and Billie priced per country group and card rates split EEA consumer, commercial and non-EEA. What I cannot plan against: settlement currencies are not stated, refunds and recurring support are not documented per method, and Apple Pay is left at a rate that depends on the underlying credit card.

PAYONE

Cards appear only as a generic claim ("alle gängigen Bezahlverfahren, Kredit-/Debitkarten") while the two documented methods — SEPA Direct Debit and the full Klarna family — are properly detailed per country and currency, including refund behaviour. We found no public information naming Apple Pay, Google Pay, iDEAL, Bancontact or Wero, so a merchant cannot plan per-market coverage beyond those two.

Checkout, SCA & fraud

Mollie

Fraud prevention is named as a module, a checkout is included at no extra cost, and the dashboard offers recovery of failed payments — but I found no public information on 3-D Secure, SCA exemptions, hosted versus embedded options, or the PCI scope of any integration. For a PSD2 shop that silence sits just above the bottom of the scale.

PAYONE

Hosted checkout and server-to-server modes, webhooks, a test mode with documented test cases, and an exemption engine with real engineering in it: low-value exemptions with the 30€ and 100€ limits, acquirer transaction risk analysis, automatic soft-decline recovery, and liability spelled out. We found no public information on PCI scope per integration type (only a "Low PCI requirements" benefit), merchant-facing risk scores, or network tokens and account updater.

Subscriptions & recurring payments

Mollie

Recurring payments are included without additional cost, subscriptions are a named module, SEPA Direct Debit is priced, and the dashboard mentions rescuing failed payments. I found no public information on SEPA mandate handling, merchant-initiated transactions, dunning, account updater, or any process for exporting stored payment credentials to another provider.

PAYONE

The SEPA mandate machinery is real — separate mandate creation, reuse of an existing mandate, a dedicated revocation endpoint, automatic revocation after 36 months, and a recurring mandate valid for an indefinite number of subsequent charges. We found no public information on subscription plans with scheduled charges, dunning or smart retries, and card-on-file is mentioned only in passing in the 3-D Secure context.

Settlement, reconciliation & API

Mollie

The developer section shows documentation, a changelog, libraries and a status link, and the test setup is exactly what I want — test keys with no contract and the same endpoints for test and live. Payout frequency and delay are not stated, and beyond a balance-reconciliation module being named I found no public information on per-transaction fee breakdowns, webhooks, or exports that tie each payout to its transactions.

PAYONE

The developer side is buildable — named payment endpoints, webhooks, documented status codes with a finality rule, and a test environment — but payouts are covered only by FAQ topic headings on timing, cycle changes and limits with no values stated. We found no public information on payout frequency or delay, per-transaction fee breakdowns, reconciliation exports that match bank lines, API versioning, idempotency or a public status page with incident history.

Licence, risk & account terms

Mollie

Both regulated entities are fully identified — Mollie B.V. as an e-money institution under the Dutch central bank with register number F0038 and Chamber of Commerce 302.04462, and Mollie UK Ltd under the FCA with FRN 977968 — and the dashboard mentions disputing a chargeback. I found no public information on safeguarding of merchant funds, chargeback fees, reserves or rolling holds, termination notice periods, or a route of appeal.

PAYONE

The legal notice names the entity, supervisor and licence type precisely — PAYONE GmbH, admitted and supervised by BaFin as an e-money institution — with commercial register and VAT details. The terms exist only as downloads whose contents are not captured, and we found no public information on safeguarding of merchant funds, reserve or hold conditions, termination notice periods, or chargeback fees and a dispute process.

European sovereignty

Mollie

An Amsterdam entity holds a Dutch central bank e-money licence, so the contracting party is European, and outside-EEA transfers are acknowledged with EU standard contractual clauses as the mechanism. Where payment and cardholder data are processed is not stated, and the subprocessor disclosure gives categories rather than named providers with locations — apart from Ekata of Mastercard for onboarding fraud checks — so the chain is only partly visible.

PAYONE

Contracting entity, licence and ownership are European — PAYONE GmbH in Frankfurt, BaFin-supervised, owned by Worldline of Paris and the German savings bank publishing group — and the privacy policy states all group companies sit within the EU/EEA with named subprocessors. We found no public information on where payment and cardholder data are processed and stored; the captured privacy pages cover website, chatbot and marketing data, not the payments platform.

Pricing transparency

Mollie

This is close to computable: EEA consumer cards at 1,80 % + 0,25 € versus non-EEA cards at 3,25 % + 0,25 €, iDEAL and Wero at 0,42 €, SEPA Direct Debit at 0,35 €, payouts free up to five a month and 1 % on payouts in another currency, no monthly fees, and interchange++ named as the model from 100.000 € monthly volume. The gaps that keep the effective fee from being fully derivable: chargeback and refund fees are not published and the per-transaction currency conversion markup is not stated.

PAYONE

Plan fees are published plainly — "49,00 € einmalige Einrichtungsgebühr" with a "0,00 € monatliche Grundgebühr" for Starter, "ab 19,00 € pro Monat" for Pro — but the variable cost reads "0,99 € + Disagio" and "ab 0,09 € + Disagio" with the Disagio itself never quantified, so the effective fee cannot be computed. We found no public information on cross-border or currency conversion markups, or chargeback and payout fees; the payout FAQ raises limits and fees without stating values.

Sovereignty, side by side

Dimension Mollie PAYONE
Legal entity Not determined Not determined
Ownership Not determined Not determined
Data residency Not determined Not determined
Subprocessors Not determined US CLOUD Act reach

Facts, side by side

Only facts both products carry under the same definition — anything else would not be a fair row.

Legal · VAT id NL81.58.39.091.B011

captured 22 Sep 2026 · Report an error

DE1859963112

captured 22 Sep 2026 · Report an error

Product · Automated decision making yes3

captured 22 Sep 2026 · Report an error

no4

captured 22 Sep 2026 · Report an error

Product · Payment methods yes5

captured 1 Oct 2026 · Report an error

alle gängigen Bezahlverfahren, Kredit-/Debitkarten, kontaktlose Transaktionen6

captured 22 Sep 2026 · Report an error

Product · Recurring payments yes7

captured 1 Oct 2026 · Report an error

recurring payments · subscriptions · on-demand services · pay-as-you-use services · instalments8

captured 1 Oct 2026 · Report an error