Match the failure type before counting delay
RBI’s 20 September 2019 failed-transaction framework, effective from 15 October 2019, uses different outer limits for different incidents. For the specified UPI/IMPS transfer failure where an account is debited but the beneficiary cannot be credited, reversal is required by T+1. A UPI merchant payment with debit but no transaction confirmation at the merchant location uses T+5. The relevant table provides ₹100 per day for delay beyond the applicable limit. This analysis is checked on 24 October 2026.
T is the transaction’s calendar date
The circular defines T as the transaction day and expressly refers to the calendar date. Do not restart the clock from the complaint date or count only branch working days. Its definition of R addresses the concluded reversal and receipt of funds at the issuer/originator, with reversal there on the same day funds are received from the beneficiary end. A complaint acknowledgement or an app’s “request raised” message is not proof of completed reversal.
The framework covers domestic transactions where both originator and beneficiary are in India, and qualifying failures not attributable to the customer. It includes the stated system, communication and credit/reversal failures. Classify the actual facts: an authorised payment successfully credited to the wrong intended recipient, a commercial dispute after a successful purchase, an ordinary merchant refund and an unauthorised fraud case need their own analysis. They are not automatically the same failure category merely because money is unavailable.
Separate reversal, compensation and who receives it
RBI requires applicable financial compensation suo moto, without waiting for a complaint or claim. The framework’s general credit-push principles distinguish beneficiary compensation for delayed credit from originator compensation for delay in initiation at the originator’s end. Identify the incident, responsible stage and entitled recipient rather than promising every complainant every amount. The numerical examples quantify qualifying reversal delay under the stated table, not liability for every payment dispute.
Keep the original transaction principal and compensation in separate columns. Returning principal is not itself paying delay compensation; conversely, a small compensation credit does not establish that the principal has been returned. Use transaction IDs and bank statements to avoid counting an interim credit and the final reversal twice. Where the bank records indicate eventual successful credit rather than a failed-transfer reversal, reassess the exact applicable incident before using a reversal illustration.
Build the complaint from facts even though compensation is automatic
Retain date/time, system and transaction identifier, debit evidence, beneficiary or merchant status, bank communication, actual reversal evidence and separate compensation entries. Raise discrepancies through the bank/payment provider’s grievance channel and, where applicable, RBI’s Integrated Ombudsman framework. The circular refers to that redress route, but this article does not invent a universal Ombudsman filing deadline or promise eligibility without the scheme’s conditions.
For the cases below, assume each transaction is domestic, falls within the specified failure category, is not attributable to the customer and is actually reversed on the stated date. Calendar calculations use the shown dates and ₹100 for each day beyond the applicable outer limit. Where a total credit to one person is shown, assume that person’s entitlement to both the principal and compensation is independently established.
Worked illustrations
These illustrations use fictional facts and expressly stated assumptions. Amounts are Indian rupees unless a different currency or unit is specified. They are independent examples, not findings about any actual client.
Illustrative example 1: UPI transfer, not merchant confirmation
A qualifying transfer fails on 1 October 2026 and reversal completes on 5 October. T+1 is 2 October. The reversal is three calendar days beyond that limit, giving ₹300 compensation under the stated assumptions.
Illustrative example 2: UPI merchant-confirmation failure
A qualifying merchant-confirmation failure occurs on 1 October 2026 and reverses on 8 October. T+5 is 6 October. Delay beyond the applicable limit is two days, giving ₹200. Using the transfer’s T+1 clock would misclassify the incident.
Illustrative example 3: IMPS reversed within the limit
A qualifying IMPS failure occurs on 1 October 2026 and is reversed on 2 October. T+1 is 2 October, so delay beyond that limit is zero and this delay calculation produces ₹0 compensation.
Illustrative example 4: Weekend is not a clock reset
A qualifying UPI transfer fails on Friday, 2 October 2026 and reverses on Monday, 5 October. T+1 is Saturday, 3 October. The calendar delay beyond the limit is two days, or ₹200; Monday is not substituted as the start merely because a branch was closed.
Illustrative example 5: Complaint date does not replace T
A qualifying IMPS transfer fails on 1 October 2026, the customer complains on 5 October, and reversal occurs on 6 October. T+1 remains 2 October. Four days of excess delay give ₹400; the complaint date does not reduce the count to one day.
Illustrative example 6: Principal and compensation are different entries
Assume a qualifying ₹8,000 debit has been reversed and the entitled recipient’s independently established three-day compensation is ₹300. The combined amount is ₹8,300. A bank statement showing only ₹8,000 does not show the ₹300 was paid; a ₹300 credit alone does not evidence return of ₹8,000 principal.
Ten-step verification table
| Step | Verification | Evidence to retain |
|---|---|---|
| 1 | Identify the actual payment system | UPI/IMPS reference and transaction record |
| 2 | Confirm domestic scope and failure facts | Debit, recipient status and incident evidence |
| 3 | Separate transfer from merchant confirmation | Correct table category |
| 4 | Record T as the calendar transaction date | Bank and system timestamp |
| 5 | Calculate the correct T+1 or T+5 outer limit | Calendar-date working |
| 6 | Establish actual completed reversal | Bank statement and settlement evidence |
| 7 | Calculate days beyond the limit | Non-negative delay and compensation working |
| 8 | Verify the entitled compensation recipient | Relevant stage and circular principles |
| 9 | Reconcile principal and compensation separately | Matched transaction-wise credits |
| 10 | Escalate unresolved discrepancies properly | Grievance trail and applicable Ombudsman conditions |
Sixteen practitioner FAQs
1. Does every failed UPI incident have the same timeline?
No. The specified fund-transfer and merchant-confirmation cases differ.
2. What does T mean?
The calendar date of the transaction.
3. Can the bank replace calendar days with branch working days?
That is not the calendar-date convention stated in this framework.
4. Does the complaint date start the original clock?
No. Retain the transaction date.
5. Is T+1 the specified UPI transfer reversal limit?
Yes, for the table’s debit-without-beneficiary-credit failure when unable to credit.
6. What is the specified UPI merchant-confirmation limit?
Auto-reversal within T+5 for the stated debit-without-confirmation incident.
7. What daily amount does the relevant table use?
₹100 per day of delay beyond the applicable limit.
8. Does reversal on the outer-limit date create excess delay?
Not in the illustrated non-negative delay calculation.
9. Must a customer first request applicable compensation?
The circular requires suo moto compensation without waiting for a claim.
10. Is every compensation amount necessarily payable to the remitter?
Identify the entitled recipient using the actual incident and the framework’s principles.
11. Is a successful payment followed by a commercial refund automatically this case?
No. Establish the qualifying failed-transaction category.
12. Does a wrong-recipient payment automatically prove a system failure?
No. Analyse its actual facts and applicable remedy.
13. Does an app complaint acknowledgement prove reversal?
No. Obtain actual settlement and statement evidence.
14. Is return of principal itself delay compensation?
No. Reconcile the entries separately.
15. Does this article decide unauthorised-transaction liability?
No. That requires the separate applicable framework and facts.
16. What should accompany an escalation?
Transaction identifiers, dates, category, debit/reversal proof, compensation working and grievance history.
Conclusion
Classify the incident, keep calendar dates and verify the actual reversal before calculating compensation. A transaction-wise principal and compensation ledger makes the unresolved amount clear.