Teen Patti Withdrawal Not Received: The Day 0–30 Fix

The 30-second answer

You requested a Teen Patti withdrawal and nothing arrived. Before you panic, sort it into one of three cases, because each has a different fix. (1) Never-debited — the app rejected or never processed the request, so no money left your withdrawable balance and there is no UTR to chase. (2) Debited-not-credited — money left somewhere but the credit failed on the UPI rail; NPCI’s rules auto-reverse it by T+1, with ₹100/day compensation after. (3) Silently-held — the payout is parked in the app’s queue for manual review and hasn’t reached the rail yet. The single highest-leverage move is getting the UTR out of the app; without it you cannot prove a “paid” payout never landed. This page is the universal countdown. For the cluster overview and your dispute rights, start at the 3 Patti withdrawal hub.

Editor’s verdict, up front. “Withdrawal not received” is the vaguest symptom in the whole payout world, and that vagueness is exactly why people escalate to the wrong door and lose days. The mistake is treating “nothing arrived” as one problem. It’s three problems wearing the same shirt. A never-debited withdrawal is a gaming-app rule problem — you fight it with the app, and there is no UTR because no transaction was ever born. A debited-not-credited withdrawal is a payment-rail problem with the strongest consumer protection in India behind it — you fight it with your bank and NPCI, and the UTR is everything. A silently-held payout is just a slow queue — you wait the stated window, then nudge. This page teaches you to tell them apart on Day 0, often before a UTR even exists, then hands you the exact countdown for each. Do the triage first. Everything downstream depends on getting the case right.

2026 reality you must read first. The legal ground shifted hard in 2025. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) received Presidential assent on 22 August 2025 and prohibits all online money games — skill or chance — where you stake money for a return; the operating Rules came into force on 1 May 2026. India’s biggest real-money operators suspended their cash formats from late August 2025. So in mid-2026, “my withdrawal wasn’t received” is often really “a discontinued app still holds my money and the recovery payout never came.” The protections below still apply to that recovery — banks kept processing withdrawals so users could pull existing balances out — but never add money “to unlock” a withdrawal. A new deposit into a money game is now illegal, and “deposit to release your payout” is the oldest theft script there is.

Why this page exists separately from the hub

The withdrawal hub maps the entire payout chain: the four gates a withdrawal passes through, the per-app rules, the tax math, the legality picture, every escalation rung. It’s the encyclopedia. This page is the emergency room for one specific arrival: you tapped withdraw, the clock has been running, and your account is still empty.

The hub answers “how does a 3 Patti withdrawal work and what are all the ways it can break.” This page answers a narrower, more urgent question: “It’s been X hours/days and nothing came — what do I do right now, in what order, when I might not even have a reference number yet?” That “no UTR yet” condition is the whole reason this page is deep rather than a redirect. Most withdrawal guides assume you already have a transaction reference to dispute. In the “not received” case you frequently don’t — the app shows “processing” with no reference, or it shows “success” but won’t surface the UTR, or it shows nothing at all because the request silently failed. Getting from “nothing” to “a confirmed status and a reference number” is its own skill, and it’s most of this article.

Three sibling pages go deeper on specific branches, and this page hands you off to them at the exact moment your case resolves into one:

• If your case turns out to be a UPI rail failure, the Teen Patti UPI withdrawal fix walks the NPCI UDIR dispute screen-by-screen and shows where each UPI app hides the UTR.
• If money left your account and didn’t arrive (debited-not-credited), the UPI failed, money debited fix covers the T+1 auto-reversal and the ₹100/day claim in full.
• If the app shows pending / processing and you can’t tell whether it’s stuck, the withdrawal stuck fix has the pending-state countdown by gate.

This page is the triage that routes you to the right one. Read it top to bottom once; after that, you’ll know your case and can jump.

First: the three sub-cases, told apart in under five minutes

Everything starts here. Before you screenshot, before you email, before you so much as open a support chat, you need to know which of three states you’re in. The test takes about five minutes and uses two pieces of information you can get right now: your withdrawable balance (not your total wallet balance) and the withdrawal request’s status line in the app’s transaction history.

The two-number test

Open the app’s transaction or withdrawal history and find your request. Note two things:

1. Did your withdrawable balance drop by the withdrawal amount? Look at the withdrawable figure, not the headline wallet number (the wallet number bundles deposit, winnings, and bonus pots; only the withdrawable pot funds a payout). If you withdrew ₹2,000 and your withdrawable balance fell by ₹2,000, the app accepted and debited the request. If your withdrawable balance is unchanged, the app never actually took the money — the request died at a gate.
2. What exact word does the status line show? “Processing” / “Pending” / “Under review” / “Initiated” all mean one thing. “Success” / “Completed” / “Paid” / “Credited” mean another. “Failed” / “Rejected” / “Declined” / “Cancelled” mean a third. Read the literal word; do not interpret.

Cross those two answers and you land in exactly one case:

That single table is the most important thing on this page. The cases below are just the long version of each row, with the fix.

Case 1 — Never-debited (the app rejected it; no money moved)

What it looks like. Your withdrawable balance is exactly what it was before you tapped withdraw. The request shows “failed,” “rejected,” “cancelled,” or simply vanished from history. There is no UTR, because no payment instruction was ever generated — the request was stopped inside the app before it touched any payment rail.

What’s really happening. The app’s own rules blocked the request at Gate 1 (KYC) or Gate 2 (limits/minimums/wagering). Common triggers: KYC not complete or name-mismatched, the amount was under the minimum or over a daily/monthly cap, or the balance you tried to withdraw was actually locked bonus money with an unmet wagering requirement. From the rail’s point of view, nothing happened — so there is no payment dispute to raise, no bank to call, no NPCI complaint to file. This is purely a gaming-app problem.

Why this is the case people get most wrong. Players in Case 1 routinely call their bank, demand a UTR that doesn’t exist, and try to file a UPI complaint on a transaction that was never sent. They burn three days fighting a payment rail that never saw their money. The tell is the unchanged withdrawable balance: if the app didn’t take the money, there is nothing on the rail to recover. Your money is safe — it’s sitting in your app wallet — and the fix is to satisfy whatever app rule blocked it, then re-request.

