Teen Patti UPI Withdrawal: The Settlement, UTR and Dispute Guide

The 30-second answer

A Teen Patti UPI withdrawal is a cash payout the app pushes over NPCI’s UPI rail to your UPI handle. Three things can stall it: the app’s own payout review (Gate 3), the NPCI switch failing to confirm the credit, or your beneficiary bank sitting on a reconciliation batch. If money was debited but not credited, RBI’s failed-transaction rules force an auto-reversal by T+1 and ₹100 per day after that, credited suo moto — without you asking. You trace the payout with its 12-digit RRN/UTR and dispute it through your UPI app’s complaint button, which feeds NPCI UDIR.

Editor’s verdict, up front. This page is the UPI-only deep dive. The 3 Patti withdrawal hub already covers per-app payout times, tax, state legality and the generic Day-0-to-30 ladder — read that first if your question is broad. What lives here is the part every other guide skips: the exact settlement mechanics of a UPI gaming payout, screen-by-screen UTR locations in PhonePe, Google Pay, Paytm, BHIM and your bank app, the real NPCI UDIR dispute screens with what each rejection means, and the precise T+1 / ₹100-a-day math with the circulars cited. If your payout rode UPI and went missing, this is the page that tells you which of three places it’s stuck and which button gets it back. One blunt rule before anything else: never deposit money “to release” a withdrawal — no legal app needs that, and post-PROGA a fresh money-game deposit is illegal.

2026 context in one line. The Promotion and Regulation of Online Gaming Act, 2025 banned online money games and the major operators suspended cash play from late August 2025, so many readers now have a recovery problem — a discontinued app still holding a balance — rather than a live-app speed problem. The good news for UPI specifically: banks kept processing withdrawals so users could pull existing balances out, and the rail protections on this page apply identically to a recovery payout. The UPI dispute machinery does not care whether the game is still running; it only cares that a debit happened and a credit didn’t.

Why UPI is the rail that gives you the most leverage

Before the mechanics, understand why a UPI payout is the best kind of stuck payout to have. Every other complaint about a gaming app — a locked bonus, a KYC freeze, a daily-limit block — is a fight against the app’s terms, where you are weak. A UPI payout that left the app and went missing on the rail is a different animal: it’s a payment-system problem, governed by RBI circulars and a real complaints authority, and the app is no longer the only party who can fix it.

UPI is run by NPCI, a not-for-profit company owned by a consortium of banks and overseen by the Reserve Bank of India. Once your ₹2,000 payout is handed to UPI, it travels through three regulated parties — the app’s payment partner (the remitter side), the NPCI switch, and your bank (the beneficiary side). Each of those is bound by RBI’s turn-around-time rules. That is the entire reason this page exists: a UPI payout converts a “the app won’t pay me” grievance, which is hard to win, into a “a regulated payment failed” grievance, which has mandated timelines and automatic compensation behind it.

So the first diagnostic question is not “is the app a scam?” It’s “did my payout actually reach the UPI rail, or is it still sitting inside the app?” Those are two completely different problems with two completely different fixes, and most players conflate them. The next section draws that line precisely.

How a Teen Patti UPI payout actually settles (the full chain)

“UPI is instant” describes the successful path. The moment something goes wrong, the payout drops onto a slower set of rails — reconciliation cycles and settlement batches — and that is where a “failed” withdrawal can sit in limbo for a day before it resolves. Here is the full chain, stage by stage, with the exact point at which each stage can stall.

Stage 1 — Inside the app: approval and debit from the withdrawable pot

When you tap “withdraw to UPI,” nothing has touched the rail yet. The app first runs its own checks — KYC match, daily limit, wagering, risk review — exactly as the hub’s four gates describe. Only after the app approves the payout does it debit your withdrawable balance and create an instruction to its payment partner (a bank or a payment aggregator like a PSP).

Where it stalls here: if your withdrawal shows “pending” or “under review” and no UTR/RRN has appeared, you are still at Stage 1. The money has not reached UPI. This is a gaming-app problem, and your lever is app support, not your bank — your bank cannot trace a transaction that was never handed to the rail. For the pending-state countdown specifically, the withdrawal-stuck page has the per-state waiting limits.

Stage 2 — The PSP / remitter bank: the debit hits the UPI switch

Once approved, the app’s payment partner sends a credit-push instruction into the UPI network through the NPCI central switch (technically the UPI Remittance and Clearing System, URCS). At this instant a 12-digit reference number is generated for the transaction — this is the RRN (Retrieval Reference Number), the single thread that ties your debit to a (hopefully) matching credit. Capture it. Without it, nobody can trace anything.

Where it stalls here: the switch may accept the instruction but be unable to immediately confirm the outcome. This produces a “deemed” state — the payment was processed but the terminal status couldn’t be confirmed with NPCI yet. Decentro’s status documentation describes a deemed transaction as one that “normally reaches its terminal state within T+3 days” through reconciliation. So a payout briefly stuck in a deemed/processing state is not lost — it is mid-reconciliation, and the rules below decide its outcome.

Stage 3 — Your beneficiary bank: the credit lands (or doesn’t)

The NPCI switch routes the credit instruction to your bank — the beneficiary bank. Your bank must credit your account and send back a confirmation. When it works, this is the sub-second part everyone calls “instant.” When it doesn’t — your bank was down, the handle no longer resolves, your receiving account hit a daily inbound limit, a timeout — your bank fails to confirm the credit, and the transaction is now deemed-failed / pending on the rail even though the app’s side already debited.

Where it stalls here: this is the dreaded debited-but-not-credited state, and it is the most consumer-protected position in the entire chain. The transaction does not reverse the instant the screen says “failed.” Instead, the banks reconcile in cycles, and RBI’s turn-around-time rules force the outcome. We’ll get to those exact numbers next.

Stage 4 — Reconciliation and the dispute layer (TCC / RET / chargeback)

If a credit can’t be confirmed, the two banks settle the truth in the next settlement cycle. The beneficiary bank raises one of two signals:

• TCC (Transaction Credit Confirmation) — “we did credit the customer.” If TCC comes back, the money reached you; check your bank statement, not just the app.
• RET (Return) — “we could not credit; returning the funds.” If RET comes back, the money bounces to the remitter side and reverses to you.

Per the NPCI circular dated 10 February 2025 (auto accept/reject effective 15 February 2025), the dispute system now automatically accepts or rejects a chargeback based on the TCC/RET the beneficiary bank raises in the next settlement cycle (Upstox summary, Business Standard). In plain terms: when you raise a dispute, you are no longer waiting on a human at a bank to read your email — the system polls for the beneficiary bank’s TCC/RET and resolves the chargeback mechanically.

The one-sentence map of the chain: Stage 1 is the app; Stages 2–4 are the rail. If there’s no RRN, you’re at Stage 1 and you fight the app. If there’s an RRN and the credit failed, you’re at Stage 3–4 and the RBI/NPCI rules are on your side. Sorting which stage you’re in is 80% of getting paid.

The status words decoded: pending vs failed vs deemed vs successful

