A build-to-order ERPNext app that extends the native Razorpay integration with RazorpayX vendor and bulk payouts, payment links, subscription billing sync, and webhook-driven settlement reconciliation. ECOSIRE builds, installs, and supports it on your bench. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A build-to-order ERPNext app that extends the native Razorpay integration with RazorpayX vendor and bulk payouts, payment links, subscription billing sync, and webhook-driven settlement reconciliation. ECOSIRE builds, installs, and supports it on your bench.
Sin pago ahora. Esto envía una solicitud de presupuesto a nuestro equipo; te responderemos por correo con precios y próximos pasos.
Indian merchants running ERPNext quickly hit the ceiling of the native Razorpay Payment Gateway integration. Out of the box, ERPNext can accept an inbound Razorpay Checkout payment against a Sales Order or web form, but it has no concept of outbound money movement, no payment-link lifecycle, no subscription reconciliation, and no automated matching of settlements against the deposits that actually land in your bank. Finance teams end up exporting the Razorpay dashboard to spreadsheets, hand-creating Payment Entries, chasing failed webhooks, and reconciling settlement UTRs manually — the exact clerical work ERPNext was supposed to remove.
Dedicated `razorpay_suite` Frappe app with its own module, DocTypes, and role profile — installed cleanly onto your bench, no core ERPNext patches
Signature-verified webhook endpoint (whitelisted method validating the `X-Razorpay-Signature` HMAC) that ingests `payment.captured`, `payment.failed`, `refund.processed`, and payout events
Idempotent Payment Entry creation keyed on the Razorpay event/payment id so retried webhooks never double-post against a Sales Order or Sales Invoice
RazorpayX vendor payouts triggered from an approved Payment Entry or Purchase Invoice via a `hooks.py` `on_submit` doc event, with beneficiary fund-account validation
Bulk payout batches for payroll runs or supplier settlements, with per-line status tracking and a consolidated `RazorpayX Payout` batch DocType
Maker-checker payout approval gated by a custom role profile and Frappe permissions so no single user can both create and release funds
ERPNext Razorpay Suite Pro is a purpose-built Frappe app (its own razorpay_suite module with dedicated DocTypes such as Razorpay Payment Link, RazorpayX Payout, Razorpay Subscription, and Razorpay Settlement) that closes those gaps end to end. On the inbound side it drives Razorpay Checkout and hosted/standard Payment Links, and a hardened webhook endpoint — a whitelisted method that verifies the X-Razorpay-Signature HMAC — turns payment.captured, payment.failed, and refund.processed events into idempotent Payment Entries against the correct party and reference document. Duplicate deliveries are de-duped on the Razorpay event id so a retried webhook never double-posts.
On the outbound side it wires the RazorpayX API for vendor payouts and bulk payout batches. An approved Payment Entry or Purchase Invoice triggers a payout via a hooks.py doc event (on_submit), with beneficiary fund-account validation, maker-checker approval gated by a custom role profile, and status sync back onto the source document as RazorpayX moves the payout through queued, processing, processed, and reversed. A scheduler event polls open payouts and pulls the daily settlement report so the Razorpay Settlement DocType reconciles gross captures, fees, GST, and net credit against your bank Account — flagging any variance instead of silently absorbing it. Subscription plans and invoices sync both ways, keeping ERPNext Subscription records and Sales Invoices aligned with Razorpay's billing cycles. Client Scripts add the Checkout and payment-link actions directly onto the relevant forms, and everything is reachable through the Frappe REST API and whitelisted methods for your own storefront or mobile app.
Because this is build-to-order, ECOSIRE builds it to your confirmed scope rather than shipping a fixed download. We start with a scoping call, agree the exact DocTypes, doc events, approval rules, and chart-of-accounts mapping, then develop, test on a staging bench, and install on your ERPNext v15 or v16 site. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full source as an installable Frappe app plus a git repository handover, so nothing is locked to us.
Runs a growing online store on ERPNext and already collects via Razorpay Checkout, but needs payment links for offline/WhatsApp sales, automatic Payment Entries, and settlement reconciliation instead of daily dashboard exports.
Owns supplier and refund payouts and wants RazorpayX vendor and bulk payouts triggered from approved Purchase Invoices, with maker-checker controls and every payout reflected in the ERPNext ledger automatically.
Bills customers on recurring Razorpay subscriptions and needs ERPNext Subscriptions and recurring Sales Invoices to stay in lockstep with Razorpay's billing cycles, dunning, and refunds.
Manages the bench and integrations and wants a clean, upgrade-safe Frappe app — signature-verified webhooks, scheduler jobs, whitelisted REST methods, and a git handover — rather than brittle server-script hacks.
Compre la licencia en ecosire.com y descargue la aplicación ZIP de ERPNext Razorpay Suite Pro desde el panel de su cuenta.
Extraiga el ZIP en la carpeta de aplicaciones de su banco o ejecute `bench get-app` con la ruta a la aplicación extraída.
Ejecute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench migrar` para instalar ERPNext Razorpay Suite Pro y aplicar su esquema.
Abra la configuración de licencia de ECOSIRE en su sitio y active su clave de licencia. Requiere las aplicaciones gratuitas ecosire_connect y ecosire_license_client.
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| Inbound payments | Checkout + hosted/standard payment links with idempotent Payment Entries | Whatever you scope and build yourself | Usually Checkout only, some add links | |
| RazorpayX payouts | Vendor + bulk payouts from approved invoices, status synced back | Buildable but significant effort | Rarely covered end to end | |
| Settlement reconciliation | Scheduler pulls settlements, matches fees/GST/net vs bank, flags variance | Must be designed from scratch | Typically manual or absent | |
| Subscription sync | Two-way Razorpay ↔ ERPNext Subscription + recurring invoices | Depends on your build | Partial or one-directional | |
| Webhook security | HMAC-verified, de-duped on event id, retry-safe | Only as good as your implementation | Varies; often basic | |
| Approval controls | Maker-checker payout release via custom role profile | You implement it | Seldom included | |
| Delivery & ownership | Build-to-order 2–4 wks, full source + git handover | Your own timeline and code | Instant download, vendor-controlled updates | |
| Support | Post-go-live window + optional maintenance retainer | Self-supported | Generic marketplace support |
ERPNext core only accepts inbound Razorpay Checkout payments against a Sales Order or web form. Razorpay Suite Pro adds outbound RazorpayX vendor and bulk payouts, hosted/standard payment links, two-way subscription sync, signature-verified webhook-driven Payment Entries, and automated settlement reconciliation against your bank — none of which native ERPNext provides.
This is a build-to-order app, not an instant download. Typical delivery is 2–4 weeks from confirmed scope. The timeline starts once we've agreed the exact DocTypes, doc events, approval rules, and account mapping on a scoping call, then we develop, test on a staging bench, and install.
We build and test against ERPNext / Frappe v15 and v16. During scoping we confirm your exact version and bench setup so the app is pinned and installed cleanly, with no patching of ERPNext core.
Every build includes a post-go-live support window for defect fixes and configuration help. Because you receive the full source and a git repository handover, your own team or ECOSIRE can maintain it. Ongoing maintenance and version-upgrade retainers are available separately if you want us to keep it current with Razorpay API and ERPNext releases.
Yes. The webhook is a whitelisted Frappe method that verifies the `X-Razorpay-Signature` HMAC before doing anything, and every event is de-duplicated on the Razorpay event/payment id. A retried or replayed webhook will never create a duplicate Payment Entry, and payout release is gated by a maker-checker role profile.
You own it. You receive the complete `razorpay_suite` Frappe app as installable source plus a git repository handover with full history. Nothing is obfuscated or license-locked, so any Frappe developer can maintain or extend it.
Yes. The app exposes whitelisted methods over the Frappe REST API so your front-end can create payment links, initiate Checkout, and read live payment and payout status. We agree the exact endpoints and payloads during scoping.
A build-to-order ERPNext app that extends the native Razorpay integration with RazorpayX vendor and bulk payouts, payment links, subscription billing sync, and webhook-driven settlement reconciliation. ECOSIRE builds, installs, and supports it on your bench.