UPI Withdrawal Failed but Money Debited: Get It Back

The 30-second answer

A UPI transaction that is debited but not credited is the most protected failure in Indian payments. Under RBI’s TAT circular, an account-to-account UPI transfer must auto-reverse by T+1, and a merchant payment (like a game deposit) by T+5. After that, your bank owes ₹100 per day — credited suo moto, without you asking. Grab the UTR/RRN, raise the dispute through NPCI UDIR, and file with the RBI Ombudsman after 30 days if it’s still missing.

This page is the deep dive on one failure only. The withdrawal hub — 3 Patti Withdrawal: Why It’s Stuck and How to Fix It — covers every reason a payout stalls (KYC holds, daily caps, bonus locks, TDS shortfalls, the whole Day-0-to-30 ladder). This spoke does not repeat any of that. It goes all the way down on the one state where the rules are hardest and your leverage is strongest: the money left an account, but it never landed where it was supposed to. If your payout is merely “pending” with nothing debited yet, you’re on the wrong page — start at the hub or the withdrawal-stuck guide. If money was actually taken and didn’t arrive, you’re in exactly the right place. We’ll classify the failure, name who is liable, and walk the claim letter that invokes the ₹100/day compensation by circular number.

2026 reality, stated once. After the Promotion and Regulation of Online Gaming Act, 2025 took effect (Rules in force 1 May 2026), India’s big real-money operators discontinued cash play, so much of today’s “debited but not credited” pain is people recovering a stranded balance rather than playing live. The rail protections below apply identically to a recovery payout. The one rule that does change: never add a fresh deposit “to release” a stuck withdrawal — a new deposit into a money game is now illegal, and the dispute paths here recover a debit, not a deposit you were tricked into making.

What “debited but not credited” actually means (and why it’s not one thing)

The phrase “UPI withdrawal failed but money debited” describes a symptom, not a cause. The same five words cover at least three mechanically different situations, and each one has a different liable party and a different clock. Before you complain to anyone, you have to know which one you’re in, because complaining to the wrong door wastes the exact days you need for the right one.

Start from the plumbing. A UPI transfer has two legs that the user sees as one instant tap:

• A debit leg, where money leaves the sending account or wallet.
• A credit leg, where money lands in the receiving account.

When UPI works, both legs complete in under three seconds and you never think about them separately. The “debited but not credited” state is simply what you call it when the debit leg completed and the credit leg did not — and crucially, the system has not yet resolved whether the credit will eventually go through, bounce back, or stay stuck. That unresolved gap is the whole problem. Money is real, it’s gone from one place, and it hasn’t arrived at the other.

Here’s the distinction almost every explainer skips: the debit can happen on either side of your gaming transaction.

• On the deposit side, you are the sender. You tapped UPI to add ₹500 to a game wallet, your bank debited ₹500, and the game balance never went up. Your money is missing.
• On the withdrawal side, the operator is the sender. The app approved a ₹2,000 payout, debited its own settlement account, and the credit to your bank never landed. The operator’s money is missing — but it’s your payout, so you’re the one chasing it.

These two look identical on the surface (“money debited, nothing received”) and are completely different to recover. The recovery section below splits them. For now, hold the core idea: a debit without a credit is a payment-system event with hard RBI timelines, not a gaming-app mood. The moment money is debited on a rail, your problem stops being “the app is slow” and becomes “a regulated entity owes me a reversal.” That shift is your single biggest lever, and the rest of this page is about pulling it correctly.

The number that matters most on Day 0

One figure decides everything that follows: the UTR/RRN — the 12-digit reference that ties a specific debit to its (missing) credit. Without it, no bank can trace your money and no dispute can be filed. With it, every door below opens. Capture it within the first hour, before the failed transaction ages out of your app’s quick view. The exact menu path per UPI app is later in this guide.

Failed vs deemed-successful vs pending: the classification that decides your case

This is the section that the hub deliberately leaves to the spoke, because it’s the technical heart of the whole problem. The system does not see “debited but not credited” as one status. It sorts every stuck transaction into one of three buckets, and which bucket yours lands in determines whether you get an automatic refund or a fight.

Bucket 1 — Failed

A failed transaction is one the system has already concluded did not complete. RBI defines it precisely: per Circular DPSS.CO.PD No.629/02.01.014/2019-20, a failed transaction is “a transaction which has not been fully completed due to any reason not attributable to the customer such as failure in communication links, non-availability of cash in an ATM, time-out of sessions, etc.” That last clause — not attributable to the customer — is the gate that lets you in to the entire compensation framework. A genuine failure caused by a downed link, a timeout, or a bank that didn’t respond is the bank’s problem to fix, on the bank’s clock, with the bank’s compensation. This is the best bucket to be in. If your transaction is cleanly marked “failed” and money left, a reversal is owed almost mechanically.

Bucket 2 — Pending

A pending transaction is one the system hasn’t decided yet. The debit happened, the credit hasn’t confirmed, and the rail is still waiting to hear back from the beneficiary bank. Pending is a temporary state by design — it’s the holding pen while reconciliation runs. Most pending UPI transactions resolve themselves within minutes to a working day, either completing (you get credited) or failing (you get reversed). The mistake people make is treating Day-0 pending as theft. It usually isn’t; it’s the rail doing what the rail does. The rule, again from the TAT circular, is that a pending account-to-account UPI transfer that doesn’t resolve must be auto-reversed by T+1 — so pending has a hard expiry, after which it must convert to a refund.

Bucket 3 — Deemed successful (the hard case)

This is the dangerous one. A deemed-successful (also called “deemed approved”) transaction is one the system has marked as completed even though your money never visibly arrived. It happens, per NPCI’s deemed-approved process, when your bank successfully sends the money out (the debit), settlement moves from the remitter bank to the beneficiary bank, but the final credit to the beneficiary account isn’t confirmed in time. To keep the rail moving, the transaction is deemed to have succeeded and pushed to settlement — the money has reached the beneficiary bank, just not yet the beneficiary account. As one payments processor explains it, the amount sits in a “deemed success” state until the beneficiary bank and NPCI reconcile it and move it to a terminal state — processed, failed, or reversed.

Why is deemed-successful the hard case? Because your app and your sender’s screen both say “success,” but your bank account is empty of the credit. The status says the money arrived; reality says it didn’t. To win this, you can’t just point at a “failed” stamp — you have to prove a negative: that no credit exists against the UTR in your account. That’s why the UTR is non-negotiable here. You hand the UTR to your bank and make them confirm there is no matching credit. A “deemed successful” payout that genuinely never arrived is the single most common reason a stuck withdrawal drags on for days, because the automated reversal that protects a “failed” transaction doesn’t auto-trigger when the system thinks it already paid you.

The one-line triage: Failed → reversal is owed, often automatic. Pending → wait for it to resolve, it has a T+1 expiry. Deemed successful but not received → you must prove the missing credit with the UTR, then force the reconciliation. The first two largely fix themselves on the rule-clock. The third is the case you actually have to work.