UPI apps throw around four or five status words, and each demands a different action. Reading the wrong action off the wrong word wastes the exact days you’d need for the right one. Here is what each actually means and what to do.

The two rows that trip people up most: “Pending with no RRN” is an app problem (your bank can do nothing yet), while “Successful but nothing arrived” is the worst state because the app insists it paid — there you need the RRN to prove the money never reached you. A genuine “Failed, money debited” is paradoxically the best state to be in, because the refund is rule-mandated and largely automatic.

Editor’s note on “deemed”: you will rarely see the literal word “deemed” as a consumer — it’s a back-end status. But knowing it exists explains why a payout can hang for a day or two without being lost: the system literally hasn’t confirmed the outcome yet and has until T+3 to resolve it through reconciliation. Don’t panic-spam support inside that window.

The RRN / UTR: what it is, and where every app hides it

You cannot trace, dispute, or prove a missing UPI payout without its reference number. The catch is twofold: every app labels it differently, and there’s a genuine technical distinction most guides get wrong. Get this right and the rest of the dispute is mechanical.

RRN vs UTR — the distinction that actually matters

Here’s the original-insight piece. People say “UTR” for everything, but they’re not the same number:

• A UPI / IMPS transaction carries a 12-digit RRN (Retrieval Reference Number) at the banking level. That is the real reference your bank and NPCI use to trace a UPI payout (xFlow, Angel One).
• A NEFT / RTGS transaction carries a longer UTR (Unique Transaction Reference), typically 16–22 characters (Winvesta, Eximpe).

Why this matters for your dispute: when a Teen Patti payout rode UPI, the number you quote to your bank should be the 12-digit RRN. If your bank’s failed-transaction desk asks for a “UTR” and you give them a UPI RRN, that’s correct — at the consumer level the apps just call the RRN a “UTR” or “transaction ID.” But if the app fell back to a bank/IMPS transfer for a larger amount, you may have an IMPS RRN or a longer reference instead, and a few-rupee-off digit count is a quick tell for which rail your payout actually used. A 12-digit number means UPI/IMPS; a long alphanumeric string means NEFT/RTGS.

The practical line: for a Teen Patti UPI payout, you’re looking for a 12-digit RRN, even though every app and your bank may print the word “UTR” next to it. It’s the single thread tying your debit to the missing credit. Capture it on Day 0 — once a failed transaction ages out of an app’s quick view, digging it back out is far harder, and your bank cannot trace a credit you can’t name.

Screen-by-screen: where to find the RRN/UTR in each app

App labels confirmed against the providers’ own help pages and a consolidated app-label reference.

PhonePe

• Tap History (bottom bar) → open the transaction → the reference appears as “UPI Reference No.” (12 digits). It also rides in the bank SMS and your statement. PhonePe groups transactions in its History/passbook view; older guides say “Passbook,” current builds say History.

Google Pay

• Tap See transaction history → open the transaction → scroll to details. Google shows two numbers: a “Google transaction ID” (Google’s own, not what your bank traces) and the “UPI transaction ID” (the 12-digit one your bank needs). Quote the UPI transaction ID, not the Google one — this is a common mix-up that gets disputes bounced.

Paytm

• Open Balance & History (or Passbook) → tap UPI & Bank Transfer to separate UPI entries from Paytm-wallet entries → open the transaction → the reference shows as “UPI Ref No.” (12 digits).

BHIM

• Open Transaction History → tap the transaction → it’s labelled “Transaction ID” (12 digits) and is the same RRN.

Your bank app / statement (the source of truth)

• This is the one most players forget, and it’s the most authoritative. In your bank’s statement the entry reads something like UPI/<RRN>/..., and a failed/reversed one often shows the tell-tale prefix UPI-REV or UPI-RET followed by the transaction ID (per Google Pay’s own guidance via CitizenNest). If you can see a UPI-RET or UPI-REV line matching your amount, that is direct evidence the rail returned the money — useful proof either way.

One thing the apps obscure: the RRN is the same 12-digit number whether it’s printed as “UPI Reference No.”, “UPI transaction ID”, “UPI Ref No.”, or “Transaction ID.” Google Pay is the only one that shows two IDs — always grab the UPI one, never the Google one.

Where exactly each stage stalls — the UPI failure map

The hub lists ten generic stall reasons. Here is the UPI-specific version: the failure modes that are peculiar to the rail, mapped to the stage they happen at, with the one fix for each.

The single most useful column is “Stage.” Anything at Stage 1 (no RRN) is the app’s problem and your bank cannot act. Everything from Stage 2 onward (RRN exists) is the rail, and the RBI/NPCI machinery applies. So before you do anything, ask: do I have an RRN? That one question routes you to the right door.

The T+1 auto-reversal and ₹100/day rule — the precise mechanics

This is the protection that makes a UPI payout the best stuck state to be in. Most guides quote “₹100 a day” loosely. Here are the exact mechanics, who owes it, and how to claim it, with the circular cited.

What the RBI circular actually says

The binding rule is RBI Circular RBI/2019-20/67, DPSS.CO.PD No.629/02.01.014/2019-20, dated 20 September 2019 — the “Harmonisation of Turn Around Time (TAT) and customer compensation for failed transactions.” Its single most important sentence is the suo moto clause: financial compensation “shall be effected to the customer’s account suo moto, without waiting for a complaint or claim from the customer.” That means the credit and the compensation are supposed to land automatically. You don’t have to ask. (You should still chase it if it doesn’t appear — automatic isn’t the same as reliable.)

For a UPI account-to-account transaction where you were debited but the beneficiary was not credited, the circular’s annex sets:

• Auto-reversal of the failed transaction by T+1 (T = the transaction day; so by the end of the next calendar day).
• If the reversal does not happen by T+1, the bank owes ₹100 per day of delay beyond T+1, credited suo moto.

For a UPI payment to a merchant where confirmation failed, the auto-reversal window is T+5 before the same ₹100/day kicks in.

A gaming payout to you travels the account-to-account path (the app is paying into your account), so the protective number is T+1, not T+5. That’s the favourable read for a stuck Teen Patti withdrawal.

The full TAT table (so you can sanity-check any rail)

The same circular harmonised the reversal windows across all payment systems. Knowing the neighbours helps you spot whether your payout used UPI or fell back to a card/IMPS rail.

Source: the annex of RBI DPSS.CO.PD No.629, 20 Sep 2019. PhonePe’s own failed-transaction guide confirms the same T+1 (P2P) / T+5 (P2M) windows and cites this exact circular.

Who owes the compensation — and the one big exclusion

The compensation is owed by the bank that failed to complete its leg — in a debited-but-not-credited case, that is generally settled between the remitter and beneficiary banks, and the credit (plus any ₹100/day) lands in your account. You raise it through your bank because that’s the door you can reach.

The exclusion to know: the ₹100/day compensation applies to technical / system failures, not to your mistakes. If you typed a wrong UPI handle and the money went to the wrong (but valid) person, that’s not a system failure — it’s a “wrong beneficiary” case with a different, weaker recovery path. But a Teen Patti payout to your own registered handle that the rail couldn’t credit is squarely a system failure, so it’s covered.

