Credit Card Auto-Debit + Standing Instructions: Why Recurring Payments Fail in 2026 (RBI AFA Rules Explained)
In short: Since October 2021, RBI requires every recurring credit card payment above ₹15,000 to be authenticated with an OTP each time. Below ₹15,000 — your Netflix, Spotify, Amazon Prime — recurring debits work automatically, but only if both your bank and the merchant have completed e-mandate registration. The single biggest reason your Netflix or Hotstar failed in 2021 is that the merchant had not onboarded onto your bank e-mandate platform. International subscriptions billed by foreign merchants face an additional layer of failure. This guide shows how the rules work, why payments fail, and the fix.
Why Your Auto-Pays Started Failing in Late 2021
On 4 December 2020, the RBI directed all card issuers, networks, and acquirers to implement an “Additional Factor of Authentication” (AFA) framework for recurring transactions on cards. The original compliance deadline of 31 March 2021 was missed industry-wide, so RBI gave a final extension to 30 September 2021. From 1 October 2021, any recurring credit-card or debit-card transaction that had not been migrated to the e-mandate framework simply stopped working.
The number of failed transactions that month ran into millions. Netflix, Amazon Prime Video, Disney+ Hotstar, BookMyShow, Tinder, Spotify, AWS, Google Workspace, Apple subscriptions — most failed at least once, requiring users to re-add their card and re-authenticate. Many users moved to UPI Autopay, debit-card e-mandate, or simply switched to manual renewal.
The problem was not the rule itself — it was the patchy industry-wide compliance. Each merchant had to integrate with each bank e-mandate gateway. Three years later the situation has improved but not normalised; international merchants in particular remain unreliable.
How the AFA Framework Actually Works
The mechanics, in plain language:
- First-time setup: When you authorise a recurring debit (say, ₹499/month for Netflix), the merchant initiates an e-mandate registration request to your bank. You receive an OTP. You enter it. The mandate is registered against your card with the recurring amount, frequency, and end date.
- Pre-debit notification: 24 hours before each recurring debit, your bank must send you an SMS and/or email. This pre-debit notification is mandatory; without it, the debit cannot proceed.
- Automatic debit (below ₹15K): If the upcoming debit is below ₹15,000, it proceeds automatically at the scheduled time, charged against your registered card.
- OTP required (above ₹15K): If the debit is ₹15,000 or higher, you receive an OTP on the debit day. Without entering it within the window (typically 24 hours), the debit fails.
- Cancellation: You can cancel any registered e-mandate from your bank app, the merchant app, or by replying STOP to the SMS. Banks must honour cancellations within one business day.
The ₹15,000 threshold was raised from the original ₹5,000 in March 2023, easing many enterprise SaaS, insurance premium, and education auto-pays. The threshold is per-debit, not cumulative — so a ₹10,000 monthly SIP and a ₹14,000 monthly subscription on the same card both run frictionlessly.
What ₹15,000 Means in Practice — Examples
| Use case | Typical amount | OTP each time? |
|---|---|---|
| Netflix Premium (₹649) | Under ₹15K | No |
| Spotify Family (₹179) | Under ₹15K | No |
| SIP ₹10,000/month | Under ₹15K | No |
| Apartment maintenance ₹8,500 | Under ₹15K | No |
| Term insurance premium ₹18,000/year | ₹15K+ | Yes, each time |
| Health insurance ₹35,000/year | ₹15K+ | Yes, each time |
| School fees ₹45,000/quarter | ₹15K+ | Yes, each time |
| AWS bill ₹22,000/month | ₹15K+ | Yes, each time |
For most middle-class subscribers, the ₹15K threshold means nothing — almost every D2C subscription, OTT plan, gym membership, and small SIP falls below it. The problems start with insurance premiums, school fees, larger SIPs, and enterprise software bills.
Why Recurring Payments Still Fail in 2026
Three years after the mandate, failures are rarer but specific patterns persist:
Failure 1: Merchant not onboarded with your bank
Each merchant must individually onboard with each bank e-mandate gateway. Major Indian merchants (Netflix, Hotstar, Amazon, Tata Play) are onboarded with all major banks. Smaller merchants and international entities may not be onboarded with smaller Indian banks (especially RBL, Yes Bank, Federal, RBL co-brands like Bajaj). Symptom: first registration attempt fails with “merchant not configured” or similar.
Failure 2: International merchant outside India e-mandate framework
Foreign merchants (Apple US, Adobe US, Notion, Substack, Patreon) often do not participate in India e-mandate system at all. Their recurring debits typically fail unless you use a forex or prepaid card outside the regulated framework. Symptom: card declined when foreign merchant attempts auto-debit even though manual purchase works.
Failure 3: Pre-debit SMS missed and ignored
If your bank sent the 24-hour pre-debit SMS and you replied STOP (sometimes accidentally, sometimes via spam filters), the mandate is cancelled. Symptom: every renewal fails despite no apparent reason.
Failure 4: Card replaced / number changed
When your bank issues a replacement card (lost card, upgrade, reissue), the old card e-mandates are typically not migrated automatically. Each mandate has to be re-registered on the new card. Symptom: every subscription fails simultaneously after card replacement.
Failure 5: Insufficient credit limit on the debit date
If your remaining credit limit is below the recurring amount on the debit day, the debit fails. Symptom: random monthly failures, especially for high-spend users approaching their limit.
Pro tip: After any card replacement, log into your bank app and check the “Standing Instructions” or “E-mandates” section. Most apps list active mandates and let you re-register them in 2 taps each. Reviewing your statement every month helps catch silent failures within 30 days.
Bank-by-Bank State of E-Mandate Compliance (FY 2026-27)
| Bank | E-mandate quality | Pre-debit SMS | App mandate management |
|---|---|---|---|
| HDFC Bank | Strong — most major merchants onboarded | Reliable, 24–48 hrs prior | Excellent — view + cancel from MyCards |
| ICICI Bank | Strong | Reliable | Good — iMobile lists active mandates |
| SBI Card | Strong for domestic, patchy for international | Reliable | Adequate — SBI Card app |
| Axis Bank | Strong | Reliable | Good — Axis Mobile |
| Amex | Patchy — many international merchants not integrated | Reliable when registered | Limited — call CS for changes |
| RBL / IndusInd / Yes | Acceptable for major merchants only | Reliable | Adequate |
| IDFC FIRST | Strong for newer fintech merchants | Reliable | Excellent — FIRST app |
| Standard Chartered | Patchy | Reliable | Limited |
HDFC, ICICI, Axis, IDFC FIRST handle the vast majority of e-mandate cases reliably. If you do a lot of recurring international payments, an Amex or SCB card is a poor primary choice.
UPI Autopay — The Better Alternative
For domestic recurring payments under ₹1 lakh, UPI Autopay is now the gold standard. Built on the BHIM-UPI framework, it operates outside the AFA-on-cards system entirely. Key differences:
- Limit: ₹1 lakh per debit (₹15,000 for AFA-exempt recurring; above that, OTP each time)
- Pre-debit notification: Mandatory via UPI app, 24 hours prior
- Setup: One-time UPI PIN authentication when registering
- Cancellation: Instant via your UPI app
- Coverage: Strong for Indian merchants — Netflix India, Hotstar, Zomato Gold, Swiggy One, JioFiber, Tata Sky, all major utility billers
- Card link: Direct from savings account, or via RuPay credit card linked to UPI (then both UPI Autopay rules and RuPay credit card e-mandate apply, complicating things)
For most subscriptions, UPI Autopay is more reliable than credit-card e-mandate today. See our UPI-on-credit-card explainer for the RuPay credit card overlap.
The International Subscription Problem
India e-mandate framework applies only to Indian acquirers. When an international merchant (Apple US, Google US, AWS, OpenAI, Adobe US, Substack, Patreon, Notion) attempts to debit your Indian credit card, the transaction routes through international card networks and bypasses India e-mandate gateway entirely. Two outcomes:
- Card issuer blocks: Some Indian issuers (especially HDFC, SBI) decline international recurring debits that have not gone through their e-mandate system. You will see “transaction declined” with no clear reason.
- Issuer allows but RBI flags: Other issuers permit the debit but the transaction may be flagged later, leading to a sudden card block. Common with Amex.
Workarounds that actually work:
- Use a forex card: Forex cards operate outside the e-mandate framework. Adobe US billing on a HDFC Multicurrency card works frictionlessly. Drawback: forex cards count toward your ₹10 lakh LRS / TCS threshold.
- Use a prepaid international card: Niyo Global, Scapia (debit variant), or USDT-backed cards from international providers. Drawback: limits and KYC complexity.
- Annual prepayment: For services that offer annual billing (AWS, Adobe), prepay one year manually. Avoids the recurring-debit issue entirely.
- Switch to invoice billing: Enterprise plans for SaaS tools usually allow invoice billing via wire transfer. Skip recurring cards entirely.
When an Auto-Debit Fails — Your 30-Minute Action Checklist
- Check the merchant email/app for the failure reason. Common codes: “Insufficient funds” (limit issue), “Authentication failed” (OTP missed), “Bank declined” (e-mandate issue), “Card expired” (reissue needed).
- Open your bank app and check Standing Instructions. If the mandate is missing, register it again from the merchant side.
- Verify the card on file is your current card number. If you have had a replacement in the last 6 months, this is the most likely culprit.
- Check available credit limit. If you are at 90%+ utilisation, the debit will fail. Pay down the balance or call your bank to temporarily increase the limit.
- Pay the missed instalment manually. Most subscriptions give you 7–14 days to retry before suspending service.
- If the failure repeats, switch payment method. UPI Autopay for domestic subscriptions, forex card for international.
Frequently Asked Questions
Can I disable e-mandates entirely on my credit card?
Yes — most banks let you block all e-mandates from your card app or by calling customer care. You would then have to manually pay every subscription, which is impractical for most people. Better to keep it enabled and manage active mandates individually.
Does the ₹15K threshold apply to debit cards too?
Yes — the same AFA framework applies to debit-card recurring transactions. The threshold is the same.
What happens if I miss the OTP for a ₹15K+ recurring debit?
The transaction fails. The merchant typically retries 1–3 times over the next few days. If all retries fail, your service is suspended. You can manually pay anytime to restore.
Can I set my own threshold higher than ₹15K?
No. The ₹15K limit is the RBI-mandated AFA threshold and cannot be modified by you, your bank, or the merchant. Above ₹15K, OTP is mandatory per debit, full stop.
Are e-mandates safer than older standing instructions?
Significantly. Pre-debit notifications, OTP for large amounts, and easy cancellation mean fraud-via-standing-instruction is much harder. The 2017 case of cards being charged years after subscription cancellation has largely been eliminated by the new framework.
Sources
- RBI Notification DPSS.CO.PD No.1342/02.14.003/2019-20 dated 16 January 2020 — original AFA framework for recurring card transactions
- RBI Notification dated 16 March 2023 — increase in AFA-exempt threshold from ₹5,000 to ₹15,000
- RBI Master Direction on Acquiring of Card Transactions — current e-mandate operational requirements
- NPCI UPI Autopay framework documentation
- Various bank disclosures on e-mandate compliance status
