ERPNext JazzCash Payment Connector

ECOSIRE builds a proper Frappe app — its own module, DocTypes, and hooks.py doc events — that registers JazzCash as a first-class integration inside ERPNext. We add a JazzCash Settings single DocType for your Merchant ID, Password, Integrity Salt, and sandbox/live toggle (secrets stored via Frappe's encrypted password fieldtype, never in plaintext), and a JazzCash Transaction DocType that logs every request and response for audit. Checkout works through ERPNext's native Payment Request: a whitelisted method (@frappe.whitelist()) builds the signed pp_ payload with the correct HMAC-SHA256 secure hash over the sorted field set, then hands off to JazzCash mobile-wallet or card checkout. Customers can also be sent a hosted payment link generated from a Sales Invoice or Sales Order.

Confirmation is webhook-first, not trust-the-redirect. An inbound endpoint validates the returned secure hash before doing anything, so a spoofed browser redirect can never mark an invoice paid. On a verified pp_ResponseCode success the app creates and submits a Payment Entry against the source invoice, sets the reference number to the JazzCash pp_TxnRefNo, and maps the deducted MDR/commission to a configurable fee account so your bank rec actually ties out. Refunds are handled through JazzCash's refund transaction and written back as a linked negative/return entry. A scheduler event (registered in scheduler_events) sweeps any pending or ambiguous transactions on an interval and re-queries JazzCash status, so a dropped webhook self-heals instead of leaving a stuck invoice. Client scripts surface transaction status and a "Retry / Reconcile" action right on the invoice form, and access is gated by a dedicated role profile so only finance users can touch gateway settings or trigger refunds.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, confirm your JazzCash merchant account type (wallet, card, or both), your ERPNext version (v15 or v16), your invoice/fee-account structure and any multi-company needs, then build against that. You get the work on a staging site first for UAT, a rollback plan, and the full git repository at handover — no black box. Typical delivery is 2-4 weeks from confirmed scope, and every method is written to the current Frappe REST/whitelisted-method conventions so it survives your next bench update.