Worked compensation timeline — a ₹2,000 payout that fails

Let’s make the math concrete. Say a ₹2,000 Teen Patti UPI payout is debited from the app’s side on Monday (T) and never lands in your bank.

• Monday (T): debit happens, app shows “success” with an RRN, your bank shows nothing. You screenshot everything and capture the RRN.
• Tuesday (T+1): the rule’s deadline. The transaction should be auto-reversed by end of today. Often it is — the ₹2,000 simply appears back on the app side or your bank shows a UPI-RET.
• Wednesday (T+2): still missing. The bank now owes ₹100 of compensation (one day beyond T+1).
• Friday (T+4): still missing. Compensation owed is ₹300 (₹100 × 3 days beyond T+1), credited suo moto alongside the ₹2,000 when it resolves.

So by the time you reach the bank-dispute rung, you’re not just asking for your ₹2,000 back — you’re entitled to ₹2,000 + ₹100/day of delay past T+1, and the rule says they should add it without you asking. Quote the circular number when you ask, because frontline staff often don’t volunteer the compensation.

When the payout doesn’t ride UPI: the IMPS / NEFT fallback

Not every “UPI withdrawal” actually settles over UPI. Operators and their payment partners route larger payouts, or payouts to a saved bank account rather than a handle, over IMPS — and for amounts above the UPI ceiling, sometimes NEFT. The screen still says “withdraw to UPI,” but the rail underneath changed, and that changes your reference number, your tracking surface and your reversal clock. Knowing which rail you actually used is the first move, because a dispute filed against the wrong rail goes nowhere.

How to tell your payout fell back to IMPS or a bank transfer

The reference number is the tell. A pure UPI payout carries a 12-digit RRN. An IMPS payout also carries a 12-digit reference, but it’s an IMPS RRN — your bank statement labels the entry IMPS/P2A/<RRN>/... (P2A = person-to-account) rather than UPI/... (HDFC’s IMPS reference primer, Razorpay). A NEFT payout carries a longer UTR (16–22 characters) and your statement reads NEFT/<UTR>/.... So the quick diagnostic is: open your bank statement, find the debit-or-credit attempt at your payout’s timestamp, and read the prefix. UPI/ means you’re on the UPI rail and everything earlier in this guide applies as-is; IMPS/P2A/ means the operator pushed it as an IMPS bank transfer; NEFT/ means it batched.

Why operators fall back at all: the standard UPI per-transaction and daily cap sits around ₹1 lakh for most users (NPCI/bank limit, per Paytm), so a payout above it can’t go P2P over UPI and the PSP reroutes it to IMPS (cap typically ₹5 lakh) or NEFT. A payout to a bank account number + IFSC you saved — rather than a VPA — also commonly settles as IMPS, because there’s no handle to push to.

The different reversal timeline for an IMPS fallback

The good news: the RBI TAT circular treats an IMPS failure on the same favourable footing as UPI. A debited-but-not-credited IMPS transaction must be auto-reversed by T+1, with the same ₹100/day beyond that (RBI DPSS.CO.PD No.629). So your compensation math doesn’t change. What changes is the tracking surface: IMPS doesn’t have UDIR’s slick per-transaction “raise complaint” button the way UPI apps do. An IMPS failure is traced and disputed through your bank, using the IMPS RRN, not through a UPI app. In practice you wait 24–48 hours for the auto-reversal, and if it doesn’t land you call the bank’s failed-transaction desk with the IMPS RRN (Razorpay, Lemonn).

NEFT is the slowest and the one to watch. NEFT settles in half-hourly batches during banking hours, so a NEFT payout that “should have arrived instantly” simply hasn’t been picked up by the next batch yet — that’s not a failure, it’s the rail’s normal cadence. A genuinely failed NEFT credit must be returned within 2 hours of the batch settling (the NEFT return-leg rule), and if the return doesn’t reach you, the same T+1 / ₹100-a-day TAT compensation applies. The trap with NEFT is panicking inside a batch window: a NEFT payout initiated at 4:55 PM that hasn’t landed by 5:10 PM is almost certainly waiting on the 5:30 PM batch, not lost.

How to track and dispute an IMPS fallback specifically

1. Confirm the rail. Statement prefix IMPS/P2A/ — capture the 12-digit IMPS RRN.
2. Wait the IMPS window. Auto-reversal target is T+1; in practice many reverse inside 24–48 hours. Don’t dispute before then unless you’re freezing evidence.
3. Use the bank, not a UPI app. There’s no UDIR front-end for IMPS the way there is for UPI. Call or message your bank’s failed-transaction / disputes desk, quote the IMPS RRN, and ask them to trace the P2A credit against the beneficiary bank.
4. Claim the same compensation. Cite the same RBI circular — IMPS sits in the same T+1 / ₹100-a-day row of the TAT table. A 3-day delay still earns you ₹200 beyond the ₹100 owed at T+2.
5. Escalate identically. If the bank hasn’t resolved a genuine IMPS rail failure in 30 days, the RBI Ombudsman covers IMPS exactly as it covers UPI.

The one-line rail map: read the statement prefix. UPI/ → work the UPI app + UDIR. IMPS/P2A/ → work your bank with the IMPS RRN, same T+1 protection, no UDIR button. NEFT/ → wait for the next half-hourly batch before assuming failure, then work the bank with the UTR. Same compensation everywhere; different doors.

NPCI UDIR: the dispute engine, screen by screen

When the auto-reversal doesn’t happen on its own, you escalate through UDIR — Unified Dispute and Issue Resolution, NPCI’s automated, single-channel system for UPI disputes (Razorpay’s UDIR explainer). The crucial thing to understand: when you tap “raise complaint” inside your UPI app, you are feeding UDIR — the app is a front-end to NPCI’s dispute machine. Here’s how that machine resolves your case.

How UDIR decides your case (the auto-resolution logic)

UDIR doesn’t wait for a human to read your complaint. It continuously polls the participating banks until the final status is confirmed, with a “Check Status” surface in the app for real-time monitoring (Razorpay). Then it applies hard timelines:

• P2P (person-to-person, which a payout-to-you resembles): if the beneficiary bank doesn’t respond by T+1, the complaint auto-converts into a chargeback.
• P2M (person-to-merchant): if no response after 3 days from the transaction date, it converts to a chargeback.
• NPCI keeps polling for up to 5 days in the absence of a response.

Once a chargeback is raised, the auto accept/reject logic (live since 15 February 2025) resolves it on the beneficiary bank’s TCC or RET in the next settlement cycle, as covered above. So the modern UDIR flow is: complaint → poll → auto-chargeback if no response → auto accept/reject on TCC/RET. Largely mechanical, and largely in your favour when the credit genuinely failed.

Raising the complaint inside each UPI app

Every app has a per-transaction complaint button. Use the transaction-level path, not the generic app-help menu — the transaction path attaches the RRN automatically.

PhonePe

• Open History → the failed transaction → Help / Contact Support → choose the issue (“money debited but not received” / “payment failed”) → submit. Mapped to PhonePe’s own escalation: Help → Report Issue → Payment Issues → select the failed transaction → “Money Deducted”, which triggers auto-resolution. PhonePe states most refunds arrive within hours but the regulatory maxima are T+1 (P2P) / T+5 (P2M) (PhonePe guide).

