Mollie review

Mollie is a vendor-hosted payments and financial platform, not a library, CLI or self-hosted server. It sits between a business’s checkout or point-of-sale flow and payment methods, with a dashboard for managing transactions and related financial work. Mollie says one integration can accept 38 payment methods.

The platform extends beyond payment acceptance: its products include in-person payments, subscriptions, funding, reconciliation, fraud prevention, business accounts, invoicing and payment links. That makes it a potential shared provider for checkout, recurring collection and some back-office payment tasks, rather than a single-purpose card gateway. The dashboard covers refunds, chargebacks and failed payments, and business accounts include IBAN payments and team cards. This breadth may reduce the number of providers a business operates, but it also places more payment and cash-flow operations with one vendor. Before adopting it, map which parts of your existing stack Mollie would replace and which remain separate.

Mollie describes online payments as accepting 38 payment methods “with one integration,” but the homepage does not name an API style, protocol, SDK, programming language, CLI or webhook interface. That leaves important implementation questions for the developer docs: confirm the API protocol, SDK availability for your language, webhook event model, authentication approach, sandbox workflow and payment-method-specific behavior before choosing an integration path.

The product surface includes Checkout, Payment Links, Invoicing and Recurring, alongside in-person payments. For teams building custom checkout or subscription flows, check which operations are available through the integration and which are handled in Mollie’s dashboard. The dashboard also supports refunds, chargeback challenges and failed-payment recovery. Mollie presents team roles for developers, finance, support and admins, with separate logins. That can help separate operational access, but it is not a substitute for verifying API permissions and production credential controls in the vendor’s docs. Confirm supported plugins or commerce integrations with Mollie if your stack depends on them.

Standard online pricing starts at €0 per month, with no minimum costs or lock-in contract. That is not free processing: EEA consumer cards cost 1.80% + €0.25 per successful transaction, and EEA commercial cards cost 2.90% + €0.25. Payment Links, Invoicing, Checkout and Recurring are included; fees vary by payment method, and UK rates are listed in GBP.

For in-person payments, Pay as you go costs €0 per month and lists domestic consumer cards at 1.20%, other consumer cards at 1.80% and commercial cards at 2.90%. Pro costs €20 per month for businesses with monthly volumes over €1,900; one terminal is included, and each additional Pro terminal costs €20 per month. Volume pricing is custom for volumes over €100,000.

Business accounts cost €9 per month after 12 months free, with five accounts and 100 outgoing transfers per month included. Additional transfers cost €0.20 each. Terminals cost €95 or €350 depending on model.

Mollie is presented as a hosted payments platform, not as an open-source library or server that you can deploy yourself. The vendor's site does not name an open-source licence or self-hosting option; treat Mollie as vendor-hosted and ask the company about data access, retention and export before signing up.

Moving payment processing can involve more than switching API calls. A commenter on r/PaymentProcessing says token-vault moves can incur a charge, while another points out that migration support and what can be ported are worth checking. That is user-reported experience, not a published Mollie migration policy. Ask Mollie and your current provider which customer records, payment tokens and subscription details can move, what the migration costs, and how long it takes. Confirm that you can export the transaction and customer data your finance and support systems need.

Before routing production traffic, ask Mollie for its API rate limits, uptime commitments, incident process and support escalation path. The vendor does not publish rate-limit figures or uptime commitments on its public product page. Confirm how payment failures, delayed notifications, refunds and chargebacks appear in your integration, and test how your application handles retries and reconciliation. Ask what security and compliance responsibilities remain with your team.

Reddit reports are anecdotal, but they raise operational questions worth resolving. One commenter says their account remained in verification for more than 40 days without a support response. A separate r/smallbusiness poster says Mollie closed their business account after an internal review and that a balance remained unpaid; this is the poster’s account, not an independently verified finding. Ask about account reviews, reserve or payout holds, dispute processes and access to undisputed balances before processing material volume. Keep reconciliation records and a contingency plan for switching providers.