RBI’s E-Mandate Framework 2026 for Digital Payments: What Has Changed and Why It Matters

Recurring payments have quietly become a part of everyday life. From OTT subscriptions and insurance premiums to SIPs and utility bills, most transactions today run on auto-debit.

Recognising this shift, the Reserve Bank of India (RBI) has introduced the Digital Payments – E-mandate Framework, 2026, bringing together all earlier guidelines into one comprehensive structure.

Invest in Indian Markets and Unlock Future Potential With 5paisa!

Open Account Now

This move is not just regulatory housekeeping; it is aimed at improving transparency, security, and user control in recurring digital payments.

A Unified Framework for Recurring Payments

RBI’s E-Mandate framework 2026 consolidates multiple circulars issued over the years into a single direction. It applies to all payment system providers and participants handling recurring transactions through cards, UPI, and prepaid instruments, whether domestic or cross-border.

By standardising rules across platforms, RBI has reduced ambiguity and ensured a consistent experience for both users and merchants.

How E-Mandates Work Under the New Rules

At the core of the framework is the concept of customer consent and control.

To activate an e-mandate, a user must complete a one-time registration, which requires Additional Factor Authentication (AFA); typically, an OTP or similar verification.

How Registration, Debit Processing, and Notifications Will Work Under the New E-Mandate Framework

The RBI has laid down a detailed process for how an e-mandate must be registered, how recurring debits should be processed, and how customers must be informed before and after every transaction. These provisions are meant to improve transparency, strengthen authentication, and give customers better control over their recurring payment instructions.

Registration and Revocation of E-Mandate

• A customer who wants to use the e-mandate facility must first complete a one-time registration process. The mandate can be registered only after successful Additional Factor Authentication (AFA), along with the issuer’s normal process.
• Every e-mandate must clearly mention its validity period. The issuer must also provide the customer with the option to change this validity period or withdraw the mandate at any time. This facility must be clearly communicated at the time of registration.
• An e-mandate can be created either for a fixed amount or a variable amount, subject to the overall cap prescribed by RBI. In the case of variable mandates, the issuer must allow the customer to define the maximum value of any recurring transaction.
• The customer must be given the option to choose or change the mode of receiving pre-transaction alerts, such as SMS, email, or other available channels.
• Any modification or withdrawal of an existing e-mandate must again go through AFA validation by the issuer.

Processing of First Transaction and Subsequent Recurring Transactions

• The first transaction under an e-mandate must necessarily undergo AFA validation.
• If the first transaction is processed at the same time as mandate registration, the AFA validation for both may be combined into a single step.
• Once the mandate is active, payments under the e-mandate will not be subject to any other limits or controls separately set by the customer.

Pre-Transaction Notification

• The issuer must send a pre-transaction notification at least 24 hours before the actual charge or debit.
• This notification must at least contain the following details:
  • Merchant name
  • Transaction amount
  • Date and time of debit
  • Reference number of the e-mandate
  • Reason for debit, namely that the charge is being made under the e-mandate registered by the customer
• The issuer must also provide the customer with a facility to opt out of a particular transaction or cancel the entire e-mandate. Any such opt-out must be validated through AFA, and the customer must be informed accordingly.
• However, pre-transaction notification will not be required in the case of e-mandates used for auto-replenishment of FASTag and National Common Mobility Card (NCMC) balances.

Post-Transaction Notification

• After the debit is processed, the issuer must send a post-transaction notification to the customer.
• This notification must include, at a minimum:
  • Merchant name
  • Transaction amount
  • Date and time of debit
  • Reference number of the transaction
  • Reference number of the e-mandate
  • Reason for debit
  • Details of grievance redressal

What This Means for Customers

• The framework makes it clear that recurring payments cannot operate in the background without customer visibility.
• The registration process has been tied closely to authentication.
• Customers are being given control not only over mandate creation, but also over validity, transaction caps, notification channels, opt-out choices, and grievance access.

Transaction Limits and Relaxations: ₹15,000 Can Be Processed Without Additional Authentication

The RBI has introduced clear thresholds for auto-debit transactions:

• Up to ₹15,000 per transaction can be processed without additional authentication
• For specific categories like insurance premiums, mutual fund SIPs, and credit card bill payments, the limit is higher up to ₹1,00,000 per transaction without AFA

Any transaction beyond these limits requires fresh authentication.

This differentiation reflects the importance and recurring nature of certain financial commitments.

Grievance Redressal and Customer Protection

The framework mandates that issuers must have a robust dispute resolution system in place.

Additionally, RBI’s existing rules on customer liability in unauthorised transactions will also apply to e-mandate payments.

This ensures that users are not left exposed in case of misuse.

Other Key Provisions You Should Know

A few important operational changes stand out:

• No charges can be levied on customers for using e-mandates
• Existing mandates can be linked to reissued cards
• Payment aggregators must ensure that merchants comply with these rules

These provisions strengthen both accessibility and accountability in the ecosystem.

Conclusion

Recurring payments are designed for convenience, but without proper checks, they can lead to unnoticed outflows. RBI’s latest framework addresses this gap by putting the user back in control; without compromising on ease of use.