Reserve Bank of India Updated Digital Payments – E-mandates Framework 2026: A Consolidated Step Forward

 22 April 2026.

A new era in E-mandate Framework – 8 Circulars Repealed

 

On April 21, 2026, the Reserve Bank of India issued the Digital Payments – E-mandate Framework, 2026, consolidating existing guidelines while incorporating stakeholder feedback into a more structured and user-aware regulatory architecture.

This framework governs recurring digital transactions across cards, UPI, and PPIs—an area that has steadily expanded with the rise of subscriptions, bill payments, and automated financial commitments.

At its core, the 2026 update represents a refinement and consolidation exercise, aimed at strengthening user control, improving transparency, and standardizing processes across the ecosystem.

The full document can be accessed @  https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=13374

What caught my eye!

What Stands Out: Two Practical Interpretations

1. One-Time Registration: Clarity Still Evolving

The framework states that a customer opting for the e-mandate facility is required to complete a one-time registration process.

While the requirement is clearly defined, the operational layer remains flexible:

• Registration could be initiated through:
• Issuer (bank) applications
• Merchant platforms
• Payment aggregator interfaces

The framework mandates Additional Factor Authentication (AFA) for this process, ensuring security and consent. However, it does not prescribe a uniform interface or centralized registration mechanism.

Brief view:
This approach enables ecosystem flexibility, though a more standardized discovery and management interface for mandates could enhance user experience over time.

---

2. Notification Mode Choice: Flexibility vs Simplicity

The framework enables customers to choose or modify the mode of receiving pre-transaction notifications (such as SMS, email, etc.).

Until now, communication for such alerts has largely followed a standard dual-channel approach (SMS and email) across most issuers. The updated provision introduces user-level choice in selecting the preferred notification channel.

Is this customer-friendly?

From a design perspective, the provision can be considered customer-friendly for the following reasons:

• It allows users to align notifications with their preferred communication habits
• It reduces dependency on a single or default channel
• It provides flexibility to adapt preferences over time

Illustrative example:
A customer who actively monitors email but does not regularly check SMS may choose email as the primary notification mode for recurring subscription debits. Conversely, a user relying on basic mobile connectivity may prefer SMS-only alerts.

At the same time, the shift introduces a practical edge case:
If a customer selects only one channel (for instance, email) and does not actively monitor it, there is a possibility of missing a pre-debit alert, which could otherwise have been noticed under a dual-channel default system.

This makes the transition from a standard model to a choice-based model a balance between flexibility and awareness.

Shared responsibility dimension:

• Issuers need to ensure clear defaults, nudges, and easy modification options
• Customers need to select and maintain an active and monitored notification channel

Brief view:
The provision reflects a move toward personalization and user control.

Its effectiveness as a customer-friendly feature will depend on how intuitively issuers implement these choices, particularly in guiding users toward reliable notification preferences.

---

Two Key Additions Driven by Feedback

The 2026 framework reflects stakeholder feedback through targeted enhancements:

 

1. Grievance Redressal in Post-Transaction Notifications

Post-transaction alerts must now include:

• Merchant details
• Transaction amount, date, and reference
• Reason for debit
• Grievance redressal details

Significance:
This strengthens the customer support layer by ensuring that users are not only informed about a transaction but are also provided with an immediate pathway to raise concerns, if required.

---

2. Mapping E-Mandates to Reissued Cards

The framework allows existing e-mandates to be mapped to reissued cards.

Significance:
This reduces disruption in recurring payments during events such as card expiry or replacement, ensuring continuity for subscriptions, bill payments, and other automated transactions.

---

Other Structural Highlights

• Additional Factor Authentication (AFA) required for:
• Registration
• First transaction
• Transactions above prescribed limits
• Transaction thresholds:
• Up to ₹15,000 per transaction without AFA
• Up to ₹1,00,000 for specified categories such as insurance premiums, mutual fund subscriptions, and credit card bill payments
• Pre-transaction notification mandated at least 24 hours prior to debit
• Opt-out facility available for individual transactions or mandates
• No charges to customers for availing e-mandate facilities

 

Conclusion

The Digital Payments – E-mandate Framework, 2026 represents a measured evolution of India’s recurring payments ecosystem.

Rather than introducing sweeping changes, the framework focuses on:

• Enhancing transparency
• Strengthening customer control
• Improving operational continuity

From a user perspective, the framework offers greater visibility, flexibility, and continuity. From a system perspective, it supports standardization while allowing implementation flexibility across participants.

Overall, the update reinforces the direction of building a reliable and user-centric digital payments environment, aligned with the growing adoption of automated financial transactions.

 

Disclaimer

This article is a general interpretation of the Digital Payments – E-mandate Framework, 2026 issued by the Reserve Bank of India and is intended for informational purposes only.

It does not constitute regulatory advice or an official interpretation.

Readers are advised to refer to the original RBI notification for complete details and consult relevant stakeholders for implementation-specific guidance.

The only Joy is in ‘Digital Transactions Day’.

---

The Joy of Digital Transactions

Nayakanti Prashant
Citizen Advocate – Digital Transactions Day (April 11, Proposed)

 

Author’s Blogs

https://prashantrandomthoughts.blogspot.com
https://prashantnepayments.blogspot.com
https://innovationinbanking.blogspot.com