Most ERPNext merchants who process payments in the US and internationally end up juggling two or three disconnected payment paths: a card gateway wired into Web Payments, a separate PayPal button, and manual reconciliation for anything in between. ERPNext's native Payment Gateway Account and the bundled integrations cover a handful of processors, but there is no first-class Braintree connector — so cards, PayPal, Venmo and Apple Pay never share a single vault, saved payment methods can't be reused across a customer's future orders, and SCA/3-D Secure challenges either fall back to clunky redirects or aren't handled at all. That gap forces workarounds that leak conversions at checkout and create reconciliation drift between Braintree's dashboard and your ERPNext ledger.

Braintree Payments Pro is a proper Frappe app (its own module, DocTypes, and hooks.py) that ECOSIRE builds against your specific ERPNext instance to close that gap. At its core it registers Braintree as a real Payment Gateway Controller so it plugs into the standard ERPNext checkout and Payment Request flow, while adding a Braintree Settings single DocType (holding merchant ID, public/private keys, tokenization key and environment, with secrets stored as Password fields, never in plaintext). Client Scripts render the Braintree Drop-in UI or Hosted Fields on the payment page and request a client_token from a whitelisted server method (frappe.whitelist()); the browser returns a payment_method_nonce, and a server-side controller calls Braintree's SDK to create the transaction or vault the payment method. Vaulted methods and network tokens are persisted in a Braintree Vault Token DocType linked to the ERPNext Customer, so returning buyers — and recurring/subscription billing runs — reuse a stored method instead of re-entering card data.

Technically, the connector is event-driven the way ERPNext expects. hooks.py doc_events on Payment Entry and Sales Invoice keep the ledger in step with Braintree's transaction lifecycle; a scheduler_events job reconciles settled, disputed and refunded transactions against a Braintree Transaction Log DocType so your books match the Braintree control panel without manual export. Webhooks land on a whitelisted, signature-verified endpoint that maps Braintree notifications (transaction_settled, subscription_charged_successfully, dispute_opened) onto the right ERPNext documents. 3-D Secure 2 is invoked during the nonce step so SCA challenges happen inline, and PayPal, Venmo and Apple Pay are exposed through the same Drop-in surface — one integration, one vault, one reconciliation path. Access is governed by ERPNext permissions and role profiles, so only authorised roles can view settings, issue refunds, or read the transaction log, and the whole thing is written for Frappe/ERPNext v15 and v16.

Because this is build-to-order, you are not downloading a generic marketplace app and hoping it fits. After a short scoping call we confirm your ERPNext version, which payment methods you actually need (cards only, or the full PayPal/Venmo/Apple Pay set), your subscription model, and your reconciliation rules. ECOSIRE then builds the connector to that scope, validates it end-to-end in Braintree's sandbox on a staging site, runs UAT with you, and installs it on your production bench with a documented rollback. Typical delivery is one working week from confirmed scope, and you receive the full source and git repository so you own what we build.