EU and Swiss enterprise merchants who acquire through Worldline (Saferpay) hit a wall with Odoo out of the box: there is no core payment provider for Saferpay, so eCommerce and sales-order online payment either fall back to a generic processor or get handled off-platform. The result is broken reconciliation, manual matching of settlements against account.move, no native support for the local methods your customers actually reach for — TWINT, iDEAL, Bancontact, Klarna — and a checkout that cannot satisfy PSD2 SCA cleanly. Odoo's generic providers were never written against Saferpay's Payment Page / Transaction JSON API, its 3DS2 liability-shift flow, or its capture/refund semantics.

ECOSIRE builds a dedicated Odoo payment provider that plugs into the standard payment framework so it behaves like a first-class acquirer everywhere Odoo already renders a pay button — website checkout, the customer portal invoice, and sales-order payment links. It ships as a proper module: a __manifest__.py declaring the payment dependency, a payment.provider record extended with a saferpay code, encrypted API-credential fields, and a payment.transaction subclass that implements the Saferpay PaymentPage/Initialize → PaymentPage/Assert lifecycle for the hosted redirect flow, or the Transaction/Initialize + secure-fields flow for the embedded iframe. We wire the return and webhook controllers, verify the notification signature server-side, and reconcile each transaction back to the originating sale.order or account.move.

Technically, the module manages the full money lifecycle rather than just authorization. capture, void, and refund are implemented against Saferpay's Transaction/Capture, Transaction/Cancel, and Transaction/Refund endpoints and surfaced as Odoo actions on the transaction, so your finance team can capture or reverse without leaving the ERP. 3DS2/SCA is handled through Saferpay's Secure Card Data and challenge flow, with the liability-shift result stored on the transaction for audit. A dedicated webhook controller ingests asynchronous status changes (authorized, captured, failed, chargeback) idempotently — keyed on the Saferpay transaction reference so retries never double-post — and moves the Odoo transaction and its linked document through the correct states. Access is locked down with ir.model.access.csv plus record rules so credential fields and the raw API log are visible only to payment administrators, and everything is scoped per company for multi-entity groups.

Because every acquirer contract, method mix, and reconciliation policy differs, this is build-to-order rather than a one-click install. After a short scoping call we confirm your exact method set (cards, TWINT, iDEAL, Bancontact, Klarna, and any others in your Saferpay terminal), your capture policy (auto vs. manual), Community-vs-Enterprise accounting depth, and your target Odoo version (17.0, 18.0, or 19.0). We then build against your sandbox credentials, run UAT on a staging database, and hand over installable source, a git repository, technical and user documentation, and a training session. Typical delivery is 2–4 weeks from confirmed scope. No instant download — you get a module built and tested for your environment, plus a post-go-live support window.