Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.
Kurze Fakten
- Preis
- $249.00 USD
- ERPNext-Versionen
- —
- Rüstzeit
- 30 Min
- Lizenz
- Einmalig und unbefristet
- Sprachen
- 11 Sprachen
Einmalkauf
JazzCash Payment Gateway for ERPNext
A native JazzCash mobile-account and card payment integration for ERPNext, built to your workflow by ECOSIRE. Collect payments, confirm them by webhook, and auto-reconcile against your Sales Invoices without leaving ERPNext.
$249.00USD
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Hauptfunktionen
JazzCash payment gateway controller registered against ERPNext's native `Payment Gateway Account` and `Payment Request` DocTypes
Mobile-account (MWALLET) checkout and card-payment checkout supported through a single configurable flow
`JazzCash Settings` single DocType storing Merchant ID, Password, and integrity/return salts in encrypted `Password` fields
Shareable Payment Request links plus on-invoice QR codes so customers can pay without a login
Webhook/IPN receiver as a `@frappe.whitelist(allow_guest=True)` method that verifies the `pp_SecureHash` HMAC-SHA256 before acting
Replay and tamper protection: secure-hash recomputation plus idempotency on `pp_TxnRefNo` to prevent duplicate Payment Entries
Automatic `Payment Entry` creation and reconciliation against the referenced Sales Invoice in one atomic transaction on a verified `000` response
`JazzCash Transaction` DocType logging every request payload, response code, and raw callback for full audit trail
Scheduler event that sweeps pending/expired transactions and queries JazzCash status to recover missed callbacks
`hooks.py` doc events keeping Sales Invoice, Payment Request, and JazzCash Transaction states synchronized
Refund action that calls the JazzCash refund API and posts the offsetting Payment Entry with linkage back to the original
Sandbox and production credential profiles with an environment toggle for safe UAT
Role profiles and DocType permissions scoping credentials, refunds, and transaction visibility to finance roles
Server-side amount, currency (PKR), and status validation so front-end tampering cannot alter the collected value
REST API and whitelisted methods for headless/e-commerce front-ends to initiate JazzCash payments programmatically
Über dieses Produkt
Pakistani e-commerce and service businesses want to collect via JazzCash — the country's largest mobile-money wallet — but ERPNext ships with no JazzCash integration out of the box. Teams end up exporting invoices, chasing payment confirmations over WhatsApp, and manually stamping Payment Entries against Sales Invoices days after the money actually landed. ERPNext's generic Payment Gateway framework assumes a hosted PSP redirect (Razorpay, Stripe, PayPal, Braintree) and has no adapter for JazzCash mobile-account (MWALLET) or card transactions, nor for JazzCash's HMAC-SHA256 secure-hash signing and IPN callback contract. That gap forces a reconciliation process that is slow, error-prone, and hard to audit.
Warum JazzCash Payment Gateway for ERPNext wählen
JazzCash payment gateway controller registered against ERPNext's native `Payment Gateway Account` and `Payment Request` DocTypes
Mobile-account (MWALLET) checkout and card-payment checkout supported through a single configurable flow
`JazzCash Settings` single DocType storing Merchant ID, Password, and integrity/return salts in encrypted `Password` fields
Shareable Payment Request links plus on-invoice QR codes so customers can pay without a login
Webhook/IPN receiver as a `@frappe.whitelist(allow_guest=True)` method that verifies the `pp_SecureHash` HMAC-SHA256 before acting
Replay and tamper protection: secure-hash recomputation plus idempotency on `pp_TxnRefNo` to prevent duplicate Payment Entries
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.
Was Sie bekommen
- Installable Frappe app source code (`jazzcash_erpnext`) built for your ERPNext v15/v16 version
- Installation and configuration on your site, including gateway credential wiring and sandbox-to-production cutover
- Technical documentation: DocType reference, hooks/doc-events map, webhook contract, and secure-hash logic
- End-user guide plus a live training session for your finance and operations staff
- UAT on a staging site with a documented test plan and a rollback plan before go-live
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with full commit history and README
- Refund and reconciliation runbook covering edge cases and failed-callback recovery
Für wen das ist
Pakistani e-commerce operator
Runs an online store on ERPNext and needs shoppers to pay via JazzCash mobile wallet or card, with the payment confirmed and reconciled automatically against the Sales Invoice.
Service business finance lead
Bills clients from ERPNext and wants to send JazzCash Payment Request links or QR codes, then have Payment Entries post themselves the moment money clears — no manual matching.
ERPNext implementation partner / IT manager
Owns the ERPNext instance and needs a clean, upgrade-safe Frappe app with proper DocTypes, permissions, and a webhook receiver rather than brittle custom scripts.
Marketplace / multi-channel seller
Collects from several sales channels and needs a whitelisted API to initiate JazzCash payments from a headless storefront while keeping ERPNext as the accounting source of truth.
Installationsübersicht
Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei der JazzCash Payment Gateway for ERPNext-App von Ihrem Konto-Dashboard herunter.
Fügen Sie die App zu Ihrer Bank hinzu
Extrahieren Sie die ZIP-Datei in den Apps-Ordner Ihrer Bank oder führen Sie „bench get-app“ mit dem Pfad zur extrahierten App aus.
Installieren Sie es auf Ihrer Website
Führen Sie „bench --site SITE_NAME install-app APP_NAME“ gefolgt von „bench migrate“ aus, um JazzCash Payment Gateway for ERPNext zu installieren und sein Schema anzuwenden.
Aktivieren Sie Ihre Lizenz
Öffnen Sie die ECOSIRE-Lizenzeinstellungen auf Ihrer Website und aktivieren Sie Ihren Lizenzschlüssel. Erfordert die kostenlosen Apps ecosire_connect und ecosire_license_client.
Wie JazzCash Payment Gateway for ERPNext im Vergleich abschneidet
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| JazzCash support | Native controller for mobile-account and cards, built in | You build the JazzCash flow from scratch | May cover one channel; often India-focused PSPs | |
| Payment confirmation | Webhook IPN with secure-hash verification + atomic reconcile | Depends on your implementation quality | Basic callback, reconciliation often manual | |
| Fit to your workflow | Scoped to your trigger docs and rules before build | Fully bespoke but you own all the effort | Generic, one-size flow you adapt to | |
| Security | HMAC verify, replay/idempotency guards, scoped permissions | Only as strong as your own review | Variable; depends on the vendor | |
| Audit trail | `JazzCash Transaction` DocType logs every request and callback | You must design the logging | Often minimal transaction logging | |
| Upgrade safety | Proper Frappe app for v15/v16, handed over on Git | Risk of brittle scripts breaking on upgrade | Depends on vendor's maintenance | |
| Support & ownership | Post-go-live window + full source and repo handover | You support it yourself | Vendor SLA, no source ownership | |
| Refund handling | Built-in refund action with offsetting entry | Must be built and tested by you | Frequently out of scope |
Häufig gestellte Fragen zu JazzCash Payment Gateway for ERPNext
+How long does delivery take?
This is a build-to-order product. After a short scoping call to confirm your exact flow (credentials, mobile-account vs cards, trigger documents, refund policy), typical delivery is 2–4 weeks from confirmed scope. You get UAT on a staging site and a rollback plan before we touch production.
+Do you support ongoing support and ERPNext updates?
Yes. Every build includes a post-go-live support window for defect fixes and configuration changes, and the app is built to be upgrade-safe across Frappe/ERPNext v15/v16. Extended support and version-migration work are available as an ongoing arrangement after the initial window.
+Is this a Frappe Cloud Marketplace app I can download instantly?
No — it is not an off-the-shelf download. ECOSIRE builds, installs, and supports the app for your specific ERPNext setup. You receive the installable source and the Git repository at handover, so you fully own your version.
+How is a JazzCash payment confirmed and matched to my invoice?
Confirmation is webhook-driven. JazzCash posts an IPN/return callback to a whitelisted endpoint; we recompute the `pp_SecureHash` to reject tampered or replayed requests, and on a verified success code we create the Payment Entry and reconcile it against the referenced Sales Invoice atomically. A scheduler sweep recovers any missed callbacks.
+Does it support both mobile-account and card payments?
Yes. The gateway can be configured for JazzCash mobile-account (MWALLET) checkout, card payments, or both, depending on what your JazzCash merchant agreement enables. We wire whichever channels you need during the build.
+Can I issue refunds from ERPNext?
Yes. A controlled refund action calls the JazzCash refund API and posts the offsetting Payment Entry linked to the original transaction, with refund rights scoped to finance roles via DocType permissions.
+Will it work with my headless storefront or custom front-end?
Yes. The app exposes whitelisted methods and uses the Frappe REST API, so a headless or custom storefront can initiate JazzCash payments programmatically while ERPNext remains the accounting source of truth.
Angebot anfordern
JazzCash Payment Gateway for ERPNext
A native JazzCash mobile-account and card payment integration for ERPNext, built to your workflow by ECOSIRE. Collect payments, confirm them by webhook, and auto-reconcile against your Sales Invoices without leaving ERPNext.
- JazzCash payment gateway controller registered against ERPNext's native `Payment Gateway Account` and `Payment Request` DocTypes
- Mobile-account (MWALLET) checkout and card-payment checkout supported through a single configurable flow
- `JazzCash Settings` single DocType storing Merchant ID, Password, and integrity/return salts in encrypted `Password` fields
- Shareable Payment Request links plus on-invoice QR codes so customers can pay without a login