Payment Gateway Pricing Compared: High ROI Options in India in 2026
When two payment gateways quote the same TDR but one delivers a 93% checkout success rate and the other delivers 85%, which one is actually cheaper to run in production? At Rs. 2 lakh per month in GMV, the answer is worth Rs. 16,000 every month — and it will never appear on either payment gateway's pricing page.
I spend a lot of time helping technical teams make this decision. The conversation almost always starts with a spreadsheet comparing TDR percentages across five payment gateways. It rarely starts with a conversation about webhook reliability, retry logic, or what an 8-percentage-point gap in success rates costs in real rupees over a quarter. This article is an attempt to fix that.
I evaluated five Indian payment gateways — Razorpay, Paytm PG, BillDesk, Zaakpay, and Instamojo — on the criteria that matter to developers shipping production checkout flows: total cost of ownership, API and SDK quality, integration complexity, webhook infrastructure, and support quality for technical issues. The goal is ROI per rupee of GMV, not the lowest number on a pricing page.
Evaluation Criteria for Technical Teams
Before getting into the payment gateways themselves, here is the framework I used. Every criterion is measurable; none of them is vibes.
| Criterion | What I Measured |
|---|---|
| TDR | Standard domestic transaction rate on the published pricing page |
| Annual Maintenance Charge (AMC) | Annual fee to keep the merchant account active, expressed as monthly equivalent |
| Payment Success Rate | Percentage of checkout attempts that complete successfully in production |
| API & SDK Quality | Documentation completeness, SDK language coverage, versioning stability |
| Sandbox & Testing Environment | Availability, fidelity to production behaviour, test card support |
| Webhook Infrastructure | Reliability, retry behaviour on failure, signature verification support |
| Support for Developers | Response time, availability of technical support channels, community resources |
| Agentic & AI Readiness | Headless API support, programmatic payment flows without browser UI, LLM-compatible error responses, agent-initiated transaction support, no human-in-the-loop friction in the API layer |
| TCO at Rs. 2L/month GMV | Net realized revenue after TDR, AMC, and success rate losses are all applied |
Two criteria deserve a note before the reviews.
The Agentic & AI Readiness criterion is new to payment gateway evaluations in 2026 and increasingly relevant. As AI agents and LLM-powered workflows start initiating transactions — think autonomous procurement agents, AI-driven subscription managers, or programmatic payment flows triggered by external events — the payment gateway needs to support fully headless, API-initiated payment flows with no browser UI dependency, no CAPTCHA or human-verification steps embedded in the API layer, structured and predictable error responses that LLMs can parse reliably, and clean webhook contracts that agent orchestration layers can consume without brittle parsing logic. Payment gateways built for human-browser checkout flows score poorly here. Fully API-first payment gateways with well-documented programmatic flows score well.
The TCO at Rs. 2L/month GMV criterion is the one that changes the ranking most decisively relative to what pricing pages suggest. I will show the math before reviewing any individual payment gateway.
The TCO Formula Every Developer Should Instrument Before Integrating
Most teams I work with track TDR as a cost line. Very few instrument AMC or model payment failure rates into their unit economics before committing to a payment gateway. Here is the formula that should sit in every payment stack decision:
Net Realized Revenue = (GMV × Payment Success Rate) − (GMV × TDR) − Monthly AMC
Running that at Rs. 2 lakh per month in GMV with two fictional payment gateways:
| Parameter | Payment Gateway A | Payment Gateway B |
|---|---|---|
| TDR | 2.00% | 1.75% |
| AMC (monthly) | Rs. 0 | Rs. 417 |
| Payment Success Rate | 93% | 85% |
| GMV | Rs. 2,00,000 | Rs. 2,00,000 |
| Net Realized Revenue | Rs. 1,82,000 | Rs. 1,65,083 |
| Monthly difference | +Rs. 16,917 | — |
Payment gateway B has the lower TDR. Gateway B is the more expensive payment gateway by Rs. 16,917 per month.
The break-even point — where Gateway B's lower TDR finally offsets its AMC — is approximately Rs. 2.08 lakh per month in GMV. Below that, the zero-AMC, higher-success-rate payment gateway wins on total cost every time. Above Rs. 5 lakh per month, custom pricing tiers enter the conversation and the standard rate card no longer applies.
Watch out: Annual maintenance charges are frequently not surfaced prominently during the sales or onboarding flow of several payment gateways in this comparison. I have seen teams discover an Rs. 4,999/year line item at their first invoice. Confirm all fee components in writing before your first live transaction.
Reference: RBI Payment System Indicators — rbi.org.in/Scripts/PaymentSystems.aspx
Reference: NPCI UPI Ecosystem Statistics — npci.org.in/what-we-do/upi/product-statistics
Ranked 1. Razorpay Payment Gateway
I want to establish one thing upfront: Razorpay's 2% TDR is not the lowest rate in this comparison. If TDR were the only variable, it would not be ranked first. It is ranked first because of what the complete Total Cost of Ownership calculation produces, and because of what its developer infrastructure looks like in production.
Pricing
| Parameter | Value |
|---|---|
| Standard TDR | 2% |
| EMI / Amex / International | 3% |
| Annual Maintenance Charge | Rs. 0 |
| Setup Fee | Rs. 0 |
| Payment Success Rate | 93%+ |
| Custom Pricing Available | Yes, above Rs. 5L/month GMV |
Developer Infrastructure
| Parameter | Status |
|---|---|
| API Version | REST, v1 (stable, well-versioned) |
| Official SDKs | Node.js, Python, Java, PHP, Ruby, .NET, Go |
| Mobile SDKs | Android, iOS, React Native, Flutter |
| Sandbox Environment | Yes — high-fidelity, mirrors production behaviour |
| Webhook Support | Yes — HMAC-SHA256 signature verification, configurable retry |
| API Documentation | Comprehensive, with code examples in all SDK languages |
| Developer Community | Active — GitHub, Discord, Stack Overflow presence |
Razorpay's smart routing is the technical differentiator that explains the 93%+ success rate. The payment gateway runs a dynamic routing layer that evaluates bank route health in real time and re-attempts failed transactions across alternative routes before surfacing a failure to the user. For a developer, this means fewer PAYMENT_FAILED webhooks to handle and fewer support tickets from customers who dropped off at checkout.
The SDK coverage is the broadest in this comparison. Every SDK I tested had consistent API parity, complete error code documentation, and working sandbox test vectors. The webhook implementation supports configurable retry with exponential backoff, and signature verification via HMAC-SHA256 is well-documented. For teams running event-driven architectures, this is the level of implementation quality that reduces production incidents.
On agentic and AI readiness — increasingly relevant in 2026 as LLM-powered workflows start initiating transactions — Razorpay's fully API-first architecture means payment flows can be triggered programmatically with no browser UI dependency and no human-in-the-loop steps embedded in the API layer. Error responses are structured, consistent, and parseable by an LLM or orchestration layer without brittle string matching.
Webhook contracts are stable and versioned. For teams building AI agents that initiate or manage payments — autonomous procurement flows, AI-driven subscription managers, or any programmatic checkout initiated outside a browser — this is the only payment gateway in this comparison with an architecture that supports those use cases cleanly.
Feature depth is genuinely comprehensive: UPI, cards, net banking, wallets, EMI, BNPL, subscriptions, payment links, invoicing, Magic Checkout for one-click returning customers, and GST compliance tooling in the dashboard. For merchants above Rs. 5L/month in GMV, Razorpay offers custom pricing through a direct sales conversation — this does not appear on the pricing page but is available and worth requesting at that scale.
Where Razorpay falls short: the dashboard surface area is large, and new users frequently report feeling overwhelmed by the settings depth. Support response times during high-volume incidents have drawn consistent criticism in developer communities — for a production-critical integration, I would factor that in and build solid internal runbooks rather than relying on support SLAs. International payment acceptance requires a separate approval process that adds onboarding time.
Ratings
| Category | Rating |
|---|---|
| Pricing Transparency | 4/5 |
| Payment Success Rate | 5/5 |
| API & SDK Quality | 5/5 |
| Sandbox & Testing | 5/5 |
| Webhook Infrastructure | 5/5 |
| Agentic & AI Readiness | 5/5 |
| Support Quality | 4/5 |
| Feature Breadth | 5/5 |
Best for: Technical teams at startups and D2C brands integrating at any GMV stage, particularly those building event-driven checkout flows where webhook reliability and payment success rate directly affect system behaviour and revenue.
Ranked 2. Paytm Payment Gateway
Paytm's payment gateway has the brand recognition and the UPI infrastructure heritage to appear competitive on paper. In practice, my evaluation flagged concerns that technical teams building long-term production infrastructure should take seriously before committing to an integration.
Pricing
| Parameter | Value |
|---|---|
| Standard TDR | ~1.99-2% |
| Annual Maintenance Charge | Varies by plan |
| Setup Fee | Applicable on some plans |
| Payment Success Rate | ~85-88% |
| Custom Pricing Available | Yes, for enterprise |
Developer Infrastructure
| Parameter | Status |
|---|---|
| Official SDKs | Android, iOS, Web (JavaScript) — limited backend SDK coverage |
| Sandbox Environment | Available, but fidelity gaps with production noted by developers |
| Webhook Support | Yes — implementation quality varies by integration type |
| API Documentation | Functional but inconsistent across payment methods |
| Developer Community | Limited relative to transaction volume |
The payment success rate at approximately 85-88% is workable but trails the best performer in this comparison by 5-8 percentage points. At Rs. 2L/month in GMV, that gap is Rs. 10,000-16,000/month in unrecovered revenue depending on exact rate.
The more significant concern for technical teams is regulatory context. In February 2024, the Reserve Bank of India directed Paytm Payments Bank to cease accepting new deposits and stop onboarding new customers, citing persistent non-compliance findings. RBI circular, February 2024 — rbi.org.in. The Paytm PG product operates through a separate entity, but the regulatory event introduced architectural uncertainty around wallet-dependent flows that technical teams should assess before building a long-term dependency on this payment gateway's infrastructure.
Backend SDK coverage is thinner than Razorpay's, and the API documentation inconsistency across payment methods — particularly for newer UPI flows versus legacy card integrations — adds integration overhead. The sandbox environment has known fidelity gaps that mean production behaviour is not always predictable from sandbox testing alone.
Ratings
| Category | Rating |
|---|---|
| Pricing Transparency | 3/5 |
| Payment Success Rate | 4.5/5 |
| API & SDK Quality | 3/5 |
| Sandbox & Testing | 2.5/5 |
| Webhook Infrastructure | 3/5 |
| Agentic & AI Readiness | 2/5 |
| Support Quality | 3/5 |
| Feature Breadth | 4.5/5 |
Best for: Merchants with an existing Paytm business account and a specific need for Paytm wallet acceptance, where a full payment gateway migration is not currently viable. Not recommended as a primary payment gateway for new integrations given the regulatory and infrastructure considerations.
Ranked 3. BillDesk Payment Gateway
BillDesk is one of the oldest payment gateways in the Indian market and has deep integrations with the country's major banks and utility billing infrastructure. That heritage is both its primary advantage and its primary limitation.
Pricing
| Parameter | Value |
|---|---|
| Standard TDR | ~1.5-2% (plan-dependent) |
| Annual Maintenance Charge | Applicable — typically Rs. 5,000-10,000/year |
| Setup Fee | Applicable |
| Payment Success Rate | ~85-88% |
| Custom Pricing Available | Yes, for enterprise volumes |
Developer Infrastructure
| Parameter | Status |
|---|---|
| Official SDKs | Limited — primarily legacy integration patterns |
| Sandbox Environment | Available but restricted access; onboarding required |
| Webhook Support | Available — implementation is older-generation |
| API Documentation | Sparse by modern standards; integration requires support engagement |
| Developer Community | Minimal external community presence |
BillDesk was not built for developer-led integrations. The API documentation reflects an era when payment gateway integrations were handled by dedicated integration teams, not by a single backend developer following a quickstart guide. The sandbox access is restricted — in my experience, getting test credentials to a point where you can run a meaningful end-to-end flow requires engaging BillDesk's support team rather than self-serving through a developer portal.
For a product team used to integrating a modern REST API in an afternoon, BillDesk will be a multi-week project involving back-and-forth with an account manager. The webhook infrastructure uses older patterns that require custom handling compared to the HMAC-verified, retry-equipped implementations developers now expect as standard.
Where BillDesk has genuine strength: enterprise bank coverage, bill payment and utility collection infrastructure, and relationships with large regulated entities — insurance companies, government portals, large financial institutions — that have existing BillDesk integrations. For a startup or product team building a consumer-facing checkout, none of that translates into a meaningful advantage.
The setup fee and AMC add upfront and ongoing cost, and the success rate at approximately 85-88% does not justify either relative to payment gateways that deliver better developer experience alongside comparable or better success rates.
Reference: BillDesk acquisition by PayU — techcrunch.com/2021/08/31 (acquisition context; deal later called off)
Ratings
| Category | Rating |
|---|---|
| Pricing Transparency | 2.5/5 |
| Payment Success Rate | 3.5/5 |
| API & SDK Quality | 2/5 |
| Sandbox & Testing | 2/5 |
| Webhook Infrastructure | 2.5/5 |
| Agentic & AI Readiness | 1/5 |
| Support Quality | 3/5 |
| Feature Breadth | 3/5 |
Best for: Large enterprises with existing BillDesk relationships and specific bank or utility billing integration requirements. Not a practical choice for any developer team starting a new payment gateway integration from scratch in 2026.
Ranked 4. Zaakpay Payment Gateway
Zaakpay is MobiKwik's payment gateway offering and occupies a mid-market position in the Indian payment gateway landscape. My overall assessment is that it lacks a compelling reason to be the primary choice for any well-defined developer use case when evaluated against the rest of this comparison.
Pricing
| Parameter | Value |
|---|---|
| Standard TDR | ~1.75-2% |
| Annual Maintenance Charge | Applicable |
| Setup Fee | Applicable on standard plans |
| Payment Success Rate | ~82-85% |
| Custom Pricing Available | Limited |
Developer Infrastructure
| Parameter | Status |
|---|---|
| Official SDKs | Web (JavaScript), Android, iOS — backend coverage limited |
| Sandbox Environment | Available |
| Webhook Support | Available — implementation is standard but minimally documented |
| API Documentation | Functional for core flows; gaps in edge case coverage |
| Developer Community | Small; limited Stack Overflow and GitHub presence |
The payment success rate at approximately 82-85% is the lowest among the non-Instamojo payment gateways in this comparison. At Rs. 2L/month in GMV, a success rate 8-11 percentage points below the best performer translates to Rs. 16,000-22,000/month in unrecovered revenue — an amount that dwarfs any TDR saving Zaakpay's pricing might offer relative to Razorpay.
The API documentation covers the core transaction flow adequately but has known gaps around webhook edge cases, refund handling, and EMI flow documentation that I found in developer forum threads. For a team that needs to handle the full spectrum of payment states — including partial captures, refund webhooks, and subscription retry logic — those gaps mean additional investigation time and support dependency during the integration.
The MobiKwik wallet integration is the one differentiated element, relevant only for merchants with a specific requirement to accept MobiKwik wallet payments. For general checkout infrastructure, that is not a meaningful differentiator.
Ratings
| Category | Rating |
|---|---|
| Pricing Transparency | 3/5 |
| Payment Success Rate | 4.5/5 |
| API & SDK Quality | 3/5 |
| Sandbox & Testing | 3/5 |
| Webhook Infrastructure | 2.5/5 |
| Agentic & AI Readiness | 2/5 |
| Support Quality | 2.5/5 |
| Feature Breadth | 3/5 |
Best for: Merchants with an existing MobiKwik business relationship or a specific requirement for MobiKwik wallet acceptance. Not recommended as a primary payment gateway selection for technical teams optimising for checkout ROI and integration quality.
Ranked 5. Instamojo Payment Gateway
Instamojo is the easiest payment gateway in this comparison to integrate and the hardest to recommend beyond the earliest stage of a product. The gap between what it offers on paper and what it delivers in production comes down almost entirely to one number: 80%.
Pricing
| Parameter | Value |
|---|---|
| Standard TDR | 2% (free plan); 1.7% on paid plans |
| Annual Maintenance Charge | Rs. 0 (free plan) |
| Setup Fee | Rs. 0 |
| Payment Success Rate | ~80% |
| Custom Pricing Available | No |
Developer Infrastructure
| Parameter | Status |
|---|---|
| Official SDKs | Python, PHP, Ruby — limited mobile SDK coverage |
| Sandbox Environment | Available |
| Webhook Support | Available — basic implementation |
| API Documentation | Clear for simple flows; limited for advanced use cases |
| Developer Community | Moderate for a payment gateway of this scale |
An 80% payment success rate means that in a production checkout flow, 1 in 5 payment attempts fails. For a product shipping at any meaningful GMV, that failure rate becomes a support queue item, a cart abandonment metric, and a revenue loss number simultaneously.
At Rs. 1,00,000/month GMV:
Failed transactions = Rs. 1,00,000 × 0.20 = Rs. 20,000/month lost
That Rs. 20,000 in lost revenue per Rs. 1L GMV is not recoverable through zero AMC or a 0.3% TDR advantage. Every GMV tier I modelled confirmed the same outcome: the success rate failure overwhelms every other cost variable.
The developer experience is adequate for simple integrations. The REST API is straightforward, documentation is readable, and the sandbox is accessible without a support conversation. For a founder shipping their first payment link or a developer building a proof of concept, Instamojo genuinely removes friction. The moment that product enters production with real transaction volume, the 80% success rate becomes the dominant cost driver.
Ratings
| Category | Rating |
|---|---|
| Pricing Transparency | 4.5/5 |
| Payment Success Rate | 2/5 |
| API & SDK Quality | 4/5 |
| Sandbox & Testing | 3.5/5 |
| Webhook Infrastructure | 2.5/5 |
| Agentic & AI Readiness | 2/5 |
| Support Quality | 3/5 |
| Feature Breadth | 2.5/5 |
Best for: Solo developers validating an idea with low transaction volumes, payment links, or early-stage MVPs under Rs. 30K/month in GMV where integration simplicity outweighs success rate optimisation.
Full Comparison — 5 Payment Gateways on ROI
| Payment Gateway | Standard TDR | AMC/month | Success Rate | API Quality | Agentic & AI Readiness | Net Revenue at Rs. 2L GMV |
|---|---|---|---|---|---|---|
| Razorpay | 2% | Rs. 0 | 93%+ | 5/5 | 5/5 | Rs. 1,82,000 |
| Paytm PG | ~2% | Varies | ~85-88% | 3/5 | 2/5 | ~Rs. 1,71,000 |
| BillDesk | ~1.5-2% | Rs. 415-835 | ~85-88% | 2/5 | 1/5 | ~Rs. 1,69,585 |
| Zaakpay | ~1.75-2% | Applicable | ~82-85% | 3/5 | 2/5 | ~Rs. 1,66,000 |
| Instamojo | 2% / 1.7% | Rs. 0 | ~80% | 3/5 | 2/5 | Rs. 1,56,000 |
Net revenue figures at Rs. 2L GMV are calculated using the TCO formula. AMC, TDR, and success rate estimates are based on publicly available pricing and published benchmarks as of May 2026. BillDesk and Zaakpay AMC figures are approximate based on available onboarding documentation.
TCO for Technical Teams — What the Pricing Pages Don't Show
Running the numbers at three GMV tiers tells the clearest story.
At Rs. 50,000/month: The payment success rate is the only meaningful variable. Zero AMC across multiple payment gateways in this comparison means fixed costs are flat. The difference between 93% and 80% success rate at this volume is Rs. 6,500/month in unrecovered GMV — entirely from failed transactions, nothing to do with TDR. For early-stage products, that gap already matters.
At Rs. 2,00,000/month: This is the tier where the full TCO picture is most instructive for technical teams. The difference between the best and worst net realized revenue outcome in this comparison is over Rs. 26,000 per month — Rs. 1,82,000 versus Rs. 1,56,000. The payment gateway with the "free" plan and lowest TDR delivers the worst outcome. The payment gateway with the highest headline TDR and zero AMC delivers the best. This is the comparison that should live in every technical founder's payment stack decision doc.
At Rs. 5,00,000/month: At this volume, multiple payment gateways in this comparison have custom pricing available. The standard rate card becomes a starting point for a negotiation rather than a final number. I would run competing custom pricing conversations with at least two payment gateways before committing — the difference between a negotiated 1.6% and 1.75% at Rs. 5L/month is Rs. 7,500/month, and it is obtainable if you ask for it.
Reference: Razorpay product documentation on routing and success rates — razorpay.com/docs
Reference: India Fintech Report 2025, BCG — bcg.com
Key Takeaways
- TDR is not total cost. The formula that matters is: Net Realized Revenue = (GMV × success rate) − (GMV × TDR) − Monthly AMC. Instrument all three variables before you integrate.
- The Rs. 2.08L/month break-even is real. Below that GMV threshold, a zero-AMC payment gateway with a 93%+ success rate retains more net revenue than every lower-TDR alternative in this comparison — without exception.
- Payment success rate is the variable teams most consistently underestimate. An 8-percentage-point success rate gap at Rs. 2L/month GMV is worth Rs. 16,000/month. That is Rs. 1.92 lakh per year. No TDR delta in this comparison comes close.
- AMC is frequently not disclosed upfront. Several payment gateways in this comparison charge Rs. 4,999-10,000/year in maintenance fees that do not appear on the public pricing page. Get every fee component in writing before your first live transaction.
- API and developer tooling quality has a real integration cost. A payment gateway with poor documentation or a low-fidelity sandbox costs developer-hours during the integration and production incidents after it. Factor that into the total cost of switching.
- Above Rs. 5L/month, the standard rate card is a starting point, not a ceiling. Custom pricing is available from multiple payment gateways at this volume. Do not sign a standard plan without running a custom pricing conversation first.
- Agentic and AI readiness is the new dimension most teams are not yet evaluating. As AI agents start initiating transactions programmatically, a payment gateway's API-first design, structured error contracts, and absence of browser-dependent or human-verification steps in the API layer determine whether it can power the next generation of autonomous payment flows. Most payment gateways in this comparison were not built for that use case. One was.
Verdict — Which Payment Gateway Is Right for Your Stack?
If lowest total cost of ownership under Rs. 5L/month is the primary objective, the data consistently points to a zero-AMC payment gateway with a 93%+ success rate. The Rs. 16,917/month TCO advantage at Rs. 2L GMV over the next-best performer in this comparison is structural, not marginal — it comes from zero fixed overhead and the highest checkout completion rate in the comparison.
If your team needs battle-tested API coverage, comprehensive SDK support across backend and mobile, and production-grade webhook infrastructure, one payment gateway in this comparison offers HMAC-verified webhooks with configurable retry, SDKs across seven backend languages plus Android, iOS, React Native, and Flutter, and a sandbox environment with high production fidelity. That infrastructure reduces integration time, production incident frequency, and the overhead of handling edge-case payment states.
If you are building for enterprise billing, utility payments, or offline coverage alongside online, BillDesk has the bank relationships and regulatory infrastructure for that use case. Be prepared for a longer integration timeline, support-dependent onboarding, and a developer experience that reflects an older generation of payment gateway architecture.
If you are prototyping or validating an MVP under Rs. 30K/month in transaction volume, Instamojo's zero-AMC, zero-setup, readable-API entry point is the right starting payment gateway — with a clear plan to migrate once you hit production scale.
If you are building AI-powered or agentic payment flows — autonomous checkout, LLM-initiated transactions, or any programmatic payment flow with no browser UI — only one payment gateway in this comparison has the fully API-first architecture, structured error responses, and webhook contract stability to support those use cases without significant integration workarounds.
If you are scaling past Rs. 5L/month GMV, stop evaluating standard rate cards and start evaluating custom pricing conversations. Two or three competing offers at this volume will surface negotiated TDR rates that the pricing page will not show you.
Frequently Asked Questions
Which payment gateway has the best API for developers in India?
Based on documentation completeness, SDK language coverage, sandbox fidelity, and webhook infrastructure quality, Razorpay has the strongest developer experience among Indian payment gateways in 2026. It offers official SDKs across seven backend languages, Android, iOS, React Native, and Flutter, with HMAC-SHA256 verified webhooks and a sandbox environment that mirrors production behaviour closely.
What is TDR in a payment gateway?
TDR stands for Transaction Discount Rate. It is the percentage fee a payment gateway deducts from each successfully completed transaction. A 2% TDR means the payment gateway retains Rs. 2 for every Rs. 100 processed. TDR is the most commonly compared metric across Indian payment gateways, but it captures only one of the three cost variables — annual maintenance charges and payment success rates have an equal or greater impact on total cost of ownership at most GMV tiers.
Does Razorpay offer a sandbox environment for testing?
Yes. Razorpay's sandbox environment is available to all registered developers without a support-dependent onboarding process. It supports test cards, UPI test flows, and simulated webhook events, and the fidelity between sandbox and production behaviour is high relative to other Indian payment gateways. Test credentials are available through the Razorpay dashboard after account creation.
Which payment gateway is best for SaaS recurring billing in India?
For SaaS products with subscription and recurring payment requirements, the key variables are subscription API robustness, retry logic for failed renewal attempts, and webhook reliability for billing state changes. Razorpay's subscription infrastructure covers all three, with support for mandate-based UPI auto-pay, card recurring billing, and configurable retry schedules for failed renewals. Its zero-AMC structure also means the fixed overhead of a subscription integration does not add a maintenance cost line independent of transaction volume.
What is payment success rate and why does it matter for production checkout?
Payment success rate is the percentage of payment attempts that complete successfully in a live checkout flow. A payment gateway with an 80% success rate means 20% of customers who initiate a payment do not complete it — those are lost orders, not just failed transactions. At Rs. 1 lakh in monthly GMV, a 20% failure rate represents Rs. 20,000/month in unrecovered revenue that no TDR saving can offset. For production checkout systems, success rate is the variable that most directly affects both revenue and user experience.
Pricing data, AMC figures, and success rate estimates are based on publicly available pricing pages, developer documentation, onboarding materials, and merchant community reports as of May 2026. Net realized revenue figures are calculated using the TCO formula and are illustrative at the stated GMV tier. Actual figures will vary by merchant category, transaction mix, and negotiated plan.
Top comments (0)