If you sell into the Netherlands, Belgium or Germany, your customers expect to pay with iDEAL, Bancontact and SEPA direct debit — not a plain card form. ERPNext ships with a generic Payment Gateway framework and integrations for a handful of processors, but Mollie is not one of them out of the box, and the local European methods that actually drive checkout conversion have no native home. Merchants end up bolting on manual bank reconciliation, chasing SEPA mandates in spreadsheets, and reconciling refunds by hand — exactly the work ERPNext is supposed to remove.

ECOSIRE builds Mollie Payments for ERPNext as a first-class Frappe app: its own module with a Mollie Settings single DocType for API keys, profile and webhook configuration, a Mollie Payment DocType that mirrors each Mollie payment and links back to the source Payment Request, Sales Invoice or Sales Order, and role-scoped permissions so only authorised accounts users touch live credentials. Checkout is wired through the Mollie Orders and Payments APIs — customers are redirected to Mollie's hosted checkout, choose iDEAL, Bancontact, SEPA, Sofort, cards, PayPal or Apple Pay, and return to a status page driven by the real payment state. We register the gateway against ERPNext's Payment Gateway and Payment Gateway Account so it appears anywhere the framework does: web checkout, Payment Request emails and the customer portal.

The connector is event-driven, not poll-and-pray. A whitelisted, signature-verified webhook endpoint receives Mollie status callbacks and, via hooks.py doc events and background jobs, marks the linked Payment Request paid, creates the Payment Entry against the right bank/clearing account, and reconciles it — no manual matching. Recurring SEPA is handled properly through Mollie customers and mandates so subscription and installment billing can charge stored mandates without re-collecting bank details. Refunds initiated in ERPNext call the Mollie refund API and write back status; chargebacks and reversals are synced so your ledger reflects Mollie reality. A scheduler event runs a daily safety-net reconciliation to catch any webhook Mollie couldn't deliver, and client scripts surface payment status and a manual "sync from Mollie" action directly on the linked documents.

Because this is build-to-order, nothing is guessed. We start with a short scoping call to confirm your Mollie account setup, which documents trigger payment (Sales Order vs Sales Invoice vs portal), which methods and currencies you need, whether recurring SEPA is in scope, and how you reconcile today. We build against your Frappe/ERPNext v15 or v16 version, test on a staging site with your real chart-of-accounts mapping, run UAT with you, then install on production with a rollback plan. Typical delivery is one working week from confirmed scope, and you get the full Git repository so the app is yours to keep, extend and audit.