Mollie vs PAYONE

Mollie

Over 38 methods with one integration, and the pricing page names the locals that decide conversion per market — iDEAL | Wero at 0,42 €, Bancontact, EPS, BLIK, Przelewy24, TWINT, Swish, Bacs, plus Klarna, Billie and in3 priced by country — which clears the DACH and Benelux baseline comfortably. What holds it below the top band: we found no public information on settlement currencies or on which methods support recurring charges and refunds, Google Pay appears nowhere in the captured pages, and countries per method show up only in the Klarna and Billie rate lines.

PAYONE

SEPA Direct Debit and Klarna are documented with real per-method detail — country lists and currencies, down to instalment and B2B variants — which is what I plan mandates against in the DACH region. But the headline pitch stops at 'all common payment methods' plus cards and contactless, and I found no public information on Apple Pay, Google Pay, iDEAL, Bancontact or other named local methods. Cards surface only indirectly through the exemption engine's American Express, Mastercard and Visa references.

Mollie

The captured pages show a checkout included at no extra cost and a fraud prevention module by name, and that is the extent of it. We found no public information on 3-D Secure, SCA exemption handling, PCI DSS scope, liability shift or declined-payment strategy, so I cannot judge what this authorisation path costs me in failed renewals.

PAYONE

The exemption strategy is engineered and public: low-value exemptions with the 30 € and 100 € limits and the five-consecutive rule, acquirer transaction risk analysis, automatic skip or rollout of 3-D Secure per transaction, and automatic Soft Decline recovery when frictionless is refused — with merchant liability for exemptions written plainly. Hosted Checkout Page and server-to-server modes, webhooks and a test environment with documented test cases are there too. I found no public information on an embedded checkout, network tokens or account updater, or authorisation-rate reporting, and PCI scope is only promised as 'Low PCI requirements'.

Mollie

Subscriptions are a named product module, recurring payments are listed as included at no cost, SEPA Direct Debit is on the rate card at 0,35 €, and the dashboard names recovering failed payments — that meets the basic bar of stored methods, SEPA and failed-payment handling. But for a business like mine the absences matter: we found no public information on trials, proration, mandate pre-notification, smart retries, account updater, or any process for exporting payment tokens to another provider.

PAYONE

Mandate management is the strongest piece: a separate mandate-creation route, reuse of an existing mandate reference for card-on-file, a RECURRING mandate valid for an indefinite number of subsequent transactions, a dedicated revoke endpoint, automatic revocation after 36 months, and a contestation period cut to 8 weeks for valid mandates. I found no public information on dunning with smart retries, subscription logic such as trials, proration or plan changes, a card account updater — and, most critically for me, any documented process for exporting payment tokens to another provider. Failed-SEPA guidance exists, but recovery looks left to the merchant.

Mollie

The developer story has real substance — test keys with no contract on the same endpoints as live, a changelog, libraries and a status link — and a balance reconciliation module is named alongside payout rules like five free payouts a month. We found no public information on payout frequency or delay, per-transaction fee breakdowns, or webhooks, so a month-end close is a product claim rather than a documented capability.

PAYONE

The developer side is real — documented endpoints, webhooks and a test environment with test cases — but the finance side is opaque to me: payouts appear as FAQ topics ('When will I receive my payouts?') with no cadence or delay stated on the captured pages, and payout limits or fees are a question without values. Transaction pricing reads 'ab 0,09 € + Disagio' with no visible breakdown of the Disagio, and I found no public information on per-transaction fee itemisation, payout-to-transaction reconciliation reports, accounting exports, API versioning or idempotency.

Mollie

Identity is fully published: Mollie B.V. as an e-money institution licensed by the Dutch central bank with register number F0038, chamber of commerce number given, and Mollie UK Ltd separately registered with the FCA under FRN 977968. The bad day is the gap — we found no public information on safeguarding of merchant funds, reserves or rolling holds, termination notice periods, chargeback fees or an appeal route; the only dispute evidence is a dashboard feature for contesting chargebacks.

PAYONE

The regulated entity is fully named: PAYONE GmbH, Frankfurt am Main, licensed and supervised by BaFin as an E-Geld-Institut, registered at Amtsgericht Frankfurt under HRB 116860 — that part is solid. I found no public information on safeguarding of merchant funds, reserve or rolling-hold limits with release timelines, chargeback fees, a notice period for ordinary termination, or the PCI DSS level; chargebacks appear only as FAQ guidance and termination as a self-service link. The bad-day terms are not written down where I can check them.

Mollie

The contracting and regulated entity is plainly European: Mollie B.V. at Keizersgracht 126, Amsterdam, licensed by DNB, with a UK entity separately FCA-registered. But we found no public information on where payment and cardholder data is processed or stored; the privacy policy only acknowledges transfers outside the EEA under EU standard contractual clauses, the subprocessor disclosure names categories rather than companies with locations, and personal data is shared with Ekata of Mastercard for onboarding fraud checks.

PAYONE

The contracting and regulated entity is German and the ownership is European — Worldline, seat in Paris, and the DSV group per the imprint — with all group companies stated to sit within the EU/EEA and SCCs plus adequacy decisions covering the disclosed third-country transfers, which are website analytics and hosting rather than payment processing. What I found no statement on is where core transaction and cardholder data are processed and stored, and the published subprocessor list covers the website, not the payment chain. For a subscription business handing over every customer's mandate, that silence matters.

Mollie

This is a rate card I can nearly compute my own fee from: every method priced, cards split into EEA consumer at 1,80 % + 0,25 €, EEA commercial at 2,90 % + 0,25 € and non-EEA at 3,25 % + 0,25 €, Klarna priced per country, payouts spelled out (five free per month then 0,25 € each below 500.000 € a year, 1 % on foreign-currency payouts), no monthly fees, and interchange-plus pricing named for volumes from 100.000 € a month. The remaining holes are ones I actually incur: we found no public information on chargeback fees or refund costs, and PayPal is priced only as PayPal fees plus 0,10 €.

PAYONE

Package prices are public and quoted exactly: Starter with '49,00 € einmalige Einrichtungsgebühr', '0,00 € monatliche Grundgebühr' and '0,99 € + Disagio' per transaction; Pro with '99,00 €' setup, 'ab 19,00 € pro Monat' and 'ab 0,09 € + Disagio'; and downloadable price lists exist for the POS tariffs. But the effective fee is unknowable: the captured pages give no breakdown of the Disagio, and I found no public information on cross-border or currency conversion costs, chargeback, refund or payout fees, contract term, or whether the model is blended or interchange++. The Individual package prices every component as 'individuell'.