Unified Payments Orchestrator for ERPNext

Key Features

`Payment Gateway Profile` DocType per PSP holding credentials, supported currencies, fee schedule, and live health state

`Routing Rule` DocType with ordered, condition-based rules on currency, amount band, card scheme, region, and success-rate thresholds

Whitelisted `initiate_payment` orchestration method that evaluates rules and dispatches to the winning gateway at request time

Automatic failover cascade that re-attempts a declined or timed-out charge on the next eligible PSP without re-collecting card data

Single tokenization vault abstracting saved payment tokens across processors so cardholder data is entered once

Least-cost routing that combines each gateway's fee schedule with real-time success rates to maximize net revenue per transaction

Unified, idempotent, signature-verified webhook endpoint that normalizes captured/refunded/disputed events from every PSP into one internal event shape

Scheduler events for periodic gateway health probes that auto-demote unhealthy PSPs in the routing order

Automated reconciliation pass matching PSP settlement reports against `Orchestrated Transaction` rows, flagging mismatches for review

`hooks.py` doc events keeping `Payment Entry`, `Sales Invoice`, and `Sales Order` in sync as attempts settle

Server-script-driven rules engine so operations can adjust routing logic from the ERPNext desk with no redeploy

Role profiles and permission rules separating routing editors, credential viewers, and reconciliation operators

Frappe REST API read models and query reports exposing attempt-level and gateway-level analytics for external dashboards

Full attempt audit trail on `Orchestrated Transaction` capturing every gateway hop, decline reason, and latency for dispute defense

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2-4 weeks from confirmed scope, depending on how many PSPs and how much custom routing logic you need.

What you get

Installable Frappe app source code built and pinned to your Frappe/ERPNext v15 or v16 version

Installation and configuration on your bench, including gateway credential setup and initial routing rules

Technical documentation covering DocType schema, hooks, whitelisted methods, scheduler events, and webhook contracts

End-user guide plus a live training session for your finance and operations team

Post-go-live support window for defect fixes and configuration tuning

UAT on a staging site with a documented rollback plan before production cutover

Private git repository handover with full commit history and deployment notes

Reconciliation and routing runbook for day-to-day operations and adding new gateways later

Who this is for

Multi-region ecommerce operator

Runs ERPNext-backed checkout across several countries with a different primary acquirer per region and needs regional failover so an outage in one market never blocks a sale in another.

Finance / reconciliation lead

Owns settlement matching across two or more PSPs and wants one automated reconciliation pipeline that ties every gateway payout back to ERPNext Payment Entries instead of manual spreadsheets.

Head of payments / revenue optimization

Cares about authorization rates and processing cost, and wants least-cost and success-rate routing rules they can tune from the desk to lift net revenue without engineering tickets.

ERPNext platform engineer

Maintains the bench and needs a clean Frappe app with proper DocTypes, hooks, permissions, and REST endpoints they can support, extend, and upgrade across v15/v16 rather than a fragile bolt-on.

How Unified Payments Orchestrator for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor
Multi-gateway routing	Rule-based routing across all your PSPs in one layer	Possible but you design and maintain the engine	Usually one gateway per integration, no routing
Automatic failover	Retry cascade to next eligible PSP, no re-entry	Must be hand-built and tested per PSP	Rarely offered; failed payment is final
Least-cost routing	Fee schedule + success rate picks best acquirer	Requires bespoke cost model and data plumbing	Not a feature of single-gateway apps
Unified reconciliation	Scheduled matching + `Reconciliation Batch` mismatch flags	You build the matching pipeline yourself	Per-gateway at best, rarely cross-PSP
ERPNext fit	Native DocTypes, hooks, permissions, REST API	Depends on your team's Frappe discipline	Varies; often thin or unmaintained
Tokenization vault	Single vault abstracted across processors	Significant PCI-scoped effort to build	Tied to the one gateway it integrates
Version support	Built and tested for your v15/v16 site	You own upgrade compatibility	May lag ERPNext releases
Support model	Post-go-live window + git handover + runbooks	Internal team only	Community or vendor forum, variable

Frequently Asked Questions about Unified Payments Orchestrator for ERPNext

Is this an app I can download and install myself right now?

No. This is a build-to-order engagement. ECOSIRE builds the orchestrator against your specific gateway mix, currencies, and routing rules, then installs it on your bench and hands over the source. There is no instant marketplace download.

How long does delivery take?

Typical delivery is 2-4 weeks from confirmed scope. The exact timeline depends on how many payment service providers you connect and how much custom routing and reconciliation logic you need, which we finalize on the scoping call.

Which payment gateways can it route across?

Any PSP with an API — for example Stripe, Razorpay, PayPal, Braintree, Adyen, Checkout.com, or regional acquirers. Each gateway is modeled as a `Payment Gateway Profile` DocType, and we build the specific connectors your business uses as part of the engagement.

Which ERPNext versions are supported?

We build and test against Frappe/ERPNext v15 or v16 to match your live site. The app is a standard Frappe app using DocTypes, `hooks.py` doc events, whitelisted methods, and scheduler events, so it upgrades cleanly with your bench.

How does support and updates work after go-live?

You get a defined post-go-live support window for defect fixes and configuration tuning, plus the full git repository so your team can maintain it. Ongoing support, new gateway connectors, and version upgrades can be arranged as a separate agreement.

Can our operations team change routing rules without a developer?

Yes. Routing is driven by `Routing Rule` records and server scripts evaluated at request time, so authorized users edit conditions and gateway priority from the ERPNext desk. Permission rules control exactly who can change routing or view credentials.

How does reconciliation across multiple gateways work?

A scheduler event runs an automated reconciliation pass that matches each PSP's settlement report against `Orchestrated Transaction` and `Payment Entry` records, groups them into a `Reconciliation Batch`, and flags any mismatch for a human to review — replacing manual multi-gateway spreadsheet work.