Google Pay

• See transaction history → tap the transaction → “Having issues?” → follow the prompts to create a ticket (Google Pay help). You may be asked to add an attachment (your bank statement covering the transaction date) in the ticket. Google states a deducted amount is typically refunded within 3 business days.
• The 21-day trap: Google Pay raises complaints through partner banks, and if more than 21 days have passed since the transaction, the partner bank can no longer raise the complaint for you — you must go to your own bank directly (Google Pay help). This is a hard deadline. Don’t sit on a Google Pay dispute for three weeks.

Paytm

• Open Balance & History → UPI & Bank Transfer → the transaction → Help & Support (at the bottom of that transaction) → pick the dispute reason → submit. Use the per-transaction Help, not the app’s generic help.

BHIM

• Transaction History → the problem transaction → “Raise Concern” → file the complaint. BHIM forwards it to your bank for verification.

Going straight to NPCI (when the app stalls)

If the app won’t let you raise a concern — common when the app no longer recognises the beneficiary, or the operator wound down — go directly to NPCI:

• The NPCI UPI Help portal → “Dispute Redressal” / “Get in touch — UPI complaint” → file with the UPI transaction ID (RRN), bank, amount, date and email. Google Pay’s own help explicitly routes unresolved cases here (per CitizenNest’s summary of GPay guidance).
• NPCI UPI complaint line: 1800-120-1740.
• NPCI’s stated UDIR resolution window is 3–5 working days.

The screen-by-screen logic in one line: raise the complaint at the transaction level inside your app (it auto-attaches the RRN), and if the app blocks you, file the same RRN directly at the NPCI portal. For the even deeper screen walkthrough of the dispute form itself, the UPI failed, money debited page goes further.

What each UDIR rejection reason actually means

A dispute can come back rejected, and the reason code tells you whether you’ve lost or whether you’ve just been routed wrong. Decoding the rejection is the difference between giving up and re-filing correctly.

The two rejections to never accept at face value: “beneficiary credited” (TCC) and “already settled.” Both claim you were paid. If you genuinely weren’t, the next move is to pull your bank statement for the exact date and search for the amount — the credit may be hiding under a UPI reference description you didn’t recognise. If it’s truly not there despite a TCC, that’s now a bank-side deficiency (the bank claimed a credit that didn’t happen), and you escalate it as a bank grievance, not a rail dispute. The RRN is your proof either way.

The per-bank failed-transaction desk: where each major bank handles your dispute

The UPI app raises the dispute, but the credit landed (or didn’t) at your bank, so eventually you’re talking to the beneficiary bank’s failed-transaction desk. Each big bank has a slightly different door, internal turnaround and reference. Here’s the walkthrough for the five banks most Teen Patti payouts land in — the exact channel, the internal TAT each quotes, and the reference number each issues so you can chase it.

SBI — State Bank of India

The in-app path runs through YONO Lite / SBI’s UPI: open UPI → UPI payment history (or Payment History) → select the failed transaction → Raise Dispute, then track it under the Dispute Status module inside UPI (per ClearTax’s SBI walkthrough). SBI’s UPI customer-care surface is its dedicated UPI care page. The reference SBI issues is a complaint/ticket number under its CMS (complaint management system) — note it, because the Dispute Status module keys off it. SBI’s standard UPI dispute resolution sits inside the NPCI 3–5 working-day window, with the T+1 reversal applying first. If SBI’s own desk stalls, the same RRN goes to NPCI directly.

HDFC Bank

HDFC takes the dispute through NetBanking or MobileBanking — register the failed transaction, attach a screenshot, and quote the transaction ID (HDFC grievance redressal); the unauthorised-transaction line is 1800 258 6161. The reference HDFC issues is an SR/CRN — Service Request / Complaint Reference Number — keep it, because every follow-up keys off it. Watch HDFC’s TAT honestly: while the reversal obeys the RBI T+1 rule, HDFC quotes up to 10 working days to resolve a complaint or query, stretching toward 15–30 days where the beneficiary leg needs investigation (HDFC grievance policy). Don’t let the 10-day complaint TAT be confused with the T+1 reversal deadline — the money should reverse far sooner than the complaint formally “closes.”

ICICI Bank

ICICI’s cleanest path is inside iMobile: log in → UPI Payments → pick the account → select the transaction → raise the dispute, and watch the Dispute Status surface. The phone route is 1800 1080 with the UPI transaction reference ID ready (ICICI UPI FAQs). ICICI quotes resolution in 3–7 days (up to 30 in hard cases), with reversals “as per RBI/NPCI guidelines within 48 working hours” and most landing in 2–4 hours. The number to know at ICICI: if the dispute stalls, you can ask ICICI to raise a chargeback within 40 days of the transaction, after which the beneficiary bank has 15 days to respond — and if it’s still unresolved after 15 days you take the same reference to the NPCI portal.

PNB — Punjab National Bank

PNB routes UPI disputes through BHIM PNB / its CGRMS grievance system and its call centre on 1800-1800 / 1800-2021 / 0120-2490000, or care@pnb.co.in (PNB grievance portal, ClearTax). PNB issues a complaint reference number you track online through its CGRMS. Resolution sits in the 3–5 working-day band, T+1 reversal first. Because PNB’s app dispute surface is less polished than the private banks’, PNB users often get faster traction filing the same RRN directly at the NPCI portal in parallel — the NPCI route doesn’t depend on PNB’s app recognising the transaction.

Axis Bank

Axis publishes a dedicated “account debited but beneficiary not credited” UPI dispute form on its support site, where you supply the 12-digit transaction reference number (Axis UPI dispute form). Axis is unusually explicit about the wait rules: for a P2P credit not received, wait T+1; for P2M, wait T+5 before the dispute is actionable (Axis dispute guidance). Axis’s overall dispute resolution window can run to 45 days, and a P2P dispute must itself be raised within 45 days of the transaction — so the deadline cuts both ways. Axis issues a dispute/complaint reference on lodgment; after Level 1 and Level 2 escalations, or 30 days without resolution, Axis points you to the Ombudsman.

The pattern across all five: the reversal is governed by the RBI T+1 rule and should happen in hours-to-a-day, while the bank’s own complaint TAT (3–5 days at SBI/PNB, 3–7 at ICICI, up to 10–30 at HDFC, up to 45 at Axis) is a separate, slower clock for formally closing the case. Never accept “it’ll take 10 days” as the answer for your money — the money is on the T+1 clock; only the paperwork is on the slow one. And every bank issues a reference number on lodgment: get it in writing, because every escalation upward keys off that one string.

The UDIR rejection-reason decoder (expanded)

When a dispute or chargeback comes back rejected, the reason is rarely “you lose.” More often it’s “you filed against the wrong leg” or “the window closed.” Here’s the expanded decoder — each common outcome, what it actually means on the rail, and the exact counter-action. This goes beyond the short table above and covers the codes the newer 2025 chargeback framework introduced.