A practical tell for which bucket you’re in: read the exact word on the transaction. UPI apps and bank SMS use these terms with surprising consistency. “Transaction failed” or “payment unsuccessful” → Bucket 1. “Pending,” “processing,” “awaiting confirmation” → Bucket 2. “Success,” “completed,” “paid,” with a UTR shown but no money in your account → Bucket 3, the one that needs the bank trace. The hub’s failure-mode taxonomy puts this in the context of every other stall; here we stay zoomed all the way in on the debit-without-credit row.

The RBI TAT framework, decoded line by line

Everything you’re entitled to flows from one document: RBI Circular DPSS.CO.PD No.629/02.01.014/2019-20, dated 20 September 2019 — officially the “Harmonisation of Turn Around Time (TAT) and customer compensation for failed transactions” circular, effective 15 October 2019. People quote “T+1” and “₹100 a day” from it constantly without ever reading the actual table. The table is short and it’s the whole game, so here it is, decoded.

The rule that makes compensation automatic

The single most under-used sentence in the circular: “Wherever financial compensation is involved, the same shall be effected to the customer’s account suo moto, without waiting for a complaint or claim.” Read that again. The ₹100/day is not a favour you beg for. It is a credit your bank is obligated to push to you on its own, the moment it blows past the TAT. In practice many banks don’t — which is exactly why the claim letter later in this guide cites this clause by name and demands it. You are not asking; you are reminding them of an existing duty.

The TAT table for the transactions you actually care about

The circular sets a turnaround time and a compensation rate per transaction type. These are the rows that matter for a gaming deposit or payout:

(Source: the TAT circular’s annex table. “T” is the date of the transaction.)

Three things in that table change how you fight, and most people miss all three.

First — T+1 vs T+5 is not arbitrary; it tracks who you paid. When the payment is an account-to-account transfer (one bank account to another), the deadline is T+1, because reconciliation between two banks is fast and the beneficiary bank is squarely on the hook. When the payment is to a merchant — and a game-wallet deposit is a merchant payment — the deadline stretches to T+5, because the merchant’s acquiring bank needs longer to confirm whether the merchant got the money. This single distinction is why a failed deposit into a game can legitimately take five days to reverse while a failed withdrawal credit to your bank should bounce back in one. People rage at their bank on Day 2 of a failed deposit not knowing the rule allows the merchant five.

Second — liability is split, and it’s not always your bank. For an account-to-account failure, the beneficiary bank (the one that was supposed to receive and credit) is liable for the reversal and the compensation. For a merchant failure, the acquirer (the merchant’s bank) carries it. This matters because when you complain, you’re really triggering a chain that lands on a specific party, and your own bank may genuinely be telling the truth when it says “the money left us cleanly.” It did. The hold-up is downstream.

Third — “not attributable to the customer” is the eligibility gate. The compensation only applies to system/technical failures, not to your own mistakes. If you typed the wrong UPI handle and the money went to a stranger, that’s not a “failed transaction” under this circular — it completed, just to the wrong person, and the recovery path is different (you request a reversal from the recipient, you don’t claim ₹100/day). But a payout that the app handed to the rail and the rail couldn’t deliver is a system path, fully covered. A stuck app-to-you payout is almost always in the covered category.

Worked timeline: a ₹2,000 withdrawal that fails on a Tuesday

Make it concrete. Say a legal app approves your ₹2,000 winnings payout and hands it to UPI at 4 p.m. on Tuesday (T). The app’s settlement account is debited; the app marks it “paid” with a UTR. Your bank account shows nothing.

• Tuesday (T): Capture the UTR immediately. The credit hasn’t landed. This is normal for the first few hours — pending resolves.
• Wednesday (T+1): This is the deadline. By end of Wednesday, either the ₹2,000 is in your account, or the system must auto-reverse it (which, for a payout, means it goes back to the operator’s settlement, and the operator should re-attempt or refund your in-app balance). If neither happened, the clock for ₹100/day starts.
• Thursday (T+2): One full day past T+1. You are now owed ₹100 compensation on top of the ₹2,000 — and you should raise the formal UPI dispute (UDIR) citing the UTR.
• By T+5 / one week: If it’s still missing, you escalate to a written bank complaint, and the compensation has accrued to several hundred rupees.

The ₹2,000 example is the account-to-account row (operator’s bank → your bank), so T+1 governs. If instead this were a failed deposit you made into the game, it would be the merchant row and T+5 would govern. Same five symptom-words, different deadline, because the direction of money changed who the law treats as the merchant.

Deposit-side debit vs withdrawal-side debit: different problems, different fixes

This split is the spoke’s most useful original cut, so it gets its own section. “Money debited but not received” recovers completely differently depending on which way the money was flowing when it vanished. Diagnose the direction first.

Case A — Deposit-side debit (you paid in, balance didn’t rise)

What you’ll see: you tapped UPI to add money to the game wallet, your bank app and SMS confirm ₹[X] debited, and the game’s wallet balance stayed the same. Your money left your account toward the operator and didn’t show up as chips.

What it is, technically: this is a P2M (person-to-merchant) transaction. The game (via its payment aggregator) is the merchant. That single fact sets your deadline at T+5, not T+1, and puts the acquirer in the liability seat. The transaction can be in any of the three buckets — failed (cleanest), pending (wait), or deemed successful (the merchant’s reconciliation says it arrived but the wallet didn’t update).

How to recover it:

1. Do not re-deposit. The most common loss here is a player who thinks the first one “didn’t go through,” tries again, and now has two debits. Confirm in your bank statement how many debits actually happened before doing anything.
2. Raise the dispute on your UPI app against that debit (the per-app path is below). For a P2M failure, NPCI UDIR auto-converts an unresolved complaint into a chargeback at T+3 if the merchant/beneficiary bank doesn’t respond — and the TAT reversal deadline is T+5, with ₹100/day after.
3. Tell the app’s support too, with the UTR, in case the money did reach the operator but didn’t credit your wallet (a wallet-update bug rather than a rail failure). If the operator confirms it received the funds, the fix is on their side — they credit your wallet or refund the source. If they confirm they did not receive it, the rail failed and the reversal is owed to your bank.
4. Post-PROGA caveat: if the deposit was into a now-illegal money game, the cleanest outcome is the reversal of the debit, not the crediting of chips. Pursue the rail reversal and stop there — do not let support “fix” it by adding chips to a game you can no longer legally play.

The deposit case is, oddly, the one where you most want the transaction to be cleanly failed, because then you simply get your own money back. A deemed-successful deposit is worse: the operator may insist it was credited and you’re stuck proving the chips never appeared.

Case B — Withdrawal-side debit (payout left the operator, never reached your bank)

What you’ll see: the app shows your withdrawal “completed,” “success,” or “paid,” often with a UTR. Your bank account never received the credit. The operator’s money left its settlement account toward you and didn’t land.

What it is, technically: this is an account-to-account credit — the operator’s bank to your bank. Deadline T+1. Liable party: the beneficiary bank (yours, the one that was supposed to credit you). This is the row with the strongest and fastest protection in the whole framework.

How to recover it:

1. Get the UTR from the app’s payout record. This is the thread. The app should display it on the completed-withdrawal screen; if not, demand it in writing from support — they cannot claim “paid” without being able to produce the reference.
2. Hand the UTR to your bank and make them trace it. Ask the specific question: “Is there any credit in my account against UTR [number]? If not, this account-to-account transfer was debited but not credited, and per the TAT circular it should have auto-reversed by T+1.” If your bank confirms no credit exists, you have proof the money didn’t reach you — that’s your entire case.
3. Raise the UPI dispute (UDIR) on the transaction if it’s visible in your app, or call the NPCI line 1800-120-1740. For account-to-account (P2P) the complaint auto-converts to a chargeback at T+1 if the beneficiary bank doesn’t resolve it.
4. Claim the ₹100/day in writing once you’re past T+1, citing the circular by number (template below).

The withdrawal case is where a deemed-successful status hurts most: the operator’s “paid” stamp and the system’s “success” make it look like you already have the money. You break that with the bank trace. A UTR that resolves to “no credit found” in your account is the lever that converts an apparent success back into a recoverable failure.

The fork in one line: deposit-side = a P2M debit, T+5 clock, acquirer liable, goal is reversal of your money; withdrawal-side = an account-to-account credit, T+1 clock, beneficiary bank liable, goal is delivery of your owed payout, proven by the UTR trace. Get the direction wrong and you’ll quote the wrong deadline at the wrong party.

For the full map of every withdrawal failure type beyond this debit-without-credit case — KYC holds, daily caps, bonus locks, the per-app reality tables — go back up to the hub. For the UPI-specific dispute screens, the Teen Patti UPI withdrawal spoke walks them.

How to read your bank statement and UPI history to prove the debit

You can’t dispute what you can’t prove. The proof lives in two places — your bank statement and your UPI app history — and both hinge on one number. Here’s how to read each to build an evidence file that survives a bank’s “we have no record” brush-off.

The UTR/RRN: one number, many names

For a UPI transaction, the UTR (Unique Transaction Reference) and the RRN (Retrieval Reference Number) are, for practical purposes, the same 12-digit number. The RRN is the 12-digit reference used for inter-bank tracking of a UPI or card transaction; the UTR is the broader term that also covers NEFT/RTGS/IMPS, where the format differs (NEFT UTRs run ~16 characters, RTGS ~22). For your UPI debit, when the bank asks for “the RRN” and the app shows you a “UPI Reference No.,” they are pointing at the same 12 digits. This is the number your bank traces. Without it, the bank’s failed-transaction desk literally cannot look up your money.

Each app labels it differently, which is why people think they “don’t have a UTR” when they’re staring right at it:

• PhonePe: “UPI Reference No.” (or “UPI Transaction ID”)
• Google Pay: “Bank Reference ID” / “UPI transaction ID”
• Paytm: “UPI Ref No.”
• BHIM: “Transaction ID”

All four are the same 12-digit thread. (The exact menu path to each is in the dispute section below.)

Reading the bank statement to confirm the debit

Open your account statement or passbook for the transaction date. A UPI debit appears as a single line that contains, in some order:

• The debit amount (with a “Dr” marker or in the withdrawal column).
• A UPI narration that typically reads something like UPI/[12-digit RRN]/[beneficiary VPA or merchant name]/[bank]. The 12-digit block in that narration is your RRN/UTR — that’s where to read it off if the app won’t show it.
• The value date and time.

What you are proving with the statement is simple and powerful: the debit happened, on this date, for this amount, with this RRN. That establishes that money left. For a deposit failure, the matching question is whether the game wallet rose by that amount (it didn’t — that’s your dispute). For a withdrawal failure, the matching question is whether a credit ever appeared against the same RRN (it didn’t — that’s your dispute). The absence of the matching credit, against a named RRN, is the entire evidentiary core of a debited-but-not-credited claim.

Reading the UPI app history

In the app, open the transaction’s detail screen (not just the list). Capture, in one screenshot:

• The amount and date/time.
• The status word — “Failed,” “Pending,” or “Success/Completed” — which tells you your bucket.
• The UTR/RRN under its app-specific label.
• The beneficiary (the VPA or account the money was heading to).

Build the one-page evidence file on Day 0

Pull all of it into a single place within the first hour, because a “failed” transaction can drop out of an app’s quick view and a bank’s quick-trace window after a few days:

1. Screenshot of the app’s transaction detail (status + UTR).
2. Screenshot or PDF line of the bank statement debit showing the same RRN.
3. The bank SMS for the debit (it independently carries the RRN and timestamp).
4. The in-app withdrawal/deposit record with the amount and timestamp.
5. The support ticket ID once you raise one.

Five artifacts, one number tying them together. With that file, no desk can tell you “we have no record” — you hand them the record. Without it, you’re arguing from memory, and memory loses every payment dispute.

The exact claim path: bank → NPCI UDIR → RBI Ombudsman

Three doors, in order, gated by the clock. Climbing in sequence matters — skip a rung and the next authority bounces you back to the one you skipped. Here is each door, what it’s for, and the timeline gate that opens it.

Step 1 — Raise the in-app UPI dispute (feeds NPCI UDIR)

This is the fastest, lowest-friction door, and it’s where most debited-but-not-credited cases actually get fixed. Every major UPI app has a per-transaction complaint button that routes into NPCI’s Unified Dispute and Issue Resolution (UDIR) system — the automated, API-based engine NPCI launched in 2020 to replace the old manual, file-based dispute process. The menu path per app:

• PhonePe: History → tap the transaction → Help / Contact Support → “money debited but not received” / “payment failed” → submit. PhonePe’s own failed-transaction guide confirms this path.
• Google Pay: tap the transaction in activity → support/question option → select the failed/not-received issue → raise dispute.
• Paytm: Balance & History → UPI & Bank Transfer → open the transaction → Help & Support → pick the dispute reason → submit.
• BHIM: Transaction History → open the transaction → Raise Concern → file.

What UDIR does behind the screen is the part worth knowing, because it tells you when to stop waiting:

• For an account-to-account (P2P) transfer — your withdrawal credit — if the beneficiary bank doesn’t respond by the day after the transaction, UDIR auto-converts the complaint into a chargeback at T+1.
• For a merchant (P2M) payment — your game deposit — the auto-conversion to chargeback happens at T+3 if the merchant or its bank doesn’t respond.
• NPCI’s system keeps polling for the final status for up to 5 days before settling the transaction to a terminal state.

So the in-app dispute isn’t a black hole — it has a built-in deadline that forces a resolution. NPCI’s stated overall window for a UPI complaint is 3–5 working days.

If the app won’t let you raise the dispute (common when the app no longer recognises the transaction, or it’s a withdrawal the operator’s app handled, not yours), go straight to the NPCI UPI Help portal “Dispute Redressal” page. File with the UPI transaction ID (UTR/RRN), bank, amount, date, registered mobile, and email. The same engine processes it. The NPCI UPI complaint line is 1800-120-1740 and the help email is [email protected].

Step 2 — Lodge the bank’s failed-transaction complaint (claim the ₹100/day here)

