JazzCash Payment Gateway for ERPNext

ECOSIRE builds a native JazzCash integration as a proper Frappe app that plugs into ERPNext's existing payment plumbing. It registers a JazzCash provider against the standard Payment Gateway and Payment Request flow, so a customer paying a Sales Invoice, a Web Order, or a portal payment link is redirected to JazzCash's HMAC-secured hosted checkout and can pay from their JazzCash Mobile Wallet, a debit/credit card, or an over-the-counter voucher. We add a dedicated JazzCash Settings DocType (Single) to hold your Merchant ID, Password, integrity salt, and the sandbox/live environment toggle, with secret fields encrypted at rest, so the same codebase moves cleanly from UAT to production by flipping one switch.

Technically, the app is built around correctness of the money trail. Outbound requests are signed with the JazzCash HMAC-SHA256 secure hash exactly to spec, and — critically — every inbound callback and return is re-hashed and compared before we trust a single rupee of it, closing the door on spoofed "payment success" posts. Payment confirmation is handled by whitelisted methods exposed through the Frappe REST API, hooks.py document events (for example on_submit of Payment Request and Sales Invoice), and scheduler events that poll JazzCash's status/inquiry endpoint for pending or dropped transactions so nothing is left in limbo. On a verified success we auto-create and submit the matching Payment Entry against the invoice, write a JazzCash Transaction log record (txn ref, MSISDN, amount, response code, raw signed payload) for audit, and fire ERPNext's normal notification path. Role-based permissions and a role profile keep the settings and raw transaction logs restricted to finance/admin users, while client scripts surface a clean pay-status on the invoice for everyone else.

Because this is build-to-order, you are not downloading a generic plugin and hoping it fits. We start from a scoping call, confirm which documents should trigger JazzCash (invoices, web checkout, subscriptions, portal links), map your Chart of Accounts and reconciliation rules, and build against your ERPNext version — we support Frappe/ERPNext v15 and v16. You get installable source code for your version, a staging UAT pass, and a documented go-live. Typical delivery is 2–4 weeks from confirmed scope, and after go-live we stay on to support the first weeks in production and hand over the git repository so your team owns what we built.