Failed UPI Transaction: When Money Debits but Receiver Does Not Get It
A failed-UPI evidence and escalation workflow distinguishing person-to-person transfers from merchant payments, the RBI T+1/T+5 timelines and delay compensation.
A debit without beneficiary credit is a failed-payment problem, not automatically fraud. The first task is to classify the transaction and preserve its reference trail.
For a UPI fund transfer where the account is debited but the beneficiary is not credited, RBI’s failed-transaction framework requires reversal latest by T+1 day if credit cannot be completed.
For a UPI merchant payment where the account is debited but confirmation is not received at the merchant, the prescribed auto-reversal timeline is T+5 days.
The framework provides ₹100 per day of delay beyond the applicable T+1 or T+5 deadline.
The app, payer bank and beneficiary or acquiring side may display different intermediate statuses; the UTR or transaction reference is the common reconciliation key.
What the customer or business should understand
- For a UPI fund transfer where the account is debited but the beneficiary is not credited, RBI’s failed-transaction framework requires reversal latest by T+1 day if credit cannot be completed.
- For a UPI merchant payment where the account is debited but confirmation is not received at the merchant, the prescribed auto-reversal timeline is T+5 days.
- The framework provides ₹100 per day of delay beyond the applicable T+1 or T+5 deadline.
- The app, payer bank and beneficiary or acquiring side may display different intermediate statuses; the UTR or transaction reference is the common reconciliation key.
- RBI’s ODR framework requires access to lodge disputes concerning failed digital transactions, including off-us transactions.
The five-point review
| Check | What to examine |
|---|---|
| Type | Person-to-person transfer or merchant payment. |
| Reference | UPI transaction ID, UTR, bank reference and time. |
| Status | Debited, pending, failed, beneficiary credit and merchant confirmation. |
| Deadline | T+1 or T+5 under the applicable failed-transaction category. |
| Escalation | App, remitter bank, beneficiary/acquirer and RBI CMS after the bank process. |
Practical example
A user sends ₹8,000 to a friend on Monday. The account is debited, but the friend is not credited. This is a P2P failure and should be reconciled against the T+1 reversal rule. A grocery QR payment with no merchant confirmation would instead fall under the T+5 merchant-payment category.
How to apply the framework
Do not repeatedly send the amount because the first transaction shows pending. Ask the receiver to check the actual bank statement, not only the app notification.
Create one issue timeline with transaction date, complaint date, prescribed deadline, actual reversal date and compensation due. This avoids a generic complaint that omits the statutory delay.
Dispute workflow
Classify the problem before choosing the remedy
Identify the regulated entity, transaction or loan account, date, amount, contractual document and exact failure. Review type, reference and status together. A failed transaction, authorised mistake, unauthorised fraud, merchant dispute, credit-report error and lawful account freeze require different remedies.
Create one written chronology
Record the event, alert, discovery, first report, complaint number, response and financial impact in date order. Attach only the documents that prove each step. Phone calls can stop urgent harm, but a written acknowledgement creates the escalation record.
Escalate to the correct authority
Start with the bank, card issuer, lender, credit institution, app or other regulated entity responsible for the service. Use cybercrime or law-enforcement channels for suspected fraud. Use RBI CMS only after the regulated entity process satisfies the Scheme’s timing or rejection condition and the issue is within Ombudsman scope.
Implementation checkpoint
Before treating the case as closed, verify the actual bank statement, loan ledger, credit report, account status or merchant refund rather than relying only on a ticket message. Record who confirmed the financial outcome, the date, remaining open amount and the next escalation deadline. This final check prevents a complaint from being marked resolved while the money, lien, overdue status or credit record remains unchanged.
Action checklist
- Capture the full transaction screen and UTR.
- Check both bank statements.
- Raise the in-app dispute immediately.
- File a written complaint with the remitter bank.
- Calculate the applicable T+1 or T+5 deadline.
- Escalate unresolved service deficiency through the official route.
Evidence to keep
- Transaction ID and UTR
- Payer and beneficiary bank statements
- Merchant receipt or failed screen
- App and bank complaint numbers
- Reversal and compensation calculation
Warning signs
- Sending the money again immediately
- Relying only on a screenshot from the receiver
- Treating every pending transaction as fraud
- No written bank complaint
- Ignoring delay compensation
Finin2min takeaway
Banking disputes are resolved through classification, speed, written evidence and the correct escalation route. No legitimate bank, regulator or recovery process requires disclosure of an OTP, UPI PIN or remote-control access.