India’s recurring payment landscape looks nothing like the card-first subscription markets global playbooks were written for. With retail digital payments reaching 245.5 billion transactions in FY2023-24, Indian subscription businesses operate on rails defined by UPI Autopay, RBI mandates, and tokenization rules that do not exist elsewhere.
This guide is a decision framework for SaaS founders, D2C subscription operators, and finance ops heads evaluating payment infrastructure. You will learn how a subscription gateway differs from a standard one, which RBI rules shape your pricing, how dunning protects revenue, and what to verify before you sign.
Key Takeaways
- Subscription businesses need gateways with mandate management, retry logic, and tokenization built in – these are not optional add-ons.
- RBI caps UPI Autopay mandates at ₹15,000 per transaction without AFA, directly shaping subscription pricing strategy.
- UPI processed 172.2 billion transactions in FY2023-24; UPI Autopay support is essential.
- Failed payments are a gateway problem, not a CRM problem – smart retries and dunning protect MRR directly.
- Tokenization can reduce card-not-present fraud by up to 60%, making it the standard for card-on-file recurring billing.
- A 1-second delay in load time can cut conversions by 7%; mobile mandate flows must be optimized.
- Settlement cycle flexibility affects working capital for high-frequency subscription businesses.
- Billing model fit determines how fast you can iterate on pricing.
Table of Contents
What Is a Subscription Payment Gateway – and Why It’s Different
A subscription payment gateway is built for recurring billing: it stores payment credentials securely, creates and manages mandates, charges on schedule, handles upgrades and proration, and orchestrates retries. A standard gateway focuses on one-time transactions and typically lacks three things subscriptions depend on: native mandate management, built-in retry logic, and tokenized card-on-file storage. Understanding payment gateway basics helps frame why this distinction matters.
Did You Know: UPI processed ₹200.2 trillion in value in FY2023-24, underscoring why UPI Autopay is non-negotiable for Indian subscription billing.
How Recurring Payment Processing Works – Step by Step
- Customer selects a subscription plan at checkout.
- Payment method is tokenized (card) or a mandate is created (UPI Autopay).
- Gateway stores the token or mandate reference against the customer profile.
- On each billing date, the billing system triggers the charge.
- The gateway routes to the card network, UPI, or bank for approval.
- On success, the subscription extends; on failure, retry and dunning logic activates.
- After repeated failures, the subscription pauses or cancels per your rules.
Why Standard Gateways Fall Short for Subscriptions
A SaaS founder whose gateway cannot process mid-cycle upgrades has to build proration logic manually. A D2C box brand loses renewals when cards expire and there is no account updater. These are gaps a transactional gateway forces you to engineer yourself.
The 5 Subscription Billing Models Your Gateway Must Support
Before evaluating any vendor, confirm it supports your billing model. Razorpay Subscriptions and similar products vary in model coverage.
Pro-Tip: Map your billing model to the supported list before evaluating any gateway. “Subscriptions” in general is not the same as your specific model.
Flat-Rate
The same price every cycle, like a ₹499 monthly OTT plan. Requires flexible billing cycles and automatic renewals.
Usage-Based
Pay for actual consumption, such as SaaS billing per API call. Requires the gateway to pass dynamic amounts each cycle.
Tiered / Per-Seat
Pricing scales with users or feature tiers, common in B2B SaaS. Requires mid-cycle upgrades, downgrades, and proration.
Freemium-to-Paid
A trial converts to a paid plan automatically. Requires trial handling, delayed first charge, and clean consent logs.
Hybrid
A fixed base fee plus usage, like ₹1,000 base plus a per-order fee. Requires both fixed and variable line items in one charge.
How Razorpay’s Subscriptions Product Handles Recurring Billing for Indian Businesses
Razorpay’s Subscriptions product is built for recurring collections in the Indian payment environment, supporting both UPI and card-based recurring flows. It is designed to handle the mandate lifecycle and failed-payment recovery that subscription businesses depend on.
- UPI Autopay mandate creation and management: Lets you create, manage, and collect against UPI Autopay mandates for recurring debits, mapping each mandate to a customer and subscription plan.
- Built-in retry logic for failed payments: Automatically re-attempts failed recurring charges according to configured rules, reducing manual follow-up for your operations team.
- Card and UPI recurring within a single integration: Supports tokenized card-on-file flows and UPI-based recurring collections through one integration, so you can serve different segments without separate builds.
These capabilities let subscription businesses run recurring billing across India’s primary payment methods. Explore the full feature set on the Razorpay Subscriptions page.
India’s Recurring Payment Compliance Rules
This is where Indian subscription billing diverges most from global models. Razorpay’s Subscriptions product is built to support RBI-compliant mandate flows, including the pre-debit notification requirements that apply to recurring collections. For a deeper explainer, see RBI e-mandate regulations.
Pro-Tip: Ask the gateway whether pre-debit notifications are handled automatically or if you must build that workflow yourself.
RBI’s Additional Factor of Authentication (AFA) Requirement
RBI mandates AFA for card-not-present transactions. For recurring cards, this typically means a one-time AFA at mandate registration, with later debits processed under the e-mandate framework. This is why global one-click subscription patterns do not translate directly to India.
Did You Know: RBI requires AFA for card-not-present transactions in India, a core reason Indian recurring flows differ from global checkout patterns.
UPI Autopay Mandate Limits and What They Mean for Your Pricing
RBI permits UPI Autopay recurring debits without AFA up to ₹15,000 per transaction. Plans above this threshold need additional authentication or a card-based mandate strategy, which directly shapes whether you price monthly or annually.
Pre-Debit Notifications – A Legal Requirement
RBI requires customers to receive a notification before each recurring debit, usually via SMS or email. Your gateway, not just your CRM, should automate this and let you control timing and content.
Card-on-File Tokenization Under RBI Rules
Merchants cannot store raw card numbers. Card-on-file must be tokenized under RBI’s framework. For the customer, this means one-time consent followed by seamless renewals.
Failed Payments and Revenue Recovery
Involuntary churn is a gateway problem, not a billing-platform afterthought. Razorpay’s Subscriptions product includes built-in retry logic for failed recurring payments, reducing manual intervention from operations teams. Learn more on the Razorpay Subscriptions page.
Did You Know: Card expiry and unexpected bank declines are among the most common causes of card-not-present payment failures.
What Causes Subscription Payment Failures in India
Common causes include card expiry and reissuance, insufficient funds, bank-side declines, paused or revoked UPI mandates, and network timeouts. Each needs different handling.
Smart Dunning – How Retry Logic Protects MRR
Dunning is the structured process of recovering failed payments through intelligent retries and customer outreach. Dumb retries fire on a fixed schedule; smart retries read decline codes and timing to decide when to try again. Look for granular retry configuration and access to decline reasons.
What a Good Dunning Sequence Looks Like
- Immediate retry on failure
- First customer notification
- Retry after 3 days
- Second notification
- Final retry after 7 days
- Pause or cancel trigger
Account Updater and Card Expiry Management
A gateway-level account updater refreshes card-on-file details automatically when cards are reissued, preventing avoidable renewal failures.
Payment Methods Your Subscription Gateway Must Support in India
The Indian stack is not card-default. With UPI at 172.2 billion transactions in FY2023-24, your gateway needs a unified method strategy.
UPI Autopay – The Recurring Rail Built for India
UPI Autopay is the default recurring rail for mass-market domestic subscriptions, ideal for lower-ticket monthly plans.
Card-Based Recurring Payments and Tokenization
Tokenized cards serve higher-ticket and international subscribers where UPI Autopay limits apply.
Net Banking and Wallet Support at Sign-Up
Wallets and net banking work well as sign-up or fallback options.
International Payment Methods for SaaS Exporters
Export SaaS needs global cards and a multi-currency payment gateway for cross-border subscribers.
Security and Compliance – What to Verify Before You Sign
Move beyond treating PCI DSS as a checkbox.
Did You Know: Tokenization can reduce card-not-present fraud by up to 60%.
PCI DSS Level 1 Compliance – What It Means for Subscription Data
Level 1 compliance governs how stored subscription card data is protected across its lifecycle.
Tokenization – How It Protects Recurring Payment Data
Tokenization replaces card numbers with non-sensitive surrogates, so a breach exposes no usable card data while renewals continue seamlessly.
Fraud Detection for Subscription Businesses
Watch for trial abuse, account takeover, and friendly fraud, which behave differently from one-time transaction fraud.
Checkout Experience and Mobile Optimization for Subscription Sign-Up
Checkout UX maps directly to MRR. 53% of mobile users abandon a site that takes longer than 3 seconds to load, and the importance of checkout experience compounds at the mandate step.
Pro-Tip: Test the mandate flow on a mid-range Android device on 4G, not a flagship phone on Wi-Fi.
Why Mobile Checkout Performance Is a Subscription Revenue Decision
A 1-second delay cuts conversions by 7%, and mandate creation is where drop-off concentrates.
Hosted vs. Embedded Checkout for Subscription Sign-Up
Hosted flows reduce compliance burden; embedded flows keep users in-app. Choose based on trust and control needs.
Reducing Friction at the Mandate Creation Step
Minimize redirects, pre-fill details, and use clear consent copy to lift completion.
Settlement, Cash Flow, and Operational Fit
Finance realities decide long-term fit. Understand payment settlement mechanics first.
How Settlement Cycles Affect Subscription Cash Flow
High-frequency, low-ticket subscriptions need predictable inflows. Razorpay’s Instant Settlements feature gives subscription businesses an option to access collected funds outside the standard settlement window.
Reconciliation – Matching Subscription Payments to Customers
Thousands of small recurring charges demand reporting that maps payments to customers, plans, and mandates.
Scalability – When Your Subscriber Base Grows 10x
Your reporting and reconciliation must hold up when subscribers jump from 10,000 to 100,000.
The Subscription Gateway Evaluation Checklist
- Does it support your billing model?
- Does it support UPI Autopay mandates?
- Does it tokenize card-on-file?
- Are mandate flows RBI-compliant?
- Does it automate pre-debit notifications?
- Is retry and dunning logic configurable?
- Is mobile checkout fast and low-friction?
- Does reporting support reconciliation?
- Is settlement timing flexible?
- Does it support international payments if needed?
How Razorpay Supports Subscription Businesses – Features at a Glance
Razorpay’s product suite is built to support the full subscription lifecycle, from mandate creation to recovery and reconciliation.
| Subscription Business Need | Razorpay Feature | What It Does |
|---|---|---|
| Recurring collections | UPI Autopay mandates | Creates and manages recurring UPI debits |
| Card-on-file billing | Tokenized card recurring | Charges saved cards via secure tokens |
| Failed payment recovery | Built-in retry logic | Re-attempts failed charges automatically |
| RBI compliance | E-mandate support | Supports compliant mandate flows |
| Pricing flexibility | Multiple billing models | Handles flat, usage, tiered, and hybrid plans |
| Cash flow | Instant Settlements | Option to access funds early |
| Single integration | Card plus UPI flows | Runs both rails in one setup |
Conclusion
The right subscription payment gateway is not the cheapest or the most popular. It is the one that handles your billing model, RBI compliance, smart dunning, tokenization, and mobile mandate flow natively, without forcing your team to rebuild payment infrastructure on top of a transactional product. Use the guide on how to choose a payment gateway alongside this framework. Start with the checklist, then map each capability to your roadmap before you sign.
FAQs
What is the difference between a payment gateway and a subscription billing platform?
A standard gateway processes one-time payments. A subscription billing platform adds mandate management, recurring schedules, proration, retries, and dunning. For recurring revenue in India, you need the latter native to your gateway.
What is UPI Autopay and how does it work for subscriptions?
UPI Autopay is RBI’s e-mandate framework for recurring UPI debits. A customer approves a mandate once, after which the gateway can debit on schedule up to ₹15,000 per transaction without additional authentication. It is the default recurring rail for Indian subscriptions.
What happens when a subscription payment fails in India?
The gateway retries based on decline reasons and timing, triggers dunning notifications, and attempts recovery. Common causes include card expiry, insufficient funds, bank declines, and paused mandates. Strong retry logic reduces involuntary churn.
Is RBI compliance handled by the payment gateway or the merchant?
Responsibility is shared. The gateway should support AFA, tokenization, and pre-debit notifications, but merchants must configure flows correctly and ensure consent is captured and logged. Ask vendors which parts they automate.
Can I use the same payment gateway for Indian and international subscribers?
Often yes, if the gateway supports UPI Autopay and tokenized cards domestically plus global cards and multi-currency for exports. Confirm both stacks are covered before committing.
What is dunning management and why does it matter?
Dunning is the structured recovery of failed payments through intelligent retries and customer outreach. It matters because failed recurring charges quietly erode MRR, and smart dunning recovers revenue that would otherwise churn involuntarily.
