Finance teams running ERPNext across borders hit the same wall: ERPNext core has a clean multi-currency accounting engine, but it has no native Airwallex integration. Collecting from customers in dozens of currencies, holding wallet balances, and paying suppliers or contractors globally all happen outside ERPNext — in the Airwallex dashboard, in spreadsheets, and in manual bank imports. The result is delayed cash visibility, error-prone hand-keyed Payment Entry records, unreconciled FX gains and losses, and no audit trail linking a settlement back to the invoice it paid. ERPNext's built-in Payment Gateway framework covers a handful of processors and only the pay-in direction; it was never designed for wallet balances, 160+ local payment methods, or outbound global payouts.

ECOSIRE builds a proper Frappe app — installed on your own bench, versioned in your git repo — that makes Airwallex a first-class part of your ERPNext money flow. We add an Airwallex Settings single DocType (encrypted Password fieldtype for the client ID and API key, environment toggle for demo vs production, webhook secret) plus Airwallex Wallet, Airwallex Collection, and Airwallex Payout DocTypes that mirror the objects in the Airwallex Global Accounts and Payments APIs. Collections are created against a Sales Invoice or Payment Request; supported local methods (cards, wallets, bank transfers, and 160+ methods across 180+ countries) are surfaced through the hosted checkout or an embedded flow. When Airwallex fires a webhook, a whitelisted endpoint (@frappe.whitelist(allow_guest=True)) verifies the HMAC signature, and a hooks.py doc-event pipeline creates and submits the matching Payment Entry, applies it against the correct outstanding invoice, and posts realized FX difference to your configured exchange-gain/loss account.

Reconciliation is the hard part, and it is the part we automate. A scheduler event (registered under scheduler_events in hooks.py) polls the Airwallex settlement and balance endpoints on your chosen cadence, pulls wallet transactions per currency, and matches them to open collections by reference and amount — writing a clean reconciliation log so finance can see exactly which settlement funded which Payment Entry. For the payout direction, an Airwallex Payout DocType drives supplier payments and contractor disbursements from your multi-currency wallet balances, with an ERPNext workflow and role-based approval before any money leaves. Everything respects ERPNext permissions: we ship a dedicated role and Role Profile so only authorized users can trigger payouts or edit gateway credentials, and every API call and webhook is logged for audit.

Because payment logic is money-critical, the app is built defensively: idempotency keys on every payout request, signature verification on every inbound webhook, retry-with-backoff on transient API failures, and a full request/response log DocType so failed transactions are diagnosable rather than silent. Client scripts add the connect-and-pay actions to the Sales Invoice and Payment Request forms; server scripts and the Frappe REST API expose the collection and payout objects for any headless or portal front-end you run. The app targets Frappe/ERPNext v15 and v16 and is packaged as a standard installable app so it upgrades cleanly with your bench.

This is build-to-order: ECOSIRE builds, installs, and supports it after you request a quotation — it is not an existing Frappe Cloud Marketplace download. We start with a short scoping call to confirm which Airwallex products you use (Collections, Global Accounts, Payouts), your currencies, your chart-of-accounts mapping, and your approval rules. Typical delivery is one working week from confirmed scope. You get the installable source for your version, install and configuration on your bench, UAT on a staging instance with a rollback plan, technical and user documentation, a training session, and a post-go-live support window — plus the git repository handed over so the code is yours.