Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Mollie B.V. · www.mollie.com

Compare with Stripe → Compare with PAYONE → Report an error on this page Is this your product? →

Link to this page

Mollie: AI-assisted analysis on whats-best.ai Mollie: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Mollie at a glance

Vendor
Mollie B.V.
Headquarters
Incorporated in the Netherlands source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates Mollie 3/5, the mean of 6 judges. Mollie B.V., a Dutch e-money institution licensed by De Nederlandsche Bank, earns its best marks on pricing transparency and 7s on payment methods and settlement and reconciliation. how scores are made
As of
Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Mollie alternatives, European ones first →

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

The panel's verdict

Mollie B.V., a Dutch e-money institution licensed by De Nederlandsche Bank, earns its best marks on pricing transparency and 7s on payment methods and settlement and reconciliation. The rate card is public per method, with cards split into EEA consumer, EEA commercial and non-EEA tiers and a two per cent conversion markup stated; settlement reports itemise fees per payout, export as CSV, PDF, MT940 and CODA, and payouts land in 1–3 business days via SEPA. The weak point is sovereignty, scored 4: payment-data processing location is not stated, transfers outside the EEA are acknowledged under EU standard contractual clauses, and we found no public information on a data processing agreement or hosting options. Checkout and SCA and recurring billing sit at 6 — dynamic 3-D Secure 2 and a subscriptions stack, but no public information on SCA exemptions, dunning or token export. Judges split on pricing transparency: high scores credit near-computable rates, lower ones weigh a chargeback fee that is not publicly listed and a PayPal rate quoted only as PayPal's fees plus €0.10; licence and account terms range 6–7.

Report an error

Speaks for it

  • Public per-method rate card distinguishing EEA consumer, EEA commercial and non-EEA cards, with a stated two per cent currency conversion markup.
  • Settlement reports itemise payment method, chargeback, refund and notification fees per payout and export in CSV, PDF, MT940 and CODA.
  • Mollie B.V. is licensed by De Nederlandsche Bank (F0038) with customer funds safeguarded by the separately supervised Stichting Mollie Payments, and PCI DSS level 1 is published.
  • Broad, named local coverage — iDEAL, Wero, Bancontact, BLIK, TWINT, Przelewy24, EPS — with Klarna and Wero priced per country group.
  • No monthly fee, no minimum fees and no fixed contract terms on the standard plan, with recurring payments included at no extra cost.

Report an error

Held against it

  • Sovereignty scored 4 — the processing location of payment data is not stated and transfers outside the EEA are acknowledged under EU standard contractual clauses.
  • We found no public information on a data processing agreement covering payment processing, on hosting options, or on where cardholder data is stored.
  • The chargeback fee is not publicly listed and PayPal is priced only as PayPal's fees plus €0.10, so those line items cannot be computed from the public pages.
  • Chargeback liability sits fully with the merchant, and reserves rest on transaction volume and refund ratios without defined limits or release timelines.
  • Failed subscription payments retry at a fixed five attempts once a day, and webhooks for subscription status changes are not provided.

Report an error

Best for

  • You sell across European markets and want local methods like iDEAL, Bancontact and BLIK priced per country, so you can compare costs before committing.
  • Your finance team needs itemised settlement data in MT940 or CODA feeding your accounting software, with payouts generally landing in 1–3 business days via SEPA.
  • You want pay-as-you-go pricing — no monthly fee, no minimum fees, no fixed contract terms — while you validate your volume.

Report an error

Avoid if

  • Your compliance regime requires a data processing agreement covering payment processing, or stated data residency and hosting locations for payment data.
  • You run a subscription model that needs trials, proration, smart dunning or a documented process for exporting your payment tokens to another provider.
  • You cannot accept full merchant chargeback liability, or reserves set from your transaction volume and refund ratios without defined limits or release timelines.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Payment methods & local coverage 3.5 of 5
Checkout, SCA & fraud 3 of 5
Subscriptions & recurring payments 3 of 5
Settlement, reconciliation & API 3.5 of 5
Licence, risk & account terms 3.5 of 5
European sovereignty 2 of 5
Pricing transparency 4 of 5

Payment methods & local coverage

Show reasoning
How this is scored