Run this in parallel with Step 1, especially for an account-to-account withdrawal credit, because the beneficiary bank is the liable party for a P2P reversal and the compensation. Call your bank’s helpline or use its app’s complaint flow and lodge a failed-transaction dispute with the UTR/RRN. Then say the sentence that most callers never say:

“This is an account debited but not credited under RBI circular DPSS.CO.PD No.629/02.01.014/2019-20. It should have auto-reversed by T+1. We are past that, so I’m claiming the ₹100-per-day compensation, which the circular says is to be credited suo moto.”

Get a complaint reference number in writing. The bank’s grievance flow is the formal record that later feeds the RBI Ombudsman, and the 30-day clock that unlocks the Ombudsman starts from this complaint, so dating it matters.

Step 3 — Escalate to the RBI Integrated Ombudsman (after 30 days)

If the regulated entity — your bank, or the payment-system participant — doesn’t resolve it, the RBI Integrated Ombudsman Scheme 2021 (RB-IOS) is the free, binding escalation. The eligibility gate is exact: you can file with the Ombudsman if the regulated entity does not respond within 30 days of your complaint, rejects it, or you’re unsatisfied with its resolution. The scheme covers banks, NBFCs, and Payment System Participants — which is why a UPI/payment failure is squarely in scope. File online at cms.rbi.org.in. Note the outer limit too: the complaint must reach the Ombudsman within one year of the entity’s reply (or within one year and 30 days of your original complaint if you got no reply), so don’t let it drift.

The timeline gates as one clock

Read it as a staircase. Don’t run to the Ombudsman on Day 2 (it’ll bounce you to the bank), and don’t let a “failed” debit sit untouched for two weeks (you’ll miss the easy UDIR window and the auto-reversal you were owed). Each rung opens on a specific day.

The copy-paste claim letter that invokes the ₹100/day compensation

Here is the letter that does the work. It’s built to be impossible to brush off: it names the circular, the deadline, the liability, and the compensation clause, and it asks for a reference number. Fill the brackets, keep it factual, and send it to your bank’s grievance channel with a copy to the app’s support.

Subject: Failed UPI transaction — UTR [RRN] — debited not credited —
reversal + TAT compensation under RBI DPSS.CO.PD No.629