TCC raised by the beneficiary bank (Transaction Credit Confirmation). The beneficiary bank is asserting it did credit you. Counter-action: pull the bank statement for the exact date and amount before accepting it — the credit may be sitting under a UPI description you didn’t recognise. If it’s genuinely absent, the TCC was wrong, and you re-escalate as a bank deficiency (a bank claiming a credit that didn’t occur), attaching the statement as proof of absence.

RET raised (Return). The beneficiary bank could not credit and is returning the funds to the remitter side. Counter-action: this is good news — confirm the reversal lands in 1–2 settlement cycles; if it doesn’t, chase the remitter side (the app’s PSP) because the money is now travelling back through them.

Chargeback auto-rejected — beneficiary responded with TCC in the cycle. Under the auto accept/reject logic live since 15 February 2025, the system closes the chargeback the moment a TCC arrives (Business Standard). Counter-action: same as a raw TCC — reconcile the statement; if truly unpaid, this is the case where the new RGNB / good-faith re-raise below matters.

Chargeback rejected — then re-raisable via RGNB (good-faith negative chargeback). Since the 15 July 2025 framework, a remitting bank can re-raise a previously rejected chargeback if the complaint is genuine, without NPCI’s old manual whitelisting (NPCI OC-184B, Businessworld). Counter-action: if your bank tells you “the chargeback was rejected, nothing more we can do,” cite RGNB explicitly and ask them to re-raise it as a good-faith chargeback — this is the lever that didn’t exist before mid-2025.

Rejected — CD1 / CD2 chargeback cap hit. Since December 2023 there’s a cap of 10 chargebacks per customer and 5 per payer-payee pair per 30 days; the 11th (CD1) or 6th (CD2) is blocked (Hero FinCorp). Counter-action: this rarely bites a normal player, but if you’ve been disputing many small payouts, space them — or route the genuine one through your bank’s manual desk rather than the auto-chargeback path.

Rejected — wrong reference / no matching transaction. The reference you quoted couldn’t be matched. Counter-action: you almost certainly quoted the Google transaction ID instead of the UPI transaction ID, or an old/typo’d RRN. Re-file with the correct 12-digit UPI RRN copied from the transaction-detail screen.

Rejected — out of TAT / window closed. You filed past a deadline (Google Pay’s 21-day partner-bank limit, or Axis’s 45-day P2P chargeback window). Counter-action: the app or partner bank can no longer raise it, so go straight to your own bank’s manual disputes desk with the RRN; the RBI Ombudsman remains available after 30 days regardless of app-level windows.

Still “pending — polling.” UDIR is still polling the banks; it polls up to 5 days and auto-converts a P2P complaint to a chargeback at T+1 if no response (Razorpay UDIR). Counter-action: wait it out; spamming new complaints resets nothing and clutters the case.

The decoder in one rule: a rejection is a routing signal, not a verdict. TCC/“already settled” → reconcile your statement. Wrong reference → re-file with the 12-digit UPI RRN. Out of TAT → go to your own bank. And after mid-2025, “chargeback rejected” is no longer final — the RGNB good-faith re-raise is the move most frontline staff won’t volunteer.

The UPI edge cases that quietly trap a gaming payout

Beyond the clean “debited, not credited” case, a handful of edge cases swallow gaming payouts specifically — because a gaming payout is a credit pushed to you on a handle the app has on file, and any drift in that handle or any cap on your receiving side breaks it silently. Each one below has a distinct fix.

Your VPA / UPI ID changed, was deactivated, or no longer resolves

This is the single most common silent trap. You registered a handle months ago, then changed banks, closed the linked account, or your PSP retired the VPA — and the app still has the dead handle on file. The payout shows “successful/paid” on the app side because the app handed a valid-looking instruction to the rail, but the credit can’t resolve to a live account. On the rail this surfaces as an invalid-VPA class failure (the U15 “invalid VPA” family in NPCI’s response codes, per Paytm’s error-code guide). The fix: update your withdrawal method to a live, verified handle first, then ask the app to re-issue the payout — and quote the original RRN as evidence the first attempt left the app, so they don’t make you re-clear KYC. Never re-request to the same dead handle; it fails identically.

The beneficiary bank is inside an NPCI / bank maintenance window

UPI’s “always on” reputation hides a real maintenance cadence. Banks and NPCI run scheduled maintenance, typically around 11:30 PM to 12:30 AM, lasting 30–60 minutes (per Paytm’s troubleshooting guide). A payout that hits your bank during its window throws a bank-down class code — U28 (beneficiary bank down) or U69 (“bank server is down, try later”) (Paytm error codes). This is the least alarming failure: nothing is lost, the debit (if any) auto-reverses, and the right move is simply to retry after the window — wait 15–30 minutes and re-request, or pull the balance the next morning. NPCI’s own benchmark is that failed-transaction refunds for this class land within 60 minutes in most cases. The mistake is disputing a midnight “bank down” failure at 12:05 AM; it’s maintenance, not theft.

You hit a per-transaction or daily inbound limit

Receiving has limits too. Most banks cap UPI at roughly ₹1 lakh per day (NPCI/bank limit, per Paytm), and that cap counts inbound credits as well as outbound. So a string of small payouts can land fine and then a larger one bounces because the day’s inbound total tipped over your bank’s ceiling — sometimes surfacing as a U30-class bank decline. The fix: wait for the 24-hour reset and re-request, or split the payout across two days, or pull it to a different bank account whose limit hasn’t been touched. This one is invisible because nothing looks “wrong” — the earlier payouts worked, so players assume the app is cheating, when it’s their own bank’s daily inbound cap.

Name mismatch on the beneficiary

Your app KYC can pass on your PAN while your bank account holder name doesn’t reconcile against what the rail expects — a maiden name, an initials-vs-full-name difference, a typo on the account. The credit-side reconciliation can stall on the name even though the handle resolves. The fix is at the bank, not the app: correct the account-holder name to match your PAN at your branch (the app can’t fix a name held by your bank), then re-issue. A few banks also block credits where the beneficiary name fails their own fuzzy-match threshold, so getting the bank-side name clean is what unblocks it.

A PIN-lock or risk freeze on your own UPI app

Less obvious: if you fumbled your UPI PIN repeatedly, the U16 “risk threshold exceeded” state can halt all UPI activity on your handle for 24–48 hours (per the U16 references). A payout pushed to a handle in that frozen state can fail to settle. The fix: clear the lock by waiting out the 24–48 hour cooldown (don’t keep retrying the PIN, which extends it), then re-request the payout once your handle transacts normally again.

The thread tying these together: a gaming payout fails quietly far more often than it fails loudly. The app says “paid,” nothing arrives, and the cause is a dead handle, a maintenance window, your own inbound cap, a name mismatch or a PIN-lock — none of which the app’s “success” screen reveals. The diagnostic is always the same: grab the RRN, read the error/response code if your bank will give it, and match it to the row above. The code names the fix.

A second worked timeline: a ₹5,000 payout that fails at the beneficiary-bank stage