Which methods a European customer can actually pay with — cards and wallets, SEPA Direct Debit, and the local methods that decide conversion per country — judged on the named list per market rather than on a method count.

0 — Not a payment acceptance product; customers cannot pay through it.

3 — Card payments with the major schemes, plus wallets such as Apple Pay or Google Pay.

5 — Cards and wallets plus SEPA Direct Debit and several European local methods (for example iDEAL or Wero, Bancontact, Klarna, EPS) listed by name.

8 — Broad EU coverage named per country with the countries and currencies each method serves — including methods such as BLIK, TWINT, Przelewy24, EPS and Wero — multi-currency acceptance with settlement currencies stated, and which methods support refunds and recurring charges documented per method.

10 — Coverage is documented as a matrix a merchant can plan against: every method with its countries, currencies, refund, partial-capture and recurring support, and the provider's own acquiring versus third-party routing stated per method.

Report an error

The Finance Lead

The named list is broad and concrete: bank methods including iDEAL, Wero, Bancontact, BLIK, TWINT, Przelewy24 and EPS, wallets, buy-now-pay-later brands and SEPA Direct Debit, with country groupings visible on the pricing page for several methods and multi-currency settlement offered subject to eligibility. What keeps it off the top anchors is that countries, currencies, refund and recurring support are not laid out per method as a matrix a merchant can plan against. 5 6 2

Report an error

The E-Commerce Lead

This is a named list, not just a count: BLIK, TWINT, Przelewy24, EPS, Bancontact, Bizum, Multibanco, Belfius, KBC and MB Way sit alongside cards, Apple Pay, Google Pay, PayPal and SEPA Direct Debit, and the pricing pages group methods per market — Klarna carries separate rates per country group and Wero is shown for Germany, France and Belgium with 0,32 € for domestic Netherlands, while checkout method ordering is tuned per country with A/B testing. I found no public information on a per-method matrix of currencies, refund support and recurring support; recurring is documented only as requiring SEPA Direct Debit or a credit card. 5 6 2 9

Report an error

The SaaS Founder

The named list is what I would plan expansion around: cards, wallets including Apple Pay and Google Pay, SEPA Direct Debit collected across more than 34 European countries, and bank methods like iDEAL, Wero, Bancontact, BLIK, TWINT, Przelewy24 and EPS, with buy-now-pay-later priced country by country. What holds it short of the top anchors is that refund and recurring support are not documented per method, and the settlement currency list itself is not shown. 5 6 2 1

Report an error

The Payments Engineer

Named, per-country coverage is real: bank methods from iDEAL, Bancontact, BLIK, EPS, Przelewy24 and TWINT to Wero sit alongside wallets, Klarna and other buy-now-pay-later options, plus SEPA Direct Debit, with country groupings priced separately on the public rate card. Recurring support is documented only for cards and SEPA Direct Debit, and I found no public matrix stating refund and recurring support per method or an enumerated list of settlement currencies, which keeps it off the top anchors. 5 6 7 9 2

Report an error

The Compliance Officer

Cards, wallets and SEPA Direct Debit are documented alongside a broad named list of local methods — BLIK, TWINT, Przelewy24, EPS, Wero, Bancontact, Bizum and Multibanco among them — with country groupings published for the buy-now-pay-later methods and multi-currency settlement available subject to eligibility. We found no public information on refund and recurring support documented per method, or on the list of settlement currencies itself. 5 6 2 13

Report an error

The Skeptic

The named list is broad and real: bank methods from BLIK, Przelewy24 and EPS to TWINT and iDEAL, wallets including Apple Pay and Google Pay, five buy-now-pay-later brands and SEPA Direct Debit, with country-level pricing published for Klarna, Wero, Alma, Billie, Billink and Riverty and multi-currency acceptance stated. Two gaps hold it back from the top: we found no public information stating refund and recurring support method by method — recurring is documented for cards, SEPA Direct Debit, PayPal and directdebit-mandate methods only — and the list of settlement currencies is referenced in the terms but never shown. 5 2 2 6 9 13

Report an error

Checkout, SCA & fraud

Show reasoning
How this is scored

The path from basket to authorised payment under PSD2: hosted and embedded checkout options, 3-D Secure and SCA exemption handling, fraud screening, and what the provider documents about keeping legitimate payments from failing.

