RBI publishes the Digital Payments- E-Mandate Framework 2026

The Reserve Bank of India (“RBI”) has, vide notification dated April 21, 2026, issued Digital Payments – E-mandate Framework, 2026, consolidating the existing circulars relating to the processing of e-mandates for recurring transactions on cards, PPIs, and UPI (“E-mandate MD”).

The key highlights of the E-mandate Framework include inter alia the following:

1. Registration and Revocation of E-Mandates: A customer desirous of opting for e-mandate facility shall undertake a one-time registration process. The mandate shall be registered only after successful validation of additional factor of authentication (AFA), in addition to the normal process required by the issuer. Every e-mandate registered by the issuer shall specify the validity period of the e-mandate. The issuer shall provide the customer with a facility to modify the validity period or withdraw the e-mandate at any point of time. Information about this facility shall be clearly communicated to the customer at the time of registration. Any modification or withdrawal of an existing e-mandate also requires AFA validation. Other conditionalities in regard are set out in the E-Mandate MD.

2. Processing of the First and Subsequent Recurring Transactions: The first transaction under an e-mandate shall require AFA validation. If the first transaction is processed along with registration of the e-mandate, then AFA validation may be combined. Payments under e-mandates shall not be subject to any other limits / controls set by the customer.

3. Pre-Transaction and Post-Transaction Notification:

• • An issuer shall send a pre-transaction notification to the customer, at least 24 hours prior to the actual charge / debit. The pre-transaction notification shall, at the minimum, inform the customer about the merchant’s name, transaction amount, date / time of debit, reference number of e-mandate, reason for debit, i.e., e-mandate registered by the customer. The issuer shall provider a customer with a facility to opt-out of any particular transaction or the e-mandate. Any such opt-out shall be validated by the issuer using AFA. An intimation to this effect shall be sent to the customer. Further, pre-transaction notification is not required for e-mandates registered to auto-replenish balances of FASTag, and National Common Mobility Card (NCMC).
  • An issuer shall send a post-transaction notification to the customer. This notification shall, at the minimum, inform the customer about the merchant’s name, transaction amount, date and time of debit, reference number of transaction and e-mandate, reason for debit, i.e., e-mandate registered by the customer, and details on grievance redressal.

4. Transaction Limits and Velocity Check: All recurring transactions may be authorised without AFA up to INR 15,000/- per transaction. Further, the E-Mandate MD provides that payment of insurance premiums, subscription to mutual funds, and credit card bill payments may be made without AFA up to INR 1,00,000/- per transaction. 

5. Dispute Resolution and Grievance Redressal: An appropriate dispute redressal system shall be put in place by the issuer to facilitate the customer to lodge grievance/s. The  RBI instructions on limiting liability of customers for unauthorized transactions shall be applicable to recurring transactions under e-mandates as well.

Conclusion

The E-mandate Framework consolidates the regulatory requirements for recurring digital payments across cards, PPIs and UPI, while preserving key customer protection safeguards such as AFA validation, pre-transaction notifications, opt-out rights and grievance redressal. The framework is expected to improve consistency in the processing of recurring transactions and provide clearer operational obligations for issuers.