RBI E-Mandate Rules 2026: A Guide for Businesses
8 min read
Written by Varsha J. · Growth Lead
Reviewed by: Onboarding Team
Updated 13 Nov 2026

Quick answer: What did RBI change in 2026?
The Reserve Bank of India issued the Digital Payments - E-mandate Framework, 2026 on 21 April 2026. It took effect immediately. The framework consolidates instructions for recurring transactions made through cards, prepaid payment instruments (PPIs) and UPI, including domestic and cross-border transactions.
For businesses, the key requirements concern how an e-mandate is registered, how the first transaction is authenticated, what customers are told before and after a debit, and which subsequent transactions can be processed without an additional factor of authentication (AFA).
The ₹15,000 threshold is not a cap on the value of a mandate. It is the general per-transaction threshold up to which a subsequent recurring transaction may be authorised without AFA. A separate ₹1 lakh threshold applies only to three specified categories: insurance premiums, mutual fund subscriptions and credit card bill payments.
RBI e-mandate rules 2026 at a glance
Requirement | What the framework says |
|---|---|
Coverage | Recurring card, PPI and UPI transactions, domestic or cross-border |
Mandate registration | One-time registration with successful AFA validation |
First transaction | AFA is required. It may be combined with registration when both happen together |
Pre-debit alert | Issuer must notify the customer at least 24 hours before the debit, subject to stated exceptions |
General AFA threshold | Subsequent recurring transactions up to ₹15,000 per transaction may be authorised without AFA |
Specified higher threshold | Insurance premiums, mutual fund subscriptions and credit card bill payments may be authorised without AFA up to ₹1 lakh per transaction |
Post-debit alert | Issuer must send transaction details, mandate reference and grievance redressal information |
Customer charge | No charge may be levied on the customer for using the e-mandate facility |
1. Mandate registration must be clear and authenticated
A customer who chooses recurring payments must complete a one-time e-mandate registration. The issuer can register the mandate only after the required additional factor of authentication has been successfully validated, along with the issuer’s normal process.
The mandate must state its validity period. Customers must be given a way to modify that period or withdraw the mandate at any time. The issuer must explain these options during registration. Any modification or withdrawal of an existing e-mandate requires AFA validation.
The framework permits both fixed-amount and variable-amount mandates within the applicable RBI-prescribed cap. For a variable-amount mandate, the issuer must let the customer specify the maximum value of an individual recurring transaction. Customers must also be able to choose or change the available notification channel, such as SMS or email.
2. The first transaction still requires AFA
The first transaction under an e-mandate requires AFA validation. When the first payment and mandate registration are processed together, the authentication may be combined into one step. This does not mean that every future debit must repeat the same authentication.
For subsequent transactions, the applicable AFA threshold depends on the transaction category and amount. Businesses should not describe recurring payments as universally frictionless or assume that a mandate removes every later authentication requirement.
3. The issuer must send a pre-debit notification at least 24 hours in advance
Before a recurring debit, the issuer must send the customer a pre-transaction notification at least 24 hours before the actual charge or debit. At a minimum, that notification must contain:
The merchant’s name.
The transaction amount.
The date and time of the planned debit.
The e-mandate reference number.
The reason for the debit, including that it is based on an e-mandate registered by the customer.
The customer must be able to opt out of a particular transaction or the e-mandate. The issuer validates that opt-out using AFA and sends an intimation to the customer. The framework makes a specific exception to the pre-transaction notification requirement for e-mandates used to auto-replenish FASTag and National Common Mobility Card (NCMC) balances.
This is an issuer obligation in the RBI direction. A merchant should confirm with its acquiring bank and payment partners how the notification is triggered, what transaction and mandate data must be passed, and how an opt-out is reflected in the merchant’s systems.
4. A post-transaction notification must follow the debit
The issuer must also send a post-transaction notification. It must include the merchant’s name, transaction amount, date and time of debit, transaction reference number, e-mandate reference number, the reason for the debit and details of how the customer can raise a grievance.
For a business, this makes accurate transaction references and customer-support routing important. A payment record should be traceable from the mandate to the debit and the related invoice, instalment or customer account.
5. Understand the ₹15,000 and ₹1 lakh AFA thresholds
The framework allows subsequent recurring transactions to be authorised without AFA up to ₹15,000 per transaction. A subsequent recurring transaction above ₹15,000 is subject to AFA, unless a specific higher threshold applies to its category.
The higher no-AFA threshold of ₹1 lakh applies only to these categories named by RBI:
Insurance premium payments.
Subscriptions to mutual funds.
Credit card bill payments.
Do not treat ₹1 lakh as a general limit for all subscription or instalment businesses. Education fees, SaaS subscriptions, loan repayments and other recurring merchant categories are not included in that specific list. They should be assessed under the general threshold and the applicable payment-rail rules.
Also, ₹15,000 is not the maximum amount a customer can authorise through a mandate. It is the threshold for processing a subsequent recurring transaction without AFA under the general rule. Higher-value transactions may be possible, but the required authentication applies.
6. Issuers and acquirers have defined responsibilities
The framework places several customer-facing obligations on the issuer, including mandate registration and authentication, mandate validity and withdrawal facilities, pre- and post-transaction notifications, opt-out handling and grievance redressal. The issuer must maintain a suitable dispute-resolution mechanism. RBI’s instructions on limiting customer liability for unauthorised transactions also apply to recurring e-mandate transactions.
The acquirer must ensure that merchants it onboards comply with the directions. Businesses should therefore agree on the division of responsibilities with their acquiring bank and payment partners. Do not assume that every notification or authentication step is implemented solely inside the merchant’s own software.
The framework also states that customers must not be charged for availing the e-mandate facility for recurring transactions. For card mandates, existing e-mandates may be mapped to reissued cards.
A practical e-mandate checklist for businesses
Identify the payment rail. Confirm whether each recurring flow uses cards, PPI or UPI. Do not assume that the same instructions automatically cover NACH or eNACH.
Document mandate consent. Make the amount, frequency, validity period and any variable-amount maximum clear during the customer journey.
Confirm AFA handling. Ask the issuer or payment partner how registration and the first transaction are authenticated, and how later transactions are evaluated against the thresholds.
Check notification fields and timing. Confirm the process for the 24-hour pre-debit alert, required fields, post-transaction alert and the FASTag/NCMC exception where relevant.
Map opt-outs and mandate changes. Ensure that pause, withdrawal or modification requests reach the correct issuer or payment partner and that your collection records are updated.
Keep customer support traceable. Store the mandate reference, transaction reference, customer account, payment status and grievance route together.
Reconcile every debit. Match payment outcomes to the correct invoice, instalment or loan schedule. Keep successful, pending, failed, reversed and unmatched entries separate.
What the 2026 framework means for education fees and instalments
An education provider collecting monthly course fees should pay particular attention to the general ₹15,000 threshold. Education fees are not one of the three categories that receive the special ₹1 lakh no-AFA threshold in the 2026 direction.
For example, a subsequent recurring instalment of ₹12,000 may fall within the general no-AFA threshold, provided the mandate is valid and all other requirements are met. A subsequent instalment of ₹25,000 is above the general threshold and is subject to AFA. The payment partner and issuer determine the actual transaction flow.
That distinction matters when an institute designs instalment plans, explains payment authorisations to students or parents, and forecasts collection dates. A business should not promise that every future instalment will be debited without customer authentication.
Does the RBI e-mandate framework cover NACH or eNACH?
The 2026 direction states that its applicability is to recurring transactions using cards, PPIs and UPI. It does not list NACH or eNACH in that applicability clause. Businesses using NACH or eNACH should check the separate network, sponsor-bank and service-provider rules that apply to those mandates. Do not assume that the card, PPI and UPI provisions in this direction automatically govern an eNACH flow.
Frequently asked questions
What is the RBI Digital Payments E-mandate Framework, 2026?
It is an RBI direction issued on 21 April 2026 that consolidates requirements for recurring transactions through cards, PPIs and UPI. It covers mandate registration, authentication, customer notifications, transaction thresholds and grievance redressal. It took effect immediately.
Is ₹15,000 the maximum amount for a UPI AutoPay mandate?
No. ₹15,000 is the general per-transaction threshold up to which a subsequent recurring transaction may be authorised without AFA. It is not a maximum mandate value. Above that amount, AFA applies under the general rule.
Which recurring transactions have a ₹1 lakh no-AFA threshold?
The specified categories are insurance premiums, mutual fund subscriptions and credit card bill payments. The higher threshold should not be applied to other merchant categories by assumption.
Who sends the 24-hour pre-debit notification?
The RBI direction says the issuer must send it at least 24 hours before the debit, with the specified transaction and mandate details. The FASTag and NCMC auto-replenishment use cases are exempt from the pre-transaction notification requirement.
Can a customer cancel or withdraw an e-mandate?
Yes. The issuer must provide a facility to modify the validity period or withdraw the mandate. Customers must also be able to opt out of a particular transaction or the mandate. The issuer validates modification, withdrawal or opt-out using AFA.
Do these rules apply to eNACH?
The applicability clause in this direction names recurring transactions through cards, PPIs and UPI. It does not name NACH or eNACH. Businesses should confirm the separate requirements for their NACH or eNACH arrangements with the relevant bank and service provider.
How SlashCollect supports recurring collection operations
For businesses collecting recurring fees, subscriptions or instalments, the mandate is only one part of the operating workflow. Teams also need due-date schedules, payment-status visibility, reminders, failed-payment follow-up and reconciliation. SlashCollect brings recurring and scheduled collection workflows, multi-channel reminders and collection tracking into one platform. Explore our recurring payment gateway guide and our guide to failed recurring payments.
The payment rail, issuer, acquirer and the business each have defined roles. Confirm the exact mandate and notification journey with your authorised payment partners before changing customer-facing promises or collection policies.
Want to review your recurring collection workflow? Book a 30-minute SlashCollect demo with our team.
Official RBI sources
Reserve Bank of India: Digital Payments - E-mandate Framework, 2026 (issued 21 April 2026).
Reserve Bank of India: Press release announcing the consolidated e-mandate directions (21 April 2026).
Let's connect to discuss more?
Whether you collect fees, EMIs, subscription payments, memberships, rent or B2B collections, SlashCollect automates the repetitive work behind payment collection.