Os detalhes do produto são exibidos em inglês. Traduções em breve.
Fatos rápidos
- Preço
- $199.00 USD
- Versões ERPNext
- —
- Tempo de configuração
- 30 min
- Licença
- Uma vez perpétua
- Idiomas
- 11 idiomas
Compra Única
PhonePe Gateway for ERPNext
A build-to-order PhonePe Payment Gateway integration for ERPNext covering UPI intent/collect, QR, cards, netbanking and wallet, with signed webhook reconciliation against Sales Orders and Sales Invoices. ECOSIRE scopes, builds, installs and supports it — this is not an instant download.
$199.00USD
Sem pagamento agora. Isto envia um pedido de orçamento à nossa equipe — responderemos por e-mail com preços e próximos passos.
Recursos Principais
Registers PhonePe as a native ERPNext `Payment Gateway` + `Payment Gateway Account`, integrating with the standard Payment Request flow on Sales Orders and Sales Invoices
UPI intent flow that deep-links straight into the PhonePe app from web checkout and portal on mobile
UPI collect requests and dynamic QR generation for in-person and remote collection
Cards, netbanking and wallet support via PhonePe Standard Checkout (redirect) plus Server-to-Server (S2S) API option
Server-side `X-VERIFY` SHA-256 checksum signing and verification — merchant salt key/index never exposed to the browser
Dedicated `PhonePe Settings` single DocType for merchant ID, salt key, salt index and sandbox/production environment switch
`PhonePe Transaction` log DocType linked to the originating Payment Request and target voucher for a full audit trail
Whitelisted Frappe REST methods to initiate payment, handle redirect/callback, and query transaction status
Signed webhook receiver plus a `scheduler_events` reconciliation job that re-verifies status via PhonePe's payment-status API for missed callbacks
Idempotent `Payment Entry` creation on `hooks.py` doc events — retried webhooks never double-post against an invoice
Refund and partial-refund endpoints wired to PhonePe's refund API, reflected back on the linked ERPNext documents
Role profile and permission rules restricting gateway configuration and refund actions to authorised users
Client scripts for the checkout/portal UPI + QR experience and status polling
Structured error logging and failed-payment handling with retry-safe state transitions
Built and tested for Frappe/ERPNext v15 and v16 benches
Sobre este Produto
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.
Por Que Escolher PhonePe Gateway for ERPNext
Registers PhonePe as a native ERPNext `Payment Gateway` + `Payment Gateway Account`, integrating with the standard Payment Request flow on Sales Orders and Sales Invoices
UPI intent flow that deep-links straight into the PhonePe app from web checkout and portal on mobile
UPI collect requests and dynamic QR generation for in-person and remote collection
Cards, netbanking and wallet support via PhonePe Standard Checkout (redirect) plus Server-to-Server (S2S) API option
Server-side `X-VERIFY` SHA-256 checksum signing and verification — merchant salt key/index never exposed to the browser
Dedicated `PhonePe Settings` single DocType for merchant ID, salt key, salt index and sandbox/production environment switch
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 2–4 weeks from confirmed scope, followed by a post-go-live support window.
O que você ganha
- Installable source code for your version of the PhonePe integration app (`phonepe_erpnext`)
- Installation and configuration on your bench, including PhonePe Settings, salt key/index and environment setup
- Technical documentation: DocTypes, hooks, whitelisted endpoints, webhook/checksum flow and scheduler jobs
- User guide plus a live training session for finance and operations staff
- UAT on a staging bench with a documented test matrix and a rollback plan
- Post-go-live support window for defect fixes and configuration adjustments
- Handover of the full git repository with commit history and README
- Sandbox-to-production cutover checklist and reconciliation runbook
Para quem é isso
D2C / retail ERPNext merchant on UPI
Runs an online store or POS on ERPNext and wants customers to pay via PhonePe UPI intent and QR at checkout, with payments auto-reconciled to Sales Invoices instead of matched by hand.
Finance controller chasing reconciliation
Owns the books and is tired of downloading PhonePe settlement reports and creating manual Payment Entries. Needs signed, idempotent webhook posting and a scheduler fallback so every paid order lands against the right invoice.
ERPNext implementation partner / systems integrator
Delivering ERPNext to an Indian client and needs a properly packaged, versioned PhonePe app (clean DocTypes, hooks, git repo) they can install, extend and support rather than a fragile one-off script.
Subscription / services business collecting recurring invoices
Bills recurring or milestone invoices and wants PhonePe collect requests and links generated from Payment Requests, with refunds and status checks handled inside ERPNext.
Visão geral da instalação
Baixe do ECOSIRE
Compre a licença em ecosire.com e baixe o ZIP do aplicativo PhonePe Gateway for ERPNext no painel da sua conta.
Adicione o aplicativo à sua bancada
Extraia o ZIP na pasta de aplicativos do seu banco ou execute `bench get-app` com o caminho para o aplicativo extraído.
Instale no seu site
Execute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench Migra` para instalar PhonePe Gateway for ERPNext e aplicar seu esquema.
Ative sua licença
Abra as configurações de licença ECOSIRE em seu site e ative sua chave de licença. Requer os aplicativos gratuitos ecosire_connect e ecosire_license_client.
Como PhonePe Gateway for ERPNext se compara
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Availability in ERPNext | Built to order as a native Payment Gateway integration | Built from scratch by your team | Depends on the marketplace app existing and being maintained | |
| Payment methods | UPI intent, collect, QR, cards, netbanking, wallet | Whatever you have time to implement | Often UPI/redirect only | |
| Reconciliation to invoices | Signed webhook + scheduler fallback, idempotent Payment Entry | You design and debug the whole flow | Varies; often no idempotency guarantee | |
| Security of credentials | Server-side X-VERIFY checksums, role-restricted settings | Depends on your implementation | Depends on the vendor's code quality | |
| Version support | Tested on Frappe/ERPNext v15 and v16 | Your responsibility to test | May lag behind current versions | |
| Fit to your workflow | Scoped to your documents and reconciliation rules | Fully bespoke but slow and costly | Generic; adapt your process to the app | |
| Ownership & maintainability | Full source + git repo handover, clean DocTypes and hooks | You own it but carry all the build risk | Usually closed source, vendor-locked | |
| Support after go-live | Post-go-live support window + optional ongoing updates | Self-supported | Vendor support of variable quality |
Perguntas frequentes sobre PhonePe Gateway for ERPNext
+Is this a ready-made app I can download and install right now?
No. This is a build-to-order integration. After a short scoping call, ECOSIRE builds your version of the PhonePe app, tests it on a staging bench, then installs it on your ERPNext instance. You receive installable source and the git repository at handover — it is not an instant Frappe marketplace download.
+How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on how many document types you collect against (web checkout, POS, subscriptions), your reconciliation rules, and whether you need S2S in addition to Standard Checkout. We confirm dates after the scoping call.
+Which ERPNext versions are supported?
We build and test against Frappe/ERPNext v15 and v16. If you are on an older version, tell us during scoping — we will advise on an upgrade path or a compatible build.
+Which PhonePe payment methods are covered?
UPI intent (deep-link into the PhonePe app), UPI collect and dynamic QR, plus cards, netbanking and wallet via PhonePe Standard Checkout. A Server-to-Server (S2S) API option is available where your flow needs it.
+How does reconciliation work — do I still post payments manually?
No. A signed PhonePe webhook (verified with the X-VERIFY checksum) plus a scheduler fallback job confirm each payment against PhonePe's status API and create a Payment Entry against the correct invoice idempotently. Retried webhooks never double-post.
+How are updates and support handled after go-live?
Every engagement includes a post-go-live support window for defect fixes and configuration changes. Because you own the git repository and source, you can maintain it yourself or contract ECOSIRE for ongoing updates, including compatibility work when you upgrade ERPNext.
+Are my PhonePe credentials kept secure?
Yes. The merchant ID, salt key and salt index live in a server-side `PhonePe Settings` DocType, and all X-VERIFY checksums are computed and validated on the server. No secret is ever exposed to the browser, and configuration/refund actions are restricted via role permissions.
Módulos Relacionados
Solicitar orçamento
PhonePe Gateway for ERPNext
A build-to-order PhonePe Payment Gateway integration for ERPNext covering UPI intent/collect, QR, cards, netbanking and wallet, with signed webhook reconciliation against Sales Orders and Sales Invoices. ECOSIRE scopes, builds, installs and supports it — this is not an instant download.
- Registers PhonePe as a native ERPNext `Payment Gateway` + `Payment Gateway Account`, integrating with the standard Payment Request flow on Sales Orders and Sales Invoices
- UPI intent flow that deep-links straight into the PhonePe app from web checkout and portal on mobile
- UPI collect requests and dynamic QR generation for in-person and remote collection
- Cards, netbanking and wallet support via PhonePe Standard Checkout (redirect) plus Server-to-Server (S2S) API option