0 — No checkout or payment form; the product does not take a payment to authorisation itself.

3 — A hosted payment page or payment links with 3-D Secure.

5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, and fraud screening with configurable rules.

8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, the PCI DSS scope of each integration type stated, fraud tooling with rules and risk scores exposed to the merchant, network tokens or account updater, and liability shift explained per flow.

10 — Authorisation is engineered and shown: exemption strategy documented, soft-decline retry handled, authorisation-rate reporting by method and issuer country, and a checkout the merchant can run in their own domain while staying at the lowest PCI scope.

Report an error

The Finance Lead

A hosted checkout that is optional with a custom checkout supported, 3-D Secure 2 applied dynamically with an opt-out to always-on, payments that still complete when authentication fails, and basic fraud screening plus an Acceptance & Risk service with configurable settings. We found no public information on an exemption strategy, risk scores exposed to the merchant, or authorisation-rate reporting by method. 7 8 13

Report an error

The E-Commerce Lead

The checkout is hosted with logo and pay-button colour configurable and using it is optional with a custom checkout supported, but I found no public information on a checkout that runs on my own domain. I found no public information on SCA exemption handling, per-integration PCI scope, exposed risk scores or authorisation-rate reporting, and the captured pages describe chargeback liability differently — one says 3DS2 helps avoid liability for certain fraud chargebacks, while the terms make me fully liable for chargebacks including those resulting from Dynamic 3DS. 7 8 13 13

Report an error

The SaaS Founder

I found no public information on SCA exemption handling such as low value, transaction risk analysis or merchant-initiated exemptions, network tokens, or an account updater, so the authorisation work beyond 3DS is undocumented. 7 8 13 14

Report an error

The Payments Engineer

I found no public information on SCA exemption strategy, soft-decline handling, or network tokens and account updater, so the authorisation engine stays half-documented. 7 8 13 13

Report an error

The Compliance Officer

A hosted checkout is offered and optional with a custom checkout supported, 3-D Secure 2 is applied dynamically with a documented opt-out to an Always On policy, and card transactions receive basic fraud screening plus a configurable Acceptance and Risk service. We found no public information on SCA exemptions, the PCI scope per integration type or network tokens, and liability shift is documented only as avoiding certain fraud chargebacks under 3-D Secure. 7 8 13

Report an error

The Skeptic

We found no public information on SCA exemptions — low-value, transaction risk analysis, merchant-initiated — being applied or documented, nor on network tokens, an account updater, risk scores shown to the merchant or authorisation-rate reporting; liability shift is documented only for fraud chargebacks under 3-D Secure, while the merchant remains fully liable for chargebacks generally. 7 8 13 13

Report an error

Subscriptions & recurring payments

Show reasoning
How this is scored

Charging the same customer again: card-on-file and merchant-initiated transactions, SEPA mandates, subscription logic and dunning — and whether the stored payment credentials can leave with the merchant.

0 — One-off payments only; the product stores no payment method for a later charge.

3 — Saved cards (card-on-file) charged again for repeat or recurring payments.

5 — Stored cards and SEPA Direct Debit mandates for recurring charges, merchant-initiated transactions, and subscriptions or scheduled payments with notification of failed payments.

8 — Subscription billing with trials, proration and plan changes, smart retries and dunning, card account updater, mandate management with pre-notification, and a documented process for exporting payment tokens to another provider.

10 — Recurring revenue is a first-class product: usage-based and invoice-based billing, dunning with measurable recovery, token migration in and out documented with a stated timeline and format, and recurring support stated for every local method that allows it.

Report an error

The Finance Lead

A first payment creates a customer mandate via the Mandates API, recurring charges run on SEPA Direct Debit or cards, subscriptions are spawned automatically through a Subscriptions API, and failed payments are retried up to five times once a day before cancellation. We found no public information on trials, proration, a card account updater, or a documented process for exporting payment tokens to another provider. 9 10

Report an error

The E-Commerce Lead