The fix. Find the block reason. Re-read the withdrawal screen for any message (“complete KYC,” “minimum ₹100,” “wagering pending,” “daily limit reached”). Then: complete or correct KYC so your bank/UPI name matches your PAN exactly; lower the amount under the daily cap; or finish the bonus wagering. Re-request the withdrawal. If the app rejects a clean, KYC-complete, within-limits request with no reason, that’s a service-deficiency complaint against the operator — but it is still not a bank/NPCI matter, because no money left your wallet.

Case 2 — Debited-not-credited (money left, credit failed on the rail)

What it looks like. Your withdrawable balance dropped by the full amount, and the status shows “success,” “paid,” “completed,” or “failed” — but your bank account never received the credit. A UTR either exists already (when status is “success”) or will exist (a “failed” rail transaction still gets a reference). This is the case with the strongest consumer protection in the entire chain, and it routes to your bank and NPCI, not to the app.

What’s really happening. The app approved the payout, handed it to UPI/IMPS, and the rail tried to credit your account — but the credit didn’t confirm. The beneficiary bank was momentarily down, your UPI handle no longer resolves, a timeout hit, or your receiving account had a daily-limit issue. The transaction is now in a deemed-failed / pending state on the rail. Critically, the money does not bounce back the instant the screen says “failed” — it reconciles on cycles governed by RBI’s Turn Around Time (TAT) circular.

The rule that protects you. Per RBI’s TAT circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 September 2019), an account-to-account UPI transaction where you were debited but the beneficiary wasn’t credited must be auto-reversed by T+1 (the day after the transaction). If it isn’t, your bank owes you ₹100 per day of delay beyond T+1, credited automatically — you don’t have to ask, though you should chase it if it doesn’t appear. For UPI-to-merchant flows where confirmation failed, the auto-reversal window is up to T+5 before the same ₹100/day kicks in. So a failed withdrawal is, counterintuitively, the best stuck state to be in: the refund is rule-mandated and largely automatic.

The fix. This routes off the app entirely. Get the UTR (the methods are below), note it, wait through T+1, and if the money isn’t back, raise a UPI dispute through your UPI app’s “raise complaint” button — which feeds NPCI’s UDIR system — or call your bank’s failed-transaction desk with the UTR and claim the ₹100/day. The screen-by-screen version lives on the UPI failed, money debited fix. The one thing you must not do: keep deposit-spamming or re-requesting, which can create duplicate debits.

Case 3 — Silently-held (sitting in the app’s payout queue)

What it looks like. Your withdrawable balance dropped, but the status is stuck on “pending,” “processing,” “under review,” or “initiated.” There’s usually no UTR yet, because the app hasn’t handed the payout to the rail — it’s sitting in the operator’s internal queue waiting for approval.

What’s really happening. This is Gate 3: the app’s payout queue and risk hold. Small, clean payouts from trusted accounts auto-approve and reach the rail in seconds. But larger amounts, brand-new accounts, accounts with unusual win patterns, a big first withdrawal, or accounts flagged for a duplicate device/IP get routed to manual review — a human or a slower batch process approves them. “Pending for 6 hours / 1 day” almost always lives here. A genuine risk hold (suspected collusion, multi-accounting, bonus abuse) can look identical from the outside; the tell is a support reply mentioning “verification,” “review,” or “security.”

The honest read. A regulated operator that wanted to keep your money wouldn’t queue it — it would reject it with a reason (that’s Case 1). A payout sitting in the queue is far more often a slow approval than a theft. The conspiracy theories are about this gate, and they’re usually wrong.

The fix. Wait the app’s stated window — for a first withdrawal, give it a full 24 hours before treating it as a problem. Past the window, raise an in-app ticket with the amount, timestamp, and screenshots, and get a ticket ID. Don’t spam; one clear, dated ticket beats ten angry chats. The pending-state countdown by gate is on the withdrawal stuck fix.

The three-case rule in one line: Case 1 (never-debited) is a gaming-app rule problem with no UTR — fix the rule, re-request, never call your bank. Case 2 (debited-not-credited) is a payment-rail problem with the strongest protection in India — get the UTR, wait T+1, dispute with your bank/NPCI. Case 3 (silently-held) is a slow queue — wait the window, then nudge the app. Sort yourself correctly and you save a week.

How to confirm whether the payout even left the operator

The hardest part of “not received” is the uncertainty: did the app actually send my money, or is it still holding it? You can’t fix what you can’t locate. Here is the systematic way to pin down where your money physically is, in order of certainty.

Signal 1 — The withdrawable-balance delta (highest certainty)

Already covered above, but it bears repeating because it’s the single most reliable signal you have. If your withdrawable balance dropped by the withdrawal amount, the app committed the payout internally. If it didn’t drop, the app never took the money and there is nothing on any rail. Screenshot the withdrawable figure now; you’ll want the before/after pair as evidence, and apps sometimes adjust balances when a payout reverts.

The trap: confusing the wallet total with the withdrawable total. Your wallet might read ₹3,000 while only ₹1,200 is withdrawable (the rest deposit/bonus). When you “withdraw ₹1,200,” watch the withdrawable line, not the wallet headline, or you’ll misread a successful debit as “balance didn’t change.”

Signal 2 — The presence (or absence) of a UTR / reference

A UTR (Unique Transaction Reference, a 12-digit number, sometimes shown as RRN) only exists once a payment instruction has been generated on the rail. So the UTR is a yes/no oracle for “did this leave the operator”:

• A UTR exists → the payout was handed to the rail. Your money is now a payment-system matter, and the UTR is your thread to trace it. This is Case 2 territory.
• No UTR, status “pending/processing” → the payout is still inside the app’s queue (Case 3). The rail never saw it.
• No UTR, status “failed/rejected,” balance unchanged → the request died inside the app (Case 1). Nothing ever left.

This is why “get the UTR” is the highest-leverage Day-0 action: the presence of a UTR alone tells you which world you’re in, before you even trace it.

Signal 3 — The app’s status word, read literally

Don’t interpret; read the literal word the app shows:

• “Initiated” / “Processing” / “Pending” / “Under review” = inside the app or just handed off; not yet confirmed on the rail.
• “Success” / “Paid” / “Completed” / “Sent to bank” = the app believes it credited you. If your bank is empty, this is the dangerous gap — the app’s status is ahead of reality, and you need the UTR to prove the credit never landed.
• “Failed” / “Reversed” / “Cancelled” / “Rejected” = the app says it didn’t go through. Now the question is where the money went back to — your app wallet (Case 1) or stuck mid-rail awaiting auto-reversal (Case 2).

