Authorize.Net Gateway for Odoo

We build a proper payment.provider implementation for Authorize.Net that behaves like a first-class Odoo gateway. Card data is captured through Accept.js hosted fields rendered inside the Odoo checkout, so the raw PAN is exchanged for a one-time payment nonce in the browser and never touches your server or database — keeping you in SAQ A-EP scope rather than handling card data directly. On the server side a new provider model extends payment.provider with _get_supported_currencies, sandbox/production credential fields (API Login ID and Transaction Key stored as Odoo config parameters, not in plain views), and the transaction methods _send_payment_request, _send_refund_request, and a _handle_notification_data hook wired to Authorize.Net webhooks. The payment.token model is backed by CIM (Customer Information Manager): on first successful charge we create a customer profile and payment profile, then store only the resulting profile IDs so returning customers and back-office agents can charge saved cards without re-entering details.

Technically the module is a clean, upgrade-safe addon. The __manifest__.py declares dependencies on payment and account, security is enforced through ir.model.access.csv plus record rules scoping tokens and transactions to the owning company and partner, and all API calls go through the Authorize.Net JSON transaction API with explicit request/response logging to a dedicated model for audit. We support the full transaction lifecycle — authorize-only, prior-auth capture, full and partial refund, and void of an un-settled transaction — surfaced as buttons on the payment transaction form via XML/OWL views. A webhook controller validates the Authorize.Net signature key and reconciles asynchronous settlement and refund events so Odoo's transaction state always matches the gateway, and an optional automated action can flag transactions that never receive a matching webhook. USD/CAD localization covers currency-to-processor mapping and correct minor-unit handling for both currencies.

Because this is build-to-order, nothing ships as a blind download. We start with a short scoping call to confirm your Odoo version and edition (Community or Enterprise), whether you need eCommerce checkout, back-office/POS charging, or subscription repeat-billing, and your sandbox credentials. Typical delivery is 2-4 weeks from confirmed scope. You receive installable source code targeted at your exact Odoo version, deployment on a staging database for UAT with a documented rollback plan, and a go-live support window. Everything integrates with the standard Odoo APIs — the provider works through the native payment flow and is reachable via XML-RPC/JSON-RPC — so nothing about your existing invoicing, sales, or accounting posture changes.