Easypaisa Payment Gateway for ERPNext

ECOSIRE builds a proper Frappe app that registers Easypaisa as a first-class payment integration inside ERPNext. It follows the same integration contract ERPNext uses for its native gateways, so an Easypaisa Payment Gateway Account becomes selectable anywhere a gateway is — on the Sales Invoice payment request, the customer portal, and hosted payment pages. The app ships a dedicated Easypaisa Settings single DocType (store id, credentials, hashing secret, sandbox/production toggle) with sensitive fields stored as Password fieldtype, plus an Easypaisa Transaction DocType that logs every attempt, order id, status, and raw gateway response for a full audit trail.

Technically, checkout is driven through whitelisted methods (@frappe.whitelist()) that create the Easypaisa order, sign the request, and redirect the customer to Easypaisa's wallet-or-card checkout. Confirmation does not rely on the browser returning — a whitelisted webhook endpoint receives Easypaisa's server-to-server callback, verifies the signature/hash, and on success uses hooks.py doc events and controller logic to create and submit a Payment Entry against the correct Sales Invoice, updating its outstanding amount. A scheduler event (scheduler_events in hooks.py) sweeps pending transactions to catch any callback that never arrived, so ERPNext state always converges with Easypaisa's. Refunds and reversals are triggered from the Easypaisa Transaction (or via a whitelisted method) and post the matching credit entry. Client Scripts add the "Pay with Easypaisa" action and inline payment link to the Sales Invoice form. Access is governed by a dedicated role and permission rules so only authorized staff can issue refunds or edit gateway settings. The app targets Frappe/ERPNext v15 and v16 and is delivered as clean, upgrade-safe source in its own module.

Because this is build-to-order, nothing is a black-box download. We start with a short scoping call to confirm your Easypaisa merchant setup (aggregator vs. direct, wallet-only vs. card, MA/Store account type), your ERPNext version, and where you want payment prompts to appear. We then build against your requirements, run UAT on a staging instance you can test, and deploy to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full git repository so you own the code.