Enterprise merchants already running Visa CyberSource for its Decision Manager fraud rules, tokenization vault, and acquirer relationships hit a wall in Odoo: the core payment framework ships Stripe, Adyen, PayPal, and a handful of others, but there is no first-party CyberSource provider. Teams end up bouncing customers to a hosted page outside Odoo, reconciling settlements by hand, and losing the fraud signals and stored credentials they already pay for. The native payment.provider model has no place to store a CyberSource merchant ID, transaction key, or profile, and no code path to sign a Secure Acceptance request or verify its signed response.

ECOSIRE builds a proper Odoo payment provider that extends payment.provider and payment.transaction so CyberSource behaves like any other acquirer in the checkout, Invoicing, and Sales flows. We implement Secure Acceptance in either hosted or flexible (Flex Microform) mode, compute and verify the HMAC-SHA256 signature on both the outbound request and the returned response, and map CyberSource decision/reason_code values onto Odoo transaction states (draft, pending, authorized, done, cancel, error). Decision Manager screening is wired in so a REVIEW outcome parks the transaction in a pending state with an activity for your finance team rather than silently failing. 3DS2 / SCA is handled through the Payer Authentication step so European and card-scheme mandates are met, and stored credentials use the Token Management Service (TMS) — the vaulted token lives on payment.token for one-click repeat orders and subscriptions, never the raw PAN.

Technically, the module is a clean Odoo addon: a __manifest__.py declaring dependencies on payment (and website_sale/account_payment where you need eCommerce or invoice payment), models in models/ using models.Model with @api.depends computes for signed-field assembly, access rules in ir.model.access.csv plus record rules so only Payment Administrators see credentials and secret keys are stored write-only. The provider form, transaction views, and any OWL/QWeb checkout snippets ship as XML; webhook and redirect handling live in controllers that validate every inbound signature before touching a transaction. Multi-currency is supported end to end — the transaction currency, presentment currency, and CyberSource processing currency are reconciled against Odoo's res.currency. Everything is exposed over Odoo's XML-RPC / JSON-RPC API so your other systems can read transaction status. We build for your exact target: Odoo 17.0, 18.0, or 19.0, Community or Enterprise, and account for the differences (for example Enterprise's accounting reconciliation and follow-up hooks).

Because this is build-to-order, nothing is pre-listed for instant download. We start with a scoping call to confirm your CyberSource account type (Secure Acceptance vs REST/Flex), which flows you need (website checkout, back-office invoice payment, subscriptions), your Odoo version and edition, and your fraud and SCA requirements. Typical delivery is one working week from confirmed scope. You receive the installable source for your version, install and configuration on your environment, UAT on a staging database with a rollback plan, documentation, a training session, and a post-go-live support window. ECOSIRE builds it, installs it, and supports it.