The 30-second answer
A 3 Patti withdrawal is a cash payout from a Teen Patti / 3 Patti app to your UPI ID or bank account. Legal apps only allow it after PAN and Aadhaar KYC, and most UPI payouts settle in minutes to 1–3 working days. If your money was debited but not credited, NPCI’s rules auto-reverse it by T+1, and your bank owes you ₹100 per day after that under RBI’s failed-transaction circular. A “pending” payout past the app’s stated window is delayed, not lost — work the escalation ladder below.
Editor’s verdict, up front. Most “stuck” 3 Patti withdrawals are not the app stealing your money. They are one of three boring things: a batch-window delay on the payout rail, an app-side risk hold (KYC mismatch, a flagged account, a duplicate-device check), or a genuine UPI failure that the rules already force a refund on. Each of those has a different fix and a different escalation rung. The trick is knowing which one you’re in — and not pouring more deposits into a stalled account while you find out. This page maps all three, with the exact dispute path, copy-paste templates, and the primary rules behind every number.
2026 reality you must read first. The legal ground has shifted hard. 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 — RummyCircle, Junglee Rummy, Dream11, MPL, Adda52, PokerBaazi — suspended their cash formats from late August 2025. If you are reading this in mid-2026, your problem is often no longer “my live app is slow” — it’s “a discontinued app still holds my balance and I need it out.” The good news: banks and payment intermediaries kept processing withdrawals so users could recover existing balances, and the same RBI/NPCI rail protections below still apply to that recovery. The bad news: a deposit into one of these games is now illegal, so never add money “to unlock” a withdrawal. This whole guide reads two ways — for a still-live legal app, and for a wind-down balance recovery — and we flag which is which.
What a 3 Patti withdrawal actually is
When people search “3 patti withdrawal,” “teen patti cash withdrawal,” or “teen patti withdrawal not received,” they are almost always talking about the same thing: getting real money — not in-game chips — out of a card-game app and into a bank account. So let’s be precise about the object.
A 3 Patti / Teen Patti app holds your money in a wallet balance. That balance is made of three different pots, and most withdrawal confusion starts because players treat them as one:
- Deposit balance — money you added with your own card or UPI. Some apps let you withdraw unused deposits; many require you to play through them first.
- Winnings balance — money you won at the table. This is the pot that taxes apply to, and the pot that triggers KYC and risk checks on the way out.
- Bonus / promotional balance — chips the app gave you (welcome bonus, referral credit, daily wheel). This is almost never directly withdrawable. A huge share of “withdrawal not working” complaints are actually players trying to cash out a non-withdrawable bonus and reading the locked balance as theft.
A withdrawal, then, is the app moving rupees from your winnings (and eligible deposit) balance to your registered UPI ID or bank account, after deducting any tax it is legally required to deduct. That payout travels over one of two rails:
- UPI — the instant rail run by NPCI (National Payments Corporation of India). Most card-game payouts under a few thousand rupees go here.
- IMPS / bank transfer (NEFT in some flows) — used for larger amounts, or as a fallback when UPI to your handle fails.
Both rails are operated by banks and payment aggregators that are regulated by the Reserve Bank of India (RBI). That single fact is the foundation of everything below: once your payout is on the rail, it stops being a “gaming app problem” and becomes a payment-system problem with hard, RBI-mandated timelines and a real complaints authority behind it. That is your leverage.
Why this distinction matters for getting paid
A player who knows their ₹2,000 is a winnings payout that has been approved and handed to UPI is in a completely different position from a player whose ₹2,000 is a bonus balance the app never intended to release. The first one has the RBI rulebook on their side. The second one is arguing about the app’s terms, where they are much weaker. Before you escalate anything, find out which balance you’re actually fighting for. The app’s transaction history and your withdrawal request screen will tell you.
The pot also decides your tax math. Only the winnings pot is taxable under Section 194BA; a returned deposit is your own money coming back and is not “net winnings.” If your withdrawal came back smaller than you expected, the first question is which pot it left from — because a 30% cut on a winnings payout is tax, while a cut on a pure deposit return is a fee dispute worth raising. The worked tax examples later in this page make that line exact.
Run the diagnostic first, then read the section that fits you
At the top of this page is the Payout Diagnostic Wizard. Pick your app, pick what you’re seeing (not received / pending / failed-but-debited / KYC blocked / limit hit), and enter how many days you’ve waited. It returns a status verdict and routes you to the exact escalation rung and the right fix page for your case. The wizard’s timings are estimates built from the published NPCI and RBI rules cited on this page — not from anyone’s personal payout tests.
If you’d rather read, the rest of this guide is the manual version of that wizard. It is long on purpose: this is the hub for the whole withdrawal cluster, so everything you might need is here, and the deeper, app-specific fixes link out from each section.
How a normal 3 Patti withdrawal works (the four gates)
Every withdrawal from a legal app passes through four gates in order. A “stuck” payout is just a payout sitting at one of these gates. Naming the gate tells you the fix.
Gate 1 — KYC verification (PAN + Aadhaar)
No legal real-money app in India can pay out cash to an un-verified account. This isn’t the app being difficult; it’s anti-money-laundering law. To withdraw, you generally need:
- PAN card — mandatory, because the app must report tax deducted against your PAN (more on this in the tax section).
- Aadhaar or another government ID — for identity and address verification.
- A bank account or UPI ID in your own name that matches the KYC name.
The single most common silent reason a first withdrawal stalls: the name on your UPI handle does not match the name on your KYC. The app’s risk system flags the mismatch and parks the payout for manual review instead of paying it instantly. If your very first withdrawal is “pending” while later small ones went through, suspect a name/KYC mismatch first.
Two concrete KYC triggers worth knowing, drawn from how the major Indian skill-game operators wrote their rules. On Junglee Rummy, KYC was mandatory at the first withdrawal or once cumulative deposits crossed ₹50,000, whichever came first — so a player who deposited small amounts could play for a while before the wall hit, then face a sudden block at cash-out. On RummyCircle, withdrawal required your PAN to be verified and to match your KYC documents exactly — one transposed letter on a name field was enough to park a payout. Both apps have since discontinued cash play under PROGA, but the pattern is identical across every legal RMG app: the cash-out is the moment KYC is enforced, not the deposit.
First-withdrawal reality check: many apps run a stricter manual review on your first ever payout — even a clean ₹100 test withdrawal — before they trust the account. A first payout taking longer than later ones is normal, not a red flag by itself.
Gate 2 — The withdrawal request and minimum/limit checks
When you tap “withdraw,” the app checks the amount against its own rules. These vary by app, but the common shapes are:
- Minimum withdrawal — frequently around ₹100, sometimes higher for bank transfer than for UPI.
- Daily / monthly limits — many apps cap how much you can pull in 24 hours or per month, partly for their own risk control. Hitting an undisclosed daily cap looks exactly like a “stuck” withdrawal: the request just sits there.
- Wagering / play-through — if your balance includes bonus money, the app may block withdrawal until you’ve wagered a multiple of the bonus. This is in the terms you accepted, and it is the legal reason a “₹500 balance” sometimes refuses to release.
If your withdrawal is rejected or stuck at this gate, the cause is a rule, not a payment failure — and the only fix is to satisfy the rule (complete KYC, lower the amount under the limit, finish the wagering) or to dispute the rule’s fairness with support.
Gate 3 — The app’s payout queue and risk hold
Once your request clears the rules, it enters the operator’s payout queue. Two things happen here, and this is where most genuine delays live:
- Auto vs manual review. Small, clean payouts from trusted accounts are usually auto-approved and pushed to UPI in seconds. Larger amounts, new accounts, accounts with unusual win patterns, or accounts flagged for a duplicate device/IP get routed to manual review — a human (or a slower batch process) approves them. Manual review is where “pending for 6 hours / 1 day” comes from.
- Risk holds. If the app’s anti-fraud system suspects collusion, multi-accounting, bonus abuse, or a payment-method problem, it can freeze the payout pending investigation. A risk hold can look identical to a normal delay from the outside; the tell is usually a support reply mentioning “verification,” “review,” or “security.”
This is the gate that the conspiracy theories are about. But the honest read is: a regulated operator that wanted to keep your money wouldn’t queue it — it would reject it with a reason. A payout sitting in the queue is far more often a slow approval than a theft.
Gate 4 — Settlement on the payment rail (UPI / IMPS)
Finally, the approved payout is handed to the bank/aggregator and travels over UPI or IMPS to your account. UPI is near-instant when it works. But the rail has its own failure modes — a beneficiary bank that’s down, a UPI handle that no longer resolves, a daily UPI limit on your receiving account — and when settlement fails after the app has already debited its own side, you get the dreaded “debited but not credited” state.
That state is the one with the strongest consumer protection in the entire chain, and it’s worth understanding precisely.
What’s actually happening when settlement fails: NPCI batch windows and auto-reversal
Here’s the original-insight piece most explainers skip. “UPI is instant” is true for the successful path. The failure path is not instant — it runs on reconciliation cycles, and that’s why a failed payout can sit in limbo for a day before it bounces back.
When a UPI payout is initiated, money is debited at the sending side and a credit instruction is sent to your bank. If your bank doesn’t confirm the credit (it was down, the handle didn’t resolve, a timeout), the transaction is now in a deemed-failed / pending state. It does not reverse the instant the screen says “failed.” Instead, the banks reconcile these in cycles, and the rule that governs the outcome is RBI’s Harmonisation of Turn Around Time (TAT) circular.
Per RBI Circular DPSS.CO.PD No.629/02.01.014/2019-20, dated 20 September 2019, the binding numbers are:
- Account-to-account UPI where you were debited but the beneficiary was not credited: the transaction must be auto-reversed by T+1 (the day after the transaction). If it isn’t, the bank owes you ₹100 per day of delay beyond T+1, credited automatically — you don’t have to ask.
- UPI to a merchant where confirmation failed: auto-reversal window is up to T+5 before the same ₹100/day compensation kicks in.
So if your 3 Patti payout shows “failed” and the money left the app’s wallet, the system is already obligated to put it back, usually within one working day, automatically. This is why the correct first move on a debited-but-not-credited payout is often wait through T+1, then dispute — not panic-spam support on hour one.
The mechanism that processes these disputes is NPCI’s Unified Dispute and Issue Resolution (UDIR) system, surfaced for consumers at the UPI Help portal (upihelp.npci.org.in). UDIR can auto-convert an unresolved complaint into a chargeback once the prescribed TAT lapses. There’s also an NPCI UPI complaint line at 1800-120-1740, and a help email at upihelp@npci.org.in. (Note: the ₹100/day compensation applies to technical/system failures, not to your mistakes like sending to a wrong handle — but a stuck app-to-you payout is a system path, so it’s covered.)
The practical takeaway: a failed UPI payout is the best stuck state to be in, because the refund is rule-mandated and largely automatic. A “success / paid” payout that never arrived is worse — there the money supposedly went somewhere, so you need the UTR to prove it didn’t reach you. And a payout still sitting at the app’s queue (Gate 3) is a gaming-app problem until the app actually hands it to the rail.
The withdrawal-time reality table
Forget “instant.” Here is what is actually normal versus delayed versus a problem, per rail and stage. Timings marked with a rule reference are RBI/NPCI-mandated; the rest are typical industry behaviour for legal apps and should be read as estimates.
| Stage / rail | Normal | Slow (watch it) | Problem (escalate) | The rule / source |
|---|---|---|---|---|
| First-ever withdrawal (manual review) | A few minutes to 24 hours | 24–48 hours | Beyond 48 hours with no support reply | App terms; manual KYC review |
| Repeat UPI payout, clean account | Seconds to a few hours | 4–24 hours | Beyond 24 hours | App SLA (typically 1–3 working days) |
| Bank/IMPS payout (larger amounts) | A few hours to 24 hours | 24–48 hours | Beyond 48 hours | App SLA |
| UPI debited but not credited | Auto-reversed by T+1 | Still missing on T+1 | Still missing after T+1 → claim ₹100/day | RBI DPSS.CO.PD No.629, 20 Sep 2019 |
| UPI to merchant, confirmation failed | Auto-reversed by T+5 | Missing after T+5 | Missing after T+5 → claim ₹100/day | RBI DPSS.CO.PD No.629, 20 Sep 2019 |
| NPCI UPI complaint resolution (UDIR) | 3–5 working days | Past 5 working days | No resolution + TAT lapsed → chargeback / RBI | NPCI UPI Help / UDIR |
| App support first response | 24–72 hours | Past 72 hours | No reply at all | App help-centre SLA |
| RBI Ombudsman eligibility | After 30 days of no resolution from the regulated entity | — | File at cms.rbi.org.in | RB-IOS 2021 |
Read that table as a clock. The moment you cross from “slow” into “problem” for your row is the moment you start the written paper trail in the next section. Don’t escalate early (you’ll just annoy support and they’ll tell you to wait), and don’t escalate late (you’ll blow past a TAT and lose the easy refund).
Per-app withdrawal reality: stated rules vs observed behaviour
The numbers below are split into two columns on purpose. Operator-claimed is what the app’s own help pages or listings state. Observed / realistic is what is widely reported by players and third-party trackers, framed third-person — not a personal test. Treat the claimed column as the promise and the observed column as the planning assumption. Every app here also deducts 30% TDS on net winnings under Section 194BA before paying, so a payout that arrives smaller than requested is usually tax, not a delay (worked examples are in the tax section).
A blunt caveat for 2026: RummyCircle and Junglee Rummy discontinued cash games after PROGA. Their rows describe how they worked and how a wind-down balance recovery still behaves, because banks were instructed to keep processing those withdrawals. Teen Patti Gold and Teen Patti Master are informal-brand card apps distributed largely outside the Play Store; their published numbers are less authoritative and the observed column matters more.
Teen Patti Gold
| Field | Operator-claimed | Observed / realistic |
|---|---|---|
| Minimum withdrawal | Often a round ₹100–₹500 floor depending on the build/operator skin | |
| Stated payout time | UPI “minutes to a few hours”; bank transfer “up to 3 working days” | UPI commonly same-day; bank/IMPS 24–48h; first payout slower |
| KYC trigger | PAN + bank/address proof required before withdrawal (source) | First withdrawal almost always triggers full manual KYC |
| Daily limit | Reported ₹10,000–₹1 lakh/day, up to ~₹10 lakh/month per third-party listings | Undisclosed caps on a given skin; large pulls routed to manual review |
| Common hold reasons | Incomplete KYC, wrong bank details, T&C violations | Name mismatch (bank vs PAN), non-withdrawable bonus balance, duplicate-account/device flags |
Editor’s note: “Teen Patti Gold” is a brand applied to multiple builds and skins, so a single authoritative limit table does not exist — judge by the specific listing you installed, never by a third-party mirror. Full app-specific walkthrough: withdrawal not received.
Teen Patti Master
| Field | Operator-claimed | Observed / realistic |
|---|---|---|
| Minimum withdrawal | ~₹100 for UPI per third-party guides (source) | ₹100 floor on most skins; bank transfer floor higher |
| Stated payout time | UPI “instant to a few hours”; bank “up to 3 working days” | UPI same-day when clean; manual review adds hours on new accounts |
| KYC trigger | KYC required before first withdrawal | Enforced at first cash-out, not at deposit |
| Daily limit | Reported up to ~₹50,000/day per third-party listings | Caps vary by skin; large/round-number pulls flagged |
| Common hold reasons | Incomplete verification, incorrect account details, T&C breach | Name mismatch, bonus-wagering not met, risk-review on win spikes |
For the contact and scam-number safety side of this app specifically, see Teen Patti Master customer care.
Junglee Rummy (cash games discontinued under PROGA — wind-down recovery)
| Field | Operator-claimed (pre-PROGA) | Observed / realistic now |
|---|---|---|
| Minimum withdrawal | Commonly ~₹100–₹200 with KYC complete | For wind-down balances, follow the in-app withdrawal flow that remains for recovery |
| Stated payout time | A few hours up to ~24 hours to bank/UPI | Recovery payouts processed by banks per the wind-down; allow normal rail timing |
| KYC trigger | First withdrawal or cumulative deposits > ₹50,000, whichever first (source) | KYC must be complete to release any balance now |
| TDS | 30% on net winnings at withdrawal, quarterly TDS certificate issued (source) | Same; expect a 30% cut on net winnings in your recovery payout |
| Status | Cash games & tournaments discontinued under PROGA 2025 | Only balance recovery; do not deposit again (illegal) |
RummyCircle (cash games discontinued under PROGA — wind-down recovery)
| Field | Operator-claimed (pre-PROGA) | Observed / realistic now |
|---|---|---|
| Minimum withdrawal | Typically ~₹100, method-dependent | Recovery follows the remaining withdrawal flow |
| Stated payout time | UPI ~2–4 hours on business days; bank ~24–48h per third-party trackers | Allow standard rail timing on recovery |
| KYC trigger | PAN verified and matching KYC required to withdraw (source) | PAN/KYC must match exactly or the recovery stalls |
| TDS | 30% on net winnings at withdrawal or financial-year end (source) | Same; net-winnings math below |
| Status | Real-money rummy banned/discontinued under PROGA 2025 | Balance recovery only; never re-deposit |
Editor’s verdict on the per-app tables: stop treating a third-party “Teen Patti Gold withdrawal limit” page as gospel — these informal-brand card apps run many skins with different limits, and the only authority is the exact build you installed. For RummyCircle and Junglee Rummy, the cash product is gone; your only live task there is recovering an existing balance, and the rail protections in this guide still cover that recovery.
The failure-mode taxonomy: which kind of “stuck” do you have?
Diagnosing the type is 80% of the fix, because each type escalates differently. Below is the short six-type triage, then a deeper ten-reason breakdown with a specific fix for each. Match your symptom, then jump to the matching rung in the ladder.
Type 1 — Pending / processing (sitting in the app’s queue)
Symptom: the app shows “processing,” “pending,” or “under review.” No UTR yet. Money has left your withdrawable balance but hasn’t hit the rail. What’s really happening: Gate 3. Auto-approval didn’t fire — manual review or a daily-limit/batch delay. Fix: Wait through the app’s stated window. If it’s a first withdrawal, give it 24 hours. Past the window, raise an in-app ticket (Day 0 rung). This is a gaming-app problem, so the lever is app support first, payment dispute later. Deeper guide: see the withdrawal-stuck fix page for the pending/processing-specific countdown.
Type 2 — “Paid / success” in the app, but nothing in your bank
Symptom: the app marks the withdrawal “completed” or “success” and may show a UTR, but your bank account never received it. What’s really happening: either a genuine rail failure that hasn’t reflected, or the payout went to a stale/wrong handle, or (rarely) the app’s status is ahead of reality. Fix: Get the UTR from the app, then ask your bank to trace that UTR. If the bank has no record of a credit against it, you have proof the money didn’t reach you — that’s your dispute. This is the type where the UTR is everything.
Type 3 — Failed, but money debited (UPI debited-but-not-credited)
Symptom: the payment screen says “failed,” yet the amount left somewhere (the app wallet, or in deposit-side failures, your bank). What’s really happening: Gate 4 rail failure. The most consumer-protected state. Fix: This is the T+1 auto-reversal case under the RBI circular. Note the UTR, wait through T+1, and if it’s not back, raise a UPI dispute via your app’s “raise complaint / dispute” button (it routes into NPCI UDIR) and claim the ₹100/day if you’re past T+1. Deeper guide: the UPI failed, money debited fix page walks the exact UDIR dispute screen-by-screen.
Type 4 — Amount received is less than you withdrew
Symptom: the money arrived, but it’s smaller than your withdrawal amount. What’s really happening: almost always TDS. This is not theft and not a fee dispute — it’s tax the app is legally required to deduct (see the tax section). On winnings, that’s 30% under Section 194BA. Fix: No dispute needed. Check the app’s tax/TDS statement; the deducted amount should appear against your PAN in Form 26AS / the Annual Information Statement (AIS) and is creditable when you file your return.
Type 5 — KYC rejected / account blocked or frozen
Symptom: withdrawal blocked with a KYC-failed, verification-pending, or account-restricted message. What’s really happening: Gate 1. Name mismatch, blurry document, a flagged account, or a risk freeze. Fix: This is a verification problem, not a payment one. Resubmit clean KYC matching your bank name exactly; if the account is frozen for “investigation,” demand a written reason and a timeline. See the KYC cluster for the document-specific fixes.
Type 6 — Limit hit / minimum not met
Symptom: withdrawal won’t submit, or silently fails, around a round number or right after a previous payout. What’s really happening: Gate 2. You’re under the minimum, over a daily/monthly cap, or have un-wagered bonus blocking the balance. Fix: Check the app’s stated minimum (often ~₹100) and daily limit. Split the withdrawal under the cap, or wait for the 24-hour window to reset.
The taxonomy in one line: Types 1, 5, 6 are gaming-app problems (escalate to the app, then consumer forums). Types 2, 3 are payment-rail problems (escalate to your bank, NPCI, then RBI). Type 4 is not a problem at all — it’s tax. Sorting your case into the right column is the difference between a fix in 3 days and a month of shouting at the wrong door.
The ten concrete reasons a payout actually stalls — with the specific fix for each
The six types above are the shape of the problem. Here is the deeper layer: the ten specific mechanical reasons a payout sits, in rough order of how often they’re the real cause, each with the one fix that clears it.
- KYC name mismatch (bank/UPI vs PAN). Your UPI handle reads “RAHUL K” but your PAN reads “Rahul Kumar.” The risk engine can’t auto-match, so it parks the payout. Fix: make your UPI/bank account name match your PAN exactly, re-submit KYC, and use the same account for deposit and withdrawal — this is the single most common silent stall.
- Name mismatch on bank vs PAN at the bank’s end. Even if the app’s KYC passed, a credit can fail if the beneficiary name on the bank account doesn’t reconcile. Fix: confirm your bank account holder name matches PAN; correct it with the bank, not the app.
- Daily or monthly withdrawal cap hit. You pulled ₹50,000 yesterday and today’s request just hangs. Fix: check the app’s stated daily cap (reported as high as ~₹50,000/day on some Teen Patti Master skins), split the request under the cap, or wait for the 24-hour reset.
- Risk-review hold on a win spike or new account. A sudden large win, a brand-new account, or a big first withdrawal triggers manual review. Fix: wait the stated window, then ask support in writing to confirm it’s a routine review and give a timeline; keep the ticket ID.
- GST/TDS deduction confusion. The payout arrived 30% lighter and you think you were robbed. Fix: none needed — that’s Section 194BA TDS; confirm the cut against the app’s TDS statement and your AIS. Separately, a deposit buying fewer chips is 28% GST, not a withdrawal problem.
- Bank batch window (especially NEFT/IMPS fallbacks). A bank-transfer payout missed a half-hourly NEFT batch or hit an off-hours window. Fix: allow 30 minutes to a couple of hours for the next batch; only escalate past 24 hours.
- NPCI / bank downtime. The beneficiary bank or the UPI rail itself is temporarily down; the credit can’t confirm. Fix: this resolves on the rail’s own reconciliation — wait through T+1; if still missing, it’s the debited-but-not-credited case with ₹100/day protection.
- App-side wallet vs withdrawable balance. Your “balance” shows ₹800 but only ₹300 is in the withdrawable pot; the rest is deposit or bonus. Fix: read the withdrawal screen’s withdrawable figure, not the headline wallet number.
- Negative bonus-wagering balance. A welcome/referral bonus carries a play-through requirement you haven’t met, so the balance is locked. Fix: finish the stated wagering multiple, or accept the bonus is non-withdrawable; this is in the terms, not a bug.
- Duplicate-account / multi-device flag. The anti-fraud system sees the same device, IP, or payment instrument across accounts and freezes the payout pending review. Fix: stop creating accounts immediately, contact support with your registered number, and ask for the specific reason in writing — never spin up a “new” account to escape it, which deepens the flag.
For the screen-by-screen version of the payment-rail reasons (6, 7) see the UPI failed, money debited fix; for the KYC reasons (1, 2) the KYC cluster has the document-level fixes.
The payout rails: UPI vs IMPS vs NEFT vs bank transfer
Which rail your payout rides decides how fast it clears, what its cap is, and which dispute path applies when it fails. Most card-game payouts default to UPI for small amounts and fall back to IMPS/NEFT for larger ones or when a UPI handle won’t resolve. Here is how each rail actually behaves.
| Rail | Typical clearing time | Per-transaction cap | Availability | Main failure mode | Dispute path |
|---|---|---|---|---|---|
| UPI | Seconds when it works | ~₹1 lakh/day for most banks (source) | 24×7×365 | Debited-but-not-credited; handle won’t resolve | In-app “raise complaint” → NPCI UDIR; T+1 auto-reversal |
| IMPS | Instant, 24×7 | Up to ₹5 lakh (source) | 24×7×365 | Beneficiary detail mismatch; rare timeout | Bank failed-transaction complaint with UTR/RRN |
| NEFT | 30 min – 2 hours (half-hourly batches) | No upper limit | 24×7 since Dec 2019 | Missed a batch window; wrong IFSC | Bank complaint; auto-return on credit failure |
| Bank transfer (generic) | Hours to ~T+2 | Bank-dependent | Business-hours-skewed | Account/IFSC mismatch | Bank failed-transaction complaint |
The practical implications for a stuck payout:
- If your payout is small and rode UPI, the strongest protection applies: the RBI TAT circular forces a T+1 auto-reversal on a debited-but-not-credited transaction, with ₹100/day after. This is the easiest case to win.
- If your payout was large and rode IMPS, it’s normally instant; a stall usually means a beneficiary-detail problem, and you dispute it through your bank with the RRN/UTR, not through a UPI app.
- If it rode NEFT, a delay of up to a couple of hours is normal batch timing, not a failure — NEFT settles in half-hourly batches, so a transfer that just missed a batch waits for the next one. Don’t escalate a NEFT payout inside the first two hours.
- A UPI handle that no longer resolves (you changed banks, deleted the app, closed the linked account) is a common reason a “paid” payout never lands — the rail tried to credit a dead address. The fix is to update your withdrawal method to a live account and ask support to re-issue, with the original UTR as evidence the first attempt failed.
Knowing the rail also tells you who to complain to. UPI failures go to the UPI app / NPCI UDIR first. IMPS and NEFT failures go to your bank’s failed-transaction desk first, because there’s no consumer UPI app in that loop. Both ultimately escalate to the same place — your bank’s grievance officer, then the RBI Ombudsman — but the first door is different.
Find your UTR and raise a UDIR complaint — exact menu path per UPI app
You cannot trace or dispute a “paid but not received” payout without the UTR (also shown as a 12-digit reference / RRN). The catch: every UPI app labels it differently and buries it in a different menu. Here is exactly where to look, and exactly how to raise the in-app complaint that feeds NPCI’s UDIR, for the four apps most Indians use (app-by-app labels confirmed here).
PhonePe
- Find the UTR: open History → tap the transaction → the reference is shown as “UPI Reference No.” (a 12-digit number). It’s also in the bank SMS and your statement.
- Raise the complaint: on that transaction’s detail screen, tap Help / Contact Support → choose the issue (“money debited but not received” / “payment failed”) → submit. PhonePe routes it to your bank and into the NPCI dispute flow. PhonePe’s own failed-transaction guide confirms the debited-but-not-credited path.
Google Pay
- Find the UTR: tap the transaction in your activity list → scroll to transaction details → it appears as “Bank Reference ID” / “UPI transaction ID” (12 digits).
- Raise the complaint: on the transaction screen, tap the support/question option → select the failed/not-received issue → raise dispute. It’s forwarded to your bank for verification through the same UDIR mechanism.
Paytm
- Find the UTR: open Balance & History / Passbook → tap UPI & Bank Transfer (this separates UPI from Paytm-wallet entries) → open the transaction → the reference shows as “UPI Ref No.”
- Raise the complaint: on that transaction, tap Help & Support at the bottom → pick the dispute reason → submit. This is the per-transaction help path, not the generic app help menu.
BHIM
- Find the UTR: open Transaction History → tap the transaction → it’s labelled “Transaction ID.”
- Raise the complaint: in Transaction History, open the problem transaction → tap “Raise Concern” → file the complaint. BHIM sends it to your bank for verification.
If the in-app route stalls or the app won’t let you raise a concern (common when the app no longer recognises the beneficiary), go straight to the NPCI UPI Help portal “Dispute Redressal” page and file with the transaction ID, bank, amount, date and email — or call 1800-120-1740. NPCI’s stated UDIR resolution window is 3–5 working days. For the full screen-by-screen walkthrough of the dispute itself, the spoke page goes deeper: UPI failed, money debited.
One thing the apps don’t make obvious: the UTR is the same number whether you call it UPI Reference No., Bank Reference ID, UPI Ref No. or Transaction ID — it’s the single thread that ties your debit to a (missing) credit. Capture it on Day 0, because once a “failed” transaction ages out of the app’s quick view, digging it back out is far harder, and your bank cannot trace a credit that you can’t name.
”I got less than I withdrew” — the tax reality (194BA and GST)
A massive share of “the app cheated me” complaints are actually tax, correctly deducted. If your payout arrived but was smaller than your winnings, read this before you dispute anything — disputing a legal TDS deduction wastes the days you’d need for a real problem.
Income tax: 30% TDS on net winnings (Section 194BA)
Since 1 April 2023, every legal online-gaming app in India must deduct TDS at 30% on your net winnings — and there is no minimum threshold. The old ₹10,000 threshold is gone. This is Section 194BA of the Income-tax Act, introduced by the Finance Act 2023, with the computation mechanism set out in Rule 133 and the CBDT Circular No. 5/2023 dated 22 May 2023.
“Net winnings” is not “every win.” Per Rule 133, the financial-year formula is:
Net winnings = (A + D) − (B + C) where A = total amount withdrawn during the year, D = closing wallet balance at 31 March, B = total non-taxable deposits during the year, C = opening wallet balance at 1 April. (Non-withdrawable bonuses are excluded from balances and are not deposits.) — Rule 133 / Circular 5/2023
In plain terms, the app taxes the amount you actually came out ahead, not every rupee that crossed the table. Critically, TDS is deducted at the time of each withdrawal and on any remaining net winnings in your account at financial-year end — so a year-end balance you never withdrew can still be taxed. The 30% is reported against your PAN, which is exactly why PAN-KYC is mandatory before you can withdraw — and why a PAN mismatch stalls payouts.
Worked example 1 — a net-winner (deposit, win, withdraw)
Let’s make it concrete. Assume a single account, no opening balance, a clean financial year.
- You deposit ₹10,000 (this is B, your non-taxable deposit).
- You play and your withdrawable balance grows to ₹25,000.
- You withdraw ₹25,000 (this is A).
- Opening balance C = ₹0, closing balance D = ₹0 (you cashed it all out).
Net winnings = (A + D) − (B + C) = (25,000 + 0) − (10,000 + 0) = ₹15,000.
TDS at 30% on ₹15,000 = ₹4,500. So the app pays out ₹25,000 − ₹4,500 = ₹20,500 to your bank, and remits ₹4,500 against your PAN. Your bank shows ₹20,500 arriving; the “missing” ₹4,500 is in Form 26AS / AIS and is creditable when you file your return — you are not simply losing it.
The per-withdrawal nuance. Within a year, the app computes net winnings comprised in each withdrawal and only taxes the part not already taxed — so it doesn’t double-tax. Per CBDT’s worked illustration, if your net winnings in April were ₹90 (below ₹100, so no TDS that month under the de-minimis rounding the rules allow) and you then have ₹200 more net winnings withdrawn in May, the app deducts 30% on the cumulative ₹290, not on ₹200 alone. The mechanism tracks cumulative deposits, prior withdrawals, and tax already deducted so the year’s total TDS lands correctly.
The year-end edge case. Suppose instead you withdrew nothing during the year but ended 31 March with ₹15,000 of net winnings still sitting in the wallet (A = 0, D = 15,000, B and C = 0). Net winnings = (0 + 15,000) − 0 = ₹15,000, and the app must deduct ₹4,500 TDS on that balance at year-end even though you never cashed out. This is why your wallet can quietly shrink at the start of April: that’s the year-end 194BA deduction, not a glitch.
Worked example 2 — a net-loser (no TDS, and you can’t reclaim the cut as TDS)
Now the player who lost on the year.
- You deposit ₹10,000 (B).
- You play, win some, lose more, and withdraw ₹6,000 total during the year (A).
- Opening C = ₹0, closing D = ₹0.
Net winnings = (6,000 + 0) − (10,000 + 0) = −₹4,000.
Net winnings are negative, so there is no TDS — you didn’t come out ahead, so there’s nothing to tax. The app should pay your ₹6,000 withdrawals in full (no 30% cut). Two warnings from the CBDT guidance: a negative net-winnings figure cannot be used to claw back TDS the app already deducted on an earlier withdrawal in the same year (you adjust that in your ITR, not against the TDS), and if you hold multiple accounts on the same platform, the app must consolidate all of them before computing net winnings — so a loss on one account genuinely offsets a win on another within the same operator, but not across different operators.
GST: 28% on deposits (why your deposit may buy fewer chips)
Separately, since 1 October 2023, online money gaming attracts 28% GST on the full value of deposits (not on winnings), under CBIC Notifications dated 29 September 2023 following the 50th and 51st GST Council recommendations. That’s a deposit-side tax, so it doesn’t reduce a withdrawal — but it’s why ₹100 deposited may convert to fewer playable chips than you expect. Players who don’t know this sometimes misread the gap as a “deposit not fully credited” bug. It isn’t; it’s the 28% GST.
The tax bottom line in two numbers: 30% comes off your net winnings on the way out (Section 194BA, no threshold), and 28% GST sits on your deposits on the way in. Neither is the app stealing from you. If your shortfall matches a 30% cut on net winnings, stand down — that’s TDS, and it’s yours to reclaim at filing. And a forward note for accuracy: from 1 April 2026, the 194BA provision is consolidated under Section 393(3) of the new Income-tax Act, 2025, but the 30% on net winnings, no threshold substance carries over.
State-by-state legality: who actually gets paid, and where
Whether an operator will (or legally can) pay out to you depends partly on where you are. This changed dramatically in 2025–26, so read the central rule first, then your state.
The central rule now: PROGA 2025 overrides the skill-vs-chance debate
For two decades, Indian RMG ran on a single distinction: a game of skill (rummy, fantasy sports, poker in many readings) was legal in most states, while a game of chance (lottery, satta, card games of pure luck) was not. PROGA 2025 collapsed that distinction for online money games. The Act prohibits all online money games — “skill-based or not” — where a player pays to play in expectation of a monetary return, and it claims overriding authority over conflicting state laws. The Rules came into force 1 May 2026. In practice, the major legal operators suspended cash play from late August 2025, right after Presidential assent.
What that means for getting paid: a new real-money deposit into one of these games is now illegal, and operators won’t take it. Recovering an existing balance is a different matter — banks and intermediaries continued processing withdrawals so users could pull their money out. So the live question for most players in 2026 is not “is my state skill-friendly” but “can I get my stranded balance out” — and the rail protections in this guide are exactly the lever for that.
The constitutional caveat that isn’t settled yet
PROGA’s blanket ban is under constitutional challenge. The Supreme Court was set to hear petitions on 21 January 2026 arguing the Act intrudes on states’ Entry-34 power over “betting and gambling” and violates the right to do business. Under the Constitution, betting and gambling sit on the State List, which is the heart of the legal fight. Until that’s resolved, treat the central ban as the operative rule for new money-gaming and watch for change.
The state layer, which still matters
Even before PROGA, states diverged sharply, and those state laws shape how the wind-down and any future framework play out (state snapshot here):
- Telangana and Andhra Pradesh imposed blanket prohibitions on all staked games, including skill games — historically the strictest, so operators often blocked these states even when skill-gaming was legal elsewhere.
- Tamil Nadu banned real-money games of chance online and layered on player-protection rules (such as time/spend limits).
- Haryana extended its gambling prohibition expressly to online mediums in 2025.
- Nagaland licensed online skill games, and Sikkim licensed casino and skill games within its own territory — the licensing outliers.
- Most other states relied on the skill-vs-chance distinction, which PROGA has now centrally overridden for online money games.
The payout takeaway: historically, if you were in Telangana or Andhra Pradesh, an operator might decline to pay out (or refuse to onboard you) because staked play was banned in your state — a real, legal reason a withdrawal could be blocked that had nothing to do with the rail. Post-PROGA, the cash product is centrally prohibited regardless of state, so the only payout that should still flow anywhere is a balance recovery. If an operator is refusing even to return your existing balance citing your state, that’s a consumer-grievance and bank-dispute matter — escalate it as a payment deficiency, not as a gaming dispute.
Editor’s verdict on legality: don’t get lost in the skill-vs-chance philosophy — for getting your money, it no longer matters, because PROGA banned online money games of both kinds. What matters now is (1) never deposit again into a discontinued cash game (it’s illegal), and (2) push hard on your right to recover an existing balance, where the RBI/NPCI rail rules still have full force. If you’re in a historically strict state (Telangana, Andhra Pradesh), expect extra friction and lean on the payment-side dispute, not the operator’s goodwill.
The universal Day-0-to-30 escalation ladder
This is the spine of the whole site, and it works because it matches each action to the rule-clock from the table above. Don’t skip rungs (you’ll waste days), and don’t jump to RBI on Day 1 (they’ll bounce you back to the entity). Climb in order. Every rung has a copy-paste template in the next section.
Day 0 — Freeze the evidence and open the in-app ticket
The single highest-leverage thing you do is on Day 0, and it’s not complaining — it’s documentation. Within the first hour:
- Screenshot everything: the withdrawal request, the status screen, the amount, the timestamp, and your wallet balance before and after. Date-stamped screenshots are your evidence later.
- Capture the UTR / transaction reference the moment one appears. No UTR = you can’t trace a “paid” payout. The UTR is a 12-digit reference in your UPI app’s transaction history and on the app’s payout record (see the per-app menu paths above).
- Raise the in-app support ticket with the amount, timestamp, and UTR. Get a ticket / complaint ID in writing. This timestamps your complaint, which matters for the 30-day Ombudsman clock later.
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 1–3 — Official support 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.
- If this is a failed/debited UPI case (Type 3), this is the T+1 window — let the auto-reversal run before you dispute.
- If the app publishes a 1–3 working-day SLA, you are still inside it. Be firm but patient.
Day 4–7 — Open the payment-side dispute (UTR + NPCI)
If the money is genuinely gone on the rail (Types 2 and 3) and hasn’t come back:
- Open your UPI app’s “raise complaint / dispute” on that transaction (the exact path per app is in the UTR section above). This feeds NPCI UDIR, which can auto-convert to a chargeback after the TAT.
- Or call your bank and lodge a failed-transaction complaint with the UTR; ask explicitly 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 use the NPCI UPI Help portal or the NPCI UPI complaint line 1800-120-1740. NPCI’s stated UDIR resolution window is 3–5 working days.
Day 8–15 — Formal bank complaint + app “final notice”
- Escalate the bank complaint to a written formal complaint if the helpline did nothing. Get a complaint reference number.
- Send the app a final-notice email: restate the facts, the ticket ID, the UTR, the days elapsed, and state that you’ll escalate to the RBI Ombudsman and a consumer forum if it isn’t resolved. A clear, dated final notice often unsticks a payout because it signals you know the process.
Day 16–30 — RBI Ombudsman and consumer forum
If the regulated entity (your bank / the payment-system participant) still hasn’t resolved a payment failure:
- After 30 days without resolution, file with the RBI Integrated Ombudsman Scheme 2021 (RB-IOS) at cms.rbi.org.in. The RB-IOS covers banks, NBFCs and Payment System Participants, and redress is free.
- For the consumer-service angle (an app that simply won’t pay a clearly-owed, KYC-clean payout), the National Consumer Helpline 1915 and the consumer-forum route apply.
- If you suspect outright fraud — a fake clone app, a phishing “customer care number,” or an OTP scam — report immediately to the cybercrime helpline 1930 and cybercrime.gov.in. You can also flag fraudulent payment entities on RBI’s Sachet portal.
Honest limit of this ladder: the RBI Ombudsman and bank disputes are powerful against the payment rail (Types 2 and 3), because banks and payment-system participants are RBI-regulated. They are weaker against a shady offshore or unlicensed app that simply ignores you (Types 1, 5, 6), because that operator may be outside Indian regulatory reach. That asymmetry is the single best argument for only playing where payouts are clean in the first place — which is the whole point of the section near the end.
Copy-paste complaint templates
Fill in the bracketed parts. Keep every message factual, dated, and ID-stamped — emotion doesn’t move a payout, a UTR does. There are five here, one per escalation rung.
Template A — In-app support ticket (Day 0)
Subject: Withdrawal not received — Ticket request
My withdrawal of ₹[AMOUNT] requested on [DATE, TIME] is showing
"[STATUS shown in app]" and has not reached my account.
Registered mobile: [NUMBER]
UPI ID / bank used: [HANDLE / A/C]
UTR / reference (if shown): [UTR]
KYC status: completed (PAN + Aadhaar verified)
Please confirm the payout status and the UTR, and resolve within your
stated payout window. Please share a complaint/ticket ID for this request.
Template B — Official support email / grievance-officer escalation (Day 1–3)
Subject: [Ticket ID] Withdrawal of ₹[AMOUNT] not credited — 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].
Transaction details:
- Amount: ₹[AMOUNT]
- Requested: [DATE, TIME]
- Status in app: [STATUS]
- UTR / reference: [UTR]
- Registered number: [NUMBER]
- KYC: completed (PAN matches bank account name)
Please 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 C — Bank / UPI failed-transaction dispute (Day 4–7)
Subject: Failed UPI credit — UTR [UTR] — request 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 and credit the applicable
compensation, and share the complaint reference number.
Template D — RBI Ombudsman (RB-IOS) grievance (Day 30+)
Nature of complaint: Deficiency in service — failed/unresolved digital
payment (UPI withdrawal 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.
File Template D at cms.rbi.org.in only after 30 days have passed without resolution from the entity, since that 30-day rule is the eligibility gate for the RB-IOS 2021.
Template E — National Consumer Helpline complaint (parallel, for app-side deficiency)
To: National Consumer Helpline (1915 / consumerhelpline.gov.in)
Complaint: Service deficiency — gaming app refusing/failing to pay a
verified, KYC-complete withdrawal.
- 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]
- KYC: completed; PAN matches bank account name
Relief sought: release of ₹[AMOUNT] to my registered account, and a
written reason for the delay.
Use Template E in parallel with the bank/RBI route when the failure is on the app’s side (it’s holding an approved, owed balance) rather than on the rail — the consumer-helpline angle reaches the operator’s service obligation, while the RBI route reaches the payment rail.
Grievance contact reference block
Keep this handy; it’s the whole escalation map in one place. Use the door that matches your problem type.
| Authority | Use it for | Channel |
|---|---|---|
| Your bank’s failed-transaction desk | UPI/IMPS/NEFT debited-but-not-credited; ₹100/day TAT claim | Bank app / branch / helpline with UTR |
| NPCI UPI Help (UDIR) | UPI dispute, chargeback after TAT | upihelp.npci.org.in · 1800-120-1740 · upihelp@npci.org.in |
| RBI Integrated Ombudsman (RB-IOS 2021) | Unresolved payment failure after 30 days; free redress | cms.rbi.org.in · scheme FAQ |
| RBI Sachet portal | Report a suspicious/unauthorised payment entity | sachet.rbi.org.in |
| National Consumer Helpline | App service deficiency (won’t pay an owed, clean balance) | 1915 · consumerhelpline.gov.in |
| Cybercrime helpline / portal | Fraud, fake “care number”, OTP/PIN scam, clone app | 1930 · cybercrime.gov.in |
Order of doors, in one line: app → bank/UPI → NPCI → RBI Ombudsman, with consumer helpline 1915 in parallel for app-side deficiency and cybercrime 1930 the instant fraud is involved.
Is it a delay or a scam? Red flags that change your strategy
Most stuck payouts on legal apps are delays. But some apps are not legal, not licensed, or outright clones, and on those the ladder above has limited teeth. Use these red flags to decide how hard to fight versus how fast to cut your losses and switch:
- No PAN/KYC was ever required to deposit or withdraw. A legal app must do KYC. No KYC is a sign you’re not on a regulated platform — your RBI leverage shrinks.
- The app pushes you to a “customer care number” found on a random website or YouTube comment. These are overwhelmingly scams that exist 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 deposit into a money game is also illegal. Stop, document, and report.
- A sideloaded / “mod” / “unlimited chips” APK. Modified builds void the app’s terms and can get your account and balance frozen with no recourse. The balance you’re fighting for may already be gone by the app’s own rules.
- 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 file). A disappeared operator is a different, worse problem — though note that a legitimate PROGA wind-down is the opposite case: the app stopped cash games but should still let you withdraw an existing balance.
If two or more of these are true, the realistic verdict is harsh: pursue the bank/UPI dispute and the cybercrime report for any rail loss, but lower your expectation of recovering balance held inside an unlicensed operator — and don’t feed it another rupee. Which leads to the only durable fix.
Where to get real, official help
There is no “faster app” that fixes a stuck payout, and after PROGA 2025 (in force 1 May 2026) moving to another online money-gaming service is not a legal option in India. What actually recovers money is the official grievance chain, used in order, with your paper trail intact:
- Your bank first. For any UPI/IMPS/NEFT debit that wasn’t credited, raise a transaction dispute. Under RBI’s failed-transaction circular the auto-reversal is T+1 and compensation is ₹100/day after that.
- NPCI UPI grievance / UDIR. Raise a dispute for the specific UTR through your UPI app or NPCI UPI Help — the rail-level escalation for UPI failures.
- RBI Ombudsman (RB-IOS). If the bank or PSP doesn’t resolve it within 30 days, file free on the RBI CMS portal.
- National Consumer Helpline 1915, and for fraud, cybercrime 1930 / cybercrime.gov.in plus the RBI Sachet portal.
Editor’s verdict. A rail failure — money left your bank but never reached you — is the recoverable kind; the rules above force a refund. A balance held inside a now-discontinued or unlicensed operator is the hard kind: pursue it through the chain above, but never deposit more “to unlock” a withdrawal. Post-PROGA that deposit is both throwing good money after bad and illegal.
Related fixes (go deeper on your exact case)
This is the withdrawal hub. For the case that matches your symptom, these spokes go step-by-step:
- UPI withdrawal failed / pending → Teen Patti UPI withdrawal fix — the exact NPCI UDIR dispute screens and UTR location.
- Withdrawal stuck / pending / processing → withdrawal stuck fix — the pending-state countdown.
- UPI failed but money debited → UPI failed, money debited — the T+1 auto-reversal and ₹100/day claim.
- Can’t reach the app → Teen Patti Master customer care — official channels and the scam-number warning.
FAQ
1. How long does a 3 Patti withdrawal take? Most UPI payouts from legal apps settle in minutes to a few hours, and apps typically publish a window of 1–3 working days. If a UPI payout is debited but not credited, RBI’s TAT circular requires auto-reversal by T+1, after which you’re owed ₹100 per day.
2. What is the minimum 3 Patti / Teen Patti withdrawal amount? It varies by app, but a common minimum is around ₹100 for UPI, sometimes ₹300 for bank transfer. You must complete PAN + Aadhaar KYC before your first withdrawal regardless of the amount.
3. Do I need KYC to withdraw from a Teen Patti app? Yes. Every legal real-money app in India requires PAN and Aadhaar-based KYC before any cash withdrawal, because the app must report 30% TDS against your PAN under Section 194BA. A name mismatch between your UPI handle and KYC is the single most common silent cause of a stuck first payout. Some apps (e.g. Junglee Rummy) forced KYC at the first withdrawal or once cumulative deposits crossed ₹50,000.
4. Why did I receive less money than I withdrew? Almost always TDS: legal apps deduct 30% on net winnings under Section 194BA, with no minimum threshold, since 1 April 2023. On a ₹25,000 withdrawal where your net winnings were ₹15,000, that’s a ₹4,500 cut. The deducted amount is reported against your PAN in Form 26AS / AIS and is adjustable when you file your return.
5. How is “net winnings” actually calculated for TDS? Per Rule 133, net winnings = (withdrawals + closing balance) − (deposits + opening balance) over the financial year, excluding non-withdrawable bonuses. TDS is deducted at each withdrawal and again on any year-end balance. So if you end 31 March with ₹15,000 of net winnings un-withdrawn, the app still deducts ₹4,500 then.
6. My 3 Patti withdrawal has been “pending” for 3 days — what do I do? Three days is past most apps’ stated window, so treat it as delayed. Raise an in-app ticket on Day 0 with the amount, timestamp, and UTR; follow up by official email on Day 1–3; and if it’s a failed UPI payout, open a bank/UPI dispute around Day 4–7 using the UTR, per NPCI timelines.
7. My UPI withdrawal was debited but not credited — what happens? Under RBI Circular DPSS.CO.PD No.629 (20 Sep 2019), such a transaction must be auto-reversed by T+1. If it isn’t, your bank owes you ₹100 per day of delay, credited automatically — you don’t have to request it, though you should chase it if it doesn’t appear.
8. What is a UTR and where do I find it? A UTR (Unique Transaction Reference) is the 12-digit reference for a UPI/bank transfer. PhonePe labels it “UPI Reference No.”, Google Pay “Bank Reference ID”, Paytm “UPI Ref No.”, and BHIM “Transaction ID” — all the same number. You cannot trace or dispute a “paid but not received” withdrawal without it, so capture it on Day 0.
9. The app says “paid / success” but I got nothing — how do I prove it? Get the UTR from the app and ask your bank to trace it. If the bank has no record of a credit against that UTR, you have evidence the money didn’t reach you — open a UPI dispute (NPCI UDIR) and escalate. NPCI’s stated complaint-resolution window is 3–5 working days.
10. Which is faster — UPI, IMPS or NEFT for my payout? UPI is instant (cap ~₹1 lakh/day) and IMPS is instant up to ₹5 lakh; NEFT settles in 30 minutes to 2 hours because it runs half-hourly batches. So a NEFT payout that takes an hour is normal, not stuck — don’t escalate it inside the first two hours.
11. Where do I complain if the app simply won’t pay? Climb in order: app support, then your bank/UPI dispute with the UTR, then NPCI UPI Help (or 1800-120-1740). After 30 days without resolution from a regulated entity, file free with the RBI Integrated Ombudsman at cms.rbi.org.in, and run the National Consumer Helpline 1915 in parallel for the app’s service deficiency.
12. How much tax is deducted from Teen Patti winnings overall? Two separate taxes: 30% TDS on your net winnings on withdrawal (Section 194BA, no threshold), plus 28% GST on deposits since 1 October 2023 under CBIC notifications. The 30% reduces your payout; the 28% reduces your playable deposit — neither is an app malfunction.
13. Are the “Teen Patti customer care numbers” on Google safe to call? Frequently not. Most legal apps have no public phone helpline and route support in-app; scammers post fake “care numbers” to phish your OTP and UPI PIN. Never share an OTP or PIN with a caller, and report fake numbers to the cybercrime helpline 1930 and cybercrime.gov.in.
14. Can I still withdraw from RummyCircle or Junglee Rummy after the ban? Their cash games are discontinued under PROGA 2025, but operators and banks kept processing withdrawals so users could recover existing balances. Complete KYC, follow the in-app withdrawal/recovery flow, expect 30% TDS on net winnings, and never deposit again — a new deposit into a money game is now illegal.
15. Can I get my money back if the app turns out to be a scam? For money lost on the payment rail, pursue the bank/UPI dispute, NPCI, and RBI Ombudsman, and report fraud to 1930 and the RBI Sachet portal. But recovery of balance held inside an unlicensed or offshore operator that ignores you is not guaranteed, because it may sit outside Indian regulatory reach — which is the strongest reason to only play where payouts are clean and KYC is real.
Sources & method. Withdrawal timings, taxes, legality and escalation steps on this page are built from primary regulatory sources and named operator help pages — 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; RBI Sachet portal; NPCI and NPCI UPI Help / UDIR; CBDT Section 194BA, Rule 133 and Circular No. 5/2023 (22 May 2023) at incometaxindia.gov.in; CBIC 28% GST notifications (29 Sep 2023) at cbic-gst.gov.in; the Promotion and Regulation of Online Gaming Act, 2025 and its Rules effective 1 May 2026; NEFT half-hourly batch timing and IMPS/UPI rail limits; operator KYC/TDS pages for Junglee Rummy and RummyCircle; cybercrime reporting at cybercrime.gov.in / helpline 1930; National Consumer Helpline 1915. 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.