ERPNext Easypaisa Payment Connector

Key Features

Easypaisa registered as a Payment Gateway in ERPNext, selectable on Sales Invoice and web checkout alongside native gateways

Encrypted integration settings DocType storing merchant/store ID and API keys as Password fieldtypes (never in plain source or client scripts)

Whitelisted server method (@frappe.whitelist()) generates hosted checkout links / payment requests against the Easypaisa API

Signed webhook endpoint verifies the Easypaisa checksum/HMAC before trusting any payment-status callback

Automatic Payment Entry creation and submission against the originating Sales Invoice on a confirmed PAID event

Idempotent transaction handling de-duplicated on Easypaisa transaction ID so retried webhooks never double-post

Reference number, mode of payment, and bank/wallet clearing account set automatically on each posted Payment Entry

Scheduler event reconciliation sweep (registered in hooks.py) that reconciles or flags missed/pending callbacks

Refund handling that posts reversing entries and triggers the Easypaisa refund request where the API allows

Transaction-fee mapping to a configurable charges/expense account for accurate net-revenue reporting

Easypaisa Transaction log DocType with status, raw payload, and audit trail for every request and callback

Role-based permissions and a dedicated role profile so only Accounts users can view keys or reprocess transactions

doc_events hooks on Payment Entry / Sales Invoice for status sync and cancellation-safe reversal

Client script on the invoice/portal to surface a Pay with Easypaisa action and live payment status

Structured error logging and retry-safe design for gateway timeouts, so partial failures are recoverable not silent

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Pakistani merchants running ERPNext on Sales Invoices quickly hit a wall at the payment step. ERPNext ships payment gateway integrations for the likes of Razorpay, Stripe, and PayPal, but there is no native Easypaisa connector — so cashiers and accountants end up copying transaction IDs out of the Easypaisa merchant portal or SMS confirmations and hand-keying Payment Entries against invoices. That manual bridge is where money leaks: mismatched references, double-posted receipts, payments applied to the wrong customer, and month-end reconciliation that drags on because the mobile-wallet ledger never automatically lines up with the ERPNext General Ledger.

The ECOSIRE ERPNext Easypaisa Payment Connector is a proper Frappe app (its own module, DocTypes, and hooks.py) that plugs Easypaisa directly into your ERPNext payment flow. We register a Payment Gateway record and integration settings DocType (with the merchant account, store ID, and API/HMAC secret keys stored encrypted as Password fieldtypes) so Easypaisa becomes a selectable gateway on the Sales Invoice and web checkout. When a customer chooses Easypaisa, a whitelisted server method (@frappe.whitelist()) generates a hosted checkout link or payment request against the Easypaisa API and returns it to the portal or POS screen. Nothing is trusted from the browser redirect alone.

Confirmation is handled server-side. A dedicated webhook endpoint receives the Easypaisa payment-status callback, verifies the signature/checksum, looks up the originating reference, and — on a genuine PAID event — creates and submits a Payment Entry against the correct Sales Invoice, sets the reference number and mode of payment, and posts to the configured bank/wallet clearing account. The whole flow is idempotent: duplicate callbacks are de-duplicated on the transaction ID so a retried webhook never double-posts. A scheduler event (registered under scheduler_events in hooks.py) runs a reconciliation sweep that reconciles or flags any transactions where the callback was missed, keeping the Easypaisa ledger and ERPNext GL in agreement. Refunds initiated from ERPNext post a reversing entry and, where the Easypaisa API supports it, trigger the refund request; transaction fees are mapped to a configurable expense/charges account so your revenue reporting stays clean.

Because this is built to order, ECOSIRE tailors the connector to your exact ERPNext version (Frappe/ERPNext v15 or v16), your chart of accounts, and your Easypaisa merchant contract — one-time payment links, recurring collection, or POS-side flows. We do not sell an anonymous marketplace download and there is no instant-download button. After a short scoping call we confirm the requirements, build against a staging copy of your site, run UAT with you, and then install on production. Typical delivery is 2-4 weeks from confirmed scope, and every engagement includes source code, documentation, training, and a post-go-live support window.

What you get

Installable Frappe app source code for your confirmed ERPNext version (v15 or v16), pinned to your scope

Installation and configuration on your ERPNext instance, including Payment Gateway setup and account mapping

Technical documentation: DocType reference, hooks.py events, webhook contract, and configuration guide

