Chat on WhatsApp
Toggle Nav
My Cart
Magento glossary

What is Mollie for Magento ?

Mollie for Magento is the official mollie/magento2 module (MIT-licensed, free, maintained by Mollie’s own team in Amsterdam) that adds Mollie Payments to Magento 2 checkout. It supports iDEAL (the #1 method in the Netherlands at 70%+ share), Bancontact, SEPA Direct Debit, Cards, Apple Pay, Google Pay, Klarna Pay-Later / Pay-Now, PayPal, Trustly, Sofort, EPS, P24, and BLIK. Per-method flat pricing (iDEAL €0.29 + 1.8%; cards ~1.8% + €0.25) and ~10-minute self-service onboarding make it the default PSP for Dutch, Belgian, German, and Austrian Magento stores.

Need Mollie + iDEAL setup? How it works

Written by Kishan Savaliya — Adobe Certified Magento & Hyvä developer, 8 years on platform

How it works

Five steps from composer install to live checkout

Mollie is not a black-box PSP — its Magento module is open-source and well-documented. Here is the wiring, end to end.

  1. 01

    Composer-install the official Mollie module

    Run composer require mollie/magento2 from the Magento project root. The package is published under the MIT licence on Packagist, maintained directly by Mollie’s engineering team in Amsterdam, and tested against Magento Open Source and Adobe Commerce 2.4.4 – 2.4.7. There is no marketplace listing to buy — pull it straight from Composer, no licence key required.

  2. 02

    Run setup:upgrade and flush cache

    Run bin/magento setup:upgrade --keep-generated && bin/magento cache:flush to register the new module, install its database schema (Mollie order ID mapping, transaction log, refund tracking), and clear the config / layout / block_html caches so the admin Stores » Configuration tree picks up the new Mollie node.

  3. 03

    Sign up at mollie.com and fetch your API key

    Self-service signup at mollie.com takes around 10 minutes — comparable to Stripe’s onboarding DX and much faster than Adyen’s enterprise contract path. KYC review is typically same-day. Once approved, the Mollie dashboard issues two API keys: a test_ key for sandbox traffic and a live_ key for production. Both are scoped to the merchant profile.

  4. 04

    Configure Mollie in admin and enable methods

    Navigate to Stores » Configuration » Sales » Payment Methods » Mollie. Paste the API key, set the profile / website scope, then enable individual payment methods one by one — iDEAL, Bancontact, SEPA Direct Debit, Cards (Visa / Master / Amex), Apple Pay, Google Pay, Klarna Pay-Later / Pay-Now, PayPal, Trustly, Sofort, EPS, P24, BLIK. Each method can be restricted by country, currency, customer group, and order total.

  5. 05

    Checkout renders methods; Mollie webhook closes the loop

    At checkout the customer sees the enabled method list and picks one (for example iDEAL → bank issuer dropdown). The shopper is redirected to their bank or a Mollie-hosted payment page, authorises the charge, and is bounced back to the storefront thank-you page. In parallel, Mollie pings /mollie/checkout/webhook on your store; the module verifies the call and updates the Magento order state (pending → processing) regardless of whether the customer landed back on the return URL.

When to use

Four situations where Mollie is the obvious answer

Mollie is not the right PSP for every Magento store, but in 2026 these four scenarios are unambiguous wins.

  • Dutch, Belgian, German, or Austrian stores

    Mollie is the regional default PSP across the Benelux + DACH. In the Netherlands, iDEAL accounts for 70%+ of online checkout share — offering a store without iDEAL is effectively a non-starter. Mollie is the cleanest path to iDEAL because the bank-issuer dropdown, redirect flow, and webhook are all native. Bancontact is the same story in Belgium (~50% share). For NL / BE / DE / AT stores, picking Mollie is rarely the wrong call.

  • D2C brands wanting one-click multi-method support

    Mollie ships every relevant European method behind a single contract and a single admin screen: BNPL via Klarna Pay-Later / Pay-Now, cards (Visa / Master / Amex), Apple Pay, Google Pay, PayPal, plus bank-direct methods (iDEAL, Bancontact, Trustly, Sofort, EPS, P24, BLIK). For a D2C brand that wants to add Klarna BNPL and Apple Pay this quarter without four separate PSP integrations, Mollie collapses the work to one module and one settlement account.

  • Stores wanting per-method pricing transparency

    Mollie publishes a flat, per-method rate card on the website: iDEAL is €0.29 + 1.8%, cards are ~1.8% + €0.25, SEPA Direct Debit is €0.25, Klarna sits at ~2.99% + €0.39. No blended «2.9% + 30¢» that hides the cheap methods behind the expensive ones. For finance teams modelling unit economics by method, this transparency is the main reason to pick Mollie over Stripe.

  • Multi-store Magento across multiple countries

    Mollie supports a separate profile_id per website scope, which means a single Magento install running NL / BE / DE / FR storefronts can route each store’s traffic to its own Mollie profile — separate settlement accounts, separate VAT registration, separate method enablement, separate dispute queues. Configure the API key at default scope and override profile_id at website scope. Adyen does the same with merchant accounts; Mollie does it with one fewer hop.

Common mistakes

Three Mollie misconfigs that hurt conversion

Every Mollie integration audit I have run on a live Magento store has hit at least one of these three. Audit your admin config and webhook log for them today.

  • Enabling iDEAL without the bank-issuer dropdown

    iDEAL is a bank-direct method — the buyer picks their bank (ABN AMRO, ING, Rabobank, etc.) before being redirected, so the bank-issuer dropdown is part of the iDEAL UX, not optional chrome. The Mollie module has a show_issuers setting in admin (Payment Methods » iDEAL » Show Issuers). Leave it on. Turning it off forces the buyer to pick a bank on a Mollie-hosted page after redirect, which adds an extra click and tanks conversion by 5 – 10% on a Dutch storefront.

  • Not whitelisting the Mollie webhook in your firewall

    Mollie pings /mollie/checkout/webhook after every payment to confirm or fail the order — the customer return URL is best-effort, the webhook is the source of truth. If your WAF / Cloudflare / nginx geo-block rules drop Mollie’s callback IPs, the webhook fails silently and orders sit in «pending_payment» forever. Always whitelist Mollie’s documented webhook IP range and tail var/log/mollie.log in staging to confirm webhook delivery before going live.

  • Confusing Klarna-via-Mollie with direct Klarna

    Mollie resells Klarna Pay-Later / Pay-Now under its own contract — convenient because you get Klarna with one signup, but Mollie applies a fixed pricing markup over Klarna’s direct merchant rate. For stores under ~€50k/month of BNPL volume the markup is rounding error; for high-volume BNPL merchants (~€500k/month+), going direct with Klarna’s own Magento module is meaningfully cheaper. Model the all-in cost on your last 12 months of BNPL volume before defaulting to Mollie’s Klarna passthrough.

Related concepts

Five neighbour concepts most readers want to look at next. Click through for the full deep-dive.

FAQ

Mollie for Magento — frequently asked questions

  • Mollie vs Adyen for Magento — when do you pick which?
    Same country (Amsterdam), different segment. Mollie targets SMB and mid-market: self-service signup in 10 minutes, per-method flat pricing on the public website, MIT-licensed Magento module pulled from Composer, no minimum volume. Adyen targets enterprise: ~€100M+ GMV merchants, negotiated interchange-plus pricing, dedicated implementation manager, sales-led onboarding that takes weeks. If you can sign up with a credit card and an email address, you want Mollie. If your finance team is negotiating interchange+ rates with a named account manager, you want Adyen. Most Magento stores in Europe (sub-€50M GMV) belong on Mollie.
  • Mollie vs Stripe for European stores?
    Both work, the decision turns on three factors. (1) Geography: Mollie wins decisively in NL / BE / DE / AT because iDEAL and Bancontact are first-class methods with proper bank-issuer dropdowns; Stripe supports them but the UX is bolted on. Stripe wins in UK / FR / IT / ES where cards dominate. (2) Pricing model: Mollie publishes per-method flat rates (iDEAL €0.29 + 1.8%); Stripe charges a blended ~1.5% + €0.25 on EU cards. For an iDEAL-heavy mix, Mollie is cheaper; for a cards-only mix, Stripe is cheaper. (3) Developer DX: Stripe’s API and docs are still the industry benchmark, but Mollie’s Magento module is genuinely well-built and Mollie-maintained, so the integration gap is smaller than it used to be.
  • What is iDEAL and why is it mandatory in the Netherlands?
    iDEAL is a Dutch bank-direct payment method launched in 2005 — the buyer picks their bank from a dropdown at checkout, gets redirected into their bank’s online banking environment, authorises the payment with their normal banking 2FA, and is bounced back to the merchant. It is owned by the Dutch banks collectively (Currence is the scheme operator). As of 2026, iDEAL accounts for ~70% of all e-commerce transactions in the Netherlands. It is not literally mandatory by law, but offering a Dutch storefront without iDEAL effectively means refusing 70% of buyers’ preferred method — conversion craters. Mollie is the cleanest way to enable iDEAL on Magento because the bank-issuer dropdown, redirect, and webhook are native.
  • Can I get Klarna BNPL through Mollie?
    Yes — Mollie resells Klarna Pay-Later (Pay in 30 days), Pay-Now, and Pay in 3 / Pay in 4 under its own merchant contract. Enable Klarna inside the Mollie admin tab and it surfaces at checkout alongside the other methods. Pros: one signup, one settlement account, one dispute queue across all methods. Cons: Mollie applies a fixed pricing markup over Klarna’s direct merchant rate (Mollie’s Klarna sits at ~2.99% + €0.39 vs Klarna direct at ~2.49% + €0.30 depending on volume tier). For sub-€50k/month BNPL volume the markup is negligible. For €500k/month+ BNPL volume, integrate Klarna directly via its own Magento module and keep Mollie for the rest.
  • Does Hyvä work with Mollie for Magento?
    Yes — Mollie’s 2.x line ships Hyvä Checkout compatibility. The Mollie module exposes a checkout step component that works against both the legacy Luma / KnockoutJS checkout and the Hyvä Checkout Alpine.js-based stack. For the iDEAL bank-issuer dropdown specifically there is a Hyvä-flavoured template override that renders the dropdown as a native Alpine select rather than the Luma Knockout binding. Confirm against the module changelog before pinning a version — Hyvä Checkout support landed in mollie/magento2 v2.30 and has improved with each minor since. Setup is the standard Hyvä compatibility module install pattern; no custom integration work needed for the common case.
  • Multi-store Magento — can each store have its own Mollie profile?
    Yes — Mollie supports a separate <code>profile_id</code> per website scope inside Magento. Configure the API key at default scope (one Mollie account) and override the <code>profile_id</code> at website scope for each storefront (NL profile / BE profile / DE profile). Each Mollie profile carries its own settlement bank account, VAT registration, method enablement matrix, dispute queue, and webhook URL. This is the standard pattern for a Magento install running multiple country storefronts off one codebase, and it is one of the reasons Mollie beats single-profile PSPs for multi-country setups. The website-scope override lives at Stores » Configuration » Sales » Payment Methods » Mollie » General » Profile ID; remember to switch the configuration scope dropdown to the target website before saving.
Mollie audit

Want a Mollie integration audit on your Magento store?

Send your storefront URL — I will audit your Mollie module version, method enablement, iDEAL issuer dropdown, webhook delivery, and per-website profile setup, then reply with a written fix plan, fixed-price quote, and earliest start date. 24-business-hour turnaround.

Get a Mollie audit Hire me directly