Digital Payments – E-mandate Framework, 2026
UR
- Applies toPayment System Providers and Payment System Participants that process recurring card, PPI or UPI payments (e-mandate issuers and acquirers)
- StatusIn force
- ImportanceFOR INFORMATION
- IssuedApr 21, 2026
- Amendmentsnone tracked
- Length30 points in 2 sections · 3 min read
The four dates on this rule
- PublishedApr 21, 2026The day RBI put this document out.
- Starts to applyNot statedNot stated separately in this document. Read the rule itself before you assume a start date.
- Time to get readyNot statedCannot be worked out until the day it starts to apply is known.
- Last date to actNot statedNo date to act by was found in this document. Other dates may sit inside single paragraphs.
Kept in your browser only. Your desk
What it says
Must know
1. Applies to recurring payments
This rule covers every recurring payment on cards, PPI or UPI, domestic or cross-border.
2. One-time registration
A customer sets up an e-mandate through a one-time registration.
3. AFA needed to register
The issuer must add an extra authentication step (AFA) before registering the mandate.
4. Mandate states its validity
Every e-mandate must state how long it stays valid.
5. Customer can cancel anytime
The customer can change or cancel an e-mandate at any time.
6. Fixed or variable amount
An e-mandate can be a fixed amount or a variable amount capped by RBI.
7. Customer sets own maximum
For a variable e-mandate, the customer sets its own maximum value.
8. Customer picks notice channel
The customer can choose how the pre-transaction notice reaches them, such as SMS or email.
9. Changes also need AFA
Changing or cancelling an e-mandate also needs AFA validation.
10. First payment needs AFA
The very first payment under an e-mandate needs AFA validation.
11. Own limits do not apply
The customer's own separate transaction limits do not apply to e-mandate payments.
12. 24-hour notice before charge
The issuer must warn the customer at least 24 hours before the charge.
13. What the notice must say
The notice must show the merchant's name, amount, time and reason for the charge.
14. Customer can opt out
The customer can opt out of one payment or the whole e-mandate.
15. Opt-out also needs AFA
Opting out needs AFA too, and the customer is told it happened.
16. Notice sent after charge too
The issuer must also tell the customer after the money is taken.
17. Notice includes complaint details
The notice must also tell the customer how to raise a complaint.
18. ₹15,000 needs no extra check
Recurring payments up to ₹15,000 need no extra AFA check.
19. Higher limit for three types
Insurance, mutual fund and credit card bill payments get a higher ₹1,00,000 limit.
20. Issuer must handle complaints
The issuer must have a system for the customer to raise complaints.
21. Old liability rules still apply
RBI's usual rules on unauthorised-transaction liability also cover e-mandate payments.
22. No charge to customer
The customer pays nothing to set up an e-mandate.
23. Acquirer answers for merchants
The acquirer must make sure its own merchants follow these rules.
Do it
1. Told about cancel rights
The issuer must tell the customer about this at registration.
2. One AFA can cover both
If the first payment happens right at registration, one AFA check can cover both.
3. FASTag and NCMC excepted
FASTag and NCMC top-up mandates do not need this advance notice.
4. Mandate follows a new card
An old e-mandate can be moved onto a new, reissued card.
Background
1. Rule effective immediately
This rule took effect the day RBI issued it, 21 April 2026.
2. Terms defined elsewhere
Key terms like issuer and merchant take their meaning from two other RBI Directions.
3. Eight old circulars withdrawn
This framework replaces eight older RBI circulars on e-mandates, now withdrawn.