The mandate flow is proper: a first payment takes customer consent and creates a mandate via the Mandates API, the Subscriptions API then spawns scheduled charges automatically with create, update and cancel endpoints, variable amounts and credit top-ups are supported, and failed payments are retried up to five times, once a day, before the subscription is cancelled with the mandate revoked; recurring is included at no extra cost. For scale I found no public information on trials, proration, dunning, a card account updater, or any process for exporting my payment tokens to another provider. 9 10 2

Report an error

The SaaS Founder

Mandates created through a first payment, a Mandates API, a full Subscriptions API with update and cancel, SEPA Direct Debit and cards for merchant-initiated charges with zero-amount first payments, and failed payments retried up to five times — that is a working recurring stack, though the retry cadence is fixed rather than smart dunning with recovery numbers. We found no public information on trials, proration, a card account updater, or a documented process for exporting stored payment tokens to another provider, which is the hostage question every subscription business has to ask. 9 10 6

Report an error

The Payments Engineer

Mandates are created through a first payment and exposed via a Mandates API, the Subscriptions API schedules charges with full create, update and cancel endpoints, SEPA Direct Debit covers over 34 European countries, and failed payments retry up to five times with reason-specific cancellation codes. For a finance team the gaps are real: no trials, proration or plan-change logic documented, no account updater, no token export process, and no webhooks for subscription status changes. 9 10 6

Report an error

The Compliance Officer

Recurring charges run on customer mandates created by a first payment, with SEPA Direct Debit or card required, a Mandates API, and a Subscriptions API covering create, update, cancel and payment listing, while failed payments are retried up to five times at once a day. We found no public information on trials, proration, a card account updater or a documented process for exporting payment tokens to another provider. 9 10 6

Report an error

The Skeptic

First-payment consent creates a mandate reachable through a Mandates API, the Subscriptions API schedules, updates and cancels subscriptions, failed payments are retried up to five times once a day, and variable-amount recurring charges run via the Payments API — for cards, SEPA Direct Debit and PayPal, with card and PayPal even supporting a zero-amount first payment. We found no public information on trials, proration, dunning, a card account updater or any process for exporting payment tokens to another provider, and the documentation states plainly that webhooks for subscription status changes are not provided. 9 10 5

Report an error

Settlement, reconciliation & API

Show reasoning
How this is scored

Getting the money and knowing what it was: payout cadence and currencies, fee itemisation per transaction, reports that match a bank statement, and an API and webhooks a team can build finance processes on.

0 — No merchant reporting: the product is a payment button or link with no dashboard, report or API.

3 — A dashboard of transactions and payouts, a stated payout schedule, and CSV export.

5 — The payout schedule stated, reports or exports that link each payout to its transactions and fees, and a documented API with webhooks and a test mode.

8 — Configurable payout schedules and settlement currencies, reconciliation reports that match bank lines, accounting integrations or exports named, a versioned API with idempotency and published rate limits, and a public status page with incident history.

10 — Finance can close the month from the provider's data: interchange and scheme fees itemised per transaction, automated reconciliation to the ledger, a deprecation policy for the API, and full historical data exportable after the contract ends.

Report an error

The Finance Lead

This is where they earn their keep: settlement reports break each payout into revenue, deductions and costs including payment method fees, chargeback fees and refund fees, exportable as CSV, PDF, MT940 and CODA, backed by a Settlements API with per-transaction detail, an accounting connection via Bizcuit, test keys, and payouts generally landing in 1–3 business days over SEPA. We found no public information on configurable payout schedules, API versioning with idempotency, or per-transaction interchange itemisation. 11 12 13

Report an error

The E-Commerce Lead

Each Settlement Report breaks a payout into revenue, deductions and costs — with payment method fees, chargeback fees, refund fees and notification fees itemised — and exports come in CSV, PDF, MT940 and CODA so my finance team can match bank lines; there is a Settlements API with per-transaction detail, an accounting connection powered by Bizcuit, payouts stated as 1–3 business days via SEPA, and API rate limits visible in the dashboard. I found no public information on configurable payout schedules, API versioning or idempotency, a deprecation policy, or interchange and scheme fees itemised per transaction. 11 12 13

Report an error

The SaaS Founder

Settlement reports break each payout into revenue, deductions and costs — payment method fees, chargeback fees, refund fees — exportable as CSV, MT940 and CODA with a Settlements API for aggregated and per-transaction detail, plus a Bizcuit bank connection, bank statements and automated exports into bookkeeping tools; payouts generally land in one to three business days via SEPA. I found no public information on configurable payout schedules, API versioning and idempotency, or a status page with incident history. 11 12 13 1

Report an error

The Payments Engineer

The settlement report itemises payment-method, chargeback, refund and notification fees per payout, exports in MT940 and CODA alongside CSV and PDF, a Settlements API returns aggregated and per-transaction data, a bank connection feeds accounting software, and test keys hit the same endpoints as live. As the engineer who gets paged: no documented API versioning or idempotency keys, rate limits live only inside the dashboard, and the captured status page link gives me no incident history. 11 12 13 1

Report an error

The Compliance Officer

Each settlement report breaks a payout into revenue, deductions and costs including payment-method, chargeback, refund and notification fees, exportable as CSV, PDF, MT940 and CODA and retrievable through a Settlements API in aggregated or per-transaction form, with a Bizcuit-powered accounting connection and payouts stated at one to three business days via SEPA. Rate limits are applied and visible in the Dashboard but vary per account rather than being published, and we found no public information on configurable payout schedules. 11 12 13

Report an error

The Skeptic

Each payout comes with a Settlement Report splitting revenue, deductions and itemised costs — payment method fees, chargeback fees, refund fees, notification fees — exportable in CSV, PDF, MT940 and CODA, backed by a Settlements API that drills from aggregated totals to single transactions, a Bizcuit bank connection into accounting software, and a stated 1–3 business day SEPA payout. We found no public information on configurable payout schedules, API versioning or idempotency, and rate limits are shown per account in the dashboard rather than published; a status page is linked but incident history is not documented in what we read. 11 12 13 1

Report an error

Licence, risk & account terms

Show reasoning
How this is scored

Who holds the merchant's money under which licence, and what the contract lets the provider do on a bad day: freezes, reserves, termination, chargebacks. Scored on what the terms and the imprint state, not on reputation.

0 — The terms let the provider freeze funds or close the account at any time with no notice, reason or timeline.

3 — The regulated entity or the licensed partner behind the payments named, and a chargeback or dispute process described.

5 — The regulated entity named with its supervisor or licence type, the dispute process and chargeback fee published, and either safeguarding of merchant funds or a notice period for ordinary termination stated.

8 — Entity, supervisor, register number and passporting stated per country; safeguarding stated; reserve and rolling-hold conditions defined with limits and release timelines; freeze and termination terms with reasons and a route to appeal; PCI DSS level and attestation published.

10 — The bad day is written down: every regulated entity in the chain named with register links, reserve calculation disclosed, funds release timelines after termination committed, a documented complaint route to the supervisor, and exit terms that include handing back payment tokens and transaction history.

Report an error

The Finance Lead

Entity, supervisor and register numbers are stated for both the Dutch e-money licence and the UK entity, all customer payments land with a DNB-supervised safeguarding foundation, and PCI DSS level 1 is published. My complaint: reserve amounts rest on transaction volume and refund ratios with possible minimum and maximum amounts but no written limit or release timeline, chargeback liability sits entirely with the merchant, and we found no public information on a route to appeal a freeze or on funds-release timelines after termination beyond a five-year claim window for unclaimed funds. 4 8 13 13

Report an error

The E-Commerce Lead

The regulated chain is named and numbered: Mollie B.V. is licensed for payment services under the Dutch Financial Supervision Act, supervised by De Nederlandsche Bank under number F0038, and all customer payments are received by Stichting Mollie Payments, a safeguarding foundation also included in DNB supervision, with PCI DSS level 1 certification published. Reserve amounts may be set on transaction volume and refund ratios with possible minimum and maximum amounts, but I found no public information on reserve release timelines, passporting per country, or a chargeback fee amount, and the terms make me fully liable for chargebacks with a right to set off against my balance. 4 13 13 8

Report an error

The SaaS Founder

Mollie B.V. is licensed under the Dutch Financial Supervision Act, supervised by the Dutch central bank under register number F0038 and registered at the Amsterdam commercial register, customer funds are safeguarded through the separately supervised Stichting Mollie Payments, chargebacks can be disputed with notification and software assistance, reserves are set on transaction volume and refund ratios with possible minimum and maximum thresholds, and PCI-DSS level 1 is stated. The captured terms do not show passporting per country, reserve release timelines, a published chargeback fee amount, or a defined appeal route for freezes and termination. 13 13 4 8

Report an error

The Payments Engineer

The licence chain is written down: Mollie B.V. is a DNB-supervised e-money institution under register number F0038, all customer funds flow to Stichting Mollie Payments under the same supervision, disputes are assisted with notifications and software, and PCI DSS Level 1 is published. The bad day stays partly unwritten: reserves are set from transaction volume and refund ratios at Mollie's discretion with no limits or release timelines, set-off reaches any balance, and I found no appeal route for freezes or terminations. 4 13 13 8

Report an error

The Compliance Officer

The regulated entity is named to the standard I expect: Mollie B.V., an e-money institution licensed by De Nederlandsche Bank under register number F0038 and registered in Amsterdam under 302.04462, safeguarding customer funds through the separately supervised Stichting Mollie Payments (chamber of commerce 50205773), with PCI DSS level 1 published and a UK entity registered with the FCA under FRN 977968. Reserve amounts are tied to transaction volume and refund ratios but without defined limits or release timelines, and we found no published passporting statement per country or appeal route against account freezes. 4 13 13 8

Report an error

The Skeptic

The licence chain is properly written down: Mollie B.V. as an e-money institution under the Dutch Financial Supervision Act, DNB number F0038, Amsterdam chamber of commerce 302.04.462, funds received by the DNB-supervised Stichting Mollie Payments, PCI-DSS level 1 certification, and a UK payment-institute subsidiary at FCA FRN 977968. On a bad day the terms read less comfortingly: reserves are decided at Mollie's discretion from volume and refund ratios, with possible minimum and maximum amounts but no release timelines, the prohibited-activities list can change at any time without prior notice, unpaid invoices allow termination with immediate effect, and Mollie may set off what you owe against any balance. We found no published chargeback fee figure, no passporting statement per country, and no appeal route in the captured terms. 4 13 13 8

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Who the contracting and regulated entity is, and where transaction and cardholder data are processed and stored. Independently sourced by the sovereignty pipeline. The card schemes are US-based for every provider, so the scheme layer is not held against any one vendor; the part the vendor controls is.

0 — Contracting entity and processing of payment data both shown to be outside the EU, with no transfer safeguard stated.

3 — A named contracting entity and a privacy policy or data processing agreement; the processing location of payment data not stated or partly outside the EU.

5 — An EU contracting or regulated entity, with EU processing of core payment data stated or a subprocessor list published, and a data processing agreement offered.

8 — EU entity and EU licence, payment and cardholder data processed and stored in the EU on named infrastructure, subprocessor list published with locations, and a DPA covering the processing the provider does as processor versus as controller.

10 — Sovereign end to end and evidenced: European ownership, EU entity and licence, every processing location and subprocessor European, European rails (SEPA, Wero or national schemes) offered alongside cards, and certifications published.

Report an error

The Finance Lead

The contracting entity is Mollie B.V. on the Keizersgracht, licensed and supervised by the Dutch central bank, with a UK subsidiary under the FCA. The processing location of payment data is not stated, transfers outside the EEA are acknowledged with EU standard contractual clauses as the mechanism, and we found no public information on a data processing agreement offer or on hosting locations. 3 4 13

Report an error

The E-Commerce Lead

Contracting lands on Mollie B.V. in Amsterdam with a DNB licence, though UK customers may be contracted with the FCA-registered Mollie UK Ltd. The processing location of payment data is not stated on the pages I read; transfers outside the EEA are confirmed with EU standard contractual clauses as the safeguard, and subprocessors appear only as categories — infrastructure plus customer-service, marketing, CRM and email SaaS — with Ekata (Mastercard) named for onboarding fraud checks and no locations given. I found no public information on hosting locations or a data processing agreement covering payment processing. 3 4 13

Report an error

The SaaS Founder

The contracting entity is Dutch and licensed by the Dutch central bank, the privacy policy discloses subprocessor categories plus a named fraud-prevention processor, and EU standard contractual clauses cover transfers outside the EEA. The processing location of payment data is stated nowhere I read, and we found no public information on a data processing agreement or hosting options — for a sovereignty verdict those gaps decide it. 3 4 13

Report an error

The Payments Engineer

The contracting and regulated entity is Dutch — Amsterdam address, DNB e-money licence F0038 — and the privacy policy names subprocessor categories including Ekata for onboarding fraud checks. Payment-data residency is not stated anywhere I read, transfers outside the EEA are acknowledged under EU standard contractual clauses, Mollie acts as processor only for its invoicing product, and I found no public information on a data processing agreement. 4 3 13

Report an error

The Compliance Officer

The contracting and regulated entity is Dutch and DNB-licensed, though UK customers may be contracted with Mollie UK Ltd instead. Where transaction and cardholder data are processed is not stated on the captured pages; transfers outside the EEA are acknowledged with standard contractual clauses, subprocessor disclosure extends only to categories plus Ekata of Mastercard without locations, and Mollie documents acting as controller for its own processing while acting as processor only for the invoicing product — we found no public information on a data processing agreement covering the payments processing itself. 3 4 13

Report an error

The Skeptic

The contracting and regulated entity is European — Mollie B.V., Keizersgracht 126, Amsterdam, licensed and supervised by De Nederlandsche Bank — but the privacy policy itself states that transfers outside the EEA take place under EU standard contractual clauses, and we found no public information on where payment and cardholder data are processed or stored. Subprocessors are disclosed only as categories — infrastructure, customer service, marketing, CRM, email — plus one named fraud-prevention processor without locations, Mollie describes itself as data processor only for its invoicing product, and UK customers may additionally contract with Mollie UK Ltd under the FCA. 14 3 4

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a merchant can compute the effective fee for their own mix of cards, countries and methods — including cross-border and currency conversion markups, chargebacks, refunds, payouts and monthly fees — from public pages alone.

0 — No public prices at all; every rate is a sales conversation.

3 — A headline rate published for one method or card type, or a "from" percentage.

5 — Rates published per main method with domestic and international cards distinguished, and any monthly or plan fee stated with its billing period; ancillary fees (currency conversion, chargeback, payout) may still be missing or "on request".

8 — Every method priced publicly, cross-border and currency conversion markups stated, chargeback, refund and payout fees listed, minimum monthly fees and contract term given, and whether the model is blended or interchange++ said plainly.

10 — Complete fee computability: the effective rate derivable for a given volume, card mix and country mix — interchange++ with the markup published or a blended rate with every exception listed — plus volume tiers, reserves and every ancillary fee on a public page.

Report an error

The Finance Lead

Per-method rates are public with EEA consumer, EEA commercial and non-EEA cards distinguished, the currency conversion markup of two per cent and the one per cent foreign-currency payout fee are stated, payout tiers are given, monthly plans are priced, and it is said plainly that the default model is blended with IC++ available from a monthly volume of 100,000 € — with no minimum fees or fixed terms. The chargeback fee amount and volume-tier rates are not publicly listed, so the last bit of computability stays with sales. 2 2 13 2

Report an error

The E-Commerce Lead

I can nearly compute my own invoice from public pages: cards are split into consumer, commercial and non-EEA rates (Mastercard EEA consumer cards at 1,80 % + 0,25 €, non-EEA cards at 3,25 % + 0,25 €), local methods each carry a rate from iDEAL | Wero at 0,42 € to BLIK at 1,60 % + 0,25 €, Klarna and Wero are priced per country group, and the two per cent currency markup, the 1 % foreign-currency payout fee and five free payouts a month are all stated, with no monthly fee, no minimum and no fixed term on the standard plan and IC++ available from a 100.000 € monthly volume. Rates exclude VAT. The gaps: I found no public chargeback fee, volume rates are individual rather than published tiers, and PayPal is quoted as "PayPal-Gebühren + 0,10 €", which I cannot compute from Mollie's pages. 2 1 13 2 2

Report an error

The SaaS Founder

Per-method, per-country and per-card-type pricing is public: EEA consumer cards at 1.80% + €0.25 against non-EEA cards at 3.25% + €0.25, iDEAL and Wero at €0.42, SEPA Direct Debit at €0.35, Klarna priced per country group, a 2% currency conversion markup also applied to refunds and chargebacks, 1% foreign-currency payouts, five free payouts a month, no monthly fee on pay-as-you-go with IC++ available from €100,000 monthly volume, and no minimum fees or fixed contract terms. A buyer can genuinely compute their effective rate; the only gap I found is a published chargeback fee amount. 2 2 2 13 2

Report an error

The Payments Engineer

Nearly everything is public: per-method rates with EEA consumer, commercial and non-EEA cards split out, a 2 percent conversion and refund markup, payout pricing with a free tier, POS plan pricing with terminal costs, and interchange++ pricing offered from a monthly volume of 100.000 €. A chargeback fee figure is the one line item I could not find in the captured pages, and the standard model is not plainly labelled blended versus interchange++. 2 2 13 13 2

Report an error

The Compliance Officer

Rates are published per method including country-grouped buy-now-pay-later pricing and card tiers split into EEA consumer, EEA commercial and non-EEA, with a two per cent conversion markup stated for payments, refunds and chargebacks, payout fees and free tiers, plan fees with no minimums or fixed terms, and interchange++ named for the volume tier. We found no published chargeback fee figure, and the PayPal rate is given only as PayPal's fees plus €0.10. 2 13 2 2

Report an error

The Skeptic

Rates are published per method to the cent — iDEAL | Wero 0,42 €, BLIK 1,60 % + 0,25 €, TWINT 2,30 % + 0,25 €, Przelewy24 2,20 % + 0,25 € — with cards tiered into EEA consumer 1,80 % + 0,25 €, EEA commercial 2,90 % + 0,25 € and non-EEA 3,25 % + 0,25 €, a two per cent currency conversion markup, 1 % per foreign-currency payout, 0,25 € per payout after five free ones a month, and no minimum fees or fixed terms. What we could not find: a chargeback fee figure — the fee appears only as a named cost category — Apple Pay priced only by the underlying card, PayPal only as PayPal-Gebühren + 0,10 €, and IC++ pricing available solely as an individual quote from 100.000 € volume. 2 2 13 14 1

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Mollie

Is Mollie European?

Yes. whats-best.ai classifies Mollie as EU-Made. Its vendor, Mollie B.V., is incorporated in the Netherlands, per the vendor’s page captured 16 Nov 2026.

Where does Mollie store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does Mollie have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to Mollie?

As of 18 Nov 2026, the panel rates Novalnet (3.5/5), PayPal (3.5/5) and Adyen (3/5) highest among the other 45 Payment products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Novalnet (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Mollie alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (16)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.mollie.com Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
  2. 2 Pricing page www.mollie.com Checked 16 Nov 2026 +3 earlier captures: 26 Oct 2026, 19 Oct 2026, 22 Sep 2026 Details →
  3. 3 Privacy policy www.mollie.com Checked 16 Nov 2026 Details →
  4. 4 Legal notice www.mollie.com Checked 16 Nov 2026 Details →
  5. 5 Payment methods & local coverage — found from sitemap docs.mollie.com Checked 16 Nov 2026 Details →
  6. 6 Payment methods & local coverage — found from sitemap www.mollie.com Checked 16 Nov 2026 Details →
  7. 7 Checkout, SCA & fraud — found from sitemap docs.mollie.com Checked 16 Nov 2026 Details →
  8. 8 Checkout, SCA & fraud — found from sitemap www.mollie.com Checked 16 Nov 2026 Details →
  9. 9 Subscriptions & recurring payments — found from sitemap docs.mollie.com Checked 16 Nov 2026 Details →
  10. 10 Subscriptions & recurring payments — found from sitemap docs.mollie.com Checked 16 Nov 2026 Details →
  11. 11 Settlement, reconciliation & API — found from sitemap docs.mollie.com Checked 16 Nov 2026 Details →
  12. 12 Settlement, reconciliation & API — found from sitemap docs.mollie.com Checked 16 Nov 2026 Details →
  13. 13 Licence, risk & account terms — found from sitemap www.mollie.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  14. 14 Licence, risk & account terms — found from sitemap www.mollie.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  15. 15 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 1 Nov 2026 Details →
  16. 16 Structured-data backfill: markup only, no text or screenshot www.mollie.com Checked 8 Nov 2026 Details →