Mid-market merchants running fraud-prone card volume face a brutal tradeoff: manual review teams that slow fulfillment and reject good customers, or loose acceptance rules that bleed money to chargebacks. Odoo's core sale and account modules have no fraud-decisioning layer at all — an order lands in draft/sale state with nothing to tell you whether the cardholder is legitimate, and by the time a charge.dispute/chargeback arrives weeks later, the goods have shipped and the funds are clawed back. Native Odoo simply has no concept of a guaranteed decision or a reimbursement claim, so most teams bolt on spreadsheets and email threads that never reconcile against the ledger.

We build a dedicated connector that wires Odoo directly into Signifyd's Decision and Guarantee APIs. On a configurable trigger — order confirmation, a payment-acquirer callback, or an automated action on sale.order — the module assembles a Signifyd case creation payload (buyer identity, billing/shipping mismatch signals, line items, device/session fingerprint, payment method) and posts it over authenticated HTTPS. The decision (APPROVE / DECLINE / HOLD with the guarantee disposition) is written back onto custom fields via models.Model with compute/@api.depends helpers, and a flagged order is automatically parked using a state guard so warehouse users cannot deliver it. A hardened webhook controller (an Odoo http.Controller route, HMAC-signature verified) ingests asynchronous guarantee/completion and case/rescore events so late decisions and reversals sync without polling.

Technically the app ships as a proper Odoo addon: __manifest__.py declaring dependencies on sale, account, and payment; new models plus extensions to sale.order and account.move; access rules in ir.model.access.csv and record rules scoping Signifyd data by company for multi-company installs; XML/OWL views surfacing the decision, score, and case link on the order form with a smart button; a QWeb-driven audit view of every case and its raw request/response for disputes; and a stored, encrypted API credential in res.config.settings. The chargeback workflow models each dispute as a reimbursement claim linked to the originating account.move, tracks its Signifyd claim status, and posts the guaranteed recovery so finance can reconcile it — closing the loop native Odoo leaves wide open. It targets Odoo 17.0, 18.0, and 19.0 (Community and Enterprise; Enterprise studio/automation hooks used where available, with Community-safe fallbacks).

Because this is build-to-order, you are not downloading a pre-baked app. After a short scoping call we confirm your Signifyd account tier, trigger points, payment acquirers, and multi-company/multi-currency needs, then build the version pinned to your exact Odoo release. Typical delivery is one working week from confirmed scope. You get UAT on a staging database, a rollback plan, a training session, a post-go-live support window, and the full git repository handed over so the code is yours.