The first worked timeline covered a ₹2,000 payout debited and never credited. Here’s a different, common failure: a larger ₹5,000 payout that clears the app and the switch fine but stalls at your bank (Stage 3) — the beneficiary-bank leg — because your bank was mid-maintenance when the credit arrived. Dates assume the payout is initiated Thursday evening.

Thursday, 11:40 PM (Day 0 / T) — the payout hits a maintenance window.

• You request ₹5,000. The app approves it, debits its withdrawable pot, and the switch generates a 12-digit RRN. The credit reaches your bank at 11:40 PM — squarely inside the typical 11:30 PM–12:30 AM maintenance window. Your bank can’t confirm the credit; the rail logs a U28/U69 bank-down class outcome.
• App shows “processing/paid”; your bank shows nothing. You screenshot the RRN and the timestamp but you do not dispute — an 11:40 PM “bank down” is almost certainly the maintenance window.

Friday, 8:00 AM (T) — first check.

• You check after the window closed overnight. NPCI’s benchmark is a refund/auto-resolve within 60 minutes for a maintenance-class failure, so a clean outcome would be the ₹5,000 already reversed to the app side or credited to you by morning. Suppose it hasn’t resolved — the credit genuinely failed to land, not just delayed.

Friday end of day (T) — still nothing.

• The credit is now a real debited-but-not-credited at the beneficiary-bank stage. You raise the per-transaction complaint in your UPI app (it auto-attaches the RRN, feeding UDIR), and note the in-app ticket ID.

Saturday (T+1) — the auto-reversal deadline.

• The RBI rule’s hard line: the failed credit should auto-reverse by end of T+1. UDIR, having polled your bank without a clean response, auto-converts the P2P complaint to a chargeback. Often the ₹5,000 reappears today.

Monday (T+3) — open the bank desk in parallel.

• Still missing across the weekend. You now call your bank’s failed-transaction desk with the RRN, citing RBI DPSS.CO.PD No.629. By Monday you’re two days past T+1, so you’re owed ₹5,000 + ₹200 compensation (₹100 × 2 days beyond T+1), credited suo moto. You get a complaint reference (SR/CRN at HDFC, ticket number at SBI, etc.).

Wednesday (T+5, within UDIR’s window) — resolution.

• NPCI’s stated UDIR window is 3–5 working days. The chargeback resolves on your bank’s TCC/RET in the settlement cycle. A RET returns your ₹5,000; a TCC means check your statement for the credit. By now the compensation owed is ₹400 (₹100 × 4 days beyond T+1) if it’s still unresolved.

Day 30 — Ombudsman gate.

• If your bank hasn’t resolved a genuine beneficiary-bank rail failure within 30 days, file free at cms.rbi.org.in under RB-IOS 2021.

The lesson this second timeline adds: a midnight payout is a bad idea precisely because it can land inside the maintenance window, and the “failure” you see at 11:40 PM is usually the rail being down for an hour — not your money gone. Capture the RRN, sleep, check in the morning, and only start the dispute clock if the credit genuinely hasn’t resolved after the window and the 60-minute auto-refund benchmark.

The worked end-to-end timeline (UPI payout, debited, never credited)

Here is the whole thing as a single dated playbook for the most common UPI failure — payout debited on the app side, RRN exists, nothing in your bank. Times assume a ₹2,000 payout failing on a Monday.

Monday (Day 0 / T) — freeze the evidence.

• Screenshot the app’s withdrawal status, the amount, the timestamp, and the RRN (12 digits).
• Screenshot your bank’s “no credit” — a clean account view at the same timestamp.
• Capture the bank SMS if one came. Note whether your statement shows any UPI-REV/UPI-RET line.
• Raise the in-app support ticket; get a ticket ID in writing. Do not deposit anything to “release” it.

Tuesday (T+1) — the auto-reversal deadline.

• This is the rule’s hard line: the failed transaction should auto-reverse by end of today. Often it does — watch for the ₹2,000 reappearing on the app side or a UPI-RET in your statement. If it’s back, you’re done.

Wednesday–Friday (T+2 to T+4) — open the rail dispute.

• Still missing? Now raise the per-transaction complaint inside your UPI app (the screens above). This feeds UDIR; it will poll the banks and auto-convert to a chargeback for a P2P-style payout.
• In parallel, call your bank’s failed-transaction desk with the RRN and explicitly ask for the ₹100/day TAT compensation beyond T+1, citing RBI DPSS.CO.PD No.629. By Friday you’re owed ₹2,000 + ~₹300.

Following week (within 3–5 working days of the dispute) — UDIR resolves.

• NPCI’s stated UDIR window is 3–5 working days. The chargeback resolves on the beneficiary bank’s TCC/RET. A RET returns your money; a TCC means check your statement.

Day 21 (Google Pay only) — the hard cutoff.

• If you used Google Pay and it’s unresolved at 21 days, the partner bank can no longer raise it — switch to your own bank immediately.

Day 30+ — RBI Ombudsman.

• If the bank/PSP hasn’t resolved a genuine rail failure within 30 days, file free with the RBI Integrated Ombudsman (RB-IOS 2021) at cms.rbi.org.in. The RBI ODR mandate (6 Aug 2020) is why your PSO must run a system-driven dispute mechanism in the first place, and the 30-day no-resolution rule is the Ombudsman eligibility gate.

The whole point of the dates: don’t escalate early (inside T+1 there’s nothing to dispute — the rail is still reconciling), and don’t escalate late (blow past the 21-day GPay window or a TAT and you lose the easy path). The clock is the strategy.

Copy-paste UPI-specific dispute templates

These are tuned for a UPI failure — they lead with the RRN and cite the exact circular. Fill the brackets. Keep every message factual and ID-stamped; a RRN moves a payout, emotion doesn’t.

Template 1 — In-app UPI complaint note (Day 0)

Issue: UPI withdrawal debited but not credited.
Amount: ₹[AMOUNT]
Date/time of withdrawal: [DATE, TIME]
RRN / UPI Reference No. (12-digit): [RRN]
Status shown in app: [STATUS]
Registered mobile: [NUMBER]
UPI ID used for payout: [HANDLE]
My bank shows no credit against this RRN.
Please confirm the payout status and the RRN, and resolve within your
stated window. Share a complaint/ticket ID for this request.

Template 2 — Bank failed-transaction dispute, with TAT compensation (T+2 onward)

Subject: Failed UPI credit — RRN [RRN] — refund + TAT compensation claim

A UPI transaction was debited but not credited to my account.
- RRN / UPI Reference No. (12-digit): [RRN]
- Amount: ₹[AMOUNT]
- Date/time: [DATE, TIME]
- Beneficiary account / UPI ID: [A/C or HANDLE]

Per RBI circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019),
a debited-but-not-credited UPI account-to-account transaction must be
auto-reversed by T+1, with ₹100/day compensation for delay beyond T+1
credited suo moto. It has now been [N] days past T+1. Please reverse
₹[AMOUNT] and credit ₹[100 × DAYS] compensation, and share the
complaint reference number.

Template 3 — NPCI UDIR direct complaint (when the app blocks you)

To: NPCI UPI Help — Dispute Redressal (upihelp.npci.org.in / 1800-120-1740)

