Braintree (PayPal) Gateway for Odoo

We build a first-class Odoo payment acquirer that plugs into the standard payment framework, so it behaves like any core provider: it appears in Invoicing/Website settings, respects the payment.transaction state machine (draft → pending → authorized/done → cancel/error), and reuses Odoo's existing checkout, portal "pay now", and subscription flows. The provider record subclasses payment.provider (payment.acquirer on 17.0) with your Braintree merchant, public and private keys stored as encrypted config fields, and a Sandbox/Production toggle. On the storefront, Braintree's Drop-in UI and Hosted Fields render inside Odoo's QWeb checkout template, so card data is tokenized in the browser and the PAN never touches your Odoo server — a clean PCI-DSS SAQ-A posture. A single container surfaces cards, the PayPal button, Venmo, and Apple/Google Pay based on what you enable.

Under the hood the module authorizes or sale-captures via Braintree's server SDK, writes back provider_reference and the transaction result, and drives 3DS2/SCA so European and UK cards clear the issuer challenge instead of soft-declining. Recurring and "save my card" use Braintree's vault: we persist payment method tokens against payment.token records so Odoo Subscriptions and portal re-orders charge without re-entering card details. A signed Braintree webhook endpoint (a controllers/ route, CSRF-exempt and signature-verified) reconciles asynchronous events — settlements, disputes, refunds, subscription charges — back onto the matching payment.transaction, and an optional ir.cron sweep catches any webhook that was missed. Access is locked down with ir.model.access.csv and record rules so only Accounting/Payment roles read raw gateway data; refunds and voids are exposed as guarded server actions on the transaction. Everything is packaged as a proper module — __manifest__.py declaring the payment dependency, versioned 17.0/18.0/19.0, with server-action and QWeb receipt reporting where you need it.

Because this is build-to-order, nothing is a black box you download blind. We start with a short scoping call to confirm your Odoo version and edition (Community vs Enterprise), which wallets and currencies you need, your settlement/multi-currency setup, and whether Subscriptions/recurring is in scope. We then build against your requirements, deliver on a staging copy of your database for UAT, and go live with you. Typical delivery is 2–4 weeks from confirmed scope, depending on wallet count, subscription depth and any custom reconciliation rules. You receive the full source, a git repository handover, and a support window after go-live.