To: [Your bank's grievance officer / failed-transaction desk]

A UPI transaction was debited from my account but the credit was not
completed. Details:

- UTR / RRN (12-digit): [RRN]
- Amount: ₹[AMOUNT]
- Date and time of transaction (T): [DATE, TIME]
- My account number / UPI ID: [A/C or HANDLE]
- Transaction type: [account-to-account withdrawal credit / merchant
  deposit]  ← state which
- App status shown: [failed / pending / success-but-not-received]

This is a "debited but not credited" failure that is NOT attributable to
me. Under RBI circular DPSS.CO.PD No.629/02.01.014/2019-20 (dated
20 September 2019), such a transaction must be auto-reversed by:
  - T+1 for an account-to-account transfer, or
  - T+5 for a merchant payment.

It has now been [N] days since T, past the applicable deadline. The same
circular states that where compensation is involved it "shall be effected
to the customer's account suo moto, without waiting for a complaint or
claim," at ₹100 per day of delay beyond the deadline.

I therefore request, within your grievance timeline:
  1. Reversal/credit of ₹[AMOUNT] against the above UTR; and
  2. Credit of the ₹100/day compensation that has accrued from the TAT
     deadline to the date of actual credit; and
  3. A written complaint reference number for this grievance.

If this is not resolved within 30 days of this complaint, I will escalate
to the RBI Integrated Ombudsman (RB-IOS 2021) at cms.rbi.org.in, citing
this reference and the circular above.

[Name] · [Registered mobile] · [Date]

Two notes on using it well. State the transaction type honestly — “account-to-account withdrawal credit” pins your bank with the T+1 deadline; “merchant deposit” invokes the T+5 acquirer path. And keep the tone flat. The letter works because every line is a fact a regulated entity must answer, not because it’s angry. A UTR and a circular number move money; adjectives don’t.

For the broader template set — the in-app ticket, the official-support escalation, the Ombudsman filing, the consumer-helpline letter — the hub’s template library has all five rungs. This page deliberately ships only the one template tuned to the debited-but-not-credited claim, because that’s the case you’re here for.

The per-bank dispute desk: SBI, HDFC, ICICI, PNB, Axis

“Raise it with your bank” is useless advice until someone tells you which screen and which words. The five banks below cover most Indian retail accounts, and each routes a failed-transaction dispute through a slightly different door with its own internal turnaround time and its own reference number. Find your bank, take the exact path, and write down the reference it issues — that reference is what every later escalation hangs on.

A note before the table: every Indian bank is bound by the same RBI TAT circular, so the outcome (T+1 reversal, ₹100/day) is identical everywhere. What differs is the channel, the bank’s own internal grievance TAT (which is longer than the RBI reversal deadline — it’s how long they take to answer your complaint, not how long the rail takes to reverse), and how long a window you have to file a chargeback. Those three are what the per-bank notes below pin down.

SBI (State Bank of India)

The cleanest path is inside the app. In YONO / YONO Lite, go to UPI Transfer → UPI payment history, open the failed transaction, and choose Raise Dispute; the status then shows under the Dispute Status module in the same UPI section. If the app won’t surface it, file through SBI’s Customer Request and Complaint Form (CRCF) portal at crcf.sbi.co.in/ccf or walk into any branch. SBI issues a reference/acknowledgement number for the complaint, and you can track it by SMS, email, or the CRCF complaint-status page. The escalation gate SBI itself states is that if the matter isn’t redressed within its grievance window you can take it to the RBI Ombudsman, per its own customer-care UPI guidance. The toll-free line for help is 1800 1234. Keep the YONO dispute reference and any CRCF number — they’re different identifiers and the Ombudsman form asks for the one that proves your complaint date.

HDFC Bank

In the HDFC mobile banking app, go to UPI → Transaction History, select the failed transaction, and tap Raise Dispute. HDFC’s own UPI-complaint guidance also points users to the NPCI grievance portal (pgrs.npci.org.in) with the HDFC UPI transaction ID as a parallel route. For an unauthorised or fraudulent UPI debit, the dedicated report line is 1800 258 6161. HDFC reminds customers of the rule you’re invoking — any failed credit-push must reverse within one working day, failing which ₹100/day compensation is due — and to watch the statement for a “UPI-REV” or “UPI-RET” narration, which is the reversal landing. If it isn’t resolved within a month, HDFC’s own guidance is to escalate under the Integrated Ombudsman Scheme 2021. The “UPI-REV/RET” tell is worth memorising — it’s how you confirm a reversal credited without having to call anyone.

ICICI Bank

Log in to iMobile, open UPI Payments, select the account and the transaction, and raise the dispute there. ICICI’s UPI FAQ states a resolution TAT of 3–7 days (up to 30 in some cases), and — importantly — that the beneficiary bank has 15 days to respond to the chargeback. ICICI’s own framing is that if a UPI issue stays unresolved you can request the bank raise a chargeback within 40 days of the transaction, and if it’s still stuck after 15 days, file on the NPCI UPI dispute portal. Have the UPI transaction ID, status, date/time, amount, receiver details, and screenshots ready; the dispute line is 1800 1080. The number to hold ICICI to is its own 3–7 day resolution TAT — past that, you have a clean reason to escalate rather than wait.

PNB (Punjab National Bank)

PNB routes UPI disputes the standard way: in the app, go to History → select the transaction → Raise Dispute / Contact Support, which logs the ticket into NPCI’s system. As PNB’s flow (and the general RBI rule it follows) makes explicit, without that logged ticket you cannot later claim the ₹100/day compensation — the ticket is the evidentiary anchor, not a formality. PNB applies the standard dispute-filing windows: 45 days for a person-to-person transaction and 90 days for a person-to-merchant transaction, measured from the transaction date. If PNB doesn’t resolve within a month, the escalation is the same Integrated Ombudsman Scheme 2021. The single most useful PNB-specific fact: file within the 45/90-day window or the chargeback right lapses and you’re left arguing on good-faith basis only.

Axis Bank

Axis is unusually explicit about the rules in its own support pages. For an “account debited but beneficiary not credited” P2P case, Axis tells you to wait for T+1 first; if it’s still unresolved you write to the bank, and its stated overall resolution TAT is up to 45 days from the dispute-lodgment date. The dispute itself must be raised within 45 days of the transaction for a P2P case — anything later is handled on a good-faith basis and depends on the beneficiary bank. For a failed/cancelled transaction where money was debited, Axis says the amount is credited back, and for a timed-out transaction it settles to the beneficiary or back to your account within two working days. Axis’s grievance-redressal policy carries the full escalation ladder. The Axis-specific catch: it asks you to actually wait out T+1 before it’ll act, so don’t expect same-day movement on a P2P dispute.

The per-bank table at a glance

(Sources: SBI UPI customer care; HDFC UPI complaint guide; ICICI UPI FAQ; Axis debited-not-credited support; and the common RBI TAT circular.)

Two patterns cut across all five. First, the bank’s internal TAT is always longer than the rail’s reversal deadline — ICICI’s “3–7 days” and Axis’s “up to 45 days” describe how long they take to answer, while the T+1 auto-reversal runs on the rail regardless. Don’t confuse the two: the money can come back on T+1 even while the complaint ticket sits “open” for a week. Second, every bank ultimately backstops to the same RBI Ombudsman after roughly 30 days, so the per-bank quirks only govern the first lap. If you bank somewhere not listed here, the shape is identical: find the in-app “Raise Dispute” button on the transaction, get a reference number, note the bank’s stated grievance TAT, and start the 30-day Ombudsman clock from the day you complained.

When the payout comes by IMPS, NEFT, or RTGS instead of UPI

Not every gaming payout rides UPI. When a withdrawal is larger, or the operator’s payout processor chooses a different rail, the money may arrive (or fail to arrive) by IMPS, NEFT, or RTGS — a plain bank transfer to your account number and IFSC rather than a UPI credit to your VPA. The “debited but not credited” protections still apply, but the deadlines, the return mechanism, and the reference format all shift. Knowing which rail carried your money changes which clock you quote.

IMPS — the closest cousin to UPI

IMPS (Immediate Payment Service) sits under the same RBI TAT harmonisation circular and NPCI’s own IMPS & UPI TAT circular, so the rule is the one you already know: an IMPS transfer that’s debited but not credited to the beneficiary must auto-reverse by T+1, with ₹100/day beyond that, and the beneficiary bank is liable. In practice IMPS auto-reversals are among the fastest on any rail — often within minutes — because IMPS was built for instant 24×7 transfer and its return path is just as quick. The reference you trace is again the RRN (a 12-digit number, same shape as a UPI RRN), and you raise the dispute the same way: in your bank’s app under the IMPS/fund-transfer history, or by calling the bank with the RRN. If a gaming recovery payout reaches you by IMPS and stalls, treat it exactly like the account-to-account UPI case — T+1 clock, beneficiary bank liable, RRN is the thread.

NEFT — the batch rail with a two-hour return rule

NEFT (National Electronic Funds Transfer) is not instant. It settles in half-hourly batches, and its failed-credit protection works on a different mechanism called the B+2 return discipline. Per RBI’s NEFT procedural guidelines, the beneficiary bank must either credit your account immediately on completing a batch, or — if it cannot, for any reason — return the transaction within two hours of that batch’s settlement to the remitting bank. So an NEFT payout that doesn’t reach you doesn’t sit indefinitely: it bounces back to the operator’s bank within roughly two hours of the relevant batch, and the operator should then re-attempt or refund. Crucially, NEFT carries its own delay penalty: where there’s a delay in crediting or returning, the RBI rule is that the beneficiary bank pays interest at the current RBI LAF Repo Rate plus 2% for the delay period — a different compensation than UPI’s flat ₹100/day, and one most people don’t know exists. The NEFT reference is a UTR, but a longer one (roughly 16 characters, not the 12-digit UPI RRN), per the UTR-format reference. When a payout arrives by NEFT and fails, you’re quoting the two-hour B+2 return and the repo-rate-plus-2% interest, not T+1 and ₹100/day.

RTGS — the large-value rail

RTGS (Real Time Gross Settlement) is the rail for large transfers (historically ₹2 lakh and above), settled individually and in real time rather than batched. If an RTGS credit can’t be applied, the funds are typically returned within two hours of the failure to the remitting bank, per RBI’s RTGS guidance. Like NEFT, the delay compensation is interest-based (repo rate plus a margin) rather than the flat ₹100/day of the UPI/IMPS framework. The RTGS UTR is longer still (around 22 characters). A gaming payout is rarely large enough to ride RTGS, but a consolidated recovery of a stranded balance occasionally is — and if so, you quote the two-hour return and the interest compensation.

The rail-parallels table

Read the table as a fork in your evidence file: before you write a single complaint, identify the rail from the reference length and the narration. A 12-digit reference and a UPI/ or IMPS/ narration puts you on the ₹100/day, T+1 track. A 16- or 22-character UTR with an NEFT/ or RTGS/ narration puts you on the two-hour-return, interest-compensation track — and quoting the UPI ₹100/day at an NEFT failure just gets you corrected. The good news for a NEFT/RTGS failure is that the money usually bounces back to the sender within two hours, so the real question becomes whether the operator re-sent it, which throws you back to the operator’s payout support rather than your own bank.

Proving a deemed-successful debit that never arrived

The deemed-successful case is where most genuinely stuck money sits, and it’s the one where you have to prove a negative: that despite a “success” stamp and a UTR, no credit ever landed in your account. This section is the evidence chain that does that, and the specific lever — TCC/RET — that forces the system to re-check.

Why “success” doesn’t mean “credited”

When your bank successfully pushes the money out and settlement moves to the beneficiary bank, the transaction can be marked deemed approved to keep the rail moving — the money has reached the beneficiary bank but the final credit to the beneficiary account isn’t yet confirmed, per NPCI’s deemed-approved process. The status word and the bank balance disagree, and the status word is the one everyone trusts by default. Your whole job is to replace the word “success” with a fact: there is no credit against this UTR in this account.

The evidence chain, in order

Each link below proves one thing the next one needs. Build them in this sequence:

1. The UTR/RRN itself. Without the 12-digit reference there is nothing to trace; it’s the index the beneficiary bank searches on. Read it off the app, the bank SMS, or the statement narration.
2. The debit proof. Your bank statement line showing money left an account on date T for amount ₹X, carrying that same UTR in the narration. For a withdrawal this is the operator’s debit (which you may have to get from the app’s payout record); for a deposit it’s your own statement.
3. The bank narration cross-check. The statement narration ties the amount, the date, the rail (UPI/, IMPS/, etc.), and the UTR into one line. This is what stops a desk from claiming “we have no such transaction.”
4. The beneficiary non-credit proof. The decisive link: your bank confirming, in response to the UTR, that no credit exists against it in your account. Ask the exact question — “Is there any credit posted to my account against UTR [number]? If not, please confirm in writing.” A bank statement for the credit window with no matching entry is the documentary version of the same proof.

Those four together convert “the app says it paid me” into “a regulated entity can confirm the money is not in my account against the reference it claims to have paid.” That’s the case.

Forcing a TCC/RET re-check

Here’s the mechanism that actually moves a deemed-successful transaction off dead centre. In UPI’s dispute back-end, two confirmations decide whether your money comes back:

• TCC (Transaction Confirmation / Credit Confirmation) — the beneficiary bank confirming it did credit the beneficiary.
• RET (Return) — the beneficiary bank returning the funds because it could not credit (a dispute, an error, or a non-credit).

When you raise a chargeback through UDIR, the beneficiary bank is forced to respond with one of these in the next settlement cycle. Under NPCI’s revised chargeback rules effective February 2025, the system now automatically accepts or rejects the chargeback based on the TCC/RET the beneficiary bank files in the settlement cycle after the chargeback is initiated — it’s no longer a slow manual reconciliation. That automation is your lever. If the beneficiary bank truly never credited you, it cannot honestly file a TCC, so it must file a RET, and the money returns automatically. If it wrongly files a TCC, you now have a documented bank assertion that it credited you — which you can disprove with your statement and escalate, because the NPCI process and RBI penalties are designed precisely to stop banks from filing false TCCs to dodge reversals.

So the move to break a deemed-successful stall is concrete: raise the chargeback through UDIR to force the beneficiary bank to file a TCC or RET in the next settlement cycle. You don’t argue the status word; you trigger the mechanism that makes the holding bank put its answer in writing, and a bank that never credited you cannot file a truthful “I credited them.” That’s how you weaponise the reconciliation instead of waiting on it.

Reason-code and rejection-reason appendix

When a dispute or chargeback comes back rejected, the rejection isn’t the end — it usually carries a reason code, and each code has a specific counter. This appendix maps the common ones (UDIR/NPCI reason codes and typical bank dispute-desk rejections) to what they actually mean and how to push back. The codes follow NPCI’s dispute framework and the UPI error/response code reference.

The pattern across the whole table: most rejections are either a mis-classification (your failed-credit case was filed under a wrong-beneficiary code like CD1/CD2, which strips your ₹100/day eligibility) or a false confirmation (a TCC asserting a credit that your statement disproves). For the first, re-file under the correct failed-transaction reason. For the second, your bank statement is the trump card, and a false TCC is exactly what the revised NPCI rules and RBI penalties exist to punish.

Two more worked timelines

Worked timeline 2: a ₹750 deposit that’s debited but the wallet stays flat (deposit-side)

You add ₹750 to a wallet on Saturday 6 June (T) at 9:10 p.m. by UPI. Your bank SMS confirms ₹750 debited; the wallet still reads its old balance.

• Sat 6 Jun (T): Capture the UTR from the SMS and the UPI app. Check the bank statement — exactly one debit of ₹750, not two. Do not re-deposit. This is a P2M (merchant) debit, so the deadline is T+5, not T+1.
• Sun 7 Jun (T+1): Raise the dispute in your UPI app against the ₹750 debit. Tell the operator’s support too, with the UTR, in case the funds reached them but the wallet didn’t update.
• Tue 9 Jun (T+3): If the merchant’s bank hasn’t responded, UDIR auto-converts the complaint to a chargeback at T+3 for P2M, per the UDIR timelines.
• Thu 11 Jun (T+5): The merchant-payment reversal deadline. If the ₹750 still hasn’t reversed, the ₹100/day clock starts and you lodge the formal bank complaint citing the circular.
• Fri 12 Jun (T+6): One day past T+5 — ₹100 compensation has now accrued on top of the ₹750. By Tue 16 Jun (T+10) that’s ₹500 of compensation if it’s still missing.

The deposit case wants a clean failure — then you simply get your ₹750 back. Because it’s PROGA-era, the goal is the reversal of the ₹750, not chips: pursue the refund and stop.

Worked timeline 3: a ₹4,300 withdrawal that’s “paid” but never lands (withdrawal-side, deemed-successful)

The app approves a ₹4,300 stranded-balance recovery payout on Monday 1 June (T) at 2:30 p.m., shows it as “paid” with a 12-digit UTR. Your account never receives ₹4,300.

• Mon 1 Jun (T): Capture the UTR from the payout screen. This is account-to-account (operator’s bank → yours), so the deadline is T+1. Build the evidence file.
• Tue 2 Jun (T+1): The reversal/credit deadline. Hand your bank the UTR and ask: “Is there any credit against UTR [number]?” The answer is no credit found — that’s your proof. Raise the UDIR chargeback, which for P2P forces the beneficiary bank to file TCC or RET in the next settlement cycle.
• Wed 3 Jun (T+2): One day past T+1. ₹100 compensation has accrued. Lodge the formal bank complaint with the UTR, citing the circular and the “suo moto” clause.
• Fri 5 Jun (T+4): If the beneficiary bank filed a RET (it never credited you), the ₹4,300 returns to the operator’s settlement and the operator re-sends or refunds your in-app balance. Compensation stands at ₹300.
• Mon 8 Jun (T+7): If a wrongful TCC was filed, you escalate with your statement disproving the credit; by now ₹500 compensation has accrued and the bank’s own grievance TAT is running out.
• Wed 1 Jul (T+30): If still unresolved, file with the RBI Ombudsman — but the TCC/RET mechanism almost always settles a ₹4,300 case well before this.

The withdrawal case is where the deemed-successful “paid” stamp does the most damage, and the UTR trace plus the forced TCC/RET re-check is what breaks it. A ₹4,300 payout that resolves to “no credit found” against its UTR is a recoverable failure wearing a “success” label.

Why “deemed successful” is the case that drags — and how to break it

Worth its own section, because it’s where most genuinely stuck money sits. When a transaction is deemed successful but never arrived, three forces work against you at once, and naming them tells you how to counter each.

Force 1 — the status lies to everyone, including the staff. Your app, the operator’s screen, and often the first bank agent you reach all see “success.” So your opening problem isn’t getting a refund; it’s getting anyone to believe there’s a problem at all. The counter is the bank trace against the UTR. You don’t argue about the status word — you ask one factual question: “Is there a credit in my account against UTR [number]?” When the answer is no, the “success” is exposed as unreconciled, and the conversation flips.

Force 2 — the auto-reversal doesn’t fire. The T+1 / T+5 auto-reversal is built for transactions the system knows failed. A deemed-successful transaction isn’t (yet) classed as failed — it’s in the reconciliation queue, waiting for the beneficiary bank and NPCI to confirm or reverse it. The counter is to force the reconciliation by raising the UDIR dispute, which makes the beneficiary bank actually respond rather than leave it pending; if it doesn’t respond, the chargeback auto-triggers and the money comes back.

Force 3 — the operator points at the bank, the bank points at the operator. Each says the other has your money. The counter is to make the direction of the debit decide who’s right. If it’s a withdrawal, the operator’s settlement was debited, so the money is downstream of the operator — it’s a beneficiary-bank reconciliation issue, and your trace proves there’s no credit in your account. If it’s a deposit, your bank debited you cleanly, so the question is whether the merchant received it — and the UDIR P2M chargeback resolves that at T+3.

The practical sequence to break a deemed-successful stall: (1) bank trace confirms no credit against the UTR, (2) UDIR dispute forces the beneficiary bank to respond or auto-chargeback, (3) if it lingers past the NPCI window, the formal bank complaint with the ₹100/day claim, (4) the Ombudsman at Day 30. The money rarely makes it to Day 30 once you’ve forced the reconciliation — but the path is there if it does.

Common mistakes that lose a debited-but-not-credited claim

The rules are on your side here, which is exactly why the losses are almost always self-inflicted. The five that cost people their refund:

1. Not capturing the UTR on Day 0. A failed transaction can drop out of an app’s quick view within days, and a bank cannot trace a credit you can’t name. No UTR, no case. This is the single most expensive mistake. Capture it in the first hour.
2. Re-depositing or re-withdrawing “because the first one failed.” On the deposit side this gives you two debits; on the withdrawal side it confuses the operator’s records and can flag your account for review. Confirm in your bank statement how many debits actually happened before doing anything.
3. Quoting the wrong deadline at the wrong party. Demanding a T+1 reversal on a failed deposit (a merchant payment, which is T+5) just gets you told “you’re early.” State the transaction direction and quote the matching deadline.
4. Treating Day-0 pending as theft and skipping straight to RBI. The Ombudsman requires the entity to have had your complaint for 30 days first. Jump the queue and you’re bounced back, having wasted the time. Climb the rungs in order.
5. Sharing an OTP or UPI PIN with anyone who “calls to help.” The single most common way a debited-but-not-credited victim loses more money is a fake “customer care” caller who promises to “reverse the failed transaction” and asks for an OTP or PIN. No legitimate bank, app, or NPCI process ever needs your PIN or OTP to refund you. A refund flows to you and never requires your PIN. Hang up and report the number to cybercrime 1930 / cybercrime.gov.in.

On that last point: if you reached a “help number” from a Google search, a YouTube comment, or an SMS rather than the app’s official listing, treat it as a scam by default. The hub’s scam red-flags section and the Teen Patti Master customer care page go deep on why most posted “care numbers” are phishing traps. A genuine failed-transaction refund never starts with you reading out a code.

How long should each stage actually take?

A realistic clock, so you know when “wait” turns into “escalate.” Rule-backed rows are marked; the rest are typical processing behaviour.

The honest read of this table: a cleanly failed debit is usually back in your account within one to five days without you lifting a finger, because the auto-reversal is mandated. The cases that drag to Day 30 are almost always deemed-successful ones where the system thinks it paid you — and even those resolve once you force the reconciliation with a UTR-backed dispute.

When the money is genuinely gone: the limits of this framework

Honesty about where the leverage ends. The RBI/NPCI machinery is overwhelmingly strong against a rail failure — money that left a bank account and didn’t arrive — because every party in that chain (your bank, the beneficiary bank, the acquirer, NPCI) is RBI-regulated and bound by the TAT circular. That’s the recoverable kind, and it’s the kind this whole page is built for.

It’s weaker in two situations, and pretending otherwise wastes your time:

• The money never reached the rail. If your withdrawal is still sitting inside the operator’s queue (Gate 3 in the hub’s model) and was never handed to UPI, then no debit happened on a rail, there’s no UTR, and the TAT framework doesn’t apply yet. That’s a gaming-app problem, and the lever is the app’s support and the consumer-grievance route, not your bank. The hub and the withdrawal-stuck spoke handle that case.
• The operator is unlicensed, offshore, or a clone. If the money did reach a “merchant” that turns out to be a scam payment endpoint, the rail dispute and a cybercrime 1930 report are still worth filing — but recovery of funds that landed inside an entity outside Indian regulatory reach is not guaranteed. The strongest protection always was to only transact where KYC is real and the operator is licensed.

The bright line: if there’s a debit on a regulated rail and a UTR, you have a strong, rule-backed claim, and the steps above usually win it. If there’s no rail debit or the destination is lawless, the rules bend, and you fall back on the app-side and fraud-reporting routes the hub maps. Know which side of that line your money is on before you decide how hard to fight.

FAQ

1. My UPI withdrawal failed but the money was debited — will I automatically get it back? For a cleanly failed account-to-account transfer, yes — under RBI’s TAT circular it must auto-reverse by T+1, and the circular says compensation is credited “suo moto, without waiting for a complaint.” The catch is the deemed-successful case, where the system thinks it paid you; that one you have to prove missing with the UTR before the reversal triggers.

2. How many days does the bank have before it owes me compensation? T+1 for an account-to-account transfer (a failed withdrawal credit) and T+5 for a merchant payment (a failed game deposit), where T is the transaction date. Beyond that deadline, your bank owes ₹100 per day of delay, per the TAT circular.

3. What is the ₹100-per-day rule exactly? If a debited-but-not-credited transaction isn’t reversed within its TAT (T+1 or T+5), the liable bank must pay ₹100 for every day of delay beyond the deadline, credited automatically. So a withdrawal credit that’s still missing 4 days after T+1 has accrued ₹400 in compensation on top of the principal — claim it in writing citing circular DPSS.CO.PD No.629.

4. What’s the difference between a “failed” and a “deemed successful” transaction? A failed transaction is one the system concluded didn’t complete — a reversal is owed, often automatically. A deemed-successful (or “deemed approved”) transaction is marked completed even though your account wasn’t credited; the money reached the beneficiary bank but not your account, and it sits in reconciliation until settled. The second is the hard case because you must prove the missing credit.

5. The app says “success / paid” but nothing reached my bank. What now? Get the UTR from the app’s payout record and ask your bank to trace it. Ask precisely: “Is there any credit against UTR [number]?” If the answer is no credit found, that proves the money didn’t reach you — open a UPI dispute (UDIR) and claim the reversal. NPCI’s stated resolution window is 3–5 working days.

6. My deposit was debited but no chips were added. Is that the same rule? Different deadline. A game-wallet deposit is a merchant (P2M) payment, so the reversal deadline is T+5, not T+1, and UDIR auto-converts the complaint to a chargeback at T+3 if the merchant’s bank stays silent. Confirm in your bank statement how many debits happened, and don’t re-deposit to “try again.”

7. What is a UTR/RRN and is it the same number? For UPI, the UTR and RRN are effectively the same 12-digit reference. It’s labelled “UPI Reference No.” in PhonePe, “Bank Reference ID” in Google Pay, “UPI Ref No.” in Paytm, and “Transaction ID” in BHIM — all the same number, and it’s what your bank traces.

8. Where exactly do I find the UTR if the app won’t show it? Read it off your bank statement: a UPI debit line reads roughly UPI/[12-digit RRN]/[VPA]/[bank], and that 12-digit block is your UTR/RRN. Your bank SMS for the debit carries it too. So even if the app hides it, the statement and SMS independently give you the number.

9. Do I have to ask for the ₹100/day, or is it automatic? The circular says it should be credited suo moto — automatically. In practice many banks don’t, so you claim it in writing, quoting the circular’s “suo moto, without waiting for a complaint or claim” clause by name. You’re reminding them of an existing duty, not requesting a favour.

10. Does the ₹100/day apply if I sent money to the wrong UPI handle? No. The compensation only covers failures “not attributable to the customer.” A wrong-handle transfer completed — to the wrong person — so it’s not a “failed transaction” under the circular. You request a reversal from the recipient through your bank; you don’t claim the ₹100/day. A system failure on an app-to-you payout is covered.

11. How do I raise the NPCI UDIR complaint without the app? Use the NPCI UPI Help portal “Dispute Redressal” page and file with the UTR/RRN, bank, amount, date, registered mobile and email, or call 1800-120-1740. This routes to the same UDIR engine your app would use, which is the fix when the app won’t let you raise a dispute on the transaction.

12. When can I go to the RBI Ombudsman, and does it cost anything? After 30 days without resolution from the bank or payment-system participant, or if it rejects your complaint or you’re unsatisfied — file free at cms.rbi.org.in under RB-IOS 2021, which covers Payment System Participants. There’s an outer limit of one year from the entity’s reply, so don’t let it drift.

13. The operator and my bank each say the other has my money. Who’s right? The direction of the debit decides it. For a withdrawal, the operator’s settlement was debited, so the money is downstream of the operator — a beneficiary-bank reconciliation issue your UTR trace resolves. For a deposit, your bank debited you cleanly, so the question is whether the merchant received it — and the UDIR P2M chargeback settles that at T+3.

14. How long before a failed debit is normally back in my account? A cleanly failed transaction is usually reversed within one to five days with no action from you, because the T+1/T+5 auto-reversal is mandated. The cases that reach Day 30 are nearly always deemed-successful ones where the system believes it paid you — and even those resolve once you force the reconciliation with a UTR-backed dispute.

15. Someone called offering to “reverse my failed transaction” and asked for an OTP — is that real? No — it’s a scam, and it’s the most common way debited-but-not-credited victims lose more money. A genuine refund flows to you and never needs your OTP or UPI PIN. No bank, app, or NPCI process asks for your PIN to refund you. Hang up and report the number to cybercrime 1930 / cybercrime.gov.in.

16. Where exactly do I raise the dispute in the SBI YONO app? Open UPI Transfer → UPI payment history, select the failed transaction, and tap Raise Dispute; track it under the Dispute Status module in the same UPI section, per SBI’s UPI guidance. If the app won’t show it, file at crcf.sbi.co.in/ccf or a branch, and keep the reference number — the SBI help line is 1800 1234.

17. How long does ICICI say it takes to resolve a UPI dispute? ICICI’s own UPI FAQ states a resolution TAT of 3–7 days (up to 30 in some cases), with the beneficiary bank getting 15 days to respond to a chargeback. You can ask ICICI to raise a chargeback within 40 days of the transaction; the dispute line is 1800 1080.

18. What’s the deadline to file an Axis Bank UPI dispute, and how long does it take? For a P2P “debited but not credited” case, Axis asks you to wait out T+1 first, then writes that its overall resolution TAT is up to 45 days from lodgment. The dispute itself must be raised within 45 days of the transaction, or it’s handled on a good-faith basis only.

19. My payout came by NEFT, not UPI, and failed — does the ₹100/day still apply? No — NEFT runs on a different rule. Under RBI’s NEFT guidelines, the beneficiary bank must credit or return the transaction within two hours of the batch settlement (the B+2 discipline), and delay compensation is interest at the RBI repo rate plus 2%, not the flat ₹100/day. So a failed NEFT credit usually bounces back to the sender within about 2 hours.

20. My withdrawal arrived by IMPS instead of UPI — is the rule different? Almost identical. IMPS falls under the same NPCI/RBI TAT circular: a debited-but-not-credited IMPS transfer must auto-reverse by T+1 with ₹100/day beyond it, beneficiary bank liable, and you trace it by the same 12-digit RRN. IMPS reversals are often the fastest of all — frequently within minutes.

21. What do “TCC” and “RET” mean, and why should I care? They’re the two answers a beneficiary bank can file: TCC (“I credited the beneficiary”) or RET (“I’m returning the funds, I couldn’t credit”). Under NPCI’s Feb-2025 rules, your chargeback is auto-accepted or rejected based on which one the bank files in the next settlement cycle — so raising the chargeback forces the bank to put its answer in writing within 1 cycle.

22. My dispute was rejected with code CD1 or CD2 — what now? Those codes mean the system read your case as money sent to the wrong account or wrong UPI ID — the customer-attributable bucket, which doesn’t get the ₹100/day. If your money was actually a failed credit, that’s a mis-classification: re-file under the failed-transaction reason, not the wrong-beneficiary one, to restore your eligibility under the TAT circular.

23. The bank says “beneficiary already credited” but I see nothing — how do I fight a false TCC? Disprove it with your account statement showing no credit against the UTR, and demand a re-check. A bank standing on a false TCC is exactly what the revised NPCI rules and RBI penalties target, so escalate to the Ombudsman after 30 days if it won’t correct the record.

Sources & method. The reversal deadlines, compensation rule, liability split, and the “not attributable to the customer” definition on this page come from primary regulatory and payment-system sources — not personal payout tests. Key references: RBI failed-transaction TAT circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019); the NPCI deemed-approved process circular; NPCI UPI Help / UDIR and the UDIR auto-chargeback timelines (P2P T+1, P2M T+3); the “deemed success” reconciliation explainer; the RBI Integrated Ombudsman Scheme 2021 FAQ and cms.rbi.org.in; UTR vs RRN reference formats and the RRN as 12-digit inter-bank reference; PhonePe’s failed-transaction resolution guide; the per-bank dispute desks at SBI UPI care, HDFC’s UPI-complaint guide, the ICICI UPI FAQ, and Axis’s debited-not-credited support; the IMPS/NEFT/RTGS rail rules from the NPCI IMPS & UPI TAT circular and RBI NEFT procedural guidelines; the NPCI Feb-2025 TCC/RET auto-chargeback rules and the UDIR reason-code reference; and cybercrime reporting at cybercrime.gov.in / helpline 1930. This is information, not legal or financial advice — verify each step against your bank’s current UPI dispute policy and the operator’s terms.