Can I vibe code Mollie?
mollie.com · payments · usage-based · transaction-fee
The verdict
NOT REALLY — THE UI ISN'T THE MOAT
Mollie charges pay-as-you-go per-transaction fees (such as 1.80% + €0.25 for EEA card transactions, €0.32 for iDEAL, and €0.35 for SEPA Direct Debit) with no base monthly subscription fee for online checkout. You are not paying Mollie for software user interfaces; you are paying for their Dutch Central Bank (DNB) payment institution license, direct settlement rails, PCI-DSS Level 1 infrastructure, and localized acquirer integrations for European payment methods like iDEAL, Bancontact, and TWINT. While you can write a software wrapper using LLMs to manage payment links or standard card checkouts in a weekend, replicating Mollie's actual service requires legal money transmitter status, ring-fenced bank accounts, direct SEPA scheme access, and card network sponsorship. Rebuilding Mollie as a software system is trivial; replacing Mollie as a regulated financial institution and acquirer is impossible for an engineering team.
- Replaces
- $165/mo
- MVP build time
- 2-3 weeks
- Full replacement
- 18-36 months
- Verdict
- NOT REALLY
What it really costs
| Standard (Pay as you go) | free / quote | Pay per successful transaction, no contracts or monthly fees |
| Pro (In-person POS) | $22/mo | Lower terminal transaction rates, includes 1 hardware terminal license |
| Volume Pricing | free / quote | For businesses processing over €100,000/month |
No monthly base fee for online payments. Pay per transaction (e.g., EEA Visa/Mastercard 1.80% + €0.25). POS terminal plan available at €20/mo.
- Captured
- 2026-08-04 (3 days ago)
- Verified by
- human
- Source
- mollie.com
Assumptions: No monthly base fee for online payments. Pay per transaction (e.g., EEA Visa/Mastercard 1.80% + €0.25). POS terminal plan available at €20/mo.
The one-shot build prompt
Build a localized payment orchestration proxy and custom checkout service using Node.js, TypeScript, and Fastify. SYSTEM ARCHITECTURE & CORE ENTITIES: 1. Define PostgreSQL schema for: - Merchants: id, business_name, api_key_hash, webhook_url, status. - PaymentIntents: id, merchant_id, amount_cents, currency, status (requires_payment_method, processing, succeeded, failed, canceled), payment_method_type, client_secret, metadata_json. - Refunds: id, payment_intent_id, amount_cents, status, reason. - Customers: id, merchant_id, email, name, mandate_id (for SEPA Direct Debit). INTEGRATIONS & GATEWAY ROUTING: 1. Implement a unified strategy pattern for PSP execution adapters: - Stripe Adapter: Map payment intents to Stripe PaymentIntents API. - Adyen Adapter: Map payment intents to Adyen /payments API. - Manual SEPA Bank Transfer Adapter: Generate unique IBAN reference codes (virtual IBAN mock) and track pending status. 2. Build an APM selection rule engine based on request currency and country code: - If currency = EUR and country = NL -> prioritize iDEAL flow (mock redirect URL generation). - If currency = EUR and country = BE -> prioritize Bancontact flow. - If currency = EUR and mandate present -> process SEPA Direct Debit. - Fall back to primary credit card adapter (Stripe/Adyen). FAILURE MODES & HANDLING: 1. Webhook Idempotency: Store processed webhook event IDs in Redis with a 72-hour TTL to prevent double-fulfillment on duplicate notifications. 2. Signature Verification: Implement HMAC-SHA256 signature calculation and verification on incoming and outgoing webhook payloads. 3. Network Timeout Resilience: Use exponential backoff circuit breakers for external PSP API requests. If gateway timeouts occur, fail gracefully without mutating order state to 'failed' prematurely. 4. Transaction State Reconciliation: Build a background worker using BullMQ that polls unconfirmed transactions every 15 minutes against the underlying PSP status endpoints. OUT OF SCOPE: - Physical POS terminal communications or Tap to Pay hardware protocols. - Regulatory KYC submission forms and identity document verification pipelines. - Direct credit card processing without an underlying upstream PSP (no raw PAN handling or card vaulting). - Banking license compliance or legal escrow ledgering.
$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs
Scorecard
What you can actually replace
- ✓Hosted checkout payment pages and payment links.
- ✓Merchant dashboard UI for manual refunds, customer list, and transaction history.
- ✓Basic recurring billing schedules and subscription state management.
- ✓Webhook dispatch engine with signature verification.
- ✓Multi-currency payment payload normalization.
What you lose
- ×Access to De Nederlandsche Bank payment institution licensing under PSD2/PSD3 regulations.
- ×Direct settlement contracts with European acquirers, card schemes, and local APMs.
- ×Managed chargeback defense mechanisms and automated fraud detection systems.
- ×Out-of-the-box support for physical hardware POS terminals and Tap to Pay frameworks.
- ×Automated cross-border SEPA clearing and multi-currency payout reconciliation.
- ×Pre-built plugins for Shopify, WooCommerce, Magento, and BigCommerce.
Why people still pay — the real moats
Moats
- — Licensed European Payment Institution (PI) status regulated by De Nederlandsche Bank (DNB).
- — Direct acquirer access to local payment schemes (iDEAL, Bancontact, TWINT, Cartes Bancaires, Wero).
- — Capital reserves, banking partnerships, and ring-fenced safeguarding accounts (Stichting Derdengelden).
- — Hardware supply chain and distribution network for physical POS terminals and Tap-to-Pay provisioning.
Hard parts
- — Achieving low-latency execution and high availability across distributed regional datacenters under peak traffic.
- — Ingesting, parsing, and normalizing heterogeneous transaction settlement files (CAMT, MT940, CSV) across dozens of acquirers.
- — Real-time fraud detection scoring and 3D Secure (3DS2) authentication challenge orchestration.
- — Building strict event-driven state machines for multi-step payment methods like SEPA Direct Debit with 8-week chargeback windows.
- — Maintaining PCI-DSS Level 1 compliance, key management, and secure tokenization vaults.
- — Managing multi-jurisdictional AML/KYC verifications, sanctions screening, and suspicious activity reporting (SAR).
- — Handling bank settlement disputes, chargebacks, SEPA R-transactions, and clawbacks from merchant accounts.
- — Sustaining capital reserves and safeguarding client funds in accordance with European banking regulations.
Network effects you cannot generate
- — Local consumer familiarity with Mollie-hosted checkout pages across European e-commerce.
- — Pre-established bank acquirer trust and volume-discount routing with European card networks and APM schemes.
Build this instead
Unified Local PSP Orchestrator
Build an open-source, self-hosted proxy that standardizes payment webhooks and payment intent APIs across Stripe, Adyen, and PayPal for unified multi-PSP routing without vendor lock-in.
Local APM Smart Checkout Widget
A localized checkout frontend engine that dynamically injects region-specific alternative payment methods (iDEAL, Bancontact, TWINT, Blik) based on client IP and browser locale while routing transactions to low-cost regional acquirers.
SEPA & Bank Settlement Reconciler
An open-source transaction reconciliation parser that ingests bank statements (MT940, CAMT.053) and PSP settlement reports to match SEPA Direct Debits and manual bank transfers to e-commerce order IDs.
Prior art — do not start from zero
Open source alternatives to Mollie
Self-hostable projects that cover most of the same ground. Free licence, your infrastructure, your on-call.
Have you actually replaced it?
Related products in this category
Global payment processor and acquiring bank with native omnichannel settlement, 200+ local payment methods, and automated interchange routing.
usage-based
A global Buy Now Pay Later (BNPL) network and consumer bank offering instant credit underwriting, Pay-in-4, and installment loans at checkout.
$5/mo
A global two-sided payment network providing online checkout, wallet storage, cross-border remittances, and buyer protection.
usage-based
FAQ
+Can I really replace Mollie with an AI-generated app?
NOT REALLY — MOLLIE IS A LICENSED FINANCIAL INSTITUTION, NOT A UI. You cannot replace Mollie with an AI prompt because Mollie is an authorized European payment institution with regulated money movement rails. Writing the software layer for checkout widgets or payment orchestration is simple, but software alone cannot process card transactions, settle iDEAL payments, or hold merchant funds. An MVP takes roughly 2-3 weeks; matching the product properly is closer to 18-36 months.
+How long does it take to rebuild Mollie?
A usable internal version: 2-3 weeks. A version you would sell or bet a business on: 18-36 months, mostly spent on achieving low-latency execution and high availability across distributed regional datacenters under peak traffic..
+What do you actually lose by leaving Mollie?
Access to De Nederlandsche Bank payment institution licensing under PSD2/PSD3 regulations. Direct settlement contracts with European acquirers, card schemes, and local APMs. Managed chargeback defense mechanisms and automated fraud detection systems.
+Is it legal to build a Mollie alternative?
Building a competing product with your own code is normal competition. Copying their code, trademarks, brand assets or scraping their platform is not. Use the prompt to build your own implementation of common features.
Written by Andrea Saccà — 18 years in the Magento ecosystem. Last reviewed 2026-08-04.
Scores are computed, not typed. Read the methodology.
One e-commerce SaaS teardown every week.
Honest verdicts, build prompts and overlooked vertical SaaS opportunities. No tracking pixels, no drip sequence, unsubscribe in one click.
free forever · no third-party tracking · the prompts stay public