What is Mollie for Magento?

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.

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.

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.

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.

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.

Yes, Mollie supports a separate profile_id per website scope inside Magento. Configure the API key at default scope (one Mollie account) and override the profile_id 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.