Razorpay & India Rails
Selling to India means UPI-first checkout, netbanking long-tail, and settlement mechanics that differ from Western gateways. Razorpay bundles the rails; the integration makes them agree with your orders.
Indian payment behavior is its own design problem: UPI dominates, cards behave differently, netbanking refuses to die, and checkout that treats these as an afterthought leaks conversions that never show up in Western analytics. Razorpay puts all the rails behind one integration — the work is making checkout feel native to how India actually pays, and making your order system believe what the money is doing.
The build covers the standard surface — checkout integration, subscription objects where recurring billing applies (an Indian e-mandate world with its own rules), webhook confirmation, refunds — plus the India-specific half: settlement timing visibility, GST-ready invoice data flowing to your accounting layer, and the practical notes (notification templates, failed-payment recovery) that come from operating here rather than reading docs abroad. This desk runs on these rails itself; the India market page covers the client-side view.
Honest boundary: KYC, RBI compliance and gateway approval are Razorpay's onboarding process — the integration starts where the account is live. Scope follows the brief; fixed quote.
What the engagement covers
- Checkout integration covering UPI, cards, netbanking and wallets through one flow
- Subscription and e-mandate setup where recurring billing applies
- Webhook handling: capture, failure, refund — verified against Razorpay's dashboard
- GST-ready invoice and settlement data mapped to your records
- Failed-payment recovery surface: retry UX and notification flow
- End-to-end tests in Razorpay test mode, then one small live transaction
Honest limits
What this is deliberately not.
Not this: Gateway account approval and KYC — Razorpay's onboarding; the build starts from a live account
Not this: Tax registration advice — your CA's jurisdiction; the integration carries the data, not the counsel
Not this: Guarantees on bank-side uptime during netbanking outages — the rails have weather; handling is graceful, not magical
Not this: Cash-pickup or COD logistics — a different problem family entirely
Questions · Razorpay
Asked before building.
For many segments, yes — and the failure mode is subtle: a card-heavy checkout does not just convert worse, it converts invisibly worse, because customers bounce without errors. UPI-first ordering with cards and netbanking behind it is the default this build recommends, adjusted to your actual audience data where you have it.
Yes, with the right Razorpay account structure — it is a common cross-border setup, and the honest complications are KYC and settlement currency, not the code. The India market page covers the market context; the gateway decides account eligibility.
Through e-mandates — RBI's recurring-payment framework, with its own authentication flow and amount rules. Razorpay exposes it cleanly; the integration maps your billing plans onto it and handles the mandate-failure paths (retries, fallbacks, dunning) that Western card-on-file habits do not cover. It is setup work, not a gamble.
WooCommerce, yes — Razorpay maintains a plugin and the work is configuration plus the reconciliation layer. Shopify India supports Razorpay through their payment settings on Indian stores. Custom stacks get the API build. The scoping call names which of the three your case is.
Related: all integrations · the integrations stack page · the requirements template.
Also in this section
Stripe Integration · PayPal Integration · POS & Inventory Syncs · Twilio: SMS & Voice · WhatsApp Business API · Email Stack & Deliverability · all →
Scoping something in this space?
Written scope within two business days — deliverables, milestones, timeline, terms, price at the bottom. Compare it against anyone.