User guide plus a live training session for your accounts and operations team

UAT on a staging copy of your site with a documented rollback plan before production install

Post-go-live support window for defect fixes and configuration adjustments

Git repository handover with full commit history and versioned releases

Easypaisa sandbox/production credential wiring and a verified end-to-end test transaction

Who this is for

Pakistani e-commerce merchant

Runs an online store on ERPNext and wants customers to pay via Easypaisa at checkout, with the payment automatically reconciled against the Sales Invoice instead of being matched by hand each evening.

SME accounts manager

Closes the books monthly and is tired of chasing Easypaisa transaction IDs across SMS, the merchant portal, and ERPNext. Needs the wallet ledger to line up with the ERPNext GL automatically, with fees booked to the right account.

ERPNext administrator / IT lead

Owns the ERPNext deployment and needs a clean, upgrade-safe Frappe app with proper permissions, encrypted keys, and documented hooks — not a fragile script pasted into the site.

Retail / POS operator

Takes payments at the counter and needs a fast Pay with Easypaisa action that generates a payment request and confirms status without leaving the ERPNext screen.

How ERPNext Easypaisa Payment Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor
Easypaisa support in ERPNext	Purpose-built connector wired to your invoices and accounts	Possible but you design the whole integration yourself	Rarely available; most marketplace gateways target India/global
Payment Entry automation	Auto-created and submitted from verified webhook events	Depends entirely on how well your developer builds it	Varies; often generic and not Easypaisa-aware
Reconciliation	Scheduler sweep keeps wallet ledger and GL in sync	Must be specified and built from scratch	Usually not included
Version fit (v15/v16)	Pinned and tested against your exact ERPNext version	Whatever your team targets and maintains	May lag ERPNext releases or break on upgrade
Security of keys	Encrypted Password fields, role-gated, signed webhooks	Only as secure as your implementation	Opaque; you cannot always audit the code
Refunds and fee mapping	Reversing entries plus configurable charges account	Extra scope you must design and test	Often absent or partial
Source and ownership	Full source and git repo handed over to you	You own it but carry all build cost and risk	Usually closed-source licensed binary
Support and delivery	Build-to-order, UAT, training, post-go-live support	Self-supported unless you hire separately	Ticket queue; no fit to your specific setup

Frequently Asked Questions about ERPNext Easypaisa Payment Connector

Is this a ready-made app I can download and install right now?

No. This is a build-to-order engagement. ECOSIRE builds the connector for your specific ERPNext version, chart of accounts, and Easypaisa merchant contract, then installs and supports it. There is no instant-download marketplace listing — every deployment is scoped and tested against your own site.

How long does delivery take?

Typical delivery is 2-4 weeks from confirmed scope. The timeline starts once we have agreed the requirements on the scoping call and you have provided Easypaisa merchant/sandbox credentials and staging access. Simpler single-flow builds land at the shorter end; POS plus recurring plus refund flows sit at the longer end.

Which ERPNext versions are supported?

We build for Frappe/ERPNext v15 and v16. During scoping we confirm your exact version and site setup so the app is pinned and tested against it. If you are on an older release, we will advise on an upgrade path as part of the call.

How does a payment become a Payment Entry in ERPNext?

When a customer pays, Easypaisa sends a status callback to a signed webhook endpoint in the app. We verify the checksum, match it to the originating reference and Sales Invoice, and on a confirmed PAID event create and submit a Payment Entry against that invoice — with the reference number, mode of payment, and clearing account set. Duplicate callbacks are de-duplicated so nothing double-posts.

What happens if a webhook is missed or Easypaisa is slow?

A scheduler event runs a reconciliation sweep that re-checks pending transactions and either reconciles them or flags them for review. The design is retry-safe and idempotent, so a delayed or repeated callback resolves to a single correct Payment Entry rather than a silent gap or a double posting.

Do you handle refunds and transaction fees?

Yes. Refunds initiated from ERPNext post a reversing entry and, where the Easypaisa API supports it, trigger the refund request. Easypaisa transaction fees are mapped to a configurable charges/expense account so your net revenue and reconciliation stay accurate.

What support and updates do we get after go-live?

Every engagement includes a post-go-live support window for defect fixes and configuration adjustments, plus a full git repository handover so you own the code. Beyond the initial window we offer ongoing support and version-upgrade retainers, including compatibility work when you move between ERPNext v15 and v16.