JazzCash Payment Gateway for ERPNext

ECOSIRE builds a proper Frappe app — jazzcash_erpnext — that plugs directly into ERPNext's payment stack rather than bolting a script onto the side. We register a JazzCash payment gateway controller so it appears as a first-class option on the standard Payment Gateway Account and Payment Request DocTypes, add a JazzCash Settings single DocType (holding Merchant ID, Password, and the integrity/return salts in encrypted Password fields), and a JazzCash Transaction DocType that logs every request, pp_TxnRefNo, response code, and raw callback payload for audit. Customers pay via a JazzCash-hosted mobile-account or card checkout, or via a shareable Payment Request link/QR — no data leaves ERPNext untracked.

Confirmation is webhook-driven, not poll-based. We expose a @frappe.whitelist(allow_guest=True) endpoint that receives the JazzCash IPN/return callback, recomputes the pp_SecureHash HMAC to reject tampered or replayed posts, and — on a verified pp_ResponseCode of 000 — creates the matching Payment Entry and reconciles it against the referenced Sales Invoice inside a single atomic transaction. hooks.py doc events keep the invoice, Payment Request, and JazzCash Transaction states in lockstep, while a scheduler event sweeps pending transactions to catch any missed callback and query JazzCash status for a definitive result. Refunds are handled through a controlled action that calls the JazzCash refund API and writes the offsetting entry, and role/permission profiles keep credentials and refund rights scoped to finance staff only.

Because this is build-to-order, nothing is a generic download. After a short scoping call we confirm your exact flow — sandbox vs production credentials, mobile-account only or cards too, which invoice/order documents trigger collection, refund policy, and any custom reconciliation rules — then build against Frappe/ERPNext v15/v16 on a staging site. You get UAT on staging, a rollback plan, the installable app source, and the Git repository handover. Typical delivery is 2–4 weeks from confirmed scope, followed by a post-go-live support window.