Indian ERPNext merchants who sell online or collect payments against invoices keep hitting the same wall: ERPNext ships a Payment Gateway framework and connectors for a handful of providers, but there is no first-party PhonePe integration. PhonePe carries a dominant share of India's UPI volume, so the moment you want customers to pay by UPI intent (open the PhonePe app straight from checkout), scan a dynamic QR, or use cards and netbanking through PhonePe's Standard Checkout, you are left stitching together portal JavaScript, manual payment entries, and spreadsheet reconciliation. That gap is exactly what this build-to-order integration closes.

We build a proper Frappe app — for example phonepe_erpnext — that registers PhonePe as a first-class Payment Gateway and a Payment Gateway Account, so it plugs into the same flows ERPNext already uses for Payment Requests on Sales Orders, Sales Invoices, POS, and web checkout. The app adds its own DocTypes (a PhonePe Settings single for merchant ID, salt key, salt index, and environment; a PhonePe Transaction log linked to the source Payment Request and voucher) and exposes whitelisted methods via the Frappe REST API to create a payment, redirect or launch the UPI intent, and receive the provider callback. Signatures are computed and verified server-side using PhonePe's X-VERIFY SHA-256 checksum scheme so no secret ever touches the browser.

Technically, the payment lifecycle is driven by hooks.py doc events and scheduler events rather than manual clicking. A PhonePe Transaction moves through created → pending → paid/failed states; the webhook (and a scheduler_events status-check job as a fallback for missed callbacks) verifies the checksum, calls PhonePe's payment-status API to confirm, and then submits a Payment Entry reconciled against the correct invoice — idempotently, so a retried webhook never double-posts. Refund and status-verification endpoints are wired to PhonePe's refund API and reflected back onto the linked ERPNext documents. Role-based permissions and a dedicated role profile keep gateway configuration and refund actions restricted, and client scripts drive the UPI collect / QR experience on the checkout and portal pages. Everything targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, you are not downloading a generic marketplace app and hoping it fits. We start with a short scoping call to confirm your PhonePe merchant setup, the documents you collect against (web orders, POS, subscription invoices, quotations), and your reconciliation rules. We then build your version of the app, run it through UAT on a staging bench, and hand over installable source, a git repository, technical and user documentation, and a training session. Typical delivery is one working week from confirmed scope, followed by a post-go-live support window.