A Mollie payment gateway built as a proper Frappe app for ERPNext, bringing iDEAL, Bancontact, SEPA, Sofort, cards, PayPal and Apple Pay into your quotation-to-payment flow. ECOSIRE scopes, builds, installs and supports it for your v15/v16 instance. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A Mollie payment gateway built as a proper Frappe app for ERPNext, bringing iDEAL, Bancontact, SEPA, Sofort, cards, PayPal and Apple Pay into your quotation-to-payment flow. ECOSIRE scopes, builds, installs and supports it for your v15/v16 instance.
Sem pagamento agora. Isto envia um pedido de orçamento à nossa equipe — responderemos por e-mail com preços e próximos passos.
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.
Registers a native ERPNext `Payment Gateway` and `Payment Gateway Account`, so Mollie appears in web checkout, Payment Requests and the customer portal
iDEAL, Bancontact, SEPA Direct Debit and Sofort exposed as first-class methods via the Mollie Orders and Payments APIs
Cards, PayPal and Apple Pay routed through the same Mollie connector with no separate integration
`Mollie Settings` single DocType for API keys, profile ID, webhook URL, method allowlist and live/test toggle, with keys stored via Frappe's encrypted field handling
`Mollie Payment` DocType mirroring each Mollie transaction and linking back to the source Payment Request, Sales Invoice or Sales Order
Signature-verified, whitelisted webhook endpoint that processes Mollie status callbacks idempotently
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 2 to 4 weeks from confirmed scope, and you get the full Git repository so the app is yours to keep, extend and audit.
Runs an online store where iDEAL and Bancontact are the default consumer payment methods and needs them wired into ERPNext checkout with automatic invoice reconciliation, not manual bank matching.
Bills recurring plans over SEPA Direct Debit and needs Mollie mandates managed inside ERPNext so renewals charge automatically without re-collecting bank details each cycle.
Wants a clean, documented Frappe app with proper DocTypes, hooks and whitelisted methods they can maintain and extend, rather than a fragile custom script glued into the site.
Cares that every Mollie payment, refund and chargeback lands correctly in the ledger against the right accounts, with a daily reconciliation safety-net and an audit trail.
Compre a licença em ecosire.com e baixe o ZIP do aplicativo Mollie Payments for ERPNext no painel da sua conta.
Extraia o ZIP na pasta de aplicativos do seu banco ou execute `bench get-app` com o caminho para o aplicativo extraído.
Execute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench Migra` para instalar Mollie Payments for ERPNext e aplicar seu esquema.
Abra as configurações de licença ECOSIRE em seu site e ative sua chave de licença. Requer os aplicativos gratuitos ecosire_connect e ecosire_license_client.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| European local methods (iDEAL, Bancontact, SEPA) | First-class, wired through Mollie Orders/Payments API | Possible but you build every method by hand | Often card-only or partial method coverage | |
| ERPNext integration depth | Proper Frappe app: DocTypes, hooks, gateway account | Depends entirely on your developer's discipline | Varies; often loosely coupled scripts | |
| Recurring SEPA mandates | Built via Mollie customers and mandates | Significant extra effort to get right | Rarely supported off the shelf | |
| Refund & chargeback sync | Refund API calls plus reversal write-back | Must be designed and tested from scratch | Frequently manual or missing | |
| Reconciliation | Auto Payment Entry + daily safety-net scheduler | You own the reconciliation logic | Basic or manual matching | |
| Fit to your workflow | Scoped to your accounts, currencies and triggers | Fully custom but you carry all risk | Generic; adapt your process to the app | |
| Code ownership | Full Git repo handover, yours to extend | You own it, and all the maintenance | Vendor-locked, closed or licensed | |
| Support & delivery | Built, installed, UAT + post-go-live window | Only what you resource internally | Forum/ticket support, no scoping |
No. Mollie Payments for ERPNext is build-to-order. ECOSIRE scopes it to your Mollie account, your ERPNext version and your reconciliation workflow, then builds, tests and installs it. There is no instant download — you receive an installable app and the full Git repository once it is built for you.
Typical delivery is 2 to 4 weeks from confirmed scope. The exact timeline depends on which payment methods you need, whether recurring SEPA mandates are in scope, and how your chart of accounts maps to bank and clearing accounts. We confirm a firm date after the scoping call.
We build against Frappe/ERPNext v15 and v16. We target your specific running version so the app installs cleanly with `bench get-app` and `bench install-app`, and we validate it on a staging site before touching production.
iDEAL, Bancontact, SEPA Direct Debit and Sofort as European local methods, plus cards, PayPal and Apple Pay through the same Mollie connector. The active method set is configurable in `Mollie Settings` and constrained by what your Mollie profile has enabled.
We use Mollie customers and mandates. The first payment establishes a mandate, and subsequent charges for subscriptions or installments reuse that stored mandate through the Mollie API — so ERPNext can charge on schedule without re-collecting IBAN details. This is only built if recurring is in your confirmed scope.
Every build includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full Git repository, your team or ours can extend the app afterwards; ongoing enhancements, ERPNext version upgrades or new Mollie features can be handled under a separate maintenance arrangement.
A signature-verified webhook marks the linked Payment Request paid and creates a Payment Entry against the bank or clearing account you specify, then reconciles it. A daily scheduler event acts as a safety-net for any webhook Mollie could not deliver, and refunds and chargebacks are synced back so the ledger stays accurate.
A Mollie payment gateway built as a proper Frappe app for ERPNext, bringing iDEAL, Bancontact, SEPA, Sofort, cards, PayPal and Apple Pay into your quotation-to-payment flow. ECOSIRE scopes, builds, installs and supports it for your v15/v16 instance.