Complaint: UPI transaction debited but not credited; in-app dispute
unavailable / unresolved.
- UPI transaction ID (RRN, 12-digit): [RRN]
- Amount: ₹[AMOUNT]
- Date/time: [DATE, TIME]
- Remitter (app's payment partner, if known): [PSP/BANK]
- My bank: [BANK]; my UPI ID: [HANDLE]
- In-app ticket ID (if any): [TICKET ID]
Request: trace the RRN, confirm whether a TCC or RET was raised by the
beneficiary bank, and resolve the chargeback per UDIR TAT.

Template 4 — “Successful but not received” trace request to your bank

Subject: UPI marked successful, not received — trace RRN [RRN]

The sender's app marks this UPI payout "successful," but my account
was never credited. Please trace the credit against:
- RRN / UPI transaction ID (12-digit): [RRN]
- Amount: ₹[AMOUNT]
- Date/time: [DATE, TIME]
- My account / UPI ID: [A/C or HANDLE]
If no credit exists against this RRN, please confirm in writing so I
can raise an NPCI UDIR dispute. If a credit was attempted to a stale/
closed handle, please advise so I can update my withdrawal method.

Why two “successful” and “failed” templates: a failed payout is a refund claim (Template 2/3); a “successful but not received” payout is a trace request (Template 4) — you need the bank to confirm there’s no credit against the RRN before you can dispute it. Sending the wrong template wastes a cycle.

UPI-specific mistakes that quietly kill a recovery

These are the errors peculiar to UPI disputes — separate from the general ones the hub covers.

• Quoting the Google transaction ID instead of the UPI transaction ID. Google Pay shows both; only the UPI one (12-digit) is traceable by your bank or NPCI. This single mix-up causes “wrong reference” rejections.
• Disputing inside T+1. The rail is still reconciling; a dispute raised on hour one just gets a “wait” reply. Let T+1 pass first unless you’re capturing evidence.
• Sitting past Google Pay’s 21-day partner-bank window. After 21 days GPay’s partner bank can’t raise it for you — you’re forced to your own bank, having lost the easiest channel.
• Checking only the app, not the bank statement, on a TCC. A “beneficiary credited” result means the money may be in your account under an unfamiliar UPI description. Search the statement for the amount and date, not the app’s status.
• Treating a “deemed/processing” hang as theft. A deemed transaction has until T+3 to resolve through reconciliation. Escalating inside that window achieves nothing.
• Re-requesting the withdrawal to a dead handle. If the first payout failed because the linked handle no longer resolves, re-issuing to the same handle fails again. Update to a live account first, then ask the app to re-issue with the original RRN as evidence.
• Depositing to “unlock” a UPI payout. No legal app needs a deposit to release a withdrawal, and post-PROGA a fresh money-game deposit is illegal. This is the single clearest theft pattern.

Editor’s verdict on the recovery: the players who get paid fastest do two unglamorous things — they capture the 12-digit RRN on Day 0, and they let T+1 pass before disputing. Everyone who panics on hour one and never grabs the RRN ends up a week behind, arguing without the one piece of evidence that resolves the case.

Where to get real, official UPI help

The official chain, in the order that works for a UPI failure specifically. Climb it; don’t skip rungs.

• Your UPI app’s per-transaction complaint — feeds NPCI UDIR with the RRN auto-attached. First door for a rail failure.
• Your bank’s failed-transaction desk — for the T+1 reversal and the ₹100/day TAT compensation, quoting RBI DPSS.CO.PD No.629 (20 Sep 2019) and the 12-digit RRN.
• NPCI UPI Help / UDIR — direct dispute with the RRN; line 1800-120-1740; stated window 3–5 working days.
• RBI Integrated Ombudsman (RB-IOS 2021) at cms.rbi.org.in — free, after 30 days without resolution from the bank/PSP. The RBI ODR mandate underpins your right to a system-driven dispute process.
• Fraud only: if a “customer care number” found on a random site asks for your OTP or UPI PIN, that’s a scam — report to cybercrime 1930 / cybercrime.gov.in and flag the entity on the RBI Sachet portal. Legitimate UPI support never needs your PIN. For the contact-channel safety side, see Teen Patti Master customer care.

Editor’s verdict. A UPI rail failure — debited, not credited, RRN in hand — is the recoverable kind; the T+1 rule and ₹100/day compensation force the outcome. A balance still sitting inside a discontinued or unlicensed app, never handed to the rail, is the hard kind. The lever that separates them is the RRN: have one, work the rail; have none, work the app. And never, on either path, deposit to “unlock” a payout.

Related fixes (go deeper on your exact case)

• Generic withdrawal problem / per-app times / tax / legality → the 3 Patti withdrawal hub — the full Day-0-to-30 ladder.
• UPI failed but money debited → UPI failed, money debited — the deepest screen walkthrough of the UDIR form and the ₹100/day claim.
• Withdrawal stuck / pending / no RRN yet → withdrawal stuck fix — the pending-state countdown when you’re still at Stage 1.
• Can’t reach the app / scam-number safety → Teen Patti Master customer care — official channels and the fake-number warning.

FAQ

1. How long does a Teen Patti UPI withdrawal take? Most UPI payouts from legal apps settle in seconds to a few hours, with apps publishing a 1–3 working-day window. If a UPI payout is debited but not credited, RBI’s TAT circular forces an auto-reversal by T+1, after which you’re owed ₹100 per day.

2. My UPI withdrawal is “pending” with no UTR — what’s happening? With no reference number, the payout is still inside the app (Stage 1) — it never reached UPI, so your bank can’t trace it. Raise an in-app ticket once you’re past the app’s stated window; the rail dispute only applies once a 12-digit RRN exists.

3. What’s the difference between an RRN and a UTR for my payout? A UPI/IMPS transaction uses a 12-digit RRN; NEFT/RTGS uses a longer UTR (16–22 characters). Apps call the UPI RRN a “UTR” or “transaction ID,” but for a UPI payout you’re quoting the 12-digit RRN — that single number traces your debit to the missing credit.

4. Where do I find the UTR in PhonePe, Google Pay, Paytm and BHIM? PhonePe labels it “UPI Reference No.”, Google Pay shows it as the “UPI transaction ID” (not the Google one), Paytm as “UPI Ref No.”, and BHIM as “Transaction ID” — all the same 12-digit number. Open the transaction in History/Passbook to see it.

5. My UPI payout was debited but not credited — what are the exact rules? Under RBI DPSS.CO.PD No.629 (20 Sep 2019), a UPI account-to-account debit not credited must be auto-reversed by T+1, with ₹100/day beyond that, credited suo moto — automatically, “without waiting for a complaint.” Chase it if it doesn’t appear by T+2.

6. Who actually pays the ₹100/day compensation? The bank that failed to complete its leg owes it, and it’s credited into your account alongside the refund. You raise it through your bank because that’s the reachable door, quoting the circular. It applies to system failures, not to your own wrong-handle mistakes. On a 4-day delay you’re owed ₹300.

7. What is NPCI UDIR and how does it resolve my dispute? UDIR (Unified Dispute and Issue Resolution) is NPCI’s automated UPI dispute system. It polls the banks for up to 5 days; for a P2P-style payout, if the beneficiary bank doesn’t respond by T+1, the complaint auto-converts to a chargeback, then resolves on the bank’s TCC/RET. Stated window: 3–5 working days.

8. What do TCC and RET mean on my dispute? TCC (Transaction Credit Confirmation) = the beneficiary bank confirms it did credit you, so check your bank statement, not the app. RET (Return) = it couldn’t credit and is returning the money. Since 15 February 2025, chargebacks auto accept/reject on the TCC/RET raised in the next settlement cycle (NPCI rule, 10 Feb 2025).

9. My Google Pay dispute is taking weeks — is there a deadline? Yes — a hard one. Google Pay raises complaints via partner banks, and after 21 days from the transaction the partner bank can no longer raise it for you (Google Pay help). Past 21 days, go to your own bank directly. Don’t let a GPay dispute sit.

10. The app says “successful” but nothing arrived — how do I prove it? Get the 12-digit RRN and ask your bank to trace a credit against it. If none exists, you have proof the money never reached you — open an NPCI UDIR dispute. If a TCC says “credited,” search your statement for the amount and date; the credit may be under an unfamiliar UPI description.

11. What does a “deemed” or stuck-processing UPI payout mean? A deemed transaction was processed but NPCI couldn’t confirm the terminal status; it resolves to success or failure by T+3 through reconciliation (status reference). So a payout hanging for a day or two isn’t lost — don’t dispute inside that T+3 window unless you’re only capturing evidence.

12. My UDIR chargeback was rejected as “beneficiary credited” — now what? That’s a TCC result claiming you were paid. Pull your bank statement for the transaction date and search for the amount — it may sit under a UPI reference you didn’t recognise. If it’s genuinely absent despite the TCC, escalate it as a bank deficiency (the bank claimed a credit that didn’t happen), with the RRN as proof.

13. Why was my dispute rejected as “wrong reference”? Almost always because you quoted the Google transaction ID instead of the UPI transaction ID, or an old/typo’d RRN. Re-file with the correct 12-digit UPI RRN from the transaction detail screen. A mismatched reference can’t be matched to a disputable transaction, so the system bounces it.

14. Can I still recover a UPI payout from a shut-down app like RummyCircle? Yes for the rail part. Banks kept processing withdrawals so users could recover balances after PROGA, and the T+1 reversal and ₹100/day rules apply identically to a recovery payout that fails on UPI. Complete KYC, capture the RRN, and never re-deposit — that’s now illegal.

15. When can I take a UPI payout failure to the RBI Ombudsman? After 30 days without resolution from the bank/PSP, file free at cms.rbi.org.in under the RB-IOS 2021, which covers Payment System Participants. The RBI ODR mandate is why your provider must run a system-driven dispute process before you ever reach the Ombudsman.

16. My payout went out as IMPS, not UPI — does the same protection apply? Yes. A debited-but-not-credited IMPS transaction sits in the same RBI TAT row as UPI: auto-reversal by T+1, then ₹100/day (RBI DPSS.CO.PD No.629). The difference is the door — IMPS has no UDIR app button, so you trace it through your bank with the 12-digit IMPS RRN, typically after waiting 24–48 hours for the auto-reversal.

17. How do I know whether my payout used UPI, IMPS or NEFT? Read the statement prefix. UPI/ is the UPI rail (12-digit RRN), IMPS/P2A/ is an IMPS bank transfer (12-digit IMPS RRN), and NEFT/ is a batch transfer (a longer 16–22-character UTR). A NEFT payout also settles in half-hourly batches, so a delay of under 30 minutes is usually the next batch, not a failure.

18. My bank says the complaint will take 10 days — but where’s my money? Separate the two clocks. The reversal is on the RBI T+1 rule and should land in hours-to-a-day; the bank’s quoted 10-day (HDFC) complaint TAT is just when the case formally closes. Insist on the T+1 reversal for the money, and quote the circular — the 10-day figure does not govern your refund, only the paperwork.

19. The app says “paid” but my old UPI ID is closed — can I still get it? Yes, but fix the handle first. The payout failed because it pushed to a dead VPA (an invalid-VPA / U15-class outcome). Update your withdrawal method to a live, verified handle, then ask the app to re-issue, quoting the original 12-digit RRN as proof the first attempt left the app — re-requesting to the same dead handle fails every time.

20. My UPI dispute was rejected — is that final? Not since 15 July 2025. Under NPCI’s RGNB (good-faith negative chargeback) rule, your remitting bank can re-raise a rejected chargeback if the complaint is genuine, without NPCI’s old manual whitelisting (NPCI OC-184B). Ask your bank to re-raise it as a good-faith chargeback — there’s also a cap of 10 chargebacks per customer per 30 days, so don’t burn them on duplicates.

21. My payout failed at 11:45 PM — should I panic? No. Banks and NPCI run scheduled maintenance roughly 11:30 PM–12:30 AM for 30–60 minutes, throwing a U28/U69 “bank down” outcome. NPCI’s benchmark auto-resolves this class within 60 minutes. Capture the RRN, wait out the window, and check in the morning before starting any dispute — a midnight “bank down” is maintenance, not theft.

Sources & method. The UPI settlement mechanics, dispute steps, reference-number labels and compensation numbers on this page are built from primary regulatory and operator 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) for the T+1 auto-reversal and ₹100/day suo moto compensation; RBI Online Dispute Resolution mandate (6 Aug 2020) and the RBI Integrated Ombudsman Scheme 2021 at cms.rbi.org.in; NPCI and NPCI UPI Help / UDIR for the dispute flow and 3–5 working-day window; NPCI’s TCC/RET auto accept-reject chargeback rule effective 15 Feb 2025 (Business Standard, Upstox) and the Razorpay UDIR explainer; the RRN-vs-UTR distinction from xFlow, Angel One and Winvesta; per-app UTR labels from Moneyview; the PhonePe complaint path and timelines from PhonePe’s failed-transaction guide; the Google Pay dispute path and 21-day partner-bank limit from Google Pay help and answer 9494510; the “deemed” status and T+3 reconciliation from Decentro’s status documentation; the 2025 chargeback framework, RGNB good-faith re-raise and CD1/CD2 caps from NPCI OC-184B (15 July 2025), Businessworld and Hero FinCorp; the per-bank dispute desks and TATs from SBI UPI care, HDFC grievance redressal, ICICI UPI FAQs, PNB grievance, Axis UPI dispute form and ClearTax’s consolidated UPI-complaint guide; the IMPS/NEFT reference and reversal mechanics from HDFC, Razorpay and Lemonn; the UPI error/response codes (U15 invalid VPA, U16 risk threshold, U28/U69 bank down, U30 risk decline) and maintenance-window behaviour from Paytm’s error-code and troubleshooting guides and Fi Money; and the post-PROGA recovery context from Mondaq and the Promotion and Regulation of Online Gaming Act, 2025. This page is information, not legal or financial advice — verify each step against your bank’s current UPI dispute policy and your operator’s Terms.