Signal 4 — Your bank’s own record (the tiebreaker)

When the app says “success” but you see nothing, your bank is the tiebreaker. Check your bank statement / passbook and your transaction SMS for any credit around the timestamp. Two outcomes:

• No credit anywhere against that UTR → strong proof the money never reached you. This is your dispute: the app claims it paid, your bank says it didn’t, the UTR is the thread that proves the gap.
• A credit you missed → it arrived under a different description (operators often credit via an aggregator name, not the app name), or it landed in a linked account you weren’t watching. Search the amount, not the app name.

The location logic in one line: balance dropped + UTR exists = it left the operator and is a rail matter (Case 2); balance dropped + no UTR + “pending” = it’s still in the app’s queue (Case 3); balance unchanged + no UTR = it never left, it’s a rule block (Case 1). Four signals, one location. Pin the location before you escalate.

The “stale success” edge case worth knowing

Occasionally an app marks a withdrawal “success” and shows a UTR, but the credit genuinely never reached the rail’s destination — the handle was dead, the account closed, the IFSC wrong. The app’s status is technically true (it initiated a credit) but functionally false (the credit failed downstream). This is the worst of the cases to be in emotionally because the app insists it paid you. But it’s recoverable: a UTR that your bank cannot match to any credit is, itself, proof the credit failed. Ask your bank to trace the UTR; if there’s no corresponding credit, the rail must reverse it. Update your withdrawal method to a live account before re-requesting, so the second attempt doesn’t die at the same dead address.

Getting a UTR or reference out of support when the app won’t surface it

In the “not received” case, the UTR is frequently the thing you don’t have — and the thing you most need. Sometimes the app shows it plainly; often it doesn’t, especially when the app’s status is “pending” or when the operator buries payout references. Here’s how to extract it, in escalating order of effort.

Step 1 — Look where the app hides it yourself first

Before you ask support, exhaust the self-serve spots, because support will often just point you back to them:

• The withdrawal/transaction detail screen. Tap the specific withdrawal in the app’s history; the reference is usually on the expanded detail, labelled “UTR,” “Transaction ID,” “Reference No.,” or “Order ID.”
• The bank SMS. If the payout reached the rail, your bank may have sent an SMS for the (attempted) credit containing the UTR/RRN — even for a failed credit. Search your messages for the amount.
• Your UPI app, not the gaming app. If the payout rode UPI, the reference also appears in your UPI app’s history (PhonePe, Google Pay, Paytm, BHIM) on the matching transaction. Every UPI app labels it differently but it’s the same 12-digit number: PhonePe calls it “UPI Reference No.,” Google Pay “Bank Reference ID” / “UPI transaction ID,” Paytm “UPI Ref No.,” BHIM “Transaction ID.”
• Your bank statement / passbook. The UTR appears against the line item for the transaction, even a failed one, once it reconciles.

If you find the UTR here, you’ve skipped the hard part. The Teen Patti UPI withdrawal fix has the exact menu path per UPI app.

Step 2 — Ask support with a precise, ID-stamped request

If the app genuinely doesn’t surface a reference, you ask — but you ask precisely, because a vague “where’s my money” gets a templated “please wait 24–48 hours” that wastes a cycle. Use language that signals you know the process and forces a specific answer:

Subject: Withdrawal of ₹[AMOUNT] on [DATE, TIME] — please provide the UTR/payout reference

My withdrawal of ₹[AMOUNT] requested on [DATE, TIME] shows status
"[exact status word]". My withdrawable balance was debited by ₹[AMOUNT].
Please provide:
1. The UTR / RRN / payout reference number for this transaction.
2. The exact date and time the payout was handed to the bank/UPI rail.
3. The beneficiary account/UPI handle the payout was sent to.
Registered mobile: [NUMBER]. I need the UTR to trace this with my bank.

Asking for the beneficiary handle it was sent to is the underused move: if the app paid a stale or wrong handle, that answer reveals it, and a wrong-handle payout is your strongest evidence the credit couldn’t have reached you.

Step 3 — If support stalls, escalate the request for a reference itself

Some operators (especially informal-brand card apps and wind-down operators) will dodge the UTR request. Treat the dodge as a data point and escalate the request:

• Restate with a deadline. “Please provide the UTR within 48 hours; without it I cannot trace the payment and will escalate the non-payment to my bank’s UPI dispute process and the National Consumer Helpline.”
• Note that a UTR is mandatory for any genuine payout. A real rail transaction has a UTR by definition. An operator that “paid” you but can’t produce a UTR has either not actually paid (Case 1/3 mislabelled as success) or is stalling — and either way you now treat it as non-payment.
• You don’t strictly need the operator’s cooperation if it rode UPI. Because the same UTR lives in your UPI app and bank statement, you can often trace and dispute without the gaming app ever handing you the number. The app’s silence slows you but doesn’t block you.

What to do if there is genuinely no UTR

No UTR, after all of the above, almost always means the money never left the operator — which is Case 1 (rule block, balance unchanged) or Case 3 (still queued, balance dropped). In both, there is nothing for your bank or NPCI to trace, because the rail never received a transaction. That’s not bad news: your money is still recoverable from inside the app, via the app’s own process, rather than gone on a rail. Stop hunting for a UTR that doesn’t exist and switch to the app-side ladder instead.

The UTR rule in one line: a UTR exists if and only if the payout left the operator onto the rail. Find it in the app, the bank SMS, your UPI app, or the statement — and if it genuinely doesn’t exist anywhere, your money never left the app, so fight it app-side, not bank-side.

The realistic arrival window per method — when “not received” is still normal

Half of “not received” panics are premature. The honest question is: has enough time actually passed for this method to fail? Different rails have wildly different normal windows, and escalating inside the normal window just gets you a “please wait” that costs you a day. Here is what is genuinely normal, slow, and a problem — per method.

Why the first withdrawal is the slow one

