Multi-region ERPNext merchants quickly hit a wall: ERPNext core supports payment gateways one at a time through the Payment Gateway Account and individual integrations (Stripe, Razorpay, PayPal, GoCardless, Braintree). There is no native concept of routing a transaction across gateways, retrying a declined charge on a different processor, or picking the cheapest acquirer for a given currency and card type. When your primary PSP has an outage or your success rate dips in one region, ERPNext has no fallback — the customer just sees a failed payment, and you lose the sale. Reconciliation across several gateways also becomes a manual, error-prone exercise across disconnected Payment Entry records.

The Unified Payments Orchestrator is a proper Frappe app that sits between ERPNext checkout and your payment service providers as a single orchestration layer. We model the domain in dedicated DocTypes — Payment Gateway Profile (per-PSP credentials, supported currencies, fee schedule, health state), Routing Rule (ordered conditions on currency, amount band, card scheme, region, and success-rate thresholds), Orchestrated Transaction (the canonical record of an attempt and its retry cascade), and Reconciliation Batch. A whitelisted method (orchestrator.api.initiate_payment) receives the checkout request, evaluates the routing rules, and dispatches to the winning gateway; on decline or timeout it walks the failover cascade to the next eligible PSP without the customer re-entering card details, because tokens are held in a single tokenization vault abstracted across processors.

Technically, routing decisions are driven by server scripts and a rules engine evaluated at request time, so your operations team can adjust routing logic from the ERPNext desk without a redeploy. hooks.py doc events keep Payment Entry, Sales Invoice, and Sales Order in sync as attempts settle, and scheduler events run periodic health probes against each gateway plus an automated reconciliation pass that matches PSP settlement reports to Orchestrated Transaction rows and flags mismatches. Every PSP webhook lands on a unified, idempotent endpoint (a whitelisted, signature-verified method) that normalizes disparate provider payloads into one internal event shape, so a captured, refunded, or disputed event from any processor updates ERPNext consistently. Least-cost routing uses the fee schedule on each Payment Gateway Profile combined with live success-rate data to choose the acquirer that maximizes net revenue for each transaction. Role profiles and permission rules gate who can edit routing logic, view raw gateway credentials, or trigger manual reconciliation, and the Frappe REST API exposes read models for your own dashboards.

Because this is build-to-order, nothing is a generic download. After a short scoping call we confirm your exact gateway mix, currencies, routing priorities, and reconciliation format, then build and test the app against Frappe/ERPNext v15 or v16 to match your site. You receive the installable source for your version, install it on your bench, and go live with a defined support window. Typical delivery is one working week from confirmed scope, depending on how many PSPs and how much custom routing logic you need.