Plan for India's recurring-payment rules before you build
As the Reserve Bank of India (RBI) enforces its updated Digital Payments – E-Mandate Framework, effective April 21, 2026, subscription and recurring-revenue businesses face critical operational adjustments. RBI’s framework establishes strict authentication, pre-debit notification, and cancellation rules across all recurring transactions in India. Modern payment orchestration serves as the control layer above payment processors, directly executing this regulatory logic across routing, retries, and re-authentication in real time.
The question isn’t whether a recurring payment is allowed. It’s whether your payment operating model can actually identify the relevant transaction attributes and apply the right authentication, notification, payment method, and recovery path, in real time, not after the fact.
Why recurring-payment rules create architectural consequences
Recurring-payment regulation doesn’t just decide whether a payment can be processed. It governs how it has to be authenticated, disclosed, and cancelled. Change one rule and you can touch payment routing, customer communications, tokenization, payment-method selection, and how your billing system schedules collections.
Hard-code one market’s rules into your billing logic and you’ve solved today’s problem while building tomorrow’s brittle operating model. The more adaptable move is a system that distinguishes transactions by issuing country, transaction value, payment method, customer segment, invoice amount, and authentication requirement.
Authentication is not simply waived
India runs a tiered authentication model: the first transaction under a new mandate requires an additional factor of authentication (AFA), while subsequent recurring transactions can skip AFA up to ₹15,000 per transaction, or up to ₹1,00,000 for insurance premiums, mutual fund subscriptions, and credit card bill payments.
Those figures come from RBI’s 2026 e-mandate framework. Confirm them before you build against them, since RBI can revise thresholds again. Don’t generalize one threshold across every recurring payment, and don’t assume a consumer-subscription rule applies to enterprise SaaS.
Pre-debit notification becomes an operating requirement
The framework requires issuers to give customers at least 24 hours’ notice before a debit, including the relevant transaction details, through a channel the customer has chosen. It also requires a post-debit confirmation afterward that includes how to raise a dispute.
For a subscription business, that touches billing schedules, notification systems, payment retries, customer-service workflows, and how you handle variable or usage-based charges. Get billing, payments, product, and compliance in the room before you build it, not after.
Cancellation and customer control
Give customers real control over their mandate: the ability to modify its validity period, withdraw it entirely, or opt out of a single transaction, each validated through the required authentication flow. If cancellation depends entirely on contacting the merchant, you’re carrying customer-experience risk and compliance risk at the same time.
Know where the mandate is managed, who owns the customer experience, and how status changes flow back into your billing and subscription system. If you can’t answer those three questions today, that’s the gap to close first.
Why B2B and B2C businesses may experience the rules differently
The rules themselves run on transaction value and payment characteristics, not on whether you’ve labeled a customer B2B or B2C. In practice, though, the operating impact still lands differently.
Consumer subscriptions tend to produce lower-value recurring charges. Enterprise SaaS, per-seat licensing, and usage-based B2B billing tend to produce larger or more variable ones, and that difference alone can force a different authentication or collection experience.
So evaluate the actual transaction profile. Don’t let “B2B” or “B2C” stand in for real transaction-level analysis. What matters is invoice amount, billing frequency, usage variability, payment method, issuing country, mandate status, and where the customer sits in their lifecycle.
Payment methods for higher-value or variable charges
When recurring charges cross the threshold or swing significantly, you’re probably going to need more than one approach:
- Build an appropriate re-authentication experience into the billing cycle.
- Offer payment methods designed for higher-value recurring collection, where available.
- Use bank-mandate-based direct debit or other regional methods where appropriate.
- Pair invoicing with bank transfer for customers or transactions that do not fit a card-on-file flow.
- Work with a payment partner that supports the required authentication and notification experience.
Which combination is right for you depends on your business model, transaction profile, provider capabilities, and the current regulatory requirements. There’s no universal answer here.
What this means for payment orchestration
India is a good stress test for billing-native payment orchestration, because every decision here depends on both payment attributes and subscription context at the same time.
A payment control plane coordinates providers, payment methods, routing, authentication requirements, retries, and downstream reporting in one place. It won’t get you out of compliance review. Nothing will. What it buys you is the ability to adapt payment operations without hard-coding every market-specific rule into its own custom integration.
Here’s how to evaluate whether an orchestration layer is actually ready for a market like this:
- Can payment decisions account for invoice value, renewal timing, usage charges, and payment method?
- Can the business route different transaction types through different providers or payment paths?
- Can it support local payment methods without creating a separate reconciliation process?
- Can finance see payment status alongside billing, settlements, refunds, and payouts?
- Can the business update authentication and notification logic as requirements change?
- Can it preserve the customer experience when a payment needs additional authentication?
A practical readiness checklist
Before you launch or expand recurring billing in India, confirm your organization actually has:
- A current regulatory interpretation approved by Legal or Compliance.
- A documented map of payment flows, providers, acquirers, wallets, and tokenization paths.
- A transaction-level view of values, currencies, payment methods, and customer segments.
- A tested pre-debit and post-debit notification process.
- Self-service mandate-management and cancellation flows where required.
- A plan for higher-value and variable recurring charges.
- Clear ownership across Billing, Payments, Finance, Product, Engineering, and Customer Support.
- Reconciliation and reporting that connect invoices, payments, settlements, refunds, chargebacks, and payouts.
- A process for monitoring regulatory changes and updating routing or payment logic.
The broader lesson
India shows exactly why payment compliance belongs in your operating model, not in a one-time integration project. The details will change market to market, but the pattern won’t: regulators are increasingly the ones defining authentication, disclosure timing, customer rights, and payment-data requirements for recurring transactions, not you.
You need a payment architecture that adapts as those requirements change, not one you rebuild every time a regulator moves. A billing-native control plane connects those payment decisions to the subscription lifecycle, so finance, payments, product, and engineering are finally operating off the same model.
See how Zuora Payments helps subscription businesses orchestrate recurring payments across providers, payment methods, routing, recovery, and every payment operation in between.
FAQs
1.
Does every recurring payment in India need extra authentication?
No. The first transaction under a new mandate requires an additional factor of authentication. Subsequent recurring transactions can skip it up to ₹15,000 per transaction, or up to ₹1,00,000 for certain categories such as insurance premiums and mutual fund subscriptions. Confirm these figures against current RBI rules before building.
2.
How much notice must a customer get before a debit?
Issuers must give at least 24 hours’ notice before a debit, including the transaction details, through a channel the customer has chosen. A post-debit confirmation that explains how to raise a dispute follows the debit.
3.
Do the rules apply differently to B2B and B2C businesses?
The rules run on transaction value and payment characteristics, not on whether a customer is labeled B2B or B2C. Evaluate the actual transaction profile, since enterprise SaaS and usage-based charges are often larger or more variable.
4.
What must a customer be able to do with a mandate?
Customers should be able to modify a mandate’s validity period, withdraw it entirely, or opt out of a single transaction, each validated through the required authentication flow. Know where the mandate is managed and how status changes flow back to billing.
5.
Does a payment orchestration platform remove these compliance requirements?
No. Compliance review still applies. An orchestration layer lets you adapt payment operations as rules change, without hard-coding every market-specific rule into a custom integration.