The 30-second answer
To recover money from a shut-down gaming app, move fast on three things: finish KYC, withdraw your existing balance through the operator’s voluntary wind-down flow (Dream11, MPL, RummyCircle, Junglee and PokerBaazi all kept withdrawals open while disabling deposits), and keep every screenshot. There is no statutory 180-day refund right — that draft rule was dropped from the final Rules 2026. Recovery rests on the operator’s own process plus consumer, RBI and contract law — this page is a spoke of the refund-dispute recovery hub. If the app stalls, climb the grievance ladder: operator, then OGAI within 30 days, then a bank/RBI rail dispute for any failed debit. Never deposit again to “unlock” a payout — that is now illegal.
Editor’s verdict, up front. “Rummy app closed my money” is the most common panic search in Indian RMG right now, and the panic is usually misplaced. In nearly every case the operator did not seize your balance — it stopped the games and left a withdrawal path open, because a clean wind-down lets it move your money out without breaking the new law. Your real enemy is time and friction: an un-completed KYC, a name mismatch, a store-removed app you can still log into, or a stalled ticket. This page is the step-by-step recovery playbook for getting your balance out, app by app — not the law lecture. The legal why lives on the shutdown-refund explainer; this page is the how.
The single fact you must get right. The widely-shared claim that you have a “180-day platform refund window” is wrong. That obligation appeared in a draft and was dropped from the final notified Rules 2026. What survives is permission for operators to remit pre-existing user balances during an orderly wind-down without that being treated as facilitating a banned money game — a permission the platform may use, not a deadline you can enforce against it. So you cannot walk into a consumer forum waving a “statutory 180-day right.” You recover through the operator’s own withdrawal flow first, backed by existing consumer / RBI / contract law and the OGAI grievance ladder if it stalls. Read that distinction twice; it changes which door you knock on.
Why your money is stuck: what actually happened in 2025–26
If you are reading this, an app you played on — most likely Dream11, MPL, RummyCircle, My11Circle, Junglee Rummy, PokerBaazi, WinZO, Zupee or a Teen Patti card app — stopped its cash games and left a balance sitting in your wallet. Three things happened in sequence, and understanding the sequence tells you exactly where your money is and how to get it.
One: the law changed. 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 monetary return. The operating PROG Rules, 2026 came into force on 1 May 2026, administered by a new regulator, the Online Gaming Authority of India (OGAI), an attached office of MeitY.
Two: the operators pulled the cash product. They did not wait for 1 May 2026. Right after the August 2025 assent, India’s biggest real-money operators suspended cash formats. By the time the Rules commenced, the commercial restructuring was largely complete — banks and payment intermediaries had already stopped accepting new deposits to these platforms from around August 2025 while continuing to allow withdrawals so users could exit their balances (per the wind-down reporting).
Three: your balance got frozen in place. When the games stopped, your deposit, winnings and bonus pots stopped moving. You can no longer play them up or down. What you can still do, in most cases, is withdraw the eligible part — and that withdrawal path is the entire subject of this page.
So the honest one-line diagnosis: your money is almost never gone. It is parked inside a discontinued operator that left a withdrawal door open but made it slightly harder to find, slower to clear, and conditional on you having completed KYC. Recovery is mostly a race against friction, not a fight against theft.
The deposit/winnings/bonus split still decides what you can pull
A wind-down does not change the basic anatomy of your wallet, and this is where most “I can’t withdraw” complaints actually start. Your balance is three pots, and only some are recoverable:
- Deposit balance — money you added yourself. Often withdrawable in a wind-down, though some apps still required play-through before the freeze.
- Winnings balance — money you won. This is the pot KYC and TDS apply to, and the pot most wind-down flows are designed to release.
- Bonus / promotional balance — chips the app gave you. Almost never withdrawable, and a wind-down does not suddenly make it cashable. A large share of “the closed app stole ₹800” complaints are players reading a locked bonus balance as theft.
Before you escalate anything, open the app (if you still can) and read the withdrawable figure, not the headline wallet number. Fighting for a non-withdrawable bonus is a fight you cannot win, wind-down or not. The deeper version of this pot logic lives on the 3 Patti withdrawal hub.
Act-fast triage: which kind of shut-down are you in?
Not every “closed app” is the same problem, and the right first move depends entirely on which of four situations you are in. Spend 60 seconds sorting yourself before you do anything else — the wrong first move (panic-depositing, spinning up a new account) can make recovery harder.
Situation A — A major operator that kept withdrawals open
You played on Dream11, MPL, RummyCircle, My11Circle, Junglee Rummy, PokerBaazi, WinZO or Zupee, the app still opens, and you can log in. These operators publicly confirmed users could continue withdrawing balances while deposits were permanently disabled. This is the easy case. Your job is to complete KYC and run the in-app withdrawal now, before any internal deadline. Skip to the step-by-step wind-down withdrawal section.
Situation B — The app was removed from the store but you still have your login
The app vanished from the Play Store or App Store (these RMG apps were delisted as the law took effect), but it’s still installed on your phone, or the operator’s website still loads, and your account still works. Your balance is tied to your registered number, not the app file. You recover through the web withdrawal flow or the still-installed app — covered in the store-removed section.
Situation C — The app and your login are gone
The app won’t open, the website is dead, or you can’t log in at all. This is the hard case, and it shifts you from “withdraw” to “document and claim.” You rebuild your claim from email records, bank/UPI statements showing your deposits, and any UTR/transaction references, then escalate through grievance and rail-dispute channels. Go to the no-login section.
Situation D — It was never a legal, licensed operator (clone / offshore / “mod” APK)
You played on a sideloaded “unlimited chips” APK, an offshore site, or a clone of a real brand. The wind-down protections do not apply, and your regulatory leverage is thin. You pursue any payment-rail loss (a debit that failed) through your bank, and report fraud — but recovery of balance held inside an unlicensed operator is not guaranteed. See the red-flags section and the refund-dispute hub.
Triage in one line: A is “withdraw now,” B is “withdraw via web,” C is “rebuild the claim and escalate,” D is “pursue the rail and report fraud.” Sorting yourself correctly is the single highest-leverage minute you’ll spend, because each situation knocks on a completely different door.
The first 48 hours: a do-this-now checklist
Whatever situation you’re in, the opening 48 hours decide how easy the rest of the recovery is. Speed protects you against a closing remittance window, and good early documentation protects you against everything else. Work this list in order before you do anything more elaborate.
Hour 0–1 — see what you’ve actually got.
- Open the app or the operator’s website and confirm you can log in with your registered number. Whether the login works is what sorts you into Situation A/B versus C/D.
- Screenshot the balance screen — both the headline wallet and the withdrawable figure. Date-stamped, before you touch anything.
- Check your KYC status. If PAN/bank verification is incomplete or shows a mismatch, that’s your first job — the withdrawal won’t clear without it.
Hour 1–6 — clear the precondition and pull the money.
- Finish or repair KYC so your PAN name matches your bank/UPI name exactly, on an account you control today.
- Initiate the withdrawal of the full withdrawable amount to that live account.
- Screenshot the request and capture the UTR the instant it appears.
Hour 6–48 — confirm or open the dispute.
- Check your bank for the credit (minus TDS). If it lands, you’re done — stop here.
- If it shows “paid” but nothing arrives, you’re now in a rail dispute: keep the UTR, and after the T+1 auto-reversal window, raise it with your bank and UPI app.
- If the operator won’t let you withdraw at all, file a written grievance to start your record and the 30-day OGAI clock.
Two rules that override the whole list: never deposit to “unlock” a withdrawal (it’s a scam and now illegal), and never share an OTP or UPI PIN with anyone “helping” you recover. Legitimate recovery never needs either. If you do nothing else from this page, do this checklist today — most Situation-A balances are fully recovered inside it.
First 48 hours in one line: log in → screenshot the balance → fix KYC → withdraw to a live account → capture the UTR → confirm arrival or open a dispute. Done early, it turns most wind-down recoveries into a same-week, low-drama job.
The legal ground you’re standing on (and the myth to drop)
Before the steps, get the law straight, because half the bad advice online rests on a rule that does not exist.
There is no statutory 180-day refund right — that draft rule was dropped
A version of the draft rules floated a platform refund obligation tied to a window. It was not carried into the final notified PROG Rules 2026. So there is no statutory safe-harbour or 180-day window in which the platform is legally compelled to refund you on demand. Anyone telling you to cite a “180-day refund right” in a complaint is sending you in with a weapon that isn’t loaded.
What does exist is narrower and worth stating precisely. The Rules permit an operator, during an orderly wind-down, to remit pre-existing user funds without that remittance being treated as facilitating a (now-banned) money game. Read carefully: that is a permission for the platform to pay you back cleanly, not a deadline you can enforce. The number sometimes attached to operator wind-down arrangements is a grace window for the platform to move funds, not a guaranteed personal refund clock. The practical effect is the same urgency — withdraw early — but for a different reason: you withdraw early because the operator’s window to remit may close, not because you hold a 180-day statutory right.
So what law does back your recovery?
Three real bodies of law, used in order:
- The operator’s own wind-down withdrawal process — your first and best route, because the operator wants a clean exit and built a flow for it. This is contractual: your account terms and the operator’s published wind-down notice are the document you hold it to.
- Existing consumer and contract law — if a licensed operator simply refuses to return a verified, owed balance, that’s a deficiency in service you can pursue through the National Consumer Helpline (1915) and the consumer-forum route, on ordinary contract principles — not on a PROGA refund clause.
- RBI/NPCI payment-rail rules — if any specific debit failed (you withdrew, money left somewhere, nothing arrived), that failed transaction is protected by RBI’s failed-transaction TAT circular — T+1 auto-reversal and ₹100/day compensation after that — completely independent of gaming law. This is your strongest lever, and it’s the subject of the refund-dispute hub.
The OGAI grievance ladder, exactly
If the operator stalls, the PROG Rules 2026 give you a defined grievance path. The draft’s intermediate Grievance Appellate Committee was removed in the final Rules, so the ladder is shorter than early commentary claimed:
- Rung 1 — the operator’s grievance officer. Every licensed online-gaming service provider must run a grievance mechanism. File there first, in writing, with your amount and a complaint ID.
- Rung 2 — the OGAI, within 30 days. A user aggrieved by the operator’s grievance outcome may directly approach the OGAI within thirty days, through the digital form on the Authority’s website or app. The Authority endeavours to dispose of the appeal within 30 days.
- Rung 3 — the Secretary, MeitY. A further appeal lies to the Appellate Authority (the Secretary, MeitY).
Note the clock: the 30-day window to approach the OGAI runs from the operator’s grievance outcome (or its silence), so don’t let an operator stall you past it. The full legal mechanics are on the PROGA Act explainer; this page keeps to the practical use of the ladder.
The myth-to-drop, in one line: stop citing a “180-day statutory refund right” — it was dropped from the final Rules. Your real levers are the operator’s voluntary wind-down flow, consumer/contract law, the RBI rail rules for any failed debit, and the OGAI ladder (operator → OGAI within 30 days → MeitY). Use the right one for your situation and you’ll recover far faster than someone shouting a non-existent right at the wrong desk.
App-by-app wind-down status: who left withdrawals open
This is the table you came for. Each row gives the operator’s wind-down withdrawal status, the route that worked, and the catch to watch. All five major operators publicly stated balances remained withdrawable while deposits were disabled — the status column reflects that, and the catch column is where recoveries actually stall. Treat the “route” as the planning assumption and always confirm against the operator’s current in-app or on-site wind-down notice, because exact flows shifted through the transition.
| Operator | Wind-down withdrawal status | Route that worked | The catch to watch |
|---|---|---|---|
| Dream11 | Cash contests stopped Aug 2025; withdrawals kept open, deposits disabled; pivoted to free-to-play (FanCode/Cricbuzz angle) (source) | Profile → My Balance → Withdraw from the Winnings column to a KYC-verified bank account (source) | Bank + PAN must be verified first; operator hadn’t clearly stated what happens to unclaimed funds — withdraw early |
| MPL | Real-money games halted; balances withdrawable seamlessly, new deposits not accepted (source) | In-app withdraw flow to verified account | KYC + bank verification gate; large/round pulls may route to manual review |
| RummyCircle / My11Circle | Cash rummy discontinued; players assured they could withdraw any wallet balance (source) | Existing in-app/web withdrawal flow | PAN must match KYC exactly or the recovery stalls; 30% TDS on net winnings still applies |
| Junglee Rummy | Cash games & tournaments discontinued; balance recovery only | In-app withdrawal that remains for recovery (deeper guide) | KYC mandatory before release; TDS on net winnings; never re-deposit |
| PokerBaazi | Real-money poker halted; “user funds remain completely safe and accessible for withdrawals” (source) | In-app withdraw to verified bank | KYC + verified account; expect TDS on net winnings |
| WinZO / Zupee | Real-money operations shut down; withdrawals processed for users to exit balances (source) | In-app withdraw flow while it remains | Confirm against current wind-down notice; bonus pots not withdrawable |
| Teen Patti card apps (Gold/Master skins) | Informal-brand card apps; status varies by skin/operator, less authoritative | Whatever withdrawal flow the specific build still exposes | Judge by the exact build you installed; clone/mod builds may have no recovery path at all |
A blunt caveat: the five named operators are licensed, identifiable Indian companies with a reputation to protect and a regulator watching — their wind-down withdrawals are real and reachable. The Teen Patti card-app row is different: “Teen Patti Gold” and “Teen Patti Master” are brands applied to many skins distributed largely outside the official stores, so there is no single authoritative wind-down policy, and a mod/clone build may simply have no recovery path. If your balance is on a named operator, you are in Situation A and should be withdrawing right now. If it’s on an unknown card skin, you may be in Situation D.
Editor’s verdict on the table: every major operator left a door open — the recoveries that fail fail at KYC, at a name mismatch, or because the player waited too long and an internal cut-off passed. Two of those three are inside your control today. The third is the reason this entire page screams “withdraw early.”
Why the major operators behaved this way (and why that’s good for you)
It helps to understand why Dream11, MPL, RummyCircle and the rest kept withdrawals open, because the reason is also your reassurance. These are publicly identifiable, licensed Indian companies — several venture-backed unicorns — with brand value, founders on record, and a regulator now watching them directly. For a company in that position, seizing user balances would be commercial suicide and a legal trap: it invites consumer litigation, regulator action, and a reputation hit that outlasts the product. A clean wind-down — disable deposits, keep withdrawals, remit balances, pivot the business — is the only rational path, and it’s exactly what they chose. Dream11 pivoted toward free-to-play and the FanCode/Cricbuzz side; others restructured around advertising and esports. The throughline: your balance is a liability they want off their books, not an asset they’re trying to keep. That’s structurally different from a clone operator, which has no brand, no founder on record, and nothing to lose by vanishing. So when you read “wind-down,” read “a company that wants to give your money back cleanly” — and recover accordingly.
The one number that varies by operator: the internal remittance window
There’s a single variable the table can’t pin down for you, because each operator set it slightly differently and may have adjusted it: how long the wind-down withdrawal flow stays open. The law permits operators to remit pre-existing balances during an orderly wind-down, but it does not force any particular operator to keep the door open forever. Dream11, notably, did not publicly state what happens to unclaimed funds after its window — which is precisely why “withdraw now” is the rule, not a suggestion. The practical implication: don’t assume the flow you see today will be there next quarter. If your balance is on a named operator and you can log in, the correct number of days to wait is zero. Run the withdrawal, capture the UTR, and confirm arrival. Everything else in this guide is for when that simple path fails.
The step-by-step wind-down withdrawal
This is the core procedure for Situations A and B — a major operator that still lets you log in. Follow it in order; each step removes one of the friction points that stalls recoveries. The whole thing is typically 20–30 minutes of your time plus normal payment-rail clearing.
Step 1 — Complete KYC first (this is the precondition, not an afterthought)
No legal Indian RMG operator can pay cash to an un-verified account, and a wind-down does not relax that — if anything it tightens it, because the operator wants a clean, auditable exit. Before you even tap “withdraw,” make sure you have:
- PAN verified in the app — mandatory, because the operator must report any TDS against your PAN.
- Bank account or UPI in your own name, with the account-holder name matching your PAN exactly. “RAHUL K” on the bank vs “Rahul Kumar” on the PAN is the single most common silent stall.
- Any address/ID proof the app requests.
If KYC is incomplete, finish it before withdrawing — an incomplete-KYC account in a wind-down can have its balance simply held, with no way to release it until you verify. On RummyCircle, withdrawal required PAN verified and matching KYC exactly; on Junglee Rummy, KYC was mandatory at first withdrawal or once cumulative deposits crossed ₹50,000. Those gates didn’t disappear in the wind-down — they became the release condition. If your KYC is stuck or rejected, the account-frozen-and-blocked fix walks the document-level repairs.
Step 2 — Read the withdrawable balance, not the wallet headline
Open the withdrawal screen and note the withdrawable figure. If it’s lower than your headline wallet, the gap is bonus or un-played-through deposit that won’t release. Don’t raise a complaint over that gap — it’s terms, not theft. Screenshot both numbers now; you’ll want the before/after later.
Step 3 — Run the withdrawal to a live account
Initiate the withdrawal of the full withdrawable amount to a bank account or UPI handle you currently control. A surprising number of “paid but never arrived” wind-down recoveries are payouts sent to a dead handle — a closed bank account or a UPI ID you stopped using. Use an account you can log into today. On Dream11, the path is Profile → My Balance → Withdraw from the Winnings column to your verified bank account; other operators are equivalent.
Step 4 — Expect the TDS cut (it’s not the app shrinking your money)
Your payout will likely arrive smaller than the balance because of 30% TDS on net winnings under Section 194BA, which has no minimum threshold and still applies to wind-down withdrawals. On a payout where your net winnings are ₹10,000, that’s a ₹3,000 deduction reported against your PAN, recoverable when you file your return. This is not a recovery failure — it’s tax, and the worked math is in the 3 Patti withdrawal tax section. If your shortfall matches a 30% cut on net winnings, stand down; that money is in your Form 26AS / AIS, not lost.
Step 5 — Capture the UTR and confirm arrival
The instant the withdrawal shows a UTR / reference number, screenshot it. Then check your bank. If it arrives (minus TDS), you’re done — done in the only sense that matters. If it shows “paid” but nothing lands, the UTR is now your single most important piece of evidence, and you move to the rail dispute path below.
Step 6 — Document the whole transaction
Save: the pre-withdrawal balance screen, the withdrawal request, the status screen, the UTR, the operator’s wind-down notice, and your bank statement showing (or not showing) the credit. A wind-down recovery that has to escalate lives and dies on this paper trail — an operator winding down has thin support, so your records do the arguing for you.
The step-by-step in one line: KYC → read the withdrawable figure → pay to a live account → expect 30% TDS → capture the UTR → document everything. Six steps, most people stall at step 1 (KYC) or step 3 (dead account). Clear those two and the typical major-operator recovery just works.
Case: the app was removed from the store but you still have login
This is Situation B, and it spooks people unnecessarily. The RMG apps were delisted from the Play Store and App Store as the law took effect — but delisting is not deletion. Your account, balance and KYC live on the operator’s servers, tied to your registered mobile number, not to the app file on your phone.
If the app is still installed, just open it and run the step-by-step withdrawal above. A store removal doesn’t touch an already-installed build’s login.
If you deleted the app or changed phones, do not assume the money is gone. Try, in order:
- The operator’s website. Most major operators kept a web login and a web withdrawal/recovery flow alive specifically for wind-down. Log in with your registered number and run the withdrawal there. This is the single most overlooked recovery route.
- A direct APK from the operator’s official site — only if the operator itself links it. Never sideload a “mod” or third-party-mirror APK to “recover” a balance; that’s a classic theft trap, and modified builds can get your account frozen.
- The operator’s grievance/support email, asking for the current wind-down withdrawal link for your registered number.
One safety rule overrides all of this: an app that was delisted in a legal wind-down is the opposite of an app that vanished with your money. The first still has a withdrawal door — you just have to find the web one. The second is Situation D. The tell is whether the operator’s official website still loads and recognises your number. If it does, you’re fine; keep going.
Store-removed reality in one line: delisted ≠ deleted. Your balance is on the server, keyed to your phone number. The recovery you’re missing is almost always the operator’s web withdrawal flow — try that before you panic.
The web-withdrawal route, step by step
Because the web route rescues so many “I deleted the app” cases, here’s the exact sequence for a major operator whose app is gone from your phone:
- Find the official domain. Use the operator’s name plus its known domain from an old confirmation email (deposit receipts and TDS certificates carry the real domain). Don’t trust a domain from a search ad or a forum — clones buy lookalike domains specifically to harvest logins during a wind-down.
- Log in with your registered mobile number and OTP. The account, balance and KYC are tied to that number, so a working OTP confirms you’re at the right place and your data is intact.
- Open the wallet/balance section and read the withdrawable figure. If the web build hides withdrawal behind a “winnings” tab, that’s where the recoverable pot lives.
- Initiate the withdrawal to your KYC-verified bank account, exactly as in the step-by-step flow. Capture the UTR.
- If the web flow is missing or broken, email the operator’s grievance officer from the official domain, quote your registered number, and ask for the current wind-down withdrawal link. Keep the reply — it’s evidence the door exists.
The reason this works: a licensed operator winding down has to keep some remittance channel alive to discharge its balances cleanly, and when the consumer app is delisted, that channel is usually the web. People who give up at “the app is gone” are most often one web login away from their money.
What if the operator paused withdrawals temporarily?
Some operators briefly paused withdrawals during the chaotic transition window — to re-tool the flow for a deposits-disabled world, or while they finalised the wind-down notice — and players read that pause as a permanent seizure. A temporary pause from a licensed operator is not theft; it’s operational. The tells that it’s a pause, not a vanishing: the website still loads, your login still works, support still replies, and there’s a dated notice explaining the pause and a restart date. If all of those are present, the right move is to document the pause (screenshot the notice), file a grievance to put your claim on record, and re-attempt withdrawal after the stated restart. If, instead, the site is dead and support is silent, treat it as Situation C or D and escalate accordingly.
Case: the app or login is gone — rebuild the claim from records
This is Situation C, the genuinely hard one: the app won’t open, the website is dead, or your login simply fails. You can no longer withdraw, so the job shifts to proving and claiming what you’re owed. This is slower and the outcome is less certain — be honest with yourself about that — but a documented claim beats a panicked one every time.
Step 1 — Rebuild the evidence from your own records
You don’t need the app to prove what you put in and what you’re owed. Pull together:
- Bank and UPI statements showing your deposits to the operator — these prove money flowed in, and the operator’s name or its payment aggregator usually appears in the narration.
- Any email from the operator: deposit confirmations, withdrawal confirmations, TDS certificates, KYC-completion emails, and crucially the wind-down notice if you received one.
- Screenshots you took before the app died — any balance screen, any withdrawal UTR.
- Your registered mobile number and the email on the account, which are how the operator (or a grievance body) identifies you.
A claim built from your bank statements is strong precisely because it’s independent of the operator’s records — you’re not relying on a dead app to confirm your own deposits.
Step 2 — File a written grievance with the operator
Even a winding-down licensed operator must run a grievance mechanism. Email its grievance officer (find the address on the operator’s official site or your old confirmation emails), state your registered number, the balance owed, your evidence, and request release to your verified account. Get a complaint reference. This timestamps your claim and starts the 30-day OGAI clock.
Step 3 — Escalate to the OGAI within 30 days
If the operator’s grievance outcome is unsatisfactory (or it’s silent), approach the OGAI within 30 days via the digital form on the Authority’s website or app. The OGAI endeavours to dispose of the appeal within 30 days. This is the regulator-level lever specifically created by the Rules 2026. For the framing and what the OGAI can and can’t do, see the PROGA explainer.
Step 4 — Run the consumer and rail levers in parallel
- For an operator refusing to return a verified, owed balance, that’s a deficiency in service: file with the National Consumer Helpline (1915) on ordinary contract/consumer principles — not on a non-existent PROGA refund right.
- For any specific debit that failed on the way out (you initiated a withdrawal, money moved, nothing arrived), pursue the bank/UPI/RBI rail dispute with the UTR — that path is rule-mandated and is the strongest in the whole guide. It’s detailed on the refund-dispute hub.
Step 5 — Be realistic about an unlicensed operator
If “gone” turns out to mean it was never a licensed Indian operator — an offshore clone, a vanished APK — your regulatory leverage is thin and recovery of in-app balance is not guaranteed. Pursue any rail loss through your bank and report fraud, but don’t keep feeding it. That’s Situation D, below.
No-login recovery in one line: you can’t withdraw, so you rebuild the claim from your own bank/email records, file a written operator grievance, escalate to the OGAI within 30 days, and run consumer (1915) + rail dispute in parallel. Slower, less certain — but a documented claim is the only thing that works once the app is dark.
Escalation when the operator stalls: the four doors
Whether you’re in Situation A with a payout that won’t arrive or Situation C rebuilding a claim, the escalation map is the same four doors. Use the one that matches your failure type, and climb in order — don’t jump to the OGAI on day one if a simple in-app withdrawal would have worked.
Door 1 — The operator’s grievance officer (always first)
Every licensed operator runs a grievance channel. File there in writing with your amount, registered number, evidence and a request for release. Get a complaint ID. A clear, dated grievance often unsticks a wind-down payout on its own, because it signals you know the process and creates a record the operator doesn’t want sitting unanswered. The contact-and-escalation playbook for this is on the refund-dispute hub.
Door 2 — The OGAI, within 30 days
If the operator’s grievance outcome doesn’t satisfy you, approach the OGAI within 30 days of that outcome, via the Authority’s digital form. The OGAI targets a 30-day disposal. This is the gaming-specific regulator door, and it’s the right one when the dispute is genuinely about the operator holding your balance.
Door 3 — The bank / RBI rail dispute (for any failed debit)
This is the strongest door, and it has nothing to do with gaming law. If any withdrawal was debited but not credited, raise a failed-transaction dispute with your bank using the UTR. Under RBI’s TAT circular DPSS.CO.PD No.629 (20 Sep 2019), a debited-but-not-credited UPI transaction must be auto-reversed by T+1, with ₹100/day compensation after that. You can also raise it through your UPI app’s “raise complaint” (which feeds NPCI UDIR) and, after 30 days of no resolution from the regulated entity, file free with the RBI Integrated Ombudsman at cms.rbi.org.in. The full screen-by-screen version is on the refund-dispute hub.
Why this door matters specifically in a wind-down. When an operator is shutting a product, its payout systems are running on reduced staff and re-tooled flows, so a higher-than-usual share of withdrawals fail on the rail — the request goes through, money leaves the operator’s side, and the credit to your bank times out or hits a dead handle. That’s not the gaming-law problem at all; it’s a payment-system failure, and the RBI rules treat it identically to any other failed UPI credit. The leverage is enormous because banks and payment aggregators are directly RBI-regulated and the auto-reversal is rule-mandated, not discretionary. So the moment a wind-down withdrawal shows “paid” but nothing lands, you stop arguing with a skeleton gaming-support desk and start a bank dispute with the UTR — a far stronger position. The catch: you can only use this door if you captured the UTR, which is why Day-0 documentation is non-negotiable.
Door 4 — Consumer forum / cybercrime
- National Consumer Helpline 1915 for an operator’s service deficiency (refusing an owed, clean balance) — on contract/consumer grounds.
- Cybercrime helpline 1930 and cybercrime.gov.in the instant fraud is involved — a fake “recovery” number, an OTP/PIN scam, a clone app, or a “deposit to unlock” demand. You can also flag suspicious payment entities on RBI’s Sachet portal.
The four doors in one line: operator grievance → OGAI (30 days) → bank/RBI rail dispute → consumer (1915)/cybercrime (1930). Match the door to the failure: an operator holding your balance is doors 1–2 and 4; a failed payment is door 3, the strongest of all because the RBI rules are automatic.
KYC completion: the precondition almost everyone underestimates
If there’s one thing that separates a recovered balance from a stuck one, it’s KYC. A wind-down does not waive it — the operator needs a verified identity to remit cash legally and to report TDS. Most stalled recoveries are, at root, a KYC problem wearing a different mask. Here’s the checklist that clears it.
- PAN must be verified and the name must match your bank/UPI exactly. This is the number-one silent stall. A single transposed letter parks the payout. Fix the bank name to match PAN, or the PAN record to match bank, before re-submitting — and use the same account for the recovery.
- Use an account in your own name. A payout to a third-party account will be rejected; the operator can only remit to the verified holder.
- Resolve a rejected KYC, don’t resubmit the same blurry document. If the app says “verification failed,” the fix is a clean, legible document that matches your details — not the same file again. The account-frozen-and-blocked fix and 3 Patti withdrawal KYC notes cover the document-level repairs.
- If the account is “frozen for investigation,” demand a written reason and a timeline through the grievance officer. A wind-down doesn’t entitle the operator to hold a verified balance indefinitely without explanation.
The reason KYC is the precondition and not a formality: in a wind-down, the operator’s whole goal is a clean, auditable exit. An un-verified or mismatched account is the one thing that forces it to hold your money — not out of malice, but because remitting to an unverified identity is exactly what the new law makes risky for it. Clear KYC and you remove the operator’s only legitimate reason to sit on your balance.
KYC in one line: it’s the release condition, not paperwork. PAN matching the bank name exactly, an account in your own name, a clean document for any rejection. Most “the closed app won’t pay me” cases are a name mismatch — fix that first, before you escalate anything.
The TDS already deducted: don’t mistake tax for a stolen balance
A large slice of “I recovered less than my balance” complaints are tax, correctly deducted, and disputing it wastes the days you’d need for a real problem. Wind-down withdrawals are not exempt from TDS.
Since 1 April 2023, every legal Indian online-gaming operator must deduct 30% TDS on net winnings under Section 194BA, with no minimum threshold. “Net winnings” is roughly (withdrawals + closing balance) − (deposits + opening balance) over the financial year, excluding non-withdrawable bonuses — the formula and worked examples are on the 3 Patti withdrawal tax section. Two wind-down-specific points:
- Your recovery payout will arrive net of TDS. If your net winnings inside the recovered amount are ₹10,000, expect a ₹3,000 cut, reported against your PAN in Form 26AS / AIS and creditable when you file. That’s not the operator shorting you — it’s the same tax that always applied.
- A year-end TDS deduction may already have hit your balance. Section 194BA also taxes any net winnings still sitting in your wallet at financial-year end. So a balance that looks smaller than you remember may have had a year-end 194BA cut before the wind-down — again, tax, not theft.
If your recovery shortfall matches a 30% cut on net winnings, there is nothing to dispute — the money is in your tax records, not gone. Save the operator’s TDS certificate if it issues one during wind-down; it’s your proof for filing. The pure-deposit case is different: a returned deposit is your own money coming back and is not “net winnings,” so it shouldn’t be taxed — if a deposit-only return came back 30% lighter, that is worth raising with the grievance officer.
TDS in one line: a recovery payout 30% lighter on net winnings is tax (Section 194BA, no threshold), sitting in your AIS and reclaimable at filing — not a theft. A returned deposit shouldn’t be taxed, so only that shortfall is worth a dispute.
How to document a recovery claim (the paper trail that actually wins)
An operator winding down has skeleton support and little incentive to chase paperwork for you. So your documentation has to do the arguing. Build the file below from Day 0; it’s the difference between a 3-day recovery and a month of silence.
Capture, in this order:
- The balance screen — your withdrawable figure before you act, date-stamped.
- Your deposit history — from the app and corroborated by your bank/UPI statements. This proves money flowed in even if the app later dies.
- The withdrawal request and status screen — amount, timestamp, status text.
- The UTR / reference — the single thread tying a debit to a (missing) credit. No UTR, no rail trace.
- The operator’s wind-down notice — the email or in-app banner stating withdrawals remain open. This is your contractual hook.
- Any TDS certificate — for your tax records and to explain a “smaller” payout.
- Every grievance reference — operator complaint ID, OGAI acknowledgement, bank dispute number.
Then write the claim as facts, not feelings. A recovery email that says “I am owed ₹X, here is my registered number, here is my deposit history, here is the wind-down notice promising withdrawals, please remit to my verified account [Y], complaint ID [Z]” moves faster than three paragraphs of anger. The operator’s grievance desk, the OGAI and a consumer forum all respond to amount + evidence + identity + a specific ask — and to nothing else.
One discipline that pays off: capture the UTR the moment it appears. Once a wind-down app stops updating or a “failed” transaction ages out of the quick view, digging the UTR back out is far harder, and your bank cannot trace a credit you can’t name.
Documentation in one line: balance screen + deposit history (with bank statements) + withdrawal status + UTR + wind-down notice + TDS cert + every grievance ID. Built on Day 0, it lets your paper trail argue the case for you — which is the only thing that works against a skeleton-staffed wind-down.
Is it a real wind-down or a vanishing act? Red flags
Most “closed app” cases are legitimate wind-downs with a withdrawal door. Some are Situation D — unlicensed operators using the chaos as cover, or outright scams targeting panicked players. Use these flags to decide how hard to fight versus how fast to cut losses.
- “Deposit ₹X to unlock your withdrawal.” No legal operator requires a deposit to withdraw, and post-PROGA a new deposit into a money game is illegal. This is the single clearest theft pattern in the whole wind-down period — stop, document, report to 1930.
- A “recovery agent” or “customer care number” from a random website, YouTube comment or WhatsApp group. These are overwhelmingly scams harvesting your OTP and UPI PIN. Real operators route support in-app or via official email; many have no public phone helpline at all. Never call back an unverified number, never share an OTP/PIN.
- No PAN/KYC was ever required. A legal operator must do KYC. If yours never did, you were likely not on a regulated platform, and your recovery leverage shrinks accordingly.
- A sideloaded “mod” / “unlimited chips” APK. Modified builds void the terms and can freeze the account; the balance may already be forfeit by the app’s own rules. A “recovery APK” you’re asked to sideload is a fresh trap.
- The official website is dead and the operator was never a named, licensed company. A licensed operator in wind-down keeps a web withdrawal path; a clone that simply vanished is the worse problem, and in-app balance recovery there is not guaranteed.
If two or more of these are true, the realistic verdict is harsh: pursue any rail loss through the bank/RBI route and file the cybercrime report, but lower your expectation of recovering balance held inside an unlicensed operator — and feed it nothing more. The deeper red-flag taxonomy and the rail-recovery steps are on the refund-dispute hub.
Red flags in one line: a deposit demand, an unverified “recovery number,” no-KYC history, a mod APK, or a vanished unlicensed brand all mean you’re likely in Situation D — chase the rail loss and report fraud, but don’t expect to recover money trapped inside an operator outside Indian regulatory reach.
How much leverage you actually have, by operator type
Recovery isn’t a single difficulty level — it scales with who held your money. Knowing your tier sets honest expectations and stops you wasting weeks on a fight you can’t win, or under-fighting one you can. There are roughly four tiers.
Tier 1 — a licensed, named major operator (Dream11, MPL, RummyCircle, My11Circle, Junglee, PokerBaazi, WinZO, Zupee). Your leverage is high. The operator is RBI/regulator-reachable, brand-sensitive, and wants a clean exit. You have the operator’s flow, the OGAI ladder, consumer law, and the rail rules all available. The realistic outcome for a clean-KYC balance here is full recovery minus TDS. Most readers are in this tier and should simply be withdrawing.
Tier 2 — a smaller but still-identifiable Indian RMG operator. Your leverage is moderate. The operator exists and is reachable, but support may be thin and the wind-down notice vaguer. You lean harder on the written grievance and the OGAI rung, and you watch the remittance window closely. Recovery is likely but slower.
Tier 3 — an informal-brand card app (a Teen Patti Gold/Master skin of unknown operator). Your leverage is low and uncertain. “The app” is one of many skins, the operator behind your specific build may be hard to identify, and there may be no clean wind-down notice at all. Pursue any rail loss with the UTR through your bank — that path is operator-independent — but lower your expectation of recovering balance held inside the app itself, and judge purely by the exact build you installed.
Tier 4 — an offshore site, a clone, or a mod/“unlimited chips” APK. Your leverage is minimal. The operator is likely outside Indian regulatory reach, has no brand to protect, and may be a scam. Your only realistic recovery is a rail loss (a failed debit) pursued through your bank, plus a fraud report to 1930. Treat any in-app balance as probably unrecoverable, and never deposit “to unlock” it.
The decision this drives: invest your effort in proportion to your tier. A Tier-1 balance deserves a full, patient escalation because it’s almost certainly recoverable. A Tier-4 balance deserves a bank dispute and a fraud report, then a clean break — pouring more time (or worse, more deposits) into it is the mistake that turns a small loss into a larger one.
Leverage in one line: named licensed operator = high leverage, recover fully (minus TDS); unknown card skin = low; offshore/clone/mod = minimal, chase only the rail loss and report fraud. Match your effort to your tier instead of fighting every case the same way.
The mistakes that quietly destroy a recovery
Some moves don’t just fail to help — they actively make recovery harder or impossible. These are the ones that turn a recoverable balance into a lost one, in rough order of how often they sink a case.
- Depositing more “to unlock” a withdrawal. This never works, it’s the clearest theft pattern in the wind-down period, and post-PROGA a new deposit into a money game is illegal. You lose the deposit and don’t free the balance. If anyone or any screen asks for a deposit to release a payout, that’s your signal it’s a scam.
- Spinning up a “new” account to escape a block. A duplicate account on the same device, IP or payment instrument deepens an anti-fraud flag and can get both accounts frozen. The balance is tied to your original registered number — work that account through grievance, never around it.
- Withdrawing to a dead handle. A payout to a closed bank account or an abandoned UPI ID “succeeds” on the operator’s side and never reaches you, then takes a rail dispute to claw back. Always recover to an account you can log into today.
- Sideloading a “recovery” or “mod” APK. A modified build voids the terms, can freeze the account, and a “recovery APK” from a mirror is a fresh trap. The only safe app is the official one (or the official web flow).
- Calling an unverified “customer care” number. Real operators route support in-app or by official email; the numbers on random sites and YouTube comments exist to phish your OTP and UPI PIN. One shared OTP can drain accounts the stuck balance never touched.
- Waiting past the operator’s remittance window. The slowest-burning mistake: the door is open now and may not be later. “I’ll do it next month” is how recoverable balances become unclaimed ones — especially where the operator never said what happens to unclaimed funds.
- Disputing TDS as if it were theft. Chasing a legitimate 30% Section 194BA deduction through grievance burns the days you’d need for a real problem, and there’s nothing to win — the money is in your AIS, reclaimable at filing.
- Escalating with no UTR and no records. A grievance officer, the OGAI, a bank and a consumer forum all respond to amount + evidence + identity. Walking in with a feeling and no paper trail gets you nowhere — which is why Day-0 documentation is the whole game.
Avoid these eight and you’ve removed the self-inflicted failures, leaving only the operator’s own pace to manage — which the escalation ladder is built to handle. Put plainly: the law and the operator’s wind-down already point your money back toward you, so most of the work is simply not getting in your own way while the process runs.
Mistakes in one line: don’t deposit to unlock, don’t open a second account, don’t pay to a dead handle, don’t sideload a “recovery” APK, don’t call unverified numbers, don’t wait, don’t dispute TDS, and don’t escalate empty-handed. Each one converts a recoverable balance into a lost cause.
A realistic recovery timeline
So you can set expectations correctly, here’s what “normal” looks like across the four situations. Timings marked with a rule are RBI/regulatory-mandated; the rest are typical wind-down behaviour and should be read as estimates, not promises.
| Stage | Situation A/B (login works) | Situation C (no login) | The clock that governs it |
|---|---|---|---|
| Complete/repair KYC | Same day to 48 hours | N/A (rebuild from records) | Operator verification |
| Initiate withdrawal | Minutes once KYC is clean | N/A | Operator wind-down flow |
| Payout clears to bank (UPI) | Seconds to 1–3 working days | N/A | App SLA / payment rail |
| Failed debit auto-reversal | By T+1, then ₹100/day | Same, for any failed debit | RBI TAT circular |
| Operator grievance response | A few days to ~2 weeks | A few days to ~2 weeks | Operator grievance SLA |
| OGAI appeal | N/A (usually unnecessary) | Approach within 30 days; disposal target 30 days | PROG Rules 2026 |
| RBI Ombudsman eligibility | After 30 days unresolved | After 30 days unresolved | RB-IOS 2021 |
Read that as a clock: in Situation A, a clean-KYC recovery is often same-week and the only “wait” is normal rail timing. In Situation C, you’re looking at weeks, because grievance and regulator timelines stack. The single biggest lever to stay in the fast lane is acting before the operator’s own wind-down window closes — which is why every section here repeats it.
Where to get real, official help
There is no “faster app” and no shortcut — and after PROGA, moving to another online money-gaming service isn’t a legal option in India anyway. What recovers money is the official chain, used in order with your paper trail intact:
- The operator’s grievance officer first — your contractual route to the wind-down withdrawal/recovery.
- The OGAI within 30 days of an unsatisfactory operator outcome — the gaming regulator door (cms framing on the PROGA explainer).
- Your bank / NPCI / RBI Ombudsman for any failed debit — the strongest, rule-mandated lever (the refund-dispute hub walks it).
- National Consumer Helpline 1915 for an operator’s service deficiency, and cybercrime 1930 / cybercrime.gov.in plus the RBI Sachet portal the instant fraud appears.
Final verdict. A balance inside a licensed major operator in a real wind-down is recoverable — finish KYC, withdraw to a live account, expect the 30% TDS, and you’re usually done. A balance inside an unlicensed or vanished operator is the hard kind: chase any rail loss and report fraud, but never deposit “to unlock” — post-PROGA that’s both throwing good money after bad and illegal. And drop the “180-day statutory refund right” entirely — it was dropped from the final Rules; your real levers are the operator’s flow, consumer/RBI law, and the OGAI ladder.
Related fixes (go deeper on your exact case)
- The recovery and refund-dispute hub → refund-dispute recovery — the full escalation chain, rail disputes, and chargeback mechanics this page links up to.
- Account frozen / KYC blocked → account frozen or blocked RMG fix — the document-level KYC repairs that unstick a held balance.
- A specific Junglee Rummy balance → Junglee Rummy withdrawal fix — the operator-specific wind-down withdrawal walkthrough.
- The withdrawal mechanics and tax math → 3 Patti withdrawal hub — gates, pots, TDS worked examples, and the rail-failure protections.
- The law behind the shutdown → Dream11/MPL shutdown refund explainer and the PROGA Act explained.
FAQ
1. Can I really recover money from a gaming app that shut down? Usually yes, if it was a licensed major operator. Dream11, MPL, RummyCircle, My11Circle, Junglee Rummy and PokerBaazi all kept withdrawals open while disabling deposits, so your existing balance is recoverable through their wind-down flow. Finish KYC, withdraw to a verified account, and expect a 30% TDS cut on net winnings. Recovery is far less certain only if the app was an unlicensed clone or a “mod” build.
2. Do I have a 180-day legal right to a refund from the shut-down app? No. A draft platform-refund obligation was dropped from the final notified PROG Rules 2026. There is no statutory 180-day refund window you can enforce. What exists is permission for operators to remit pre-existing balances during wind-down — a reason to withdraw early (the operator’s window may close), not a personal deadline. Your real levers are the operator’s flow, consumer/RBI law, and the OGAI ladder.
3. My rummy app closed my money — is it gone? Almost never. When the games stopped, your withdrawable balance was parked in place, not seized — the operator left a withdrawal door open precisely so it could remit cleanly under the new law. The usual reasons it feels gone are an incomplete KYC, a name mismatch, or a bonus pot that was never withdrawable. Open the app, read the withdrawable figure, and run the withdrawal.
4. How do I withdraw my Dream11 balance after the shutdown? Open the app, go to Profile → My Balance → Withdraw from the Winnings column to a KYC-verified bank account, per the post-shutdown withdrawal guidance. Your PAN and bank must be verified first. Dream11 didn’t clearly state what happens to unclaimed funds, so withdraw immediately rather than waiting.
5. The app was removed from the Play Store — can I still get my money? Yes. Delisting is not deletion — your balance lives on the operator’s server, keyed to your registered mobile number, not the app file. If the app is still installed, just withdraw. If you deleted it, log in via the operator’s website and use the web withdrawal flow. Never sideload a “recovery” APK from a third-party mirror.
6. Why did my recovered payout arrive smaller than my balance? Almost always TDS: 30% on net winnings under Section 194BA, with no threshold, still applies to wind-down withdrawals. On ₹10,000 of net winnings inside your balance, that’s a ₹3,000 cut, reported against your PAN in Form 26AS / AIS and reclaimable at filing. A returned deposit shouldn’t be taxed — so only a deposit-only shortfall is worth disputing.
7. Is KYC really required to recover a balance from a closed app? Yes — KYC is the release condition, not a formality. No legal operator can remit cash to an unverified account, and a wind-down tightens that, not loosens it. The most common silent stall is a PAN name that doesn’t match your bank/UPI name exactly. Fix the mismatch, use an account in your own name, and submit a clean document for any rejection. See the account-frozen fix.
8. The operator is ignoring my recovery request — what do I do? Climb four doors in order: the operator’s grievance officer (get a complaint ID), then the OGAI within 30 days of an unsatisfactory outcome, then your bank/RBI dispute for any failed debit (the strongest lever), and the National Consumer Helpline 1915 in parallel for service deficiency. The full chain is on the refund-dispute hub.
9. What is the OGAI and how does the grievance ladder work? The Online Gaming Authority of India is the regulator created by the Rules 2026, an attached office of MeitY. The ladder is: operator grievance officer → OGAI within 30 days → Secretary, MeitY. The intermediate appellate committee from the draft was removed. The OGAI targets a 30-day disposal, so don’t let an operator stall you past your 30-day window to appeal.
10. My withdrawal showed “paid” but nothing reached my bank — now what? Get the UTR from the app and ask your bank to trace it. If there’s no credit against that UTR, you have proof the money didn’t arrive, and this becomes a rail dispute: under RBI’s TAT circular, a debited-but-not-credited UPI transaction is auto-reversed by T+1, with ₹100/day after. Raise it via your UPI app (it feeds NPCI UDIR) and your bank. Details on the refund-dispute hub.
11. Can I recover my balance if the app login is completely gone? It’s harder, but you rebuild the claim from your own bank/UPI statements (proving deposits), any emails from the operator, and pre-death screenshots. File a written grievance with the operator, escalate to the OGAI within 30 days, and run consumer (1915) + rail dispute in parallel. A claim built from your bank records is strong because it doesn’t depend on the dead app.
12. Is there a deadline to withdraw my balance from a wind-down app? There’s no statutory personal deadline — but operators have an internal wind-down window to remit funds, and that window can close. So the practical answer is withdraw as early as possible: Dream11, for one, didn’t state what happens to unclaimed funds. Treat “withdraw now” as the rule even though no law gives you a fixed personal clock.
13. Someone offered to “recover” my stuck balance for a fee — is that safe? No. “Recovery agents,” unverified “customer care numbers,” and anyone asking you to deposit to unlock a withdrawal are overwhelmingly scams harvesting your OTP and UPI PIN — and a new deposit into a money game is now illegal. Real operators route support in-app or by official email. Report these to cybercrime 1930 and cybercrime.gov.in.
14. Can I still withdraw from RummyCircle, Junglee Rummy or PokerBaazi? Their cash games are discontinued, but all three kept withdrawals open for balance recovery — PokerBaazi stated user funds “remain completely safe and accessible,” and RummyCircle/My11Circle players were assured they could withdraw any wallet balance. Complete KYC (PAN matching exactly), follow the in-app flow, expect 30% TDS, and never re-deposit. The Junglee-specific walkthrough is on its withdrawal fix.
15. What if it turns out the app was never a legal operator? Then the wind-down protections don’t apply and recovery of in-app balance is not guaranteed. Pursue any payment-rail loss (a failed debit) through your bank/RBI with the UTR, and report fraud to 1930 and the RBI Sachet portal. But money held inside an unlicensed or offshore operator that ignores you may sit outside Indian regulatory reach — which is why a deposit demand or a no-KYC history is such a serious red flag.
Sources & method. Recovery steps, wind-down statuses, the dropped 180-day refund point, the OGAI grievance ladder, taxes and the rail protections on this page are built from primary and named secondary sources — not personal recovery tests. Key references: the Promotion and Regulation of Online Gaming Act, 2025 and its Rules effective 1 May 2026; the analysis of the dropped draft refund rule and the operator → OGAI (30-day) grievance ladder in Mondaq’s “India’s Online Gaming Reset: Decoding PROGA and the 2026 Rules”; operator wind-down withdrawal statements reported by AngelOne, ThePrint and Inc42; the Dream11 post-shutdown withdrawal path via Possible11; 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; CBDT Section 194BA TDS at incometaxindia.gov.in; cybercrime reporting at cybercrime.gov.in / helpline 1930; National Consumer Helpline 1915. This page is the practical recovery playbook, not the law explainer — for the legal mechanics see the Dream11/MPL shutdown-refund page and the PROGA Act explained. It is information, not legal or financial advice — verify each step against your operator’s current wind-down notice and your bank’s UPI dispute policy.