If your very first withdrawal from an app is “not received” while you’ve heard others get paid instantly, that’s almost always normal, not a red flag. Many apps run a stricter manual review on your first-ever payout — even a clean ₹100 test — before they trust the account. A first payout taking up to 24 hours while later small ones go through in seconds is expected behaviour. The corollary: always make your first withdrawal a small test amount (₹100–₹200) precisely so this slow first-review happens on a tiny sum, not on your whole balance.

Why a NEFT payout that takes an hour isn’t stuck

If your payout fell back to NEFT (common for larger amounts or when a UPI handle won’t resolve), it settles in half-hourly batches — a transfer initiated at 11:02 settles by 11:30, one at 11:25 also by 11:30. So a NEFT payout that’s been “pending” for 40 minutes is simply waiting for the next batch; it is not a failure. Don’t escalate a NEFT payout inside the first two hours. NEFT has been 24×7×365 since December 2019, so even an overnight or weekend NEFT keeps moving in batches.

Why an IMPS payout should be near-instant

IMPS is instant and 24×7 up to ₹5 lakh per transaction. So if a bank-transfer payout that rode IMPS hasn’t arrived within a couple of hours, that’s not normal-batch-timing — it usually means a beneficiary-detail mismatch (wrong account number, name reconciliation failure), and you dispute it through your bank with the UTR/RRN, not by waiting for a batch that doesn’t exist on IMPS.

The working-days trap

“1–3 working days” excludes weekends and bank holidays. A withdrawal requested Friday evening with a “3 working day” SLA can legitimately arrive the following Wednesday without anything being wrong, because Saturday and Sunday don’t count and Monday is day one. Before you declare a payout “late,” count working days from the request, and remember that UPI and IMPS run 24×7 (so those don’t get the weekend excuse) while bank-side processing and app manual review often pause on holidays. Match your impatience to the actual rail.

The arrival-window rule in one line: a clean repeat UPI payout past 24 hours, a first payout past 48 hours, an IMPS payout past 2 hours, a NEFT payout past 24 hours, or a debited-not-credited UPI past T+1 is your trigger to start the paper trail — and not one minute before, because escalating inside the window just buys you a “please wait.”

The precise Day-0-to-30 escalation calendar (for the “not received” case)

This is the spine. It matches each action to the rule-clock above, branches by your case, and tells you exactly what to do on each day. Don’t skip rungs and don’t jump to RBI on Day 1 — they’ll bounce you back to the entity. Climb in order. Templates for every rung are in the next section.

Day 0 (first hour) — Triage, freeze evidence, get the reference

The highest-leverage hour of the whole process. In the first 60 minutes:

1. Run the two-number test above. Determine your case (1, 2, or 3) from the withdrawable-balance delta and the literal status word. This decides everything that follows.
2. Screenshot everything: the withdrawal request, the status screen, the amount, the timestamp, and your withdrawable balance before and after. Date-stamped screenshots are your evidence later, and apps sometimes change a status retroactively.
3. Capture the UTR / reference the moment one exists (Case 2). If status is “pending” with no UTR (Case 3) or “failed” with unchanged balance (Case 1), note that no UTR exists yet — that’s itself a finding.
4. Open the in-app ticket with amount, timestamp, and (if any) UTR, and get a ticket/complaint ID in writing. This timestamps your complaint, which matters for the 30-day Ombudsman clock later.

Hard rules for Day 0, every case: do not start a second account, do not deposit more “to unlock” the withdrawal, and never share an OTP or UPI PIN with anyone who “calls to help.” Legitimate support never needs your PIN or OTP.

Day 0–1 — Branch by case

• Case 1 (never-debited): there’s no rail transaction, so there’s nothing to wait for on a rail. Fix the app-side block today — complete/correct KYC, get under the limit, finish wagering — and re-request. If a clean request keeps getting rejected with no reason, jump to the Day 1–3 official-email rung as a service-deficiency complaint, but never call your bank.
• Case 2 (debited-not-credited): this is the T+1 window. Note the UTR and let the auto-reversal run before disputing. Don’t spam support; the rail’s own reconciliation often fixes this within one working day.
• Case 3 (silently-held): you’re inside the app’s queue. If it’s a first withdrawal, give it the full 24-hour manual-review window before treating it as a problem.

Day 1–3 — Official email + wait the rail’s TAT

• Send the same complaint by the app’s official support email (from its Play listing / official site), referencing the in-app ticket ID. Email creates a paper trail an in-app chat can’t, and a dated email is what the Ombudsman and consumer forum want to see later.
• Case 2: you’re still inside or at the edge of the T+1 auto-reversal window. If the money returns, you’re done. If T+1 passes and it’s still gone, you move to the payment-side dispute at Day 4.
• Case 3: if the app publishes a 1–3 working-day SLA, you may still be inside it. Be firm but patient; ask for a UTR and a definite timeline in writing.

Day 4–7 — Open the payment-side dispute (Case 2 only)

If the money is genuinely gone on the rail and hasn’t come back:

• Open your UPI app’s “raise complaint / dispute” on that transaction. This feeds NPCI’s UDIR, which can auto-convert to a chargeback after the TAT. The exact per-app path is on the UPI withdrawal fix.
• Or call your bank’s failed-transaction desk with the UTR/RRN and lodge a complaint; explicitly ask for the ₹100/day compensation if you’re past T+1 — the RBI TAT circular entitles you to it on system failures.
• You can also file at the NPCI UPI Help portal or call 1800-120-1740. NPCI’s stated UDIR resolution window is 3–5 working days. (Cases 1 and 3 have no rail transaction, so this rung doesn’t apply to them — there’s nothing for NPCI to find.)

Day 8–15 — Formal bank complaint + app “final notice”

• Case 2: escalate the bank complaint to a written formal complaint if the helpline did nothing; get a complaint reference number. Your bank is an RBI-regulated entity, so this written complaint starts the 30-day clock toward the Ombudsman.
• All cases: send the app a final-notice email — restate the facts, the ticket ID, the UTR (or note its absence), the days elapsed, and state you’ll escalate to the RBI Ombudsman and the National Consumer Helpline if unresolved. A clear, dated final notice often unsticks a payout because it signals you understand the process.

Day 16–30 — RBI Ombudsman and consumer forum

If a regulated entity (your bank / payment-system participant) still hasn’t resolved a payment failure:

• After 30 days without resolution from the entity, file with the RBI Integrated Ombudsman Scheme 2021 (RB-IOS) at cms.rbi.org.in. The scheme covers banks, NBFCs, and Payment System Participants, redress is free, and the Ombudsman can award compensation up to ₹20 lakh for consequential loss plus up to ₹1 lakh for time, expense, and harassment. The 30-day rule is a hard eligibility gate: filing earlier (when the entity hasn’t had 30 days to respond) makes the complaint non-maintainable.
• For the consumer-service angle (an app refusing to pay a clearly-owed, KYC-clean balance — common in Cases 1 and 3), the National Consumer Helpline 1915 and the consumer-forum route apply.
• If you suspect fraud — a clone app, a fake “customer care number,” an OTP scam — report immediately to the cybercrime helpline 1930 and cybercrime.gov.in, and flag suspicious payment entities on RBI’s Sachet portal.

Honest limit of this calendar: the bank/NPCI/RBI rungs are powerful against a payment-rail failure (Case 2), because banks and payment-system participants are RBI-regulated. They are weaker against a shady offshore or unlicensed app holding your balance inside its wallet (a Case 1/3 that won’t release), because that operator may sit outside Indian regulatory reach. That asymmetry is why you only play where payouts are clean — and why a never-debited balance stuck in a dodgy app is the hardest money to get back.

Copy-paste templates for the “not received” case

Fill in the brackets. Keep every message factual, dated, and ID-stamped — emotion doesn’t move a payout, a UTR does. These are tuned for “nothing arrived,” with one tuned for the case where you don’t even have a reference yet.

Template A — In-app ticket, Day 0 (any case)

Subject: Withdrawal not received — please confirm status and UTR

My withdrawal of ₹[AMOUNT] requested on [DATE, TIME] shows status
"[exact status word]" and has not reached my account.
- Withdrawable balance before: ₹[X]; after request: ₹[Y]
- UPI ID / bank used: [HANDLE / A/C]
- UTR / reference (if shown): [UTR or "not shown"]
- Registered mobile: [NUMBER]
- KYC status: completed (PAN + Aadhaar verified, name matches bank)
Please confirm whether this payout was sent to the bank/UPI rail, the
UTR, and the exact date/time it was handed off. Please share a
complaint/ticket ID for this request.

Template B — “Give me the reference or it’s non-payment” (when support dodges the UTR)

Subject: [Ticket ID] Request for UTR — ₹[AMOUNT] withdrawal, [DATE]

My withdrawable balance was debited ₹[AMOUNT] on [DATE, TIME] and the
app shows "[status]", but nothing has reached my account and no UTR
has been provided. A genuine rail payout has a UTR by definition.

Please provide, within 48 hours:
1. The UTR / RRN for this payout.
2. The exact date/time it was handed to the bank/UPI rail.
3. The beneficiary account/UPI handle it was sent to.

If no UTR can be provided, I will treat this as a non-paid, owed
balance and escalate to my bank's UPI dispute process, NPCI UDIR
(upihelp.npci.org.in / 1800-120-1740), the RBI Ombudsman (RB-IOS
2021), and the National Consumer Helpline (1915).

Template C — Official support email / grievance escalation, Day 1–3

Subject: [Ticket ID] Withdrawal of ₹[AMOUNT] not received — escalation

To: [official support email] / Grievance Officer

I raised in-app ticket [TICKET ID] on [DATE] for a withdrawal of
₹[AMOUNT] that has not been credited to [UPI/bank]. It has now been
[N] days, past your stated payout window of [X working days].

- Amount: ₹[AMOUNT]   Requested: [DATE, TIME]
- Status in app: [STATUS]   UTR / reference: [UTR or "none provided"]
- Withdrawable balance was debited: yes/no
- Registered number: [NUMBER]   KYC: completed, PAN matches bank name

Please either credit the payout, or provide the UTR and a written
reason for the delay, within 48 hours. If unresolved I will escalate
to my bank's UPI dispute process, NPCI UDIR, the RBI Ombudsman
(RB-IOS 2021), and the National Consumer Helpline (1915).

Template D — Bank / UPI failed-transaction dispute, Day 4–7 (Case 2)

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

A UPI transaction was debited but not credited to my account.
- UTR / reference (RRN): [UTR]
- Amount: ₹[AMOUNT]   Date/time: [DATE, TIME]
- My 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 transaction must be auto-reversed by T+1,
with ₹100/day compensation for delay beyond T+1. It has now been
[N] days. Please reverse the amount, credit the applicable
compensation, and share the complaint reference number.

Template E — RBI Ombudsman grievance, Day 30+ (Case 2, unresolved)

Nature of complaint: Deficiency in service — failed/unresolved digital
payment (UPI withdrawal debited but not credited).

Regulated entity: [YOUR BANK / payment system participant]
Date of original transaction: [DATE]   Amount: ₹[AMOUNT]   UTR: [UTR]
Complaint first raised with the entity on: [DATE], reference [REF].
Entity's response: [none / unresolved] after 30 days.
Relief sought: credit of ₹[AMOUNT] + ₹100/day compensation per RBI
TAT circular DPSS.CO.PD No.629/02.01.014/2019-20, plus compensation
for time and expense.

File Template E at cms.rbi.org.in only after 30 days have passed without resolution from the entity — that 30-day rule is the eligibility gate for RB-IOS 2021.

Template F — National Consumer Helpline, parallel (Cases 1 and 3, app won’t pay)

To: National Consumer Helpline (1915 / consumerhelpline.gov.in)

Complaint: Service deficiency — gaming app refusing/failing to pay a
verified, KYC-complete withdrawal that never reached the bank rail.

- Operator / app: [APP NAME]   Registered mobile: [NUMBER]
- Withdrawal amount owed: ₹[AMOUNT]   Requested on: [DATE]
- In-app ticket [TICKET ID] raised [DATE]
- App's status / response: [STATUS / no response after N days]
- No UTR was generated, indicating the payout never left the operator.
- KYC: completed; PAN matches bank account name.
Relief sought: release of ₹[AMOUNT] to my registered account, and a
written reason for the non-payment.

Use Template F in parallel with the app escalation when no UTR exists (the money never left the operator), because the consumer-helpline angle reaches the operator’s service obligation — which is exactly the lever for a held balance that the bank/RBI rail route can’t touch.

Grievance contact reference block

Keep this handy; it’s the whole escalation map in one place. Use the door that matches your case.

