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 Payments Engineer

Weighted verdict

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.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Payments Engineer

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

Payment methods & local coverage

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

Checkout, SCA & fraud

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

Subscriptions & recurring payments

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

Settlement, reconciliation & API

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

Licence, risk & account terms

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

European sovereignty

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

Pricing transparency

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

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 →