Mollie vs PAYONE

Mollie

The pricing page names exactly the methods my markets need — iDEAL and Wero at 0,42 €, Bancontact, BLIK, EPS, Przelewy24, TWINT and Swish alongside cards, Apple Pay and SEPA Direct Debit, with Klarna priced per country for Germany, Austria and Switzerland, France, the Netherlands and Belgium, and the Nordics. The "over 38 payment methods" headline stays a count rather than a list, and we found no public information on which countries and settlement currencies each method covers, on per-method refund and recurring support, or on Google Pay.

PAYONE

The developer pages name the Klarna family with twelve countries and seven currencies, SEPA Direct Debit with its country list, and girocard terms, while American Express, MasterCard and Visa appear by name only in the exemption documentation. The homepage's "alle gängigen Bezahlverfahren" is exactly the vague count-claim I distrust, and we found no public information on iDEAL, Bancontact, BLIK, TWINT, EPS, Wero or wallet coverage named per market. Two methods documented with country lists is real work, but it is not a matrix I can plan eight markets against.

Mollie

Checkout is listed as included at no extra cost and fraud prevention appears as a module name, with the dashboard promising to rescue failed payments — but we found no public information on hosted versus on-domain checkout options, on 3-D Secure or SCA exemptions, on PCI scope, or on authorisation rates. As someone judged on conversion, I cannot see from the public pages whether the challenge fires only when it must.

PAYONE

The exemption documentation is the strongest thing here: the engine decides per transaction whether to challenge, low-value exemption rules with the 30€ and 100€ figures are written down, acquirer TRA and soft-decline recovery are explained, and the merchant-liability caveat is stated plainly, with Hosted Checkout Page and server-to-server both documented. But we found no public information on a checkout I could run in my own domain, on PCI DSS scope per integration type beyond a "Low PCI requirements" marketing line, on fraud rules or risk scores exposed to me, or on authorisation-rate reporting. That lands between the anchors, above a basic hosted page, short of a fully engineered authorisation story.

Mollie

Recurring payments are included at no extra cost, subscriptions are a named module, and the dashboard advertises recovery of failed payments. We found no public information on SEPA mandate handling, merchant-initiated transactions, dunning and smart retries, or whether stored payment credentials can be exported to another provider.

PAYONE

SEPA mandates are handled as a real product: separate CreateMandate and RevokeMandate endpoints, mandate reuse for card-on-file, recurring mandates valid for an indefinite number of subsequent transactions, a 36-month lifecycle, an 8-week contestation period for valid mandates, plus recovery guidance for failed direct debits. What I cannot see is any subscription logic — plans, scheduled charges, trials, proration, smart retries or dunning — and we found no public information on exporting stored payment credentials to another provider. The rails are there; the billing brain is undocumented.

Mollie

Balance reconciliation is a named module, and developers get documentation, libraries, a changelog, a status link and test keys on the same endpoints as live. The pricing page states five free payouts per month when processing under 500.000 € a year and then 0,25 € per extra payout, but we found no public information on payout delay, per-transaction fee breakdowns, webhooks or accounting exports.

PAYONE

The payout FAQs list the right questions — timing, cycle changes, missing transactions, limits and fees — but the captured pages give no cadence, delay or fee values for any of them, and we found no public information on per-transaction fee breakdowns or reports that tie a payout to its transactions. The API side is more solid, with documented endpoints, webhooks and a test environment with test cases. Finance could integrate; finance could not close a month from this.

Mollie

The imprint names the regulated entity in full — Mollie B.V. of Amsterdam, licensed as an e-money institution by the Dutch Central Bank under register number F0038 with commercial register number 302.04462, plus Mollie UK Ltd under the FCA with FRN 977968 — and the dashboard lets merchants contest chargebacks. We found no public information on safeguarding of merchant funds, reserve and rolling-hold conditions with limits, chargeback fees, or termination notice and appeal terms.

PAYONE

The imprint does the basics properly: PAYONE GmbH in Frankfurt, admitted and supervised by BaFin as an E-Geld-Institut, commercial register HRB 116860, VAT ID, downloadable terms including girocard and factoring conditions, and an online contract termination option. We found no public information on safeguarding of merchant funds, reserve or rolling-hold limits, freeze and termination notice periods, or chargeback fee amounts beyond FAQ topics. The licence is named; the bad-day rules are not on the captured pages.

Mollie

Mollie B.V. is an Amsterdam company licensed by the Dutch Central Bank, which puts contracting and regulation inside the EU. But we found no public information on where payment and cardholder data are processed or stored, on ownership, or on named subprocessors — only categories such as infrastructure and customer-service, marketing, CRM and email software are given — while the privacy policy confirms transfers outside the EEA under standard contractual clauses, personal data used to train AI models, and fraud checks at Ekata (Mastercard).

PAYONE

The contracting chain is European on the vendor's own pages: a Frankfurt entity supervised by BaFin as an e-money institution, owned by Worldline and the DSV-Gruppe, with all group companies seated within the EU/EWR and standard contractual clauses plus adequacy decisions covering third-country recipients. The decisive gap is that we found no public information on where payment and cardholder data are processed and stored, and the published recipient list covers website hosting, analytics and marketing tools rather than the payment chain. European entity, unproven data residency.

Mollie

Nearly every method carries a public rate: EEA consumer cards 1,80 % + 0,25 €, non-EEA cards 3,25 % + 0,25 €, Klarna split by country, five free payouts per month then 0,25 € each under 500.000 € a year of processing, 1 % for payouts in another currency, no monthly fees, and IC++ pricing named from 100.000 € monthly volume. We found no public information on chargeback or refund fees, which is what keeps the effective rate from being computed end to end.

PAYONE

Starter and Pro publish setup fees of "49,00 €" and "99,00 €", a monthly fee of "19,00 €" for Pro, and transaction fees of "0,99 € + Disagio" and "ab 0,09 € + Disagio" — but the captured pages give no figure for the Disagio itself, which is the rate that decides my margin. Chargeback, payout and withdrawal costs appear only as FAQ topics with no values stated, and the further price lists exist only as downloads whose contents are not captured. For my card and country mix the effective fee is not computable from public pages.