Order of doors, in one line: for a rail failure (Case 2), app → bank/UPI → NPCI → RBI Ombudsman; for a held balance with no UTR (Cases 1, 3), app → final notice → National Consumer Helpline 1915 — and cybercrime 1930 the instant fraud is involved.

When “not received” turns out to be tax, not a missing payout

A large share of “I got less than I withdrew” complaints aren’t “not received” at all — the money did arrive, just smaller, and the gap is tax. If your payout landed but was 30% lighter than your winnings, read this before disputing, because disputing a legal TDS deduction wastes the days you’d need for a real problem.

Since 1 April 2023, every legal online-gaming app in India must deduct TDS at 30% on your net winnings — with no minimum threshold (the old ₹10,000 floor is gone). This is Section 194BA of the Income-tax Act, with the computation in Rule 133. “Net winnings” is not “every win”: per Rule 133, the financial-year figure is (total withdrawals + closing wallet balance) − (total deposits + opening wallet balance), excluding non-withdrawable bonuses. So a ₹25,000 withdrawal where your net winnings were ₹15,000 carries ₹4,500 TDS, and you receive ₹20,500 — the missing ₹4,500 is remitted against your PAN and shows in your Form 26AS / AIS, creditable when you file. That’s a smaller-than-expected arrival, not a missing one, and it routes to your tax return, not to a dispute. The hub’s withdrawal page has the full worked examples, including the year-end deduction that quietly shrinks an un-withdrawn balance every April.

The distinction that matters for this page: a smaller arrival is not a non-arrival. If the amount that hit your bank equals (withdrawal − 30% of net winnings), stand down — that’s TDS, and it’s yours to reclaim at filing. Only if nothing arrived, or the cut doesn’t match the 194BA math, are you actually in a “not received” case worth escalating. Separately, a deposit buying fewer chips than expected is the 28% GST on deposits (since 1 October 2023), a deposit-side tax that never touches a withdrawal — players sometimes misread it as a missing payout, but it isn’t one.

The tax-vs-missing rule in one line: if the gap equals 30% of your net winnings, it’s Section 194BA TDS reported against your PAN — the money arrived, just taxed — and you reclaim it at filing rather than disputing a payout that wasn’t actually lost.

The wind-down case: when “not received” means a discontinued app still holds your money

In 2026 the most common “withdrawal not received” is no longer a slow live app — it’s a discontinued operator that owes you a balance. After PROGA 2025, the major real-money operators suspended cash play from late August 2025, and players were left with money sitting inside apps whose cash games had stopped. The good news: banks and intermediaries kept processing withdrawals so users could recover existing balances. The “not received” question for a wind-down balance is the same triage, with three wrinkles.

Wrinkle 1 — the payout still rides the same protected rails. A recovery withdrawal from a discontinued app still goes over UPI/IMPS/NEFT, so the same RBI TAT protection applies: if it’s debited and not credited, it’s auto-reversed by T+1 with ₹100/day after. Your rail rights don’t evaporate because the game stopped.

Wrinkle 2 — KYC must be fully clean to release anything. Wind-down operators won’t release a balance to an unverified or name-mismatched account. If your recovery withdrawal isn’t arriving, the first suspect is incomplete or mismatched KYC (Case 1, never-debited), not a rail failure. Fix the KYC, re-request.

Wrinkle 3 — expect the 30% TDS on net winnings even on recovery. A recovery payout of winnings is still taxed at 30% under Section 194BA, so a smaller arrival is, again, often tax rather than a missing payout.

The one absolute rule for wind-down recovery: never deposit again to “unlock” a stuck balance. A new deposit into a money game is now illegal in India, and “deposit ₹X to release your withdrawal” is the clearest theft pattern there is — no legal app has ever required a deposit to process a withdrawal. If a discontinued operator simply ignores a clean recovery request with no UTR, that’s a service-deficiency and consumer-grievance matter (National Consumer Helpline 1915), plus a bank/RBI dispute for any rail loss with a UTR.

The wind-down rule in one line: a recovery withdrawal from a discontinued app gets the same T+1 / ₹100-a-day rail protection, demands fully clean KYC to release, and still loses 30% to 194BA TDS on net winnings — and you never, ever deposit again to free it.

Is it a delay or a scam? The red flags that change your strategy

Most “not received” cases on legal apps are delays. But some apps are unlicensed, offshore, or outright clones, and on those the escalation ladder has limited teeth. Use these red flags to decide whether to keep fighting or to cut losses, report, and walk:

• No PAN/KYC was ever required to deposit or withdraw. A legal app must do KYC before paying out. No KYC means you’re likely not on a regulated platform, so your RBI/bank leverage shrinks.
• Support pushes you to a “customer care number” from a random website, YouTube comment, or search ad. These are overwhelmingly scams built to phish your OTP and UPI PIN. Real apps route support in-app; many have no public phone helpline at all. Never call back a number you didn’t get from the official listing, and never share an OTP/PIN. Report fake numbers to 1930 / cybercrime.gov.in.
• “Deposit ₹X to release your withdrawal.” No legal app requires a deposit to withdraw. This is the single clearest theft pattern — and post-PROGA a new money-game deposit is also illegal. Stop, document, report.
• The status flips to “success” instantly but no UTR is ever produced, on every attempt. A genuine rail payout generates a UTR. An operator that always shows “success” yet can never surface a reference is faking the status — your strongest evidence the money never actually left.
• The app vanished from its official source and pending withdrawals went dark. A genuine reinstall keeps your balance (it’s tied to your registered number, not the app file). A disappeared operator is a worse problem — though note a legitimate PROGA wind-down is the opposite case: cash games stopped, but the app should still let you withdraw.

If two or more are true, the realistic verdict is harsh: pursue the bank/UPI dispute and cybercrime report for any rail loss (Case 2), but lower your expectation of recovering a balance held inside an unlicensed operator (Case 1/3) — and don’t feed it another rupee. The detailed scam-vs-delay decision tree lives in the refund/dispute cluster; the hub summarizes it.

Mistakes that turn a recoverable “not received” into a lost one

The “not received” case is usually winnable. People lose winnable cases by doing avoidable things. Here are the ones that actually cost players their money, each with the reason it backfires.

1. Re-requesting the same withdrawal repeatedly. Tapping withdraw five times because nothing arrived can create duplicate debits, trip the anti-fraud system into a risk hold, and tangle your transaction history so badly the operator and your bank can’t tell which UTR is the real one. One request, then escalate — never re-request a payout that’s already showing pending.
2. Depositing more “to unlock” the withdrawal. There is no legal app on earth where a deposit unlocks a withdrawal. This is throwing good money after bad, and post-PROGA it’s also an illegal money-game deposit. The “unlock” framing is a scam tell, full stop.
3. Spinning up a second account to “try again.” Multi-accounting is the fastest way to get both accounts frozen for duplicate-device/IP. If your payout is held on a risk review, a new account deepens the flag — it doesn’t escape it.
4. Chasing a UTR that doesn’t exist. Calling your bank and demanding a UTR for a Case 1 (never-debited) withdrawal wastes days; the rail never saw your money, so there’s nothing to trace. Confirm the case first.
5. Sharing an OTP or UPI PIN with “support.” Legitimate support never needs your PIN or OTP. Anyone who asks is phishing. This single mistake converts a delayed payout into a drained account.
6. Escalating to RBI on Day 2. The Ombudsman bounces any complaint filed before the entity has had 30 days, making it non-maintainable. Premature filing doesn’t speed things up; it resets your clock.
7. Losing the evidence. A “failed” transaction ages out of the app’s quick view, and your bank cannot trace a credit you can’t name. Screenshot the status and capture any UTR on Day 0, while it’s all still visible.
8. Disputing TDS as theft. A payout that arrived 30% lighter on net winnings is Section 194BA tax, creditable at filing — disputing it as a “missing payout” burns the cycle you’d need for a real failure.

The mistakes rule in one line: request once, deposit never, account once, escalate in order, keep the OTP secret, and screenshot on Day 0 — every lost “not received” case traces back to breaking one of these.

Worked timeline example — the universal “nothing arrived” countdown

To make the calendar concrete, here is how a textbook “not received” case resolves, with no fabricated personal claim — just the mechanics applied to round numbers.

Take a ₹3,000 winnings withdrawal requested on a Monday evening via UPI, status “processing,” withdrawable balance dropped by ₹3,000, no UTR shown.

• Monday (Day 0): Two-number test → balance dropped, status “processing,” no UTR → Case 3 (silently-held), in the app’s queue. Screenshot everything; open an in-app ticket; get ticket ID. No bank call (no rail transaction yet).
• Tuesday (Day 1): Still “processing.” It’s a clean repeat payout, so the 24-hour mark is the watch line. Send the official support email referencing the ticket ID; ask for the UTR and the hand-off time.
• Wednesday (Day 2): Status flips to “success” and a UTR finally appears — but the bank account is still empty. The case has now migrated from Case 3 to Case 2 (debited-not-credited). Note the UTR. Because it’s UPI, T+1 from the hand-off applies.
• Thursday (Day 3): T+1 has passed and the money hasn’t auto-reversed. Now you open the UPI app’s “raise complaint” on that UTR (feeds NPCI UDIR) and call the bank’s failed-transaction desk with the UTR, claiming the ₹100/day.
• Days 4–8: NPCI’s stated UDIR window is 3–5 working days. The dispute either credits the ₹3,000 (plus any TAT compensation) or escalates.
• Day 30+: If the bank hasn’t resolved it, file at the RBI Ombudsman (cms.rbi.org.in) with the 30-day-old written complaint reference.

The lesson the timeline teaches: a case can change type mid-stream (here, queue → rail), and the day a UTR appears is the day your fix switches from “wait the app” to “dispute the rail.” Watch for the migration; it’s the moment your leverage jumps from the app’s goodwill to the RBI rulebook.

Quick-reference decision flow

If you want the whole page as a single flow you can run from memory, here it is.

1. Did your withdrawable balance drop?
   • No → Case 1 (never-debited). App-rule block. Fix KYC/limit/wagering, re-request. No bank, no UTR.
   • Yes → go to 2.
2. Is there a UTR?
   • No, status “pending/processing” → Case 3 (silently-held). Wait the window (24h for a first payout), then in-app ticket.
   • Yes (or status “success”) → go to 3.
3. Did your bank receive the credit against that UTR?
   • No → Case 2 (debited-not-credited). Wait T+1, then UPI dispute (NPCI UDIR) + bank claim with the UTR; ₹100/day if past T+1; RBI Ombudsman after 30 days.
   • Yes, under a different name/amount → it arrived; search your statement for the amount, not the app name.
4. Did it arrive but smaller? → Likely 30% Section 194BA TDS on net winnings. Check the math; if it matches, it’s tax, not a missing payout.
5. Two-plus scam red flags? → Pursue rail loss via bank/NPCI/cybercrime; lower expectations on balance held inside an unlicensed app; never deposit to unlock.

The whole page collapses to: find the case, then climb the matching ladder in order. For the cluster overview, the four payout gates, and your full dispute rights, the 3 Patti withdrawal hub is the parent page.

FAQ

1. My Teen Patti withdrawal wasn’t received — how do I know if the money even left the app? Run the two-number test: check whether your withdrawable balance dropped by the withdrawal amount, and read the literal status word. If the balance is unchanged, the app never took the money (Case 1) and no UTR exists. If it dropped and a UTR exists, the payout left onto the rail (Case 2). If it dropped with status “pending” and no UTR, it’s still in the app’s queue (Case 3). A UTR exists only once a payout has actually left the operator — that’s your single clearest location signal, and it takes about 5 minutes to check.

2. How long should I wait before a Teen Patti withdrawal counts as “not received”? For a clean repeat UPI payout, past 24 hours; for your first-ever withdrawal (manual review), past 48 hours; for an IMPS bank payout, past 2 hours; for a NEFT fallback, past 24 hours. For a UPI that was debited but not credited, the line is T+1 (the day after), after which you can claim ₹100/day. Escalating inside these windows just buys a “please wait,” so start the paper trail only once you cross the line for your method — typically 24 hours for a clean UPI payout.

3. There’s no UTR anywhere — what does that mean? No UTR after checking the app, the bank SMS, your UPI app, and your bank statement almost always means the money never left the operator — either a rule block (balance unchanged, Case 1) or a payout still queued (balance dropped, Case 2/3 not yet on the rail). There is nothing for your bank or NPCI to trace, because no rail transaction was ever generated. Fight it app-side, not bank-side, via the in-app ticket and the National Consumer Helpline 1915 — not your bank.

4. The app says “success” but nothing reached my bank — how do I prove it? Get the UTR from the app (or from your own UPI app / bank statement, where the same number appears) and ask your bank to trace it. If the bank has no record of a credit against that UTR, you have proof the money didn’t reach you — open a UPI dispute via NPCI UDIR and escalate. NPCI’s stated UDIR resolution window is 3–5 working days.

5. My withdrawable balance didn’t drop, but the withdrawal “failed” — where’s my money? It’s still in your app wallet. A failed request with an unchanged withdrawable balance means no payment was ever sent (Case 1); the app blocked it at a rule gate — incomplete KYC, a name mismatch, an amount under the ₹100 minimum or over a daily cap, or locked bonus money with unmet wagering. Fix the specific block and re-request; there’s no rail transaction to dispute, so a bank call wastes the 3–5 working days you’d want for a real failure.

6. How do I get the UTR if the app won’t give it to me? First check the spots that don’t need support: the transaction detail screen, your bank SMS, your own UPI app’s history, and your bank statement — the same 12-digit number appears in all of them for a rail payout. If you still can’t find it, email support asking specifically for the UTR, the hand-off time, and the beneficiary handle, with a 48-hour deadline. If a payout rode UPI, you can often dispute it through your UPI app without the gaming app’s cooperation at all — the same 12-digit reference lives in your UPI app and bank statement.

7. My UPI withdrawal was debited but never credited — what’s the rule? Per RBI’s TAT circular DPSS.CO.PD No.629 (20 Sep 2019), an account-to-account UPI transaction that’s debited but not credited must be auto-reversed by T+1. If it isn’t, your bank owes ₹100 per day of delay, credited automatically — though you should chase it if it doesn’t appear. For UPI-to-merchant flows the window is T+5.

8. My first-ever withdrawal hasn’t arrived but others say it’s instant — is something wrong? Probably not. Many apps run stricter manual review on the first-ever payout, even a clean ₹100 test, so a first withdrawal taking up to 24 hours while later ones clear in seconds is normal. That’s exactly why you make your first withdrawal a small ₹100–₹200 test amount — so this slow first review happens on a tiny sum.

9. My bank-transfer withdrawal has been pending an hour — is it stuck? Depends on the rail. IMPS is instant, so an IMPS bank payout past 2 hours is likely a beneficiary-detail problem to dispute with your bank. NEFT settles in half-hourly batches, so a NEFT payout pending 40 minutes is just waiting for the next batch — don’t escalate a NEFT transfer inside the first 2 hours.

10. I got less than I withdrew — is that “not received”? No — that’s almost always TDS, not a missing payout. Legal apps deduct 30% on net winnings under Section 194BA with no threshold. On a ₹25,000 withdrawal where net winnings were ₹15,000, that’s a ₹4,500 cut, and you receive ₹20,500; the ₹4,500 is reported against your PAN in Form 26AS/AIS and reclaimed at filing. If the gap matches 30% of net winnings, it’s tax — stand down.

11. Where do I complain if the app simply won’t pay an owed balance with no UTR? Because there’s no rail transaction, the bank/NPCI route has nothing to trace. Escalate the app side: in-app ticket → official email → final-notice email → National Consumer Helpline 1915 for service deficiency. Run a bank/RBI dispute only for any loss that did leave on a rail (with a UTR). The Ombudsman is for payment failures, available after 30 days of no resolution.

12. Can a withdrawal change from one case to another while I wait? Yes, and watching for it matters. A payout can sit in the app’s queue (Case 3, no UTR) and then flip to “success” with a UTR — at which point it becomes a rail matter (Case 2). The day a UTR appears is the day your fix switches from “wait the app” to “dispute the rail,” and your leverage jumps from the app’s goodwill to the RBI rulebook with its ₹100/day teeth.

13. The app is one of the discontinued ones (RummyCircle, Junglee, etc.) and my recovery withdrawal hasn’t come — what now? Same triage. A recovery payout still rides UPI/IMPS/NEFT with the same T+1 / ₹100-a-day protection, but it needs fully clean KYC to release and still loses 30% to 194BA TDS on net winnings. If a clean recovery request shows no UTR and the operator ignores you, that’s a service-deficiency matter (1915) plus a rail dispute for any UTR’d loss. Never deposit again — a new money-game deposit is illegal post-PROGA.

14. How long does the whole escalation take if nothing resolves quickly? The realistic clock: Day 0 ticket, Day 1–3 official email, Day 4–7 bank/NPCI dispute (NPCI UDIR resolves in 3–5 working days), Day 8–15 formal bank complaint and final notice, and the RBI Ombudsman only after 30 days of no resolution from the entity. Most genuine rail failures (Case 2) resolve inside the 3–5 working-day UDIR window; only the stubborn ones reach Day 30.

15. Could “withdrawal not received” actually be a scam rather than a delay? Sometimes. Treat it as a likely scam if two or more of these are true: no KYC was ever required, support pushes a “care number” from a random source, the app demands a deposit “to unlock” the payout, the status flips to “success” but no UTR is ever produced, or the operator vanished. For any rail loss pursue the bank/NPCI/cybercrime route (1930), but lower your expectation of recovering a balance held inside an unlicensed app — and never deposit to unlock it.

Sources & method. Arrival windows, the failed-transaction protections, and the escalation steps on this page are built from primary regulatory sources and named operator behaviour — not personal payout tests. Key references: RBI failed-transaction TAT circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019); RBI Integrated Ombudsman Scheme 2021 and cms.rbi.org.in; NPCI UPI Help / UDIR; NEFT half-hourly batch timing and IMPS/UPI rail comparison; the Promotion and Regulation of Online Gaming Act, 2025 and its Rules effective 1 May 2026; the wind-down balance-recovery position; cybercrime reporting at cybercrime.gov.in / helpline 1930; National Consumer Helpline 1915; RBI Sachet portal. Section 194BA TDS and 28% GST figures are summarized here and detailed on the 3 Patti withdrawal hub. This page is information, not legal or financial advice — verify each step against your operator’s current Terms and your bank’s UPI dispute policy.