iDEAL & Bancontact Local Checkout for Odoo

This is a build-to-order engagement, not an instant apps.odoo.com download. After purchase we confirm your Odoo version, PSP and requirements, then build, install and test the module. Typical delivery is 2–4 weeks depending on your acquirer and any edge cases (multi-company, POS, custom checkout). You get a scoped timeline at kickoff and a working, validated provider on your own environment — not a zip you have to integrate yourself.

Every build includes a post-launch support window covering defect fixes and questions about operating the module. During that window we also verify the provider against your Odoo minor upgrades so a point release doesn't break checkout. When the window ends you can extend with a support/maintenance plan, or simply keep the source — you own the code and can maintain it yourself or with any Odoo partner.

The module is PSP-agnostic. We integrate with the Benelux-capable acquirer you already use — Mollie, Stripe, Adyen, Buckaroo, MultiSafepay and others are all supported. You keep your merchant contract and pricing directly with the PSP; we build the Odoo provider that talks to them. If you haven't chosen a PSP yet, we'll advise on options during scoping.

Yes. We deliver against your exact major version — 17, 18 or 19 — and the module runs on both Community and Enterprise editions since it builds on the core payment framework present in both. Tell us your version at kickoff and that's the target we build, test and hand over.

Correctly. The sale order is only marked paid when your PSP's webhook confirms a settled transaction — never on the browser redirect. If a shopper closes the tab mid-payment, the transaction stays pending and an automated action can re-poll or auto-cancel it after a timeout, so your order pipeline and reconciliation stay clean instead of stranding phantom paid orders.

Yes. Refunds are wired to Odoo credit notes — you trigger a full or partial refund from the transaction and it's pushed to the PSP. Incoming payments are reconciled by the webhook controller back to the originating sale order and invoice, with idempotent handling so retried callbacks don't double-post. All transaction states are logged for audit and dispute purposes.

We build on the standard Odoo payment abstraction (payment.provider / payment.method / payment.transaction) and avoid brittle core overrides, which keeps the module upgrade-safe. The included support window covers a compatibility check against your minor upgrades, and because you hold the source, any Odoo developer can adapt it for a future major-version migration.