Cross-border ERPNext merchants keep losing crypto-paying customers because ERPNext has no native way to take a stablecoin payment. Out of the box, ERPNext Payments supports card and bank gateways like Stripe, Razorpay and PayPal, but there is no Payment Gateway document for USDT, USDC or BTC, no way to watch a blockchain for confirmations, and no mechanism to lock the fiat value of a volatile asset at the moment of sale. Teams end up emailing a wallet address manually, reconciling transactions by hand in Payment Entry, and arguing with customers about which exchange rate applied. That is where ERPNext native runs out of road.

We build a proper Frappe app (its own module, installed with bench get-app and bench install-app) that plugs crypto acceptance directly into the ERPNext checkout and sales flow. The app registers a new payment method backed by either CoinGate (hosted, custody-managed) or a self-hosted BTCPay Server (non-custodial, your own node), selected per your risk appetite during scoping. When a customer chooses to pay in crypto on a Sales Invoice, Sales Order or web checkout, the app calls the provider API, generates a payment request for the exact stablecoin or coin, and stores the invoice, wallet address, expected amount and expiry in a dedicated Crypto Payment DocType linked back to the source document.

Technically, confirmation is event-driven. The provider's webhook hits a whitelisted Frappe method (@frappe.whitelist(allow_guest=True)) that verifies the HMAC signature, then updates the Crypto Payment state machine (Pending → Seen on chain → Confirmed → Settled). A hooks.py scheduler event polls for stuck or under-confirmed transactions as a safety net, and doc_events handlers auto-create the matching Payment Entry and reconcile it against the invoice once the required on-chain confirmations are reached. At checkout we call the provider's rate endpoint to lock the FX rate, persist the locked rate and coin amount on the payment record, and post the accounting entry in your ERPNext base currency so your GL and receivables stay clean regardless of coin volatility. Refunds are handled through a role-gated action that issues a refund to the customer's wallet and writes the corresponding credit note and Payment Entry. Client scripts surface a live QR code and confirmation status on the transaction form; permissions and role profiles keep wallet actions restricted to finance roles.

Because this is build-to-order, nothing ships until we agree on scope. It starts with a short scoping call to confirm your coins, provider (CoinGate vs BTCPay), ERPNext version (v15 or v16), and reconciliation rules. We then build against your requirements, deliver on a staging instance for UAT, and only cut over to production after you sign off. Typical delivery is one working week from confirmed scope, and you receive the full source repository, so you are never locked to us.