Account Frozen or Blocked on an RMG App: Why and How to Unblock It

The 40-second answer

A frozen RMG account is a hold placed by the operator (risk review), a bank or aggregator (settlement hold or cyber-fraud lien), or a law-enforcement agency (a BNSS 106/107 or PMLA 17 order). The cause sets the duration — from 24 hours for a win-spike review to 180 days for a PMLA attachment. Find out who froze it and why first, then use the matching hub: KYC and account recovery.

Editor’s verdict, up front. Almost every “my account is frozen, the app stole my money” message is one of six boring, distinguishable things — not a single conspiracy. Five of the six are recoverable if you act in the right order: an operator risk hold clears with a written reason and clean KYC; a payment-aggregator settlement hold clears on its own timer; a chargeback hold reverses when you withdraw the dispute; a bank cyber-fraud lien now has a 90-day SOP and a formal grievance route; and even a court/LEA freeze under BNSS or PMLA has a defined adjudication clock and an appeal. The sixth — a balance held inside an unlicensed or wound-down operator — is the hard one. The whole game is telling them apart fast, because each one has a different door and a different deadline. Pour no more deposits into a frozen account while you work this out; post-PROGA that deposit is also illegal.

2026 reality you must read first. Two things changed how a freeze works in India. First, the Promotion and Regulation of Online Gaming Act, 2025 (PROGA) — Presidential assent 22 August 2025, Rules in force 1 May 2026 — banned all online money games, so a large share of “frozen account” searches are now really “a wound-down operator still holds my balance.” Second, the Bharatiya Nagarik Suraksha Sanhita (BNSS) replaced the CrPC on 1 July 2024, renumbering the police-seizure power from old Section 102 CrPC to Section 106 BNSS, with Section 107 BNSS now governing magistrate-ordered attachment of crime proceeds. If your bank account is frozen because money flowed through a gaming app the police are probing, that’s the law you’re under — and the MHA / I4C account-freeze SOP now limits the freeze to the disputed amount, not your whole balance. This page reads two ways throughout — an in-app freeze (operator side) and a bank/LEA freeze (rail and law side) — and flags which is which.

What “frozen” and “blocked” actually mean (they are not the same thing)

People use “frozen,” “blocked,” “suspended,” “banned,” and “on hold” as if they were one state. They are not, and the difference decides your fix. Be precise about the object before you escalate anything.

• Login blocked / account suspended. You can’t log in at all, or you log in but every action is greyed out. This is an operator action against your access. Your balance may be untouched behind it.
• Withdrawal frozen, login fine. You can play and deposit, but the cash-out button is disabled or every withdrawal sits in “review.” This is a payout hold, usually a risk or KYC gate — closer to a stuck withdrawal than a true freeze. The withdrawal-stuck fix covers the pure-payout version.
• Balance frozen / funds on hold. Your money is visible but un-withdrawable and sometimes un-playable. This is the classic “frozen balance,” and it can be operator-side or rail-side.
• Bank account frozen / lien-marked. Your bank account — not the app — has a debit freeze or a lien on a specific amount. This is almost always a cyber-fraud complaint or an LEA order, and it is a different legal universe from an in-app freeze.
• Account permanently closed / forfeited. The operator has terminated the account under its terms (multi-accounting, fraud, mod-APK use) and may claim the balance is forfeited. This is the worst operator-side outcome and the hardest to reverse.

The single most useful first question: is the freeze inside the app, or on my bank account? An in-app freeze is a contract and operator-grievance problem. A bank-account freeze is a law-enforcement and RBI-grievance problem. They share almost no steps. The diagnostic below splits on exactly that line.

Why the distinction is leverage, not pedantry

A player whose withdrawals are frozen on a licensed operator while login works is in a strong position — that’s a payout review with a written-reason right and a consumer-grievance route. A player whose bank account is lien-marked over a ₹5,000 disputed transaction is in a different fight entirely, but a winnable one: the MHA SOP now caps the lien at the disputed sum and gives a 15-day officer-response clock. And a player whose balance is held inside a wound-down operator is in the hard case — recoverable only through the operator’s recovery flow and the payment rail. Naming your state correctly is the difference between escalating to the right authority on day three and shouting at the wrong one for a month.

Run the freeze diagnostic first

Before reading the long version, sort your case into one of six. Each links to the section that fixes it. The durations are estimates built from the published rules and operator terms cited on this page — not from anyone’s personal account tests.

If none fits cleanly, you may be in two at once (a win-spike review that escalated into an STR, say). Read the closest match first, then the second. The rest of this page is the manual version of that table — long on purpose, because this is the freeze hub for the KYC cluster and every freeze type you might hit lives here.

The six freeze causes, in detail — with the unblock path for each

Cause 1 — The AML / win-spike risk review

This is the most common legitimate operator freeze, and the most reversible. A sudden large win, a first big withdrawal, an unusual deposit-then-immediate-withdraw pattern, or a velocity spike trips the operator’s anti-money-laundering monitoring, and the payout (sometimes the whole account) is parked for manual review.

This isn’t the operator inventing an excuse. Under Section 2(1)(wa) of the PMLA, online gaming operators are designated Reporting Entities — the same status as a bank. That obliges them to monitor for suspicious patterns and to file a Suspicious Transaction Report (STR) with FIU-IND within 7 working days of detecting the activity, regardless of amount. They must also file a Cash Transaction Report when deposits or withdrawals hit ₹10 lakh or more in a month, and retain transaction records for 5 years under the FIU-IND Guidelines, 2023. The triggers their software watches for include multiple accounts on the same IP or device and high-value transactions that don’t match your known profile — exactly the patterns a lucky-streak player produces by accident.

So a win-spike freeze is the AML system doing its job. The good news: a routine review on a clean account clears in hours to a couple of days, and even if it escalates to an STR, the report is filed about you — it does not by itself freeze your money for the 7-day window; the operator’s own hold timer governs that.

The unblock path for Cause 1:

1. Don’t panic-spam, document. Screenshot the freeze message, the balance, and the win that triggered it, date-stamped.
2. Demand a written reason and a timeline. Raise an in-app ticket asking the operator to confirm in writing whether this is a routine review, what document or step (if any) it needs from you, and the expected resolution date. Get a ticket ID.
3. Complete or refresh KYC cleanly. A win-spike review almost always re-checks identity. Make sure your PAN, your bank/UPI name, and your KYC name match exactly — a mismatch turns a 1-day review into a 2-week one. The KYC-rejected fix has the document-level corrections.
4. Wait the stated window before escalating. If the operator gave 48–72 hours, let it run. Escalate to the grievance officer only past the stated window or past 7 working days with no reply.

Cause-1 tell: the freeze wording mentions “verification,” “review,” “security,” or “compliance,” login still works, and only withdrawals are blocked. That’s a review, not a ban — the most winnable freeze on this page.

Cause 2 — The multi-account / collusion flag

This is the operator freeze most likely to end in forfeiture, and the one players most often cause themselves without realising. The anti-fraud system sees the same device fingerprint, IP, payment instrument, or KYC identity across two or more accounts and freezes the lot pending investigation.

Operator terms are uniformly harsh here. Across the industry, once multiple linked accounts are detected, all associated accounts are typically suspended or permanently closed, and — the painful part — winnings earned through the linked accounts are commonly voided or confiscated under the terms, even legitimate winnings on one account. In multiplayer formats like online poker or Teen Patti tables, multi-accounting also reads as collusion — one person playing several hands at one table — which operators treat as serious fraud, not a technicality. Some operators also share fraud data and blacklist players across platforms.

The cruel edge case: you can trip this flag innocently. A shared family device, a public Wi-Fi IP, a sibling who also plays, or reinstalling on a new phone that still carries an old fingerprint can all read as “multi-account” to a blunt risk engine. That’s why the written-reason step matters so much — a genuine false positive is reversible; an admitted second account usually isn’t.

The unblock path for Cause 2:

1. Stop creating accounts immediately. Spinning up a “fresh” account to escape the flag is the single worst move — it confirms the pattern and deepens the forfeiture case. This is the one rule with no exceptions.
2. Contact support from your registered number, once, in writing. Ask for the specific reason the account was flagged and which accounts it believes are linked. Get it in writing.
3. If it’s a false positive, prove the single-identity case. State plainly that you operate one account, explain the shared-device/IP situation if that’s the cause, and offer to re-verify KYC against the one identity. A clean, single PAN tied to one account is your strongest evidence.
4. If a second account genuinely exists, expect limited recourse. The terms you accepted likely permit forfeiture. Your realistic ask shrinks to recovering your own deposits (not winnings) on the primary account, via the operator grievance officer, then the consumer-helpline route.

Cause-2 tell: the freeze wording mentions “multiple accounts,” “duplicate,” “device,” “same details,” or “terms violation,” and often hits login, not just withdrawals. This is the freeze where forfeiture is real — argue false-positive hard and early, or accept the deposit-only recovery.

Cause 3 — The chargeback / payment-dispute freeze

A specific, self-inflicted freeze worth isolating because the fix is in your own hands. If you (or your bank) raised a chargeback or payment dispute on a deposit — say a UPI/card payment you didn’t recognise, or one you disputed to claw back a loss — the operator’s payment processor flags the account and freezes the balance and often the login while the dispute runs.

From the operator’s side this is rational self-defence: a chargeback means a deposit it credited as chips is being reversed at the bank, so it freezes the account to stop you withdrawing money the deposit no longer backs. Some operators treat a chargeback as a terms breach in itself and may close the account.

The unblock path for Cause 3:

1. Identify whether a dispute exists. Check whether you, or your bank on your behalf, raised a chargeback/dispute on any deposit. A “deposit reversed” or “payment under dispute” note in the app is the tell.
2. If the dispute was a mistake, withdraw it. Contact your bank/card issuer and close the chargeback. The operator generally cannot unfreeze while an active reversal is pending against it.
3. If the dispute was genuine fraud on your card, let it run and don’t expect to play. A legitimately disputed deposit isn’t yours to game with; recovering the disputed money goes through the bank, not the operator. The general chargeback and dispute logic is in the withdrawal hub.
4. Never chargeback a deposit just to recover a gambling loss. It works once, freezes the account, and can get you blacklisted — and post-PROGA the underlying deposit was illegal anyway.

Cause-3 tell: the freeze followed a deposit reversal or a “payment dispute” note, not a win. The lever is your bank dispute, not the operator’s goodwill.

Cause 4 — The payment-aggregator settlement / escrow hold

Not every “frozen payout” is the operator. Sometimes the money has left the operator and is sitting in the payment aggregator’s escrow waiting to settle to you. This looks like a freeze — “processing,” no movement — but it’s a rail-timing state with a hard RBI deadline, which makes it one of the easier ones.

Under the RBI Payment Aggregator framework, an aggregator must hold collected funds in an escrow account with a scheduled commercial bank, keep merchant funds separate from its own, and settle to the merchant within a maximum of T+1 (with the exact timeline set by a fair, transparent contract). The RBI’s Payment Aggregators Directions, 2025 (15 September 2025) tightened this and moved the industry from the older nodal-account model (where settlement could take up to 3 days) to the stricter escrow regime. The practical upshot: a payout genuinely on the rail should clear by T+1, and a “frozen” payout still inside escrow past that window is escalatable as a settlement deficiency.

There’s a freeze-specific twist for gaming: payment processors increasingly receive Law Enforcement Agency (LEA) hold requests, and a gateway that gets an LEA hold on a flagged transaction will freeze that settlement rather than pass it to you. So a settlement that stalls past T+1 can mean either a routine batch delay or an LEA hold riding on the rail — and the second one shades into Cause 5.

The unblock path for Cause 4:

1. Get the UTR/reference and check it against T+1. If it’s inside T+1, it’s normal rail timing — wait. The withdrawal-stuck page covers the pending-state countdown.
2. Past T+1, treat it as a failed/held settlement. Raise the operator ticket and a bank/UPI dispute with the UTR — the rail protections (auto-reversal, ₹100/day on system failures) apply, as detailed in the withdrawal hub.
3. If support says “the payment is on hold by the bank/authority,” you’ve likely crossed into an LEA hold (Cause 5) — switch to that section.

Cause-4 tell: login and balance are fine, only a specific outgoing payout is stuck at “processing,” and it’s within or just past T+1. This is the rail, not a ban.

Cause 5 — The bank cyber-fraud freeze (Section 106/107 BNSS)

This is the freeze that scares people most and is most misunderstood. Your bank account — not the app — gets a debit freeze or a lien on a specific amount, often with no warning, because money you received (or sent) is tied to a cyber-fraud complaint filed on the National Cybercrime Reporting Portal (NCRP). RMG players hit this two ways: a deposit you received from someone whose money was later disputed, or your own account flagged because a counterparty was a fraud “mule.”

Here’s the law, corrected for 2024–26. The police power to seize property — and the Supreme Court has held a bank account is “property” — moved from old Section 102 CrPC to Section 106 BNSS when the BNSS replaced the CrPC on 1 July 2024. But courts have drawn a sharp line in 2024–26: Section 106 lets police seize for evidence but does not by itself authorise a debit-freeze or attachment of a bank account — that requires Section 107 BNSS and a competent magistrate’s order, following procedural safeguards. The Kerala High Court and Madras High Court have held that a freeze must be proportionate and confined to the specific amount in the police requisition; freezing an entire account without quantifying the amount is “manifestly arbitrary” and violates Article 19(1)(g) and Article 21.

The administrative layer reinforces this. The MHA / I4C account-freeze SOP changed the old practice where a ₹10 disputed transaction could freeze lakhs. Now the bank places a lien limited to the disputed amount — if your balance is ₹1,00,000 and the suspicious transaction is ₹5,000, only ₹5,000 is blocked. The SOP also sets timelines: under Para 10.1, the Investigating Officer must respond within 15 days, and holds should be removed after 90 days if no lawful continuation direction arrives. For small-value cases, refunds where the disputed amount is below ₹50,000 can be processed without a court order. And the I4C now runs a Grievance Redressal Mechanism (GRM) module where a District-rank officer is the first redressal point, with auto-escalation if no response in 15 days.

The unblock path for Cause 5:

1. Find out which police station and complaint froze it. Ask your bank for the freezing-authority details — the cyber police station, the complaint/NCRP reference, and the lien amount. The bank holds this; you’re entitled to it.
2. Check proportionality. If the entire account is frozen over a small disputed amount, that likely violates the SOP and the proportionality rulings — raise it. The lien should be the disputed sum only.
3. Approach the Investigating Officer for a No-Objection Certificate (NOC). Defreezing happens when the IO issues an NOC after finding you not at fault, which is forwarded to your branch. If you can show the credit was a legitimate gaming withdrawal, that’s your case.
4. Use the I4C GRM module if the officer is unresponsive. File on the GRM; the 15-day clock and auto-escalation are your lever when the local cell goes silent.
5. For a disproportionate or stale freeze, the writ route exists. Courts have repeatedly unfrozen accounts where police exceeded Section 106 or held the account past purpose — a Delhi court de-froze accounts in a USD 40 million cyber-fraud case for exactly this.

Cause-5 tell: the freeze is on your bank account, not the app; the bank cites a “lien,” “cyber complaint,” or “LEA request.” The 90-day SOP timer and the proportionality rule are your two strongest levers.

Cause 6 — The PMLA / ED freeze, and the PROGA wind-down balance

Two different “investigation” situations get conflated here. Separate them, because one is a heavy legal freeze and the other isn’t really a freeze at all.

The PMLA / ED freeze. If your account is caught in an Enforcement Directorate money-laundering probe — which has targeted real-money gaming operators directly — the freeze runs under the PMLA, not the BNSS. The ED freezes accounts using Section 17(1A) of the PMLA when physical seizure is impractical, to stop dissipation of suspected proceeds of crime. The procedural clock is defined: a provisional freeze must lead to a Section 17(4) application to the Adjudicating Authority, the officer must file a complaint within 30 days, and a provisional attachment ceases after 180 days unless the Adjudicating Authority confirms it under Section 8. Courts have insisted the “reasons to believe” can’t be a mere formality, and an appeal to the Appellate Tribunal lies within 45 days of the Adjudicating Authority’s order. The high-profile gaming example: the Karnataka HC stayed an ED probe against Gameskraft, and the same court has permitted operation of PMLA-frozen accounts for salary payments under Section 17(1A) — proof the freeze isn’t absolute. For an ordinary player, a direct PMLA freeze is rare; it usually catches operators and high-value mules, not a recreational ₹5,000 winner.

The PROGA wind-down “freeze” that isn’t one. Far more common in 2026: your account is on a discontinued operator (RummyCircle, Junglee Rummy, Dream11, MPL, Adda52, PokerBaazi all suspended cash play from late August 2025), and you read the inaccessible balance as “frozen.” It usually isn’t legally frozen — the cash game stopped, but banks and intermediaries kept processing withdrawals so users could recover existing balances. The blocker is typically incomplete KYC or a dormant recovery flow, not a hold.

The unblock path for Cause 6:

1. Find out if it’s PMLA or PROGA. A PMLA freeze comes with an ED order or a bank notice naming the PMLA; a PROGA wind-down comes with a “cash games discontinued” notice and a recovery flow. Different problems.
2. For a PMLA freeze, get the order and the clock. Obtain the freezing order, note the 180-day adjudication ceiling, and engage a lawyer for the Section 8 hearing or the Appellate Tribunal — this is not a self-service grievance.
3. For a PROGA wind-down, complete KYC and run the recovery flow. Make PAN/bank/KYC names match, follow the operator’s remaining withdrawal/recovery path, and expect 30% TDS on net winnings on the way out, as the withdrawal hub explains. Recovery is the biggest 2026 need, and the rail protections still cover it.
4. Never deposit again “to unlock.” A new deposit into a money game is illegal post-PROGA — and no legitimate freeze is lifted by depositing more.

Cause-6 tell: the wording mentions “ED,” “PMLA,” “investigation” (heavy freeze, lawyer territory) or “cash games discontinued / service closed” (wind-down recovery, KYC territory). They look similar and are nothing alike.

How to tell which freeze you actually have — the decision tree

Pattern-match in this order; the first branch that fits is your answer.

1. Is the freeze on your bank account (the bank told you), or inside the app?
   • Bank account → it’s a lien/LEA freeze. Is the authority the police/I4C (cyber complaint) or the ED (PMLA)? Police/I4C = Cause 5; ED/PMLA = Cause 6 (PMLA).
   • Inside the app → continue.
2. Did the freeze follow a deposit reversal / chargeback? → Cause 3.
3. Does the message mention multiple accounts / device / duplicate? → Cause 2 (forfeiture risk).
4. Did it follow a big win / first large withdrawal and mention review/verification/compliance? → Cause 1 (most reversible).
5. Is only a specific outgoing payout stuck at “processing,” login fine? → Cause 4 (rail/escrow timing).
6. Is the whole operator down with a “discontinued/closed” notice? → Cause 6 (PROGA wind-down) — a recovery problem, not a freeze.

Two freeze causes can stack: a win-spike review (1) that the operator escalates into an STR, or a settlement hold (4) that turns out to be an LEA hold (5). When two fit, work the heavier one’s clock (the LEA/PMLA timeline) while keeping the lighter one’s paper trail alive.

The realistic duration of each freeze — what’s normal vs stuck

Forget “they’ll release it tomorrow” and forget “it’s gone forever.” Here is how long each freeze legitimately lasts, with the rule behind the number where one exists. Anything past the “stuck” column is your cue to escalate.

Read it as a set of clocks. The 15-day officer reply and 90-day removal on a bank lien, and the 180-day ceiling on a PMLA attachment, are the hardest deadlines you can hold an authority to. An operator’s review window is softer but still has the 7-working-day STR backstop as context. The moment your case crosses from “normal” into “stuck,” start the written escalation in the next section.

How to get a written reason — the single most important step

Every freeze type above has one thing in common: you cannot fix it until you know why it happened, and the operator or authority is rarely volunteering it. Forcing a written reason is the highest-leverage move on this page, because it converts a vague “your account is restricted” into a specific, escalatable claim.

For an operator freeze, your written-reason demand should ask four things, in one ticket:

1. The specific reason the account/payout was frozen (which rule or flag).
2. Whether this is a review (temporary) or a terms-based closure (permanent), in plain words.
3. The exact step or document required from you to clear it, if any.
4. A resolution timeline and a ticket/complaint ID for the record.

For a bank/LEA freeze, the equivalent demand goes to the bank:

1. The freezing authority — which police station / cyber cell, and the complaint/NCRP reference.
2. The lien amount and confirmation it’s limited to the disputed sum, not the whole account.
3. The date the freeze was placed (this starts your 90-day SOP clock).
4. The contact for the Investigating Officer who can issue an NOC.

Two reasons this matters so much. First, a written reason exposes a false positive — if the operator says “multiple accounts” and you genuinely have one, you now have a concrete claim to disprove. Second, a written reason and a dated ticket start the clocks that every escalation route depends on: the operator’s own SLA, the 7-working-day STR context, the 15-day officer-reply rule, the 90-day lien-removal rule, the 180-day PMLA ceiling. No written timestamp, no clock — and without a clock, you can’t prove anyone is late.

If an operator refuses to give any reason and simply repeats “restricted,” treat that refusal itself as the grievance and escalate it as a service deficiency. A regulated entity that owes you a clean balance cannot lawfully freeze it indefinitely with no stated cause.

The unblock escalation ladder — Day 0 to Day 90+

This ladder works for all operator-side freezes and bridges to the LEA/PMLA routes. Climb in order; skipping rungs wastes days, and jumping to the Ombudsman or a writ on Day 1 gets you bounced back to start. Templates follow in the next section.

Day 0 — Freeze the evidence, open the ticket, identify the side

The highest-value hour is documentation, not argument.

• Screenshot everything: the freeze message verbatim, the balance, the triggering event (the win, the deposit reversal, the device warning), and the date/time.
• Determine the side: bank account or in-app? This routes everything. If it’s your bank, call the bank first for the freezing-authority details.
• Open the in-app ticket (operator freeze) demanding the written reason, with a ticket ID. For a bank freeze, ask the branch for the lien details in writing.
• Do not create a second account, do not deposit “to unlock,” and never share an OTP or UPI PIN with anyone who “calls to help” — legitimate support and real police never ask for your PIN/OTP.

Day 1–3 — Written reason + the right clock

• For an operator freeze, email the official support address referencing the in-app ticket, restating the four written-reason questions. Email creates a paper trail in-app chat can’t.
• For a win-spike review (Cause 1), you’re inside the normal window — let it run unless it passes 72h with no reply.
• For a bank lien (Cause 5), you now know the police station; begin the NOC approach to the Investigating Officer.

Day 4–7 — Grievance officer + payment-side dispute

• Escalate the operator ticket to its grievance/nodal officer (every regulated operator publishes one) with the days elapsed and the still-missing written reason.
• If the freeze is really a settlement/escrow hold past T+1 (Cause 4), open a bank/UPI dispute with the UTR in parallel — the rail protections in the withdrawal hub apply.
• For a bank lien, if the IO hasn’t responded, prepare the I4C GRM filing (the 15-day officer-reply clock is now your lever).

Day 8–15 — Final notice + GRM / formal complaint

• Send the operator a final-notice email: restate the facts, the ticket ID, the days elapsed, the absent reason, and state you’ll escalate to the consumer forum and (for a payment failure) the RBI Ombudsman. A dated final notice often unsticks a soft hold.
• For a bank lien, file the I4C GRM grievance if the officer is silent past 15 days — it auto-escalates to a District Grievance Redressal Officer.

Day 16–90+ — Consumer forum, RBI, GRM escalation, or writ

• For an operator that won’t return a clean, owed balance, file with the National Consumer Helpline 1915 / consumerhelpline.gov.in (service deficiency).
• For a payment-rail failure, after 30 days file free with the RBI Integrated Ombudsman (RB-IOS 2021) at cms.rbi.org.in.
• For a bank lien past 90 days with no continuation direction, the SOP says it should be removed — push that explicitly, and if a court order is genuinely absent and the amount is below ₹50,000, no court order is needed to refund.
• For a disproportionate or stale freeze, a writ petition is the constitutional remedy — courts have repeatedly unfrozen accounts where police exceeded Section 106/107 BNSS.
• For suspected fraud — a fake “account-recovery agent,” a phishing “unblock fee” call, a clone app — report to cybercrime 1930 / cybercrime.gov.in.

Honest limit of this ladder: it’s powerful against a licensed operator (consumer + grievance routes), against a bank/rail failure (RBI Ombudsman), and against a disproportionate LEA freeze (GRM + writ). It’s weaker against an unlicensed or offshore operator that simply ignores you, and a PMLA freeze is lawyer territory, not a self-service grievance. Match the rung to the type.

Two worked freeze timelines, start to finish

To make the ladder concrete, here are two composite walkthroughs — built from the rules and operator patterns above, not from any single real account. They show how the same discipline plays out across the two main freeze sides.

Timeline 1 — A win-spike operator hold that resolves in four days

The scenario: a player on a licensed operator hits an unusually large win, requests a withdrawal well above their usual size, and the cash-out flips to “under review.” Login still works.

• Day 0. The status screen reads “withdrawal under security review.” The player screenshots the win, the balance, and the freeze message, then opens an in-app ticket with the four written-reason questions and gets ticket ID. No second account, no extra deposit. Crucially, the player recognises the tell — “review/security/verification” wording, login fine, only the payout blocked — as Cause 1, the most reversible type.
• Day 1. The operator replies that the account is in routine AML review and asks the player to re-confirm KYC. The player checks that PAN, bank name, and UPI handle match exactly — they do — and re-submits. Because the names already match, there’s nothing to fix; the mismatch trap that turns a 1-day review into a 2-week one is avoided.
• Day 2–3. The player waits inside the stated 72-hour window rather than spamming support, since premature escalation just resets the queue. The operator’s compliance team clears the review.
• Day 4. The payout is approved and lands, 30% TDS on net winnings deducted as expected — the smaller-than-requested amount is tax, not a fresh problem, exactly as the 194BA math in the withdrawal hub predicts. Total elapsed: four days, zero escalation beyond the operator. This is the typical outcome for a clean account — which is why the loudest advice on Cause 1 is “document, demand a reason, then wait the window.”

Timeline 2 — A bank lien that takes the GRM route

The scenario: a player’s bank account — not the app — gets a debit freeze on ₹8,000 a week after a gaming withdrawal lands, because the sender of an earlier credit was named in a cyber-fraud complaint.

• Day 0. The bank app shows a lien of ₹8,000 on an account holding ₹40,000; the rest is still usable, which already signals the proportionate-lien SOP is being followed. The player asks the branch, in writing, for the freezing authority, the complaint reference, and the date the lien was placed — starting the 90-day clock.
• Day 1–5. Armed with the police station and complaint reference, the player approaches the Investigating Officer with the facts: the credit was a legitimate gaming withdrawal, with the UTR as proof, and the player is not a party to any fraud. The ask is a No-Objection Certificate.
• Day 6–15. The officer doesn’t respond. The player files on the I4C GRM module, citing the 15-day non-response. The grievance auto-escalates to a District Grievance Redressal Officer.
• Day 20–40. With the GRM pressure and a clean, documented transaction trail, the IO issues the NOC, which the bank uses to lift the ₹8,000 lien. Because the disputed amount was below ₹50,000, no court order was needed. Had the freeze sat past 90 days with no continuation direction, the SOP’s removal rule would have been the next lever, and a writ the backstop. This is slower than Timeline 1 — but it follows a defined path, not a black hole.

The lesson across both: a freeze you document on Day 0 and route to the correct holder of the money resolves on a knowable clock. A freeze you panic over, deposit into, or escalate to the wrong authority drifts for weeks. The discipline is identical whether the hold lasts four days or forty.

Copy-paste templates for an unblock fight

Fill the bracketed parts. Keep every message factual, dated, and ID-stamped. There are five, one per situation.

Template A — Operator written-reason demand (Day 0)

Subject: Account/withdrawal frozen — written reason and timeline requested

My account (registered mobile [NUMBER]) shows "[FREEZE MESSAGE]" since
[DATE, TIME]. Balance affected: ₹[AMOUNT].
Please confirm in writing:
1. The specific reason this account/payout was frozen.
2. Whether this is a temporary review or a terms-based closure.
3. The exact document or step required from me to clear it.
4. The expected resolution date.
KYC status: completed (PAN + Aadhaar verified, name matches bank).
Please share a complaint/ticket ID for this request.

Template B — Grievance-officer escalation (Day 4–7)

Subject: [Ticket ID] Frozen account/balance — escalation to Grievance Officer

I raised ticket [TICKET ID] on [DATE] regarding a freeze on my account
(₹[AMOUNT], registered number [NUMBER]). It has now been [N] days with
no written reason as required.
- Freeze message: [VERBATIM]
- Triggering event: [big win / deposit reversal / device flag / none]
- KYC: completed, PAN matches bank account name
Please provide the specific reason in writing and either release the
balance or state the exact step to clear it within 48 hours. If
unresolved, I will escalate to the National Consumer Helpline (1915)
and, for any payment failure, the RBI Ombudsman (RB-IOS 2021).

Template C — Bank lien / NOC request to the Investigating Officer (Cause 5)

Subject: Request for NOC — lien on account [A/C], complaint ref [REF]

My account [A/C] at [BANK] has a lien of ₹[LIEN AMOUNT] placed on
[DATE] pursuant to cyber-complaint reference [NCRP/COMPLAINT REF],
[POLICE STATION].
The credit in question was a legitimate gaming withdrawal/transfer:
[brief facts + UTR if available]. I am not a party to any fraud.
Per the MHA/I4C account-freeze SOP, the lien should be limited to the
disputed amount and the response provided within 15 days. I request a
No-Objection Certificate to release the lien, or the specific reason it
must continue, in writing.

Template D — I4C GRM grievance (officer unresponsive past 15 days)

To: I4C Grievance Redressal Mechanism (GRM) module

Grievance: Lien/freeze on my account not responded to within 15 days.
- Account: [A/C], Bank: [BANK]
- Lien amount: ₹[LIEN AMOUNT], placed on [DATE]
- Complaint reference: [NCRP/COMPLAINT REF], [POLICE STATION]
- Investigating Officer approached on: [DATE]; no response in [N] days.
Relief sought: removal of the lien / NOC, as the officer has not
responded within the SOP's 15-day window. Per the SOP, holds should be
removed after 90 days without a lawful continuation direction.

Template E — National Consumer Helpline (operator won’t return a clean balance)

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

Complaint: Service deficiency — gaming app freezing a verified,
KYC-complete balance without a stated reason.
- Operator / app: [APP NAME]
- Registered mobile: [NUMBER]
- Balance frozen: ₹[AMOUNT]; frozen since [DATE]
- In-app ticket [TICKET ID] raised [DATE]; no written reason given.
- KYC: completed; PAN matches bank account name; one account only.
Relief sought: release of ₹[AMOUNT] to my registered account, and a
written reason for the freeze.

Use Template E in parallel with the bank/RBI route when the freeze is on the operator’s side; the consumer angle reaches the operator’s service obligation while the RBI route reaches the payment rail.

The grievance-and-authority map for a freeze

One table, the whole escalation map. Pick the door that matches your freeze type.

Order of doors, in one line for the two main paths: operator side → operator grievance officer → consumer helpline 1915 (+ RBI Ombudsman for any rail failure); bank side → IO for NOC → I4C GRM → writ. Cybercrime 1930 runs the instant a scam is involved on either path.

The legal recourse when the frozen money is genuinely yours

This is the part players most need and most lack: what your rights are when a freeze sits on money that is legitimately yours.

Against an operator. A licensed operator that froze a clean, KYC-verified balance with no stated reason is in deficiency of service. Your rights are a written reason, a grievance-officer hearing, and — if it still won’t release — a consumer-forum complaint under the consumer-protection framework. The operator’s terms permit forfeiture only for genuine breaches (multi-accounting, fraud, mod-APK), and even then a forfeiture asserted with no reason is contestable. The weakness is jurisdiction: an offshore or unlicensed operator may sit outside Indian reach, which is exactly why a clean balance held inside one is the hardest case.

Against a bank lien (BNSS). Your rights are stronger and clearer than most people realise. The freeze must be proportionate — confined to the disputed amount, per the MHA SOP and the Kerala/Madras High Court rulings. It must be time-bound — the SOP says holds should be removed after 90 days without a lawful continuation direction. Any blanket freeze of an entire account over a small amount is “manifestly arbitrary” and breaches Article 19(1)(g) and Article 21, which is the basis on which courts have unfrozen accounts. And the police power to attach requires Section 107 BNSS and a magistrate’s order — a bare Section 106 seizure does not authorise an indefinite debit-freeze.

Against a PMLA freeze. Even here the law is not open-ended. A provisional freeze under Section 17(1A) must be confirmed by the Adjudicating Authority within 180 days or it automatically ceases; the officer must file the complaint within 30 days; the “reasons to believe” can’t be a mere formality; and you can operate the account for limited purposes with court permission and appeal to the Appellate Tribunal within 45 days.

The thread through all three: a freeze on your money is time-bound, reasoned, and proportionate under Indian law — it is not a black hole. The remedy scales with the freezing party: grievance and consumer routes against an operator, NOC and GRM and (if needed) writ against a bank lien, and the Adjudicating Authority and Appellate Tribunal against a PMLA order. Match the remedy to the party, hold them to the clock, and a legitimately-yours balance is recoverable in the large majority of cases that aren’t trapped inside an unreachable operator.

Recovering a balance from a wound-down (post-PROGA) operator

The biggest 2026 freeze scenario isn’t really a freeze — it’s a stranded balance on an operator that stopped cash play. This deserves its own section because the steps differ from a true hold.

When RummyCircle, Junglee Rummy, Dream11, MPL, Adda52, and PokerBaazi suspended cash formats from late August 2025, they did not simply vanish with your money. Banks and intermediaries were kept processing withdrawals so users could recover existing balances, and the operators left a recovery/withdrawal flow open. So the inaccessible balance you’re reading as “frozen” is usually blocked by one of three ordinary things, each fixable:

1. Incomplete or mismatched KYC. The recovery flow enforces the same PAN/Aadhaar checks as a normal cash-out. A PAN that doesn’t match your bank name stalls the recovery exactly as it stalls a live withdrawal. Fix it via the KYC-rejected steps.
2. A dormant or hard-to-find recovery flow. The cash game is gone, so the withdrawal option may be buried in a “claim balance” or “settlement” screen rather than the usual cash-out button. Look for it, and if you can’t find it, the operator’s grievance officer must point you to it.
3. A genuine refusal to return an owed balance — the only case that’s a real grievance. If the operator refuses to return a clean, KYC-complete balance citing the shutdown, escalate it as a payment/service deficiency: consumer helpline 1915 plus, for any rail-side failure, the RBI Ombudsman.

Two non-negotiables for a wind-down recovery. First, expect 30% TDS on net winnings on the recovery payout, the same as a live withdrawal — money that arrives 30% lighter is tax, not a fresh freeze (the withdrawal hub has the 194BA math). Second, never deposit again to “reactivate” the account — a new deposit into a money game is illegal post-PROGA, and no recovery flow ever requires one. Any prompt to deposit-to-recover is a scam, full stop.

Editor’s verdict on wind-down balances: the cash product is gone, but your existing balance is not forfeited by the shutdown — it’s recoverable through KYC + the recovery flow + (if refused) the consumer/RBI route, with a 30% TDS cut expected. Treat it as a withdrawal problem with extra friction, not as a lost-money freeze.

Frozen vs banned vs dormant vs self-excluded — four states people confuse

“Frozen” gets used for four different account states that have nothing to do with each other. Getting the label wrong sends you down the wrong path, so pin down which one you’re actually in.

• Frozen / on hold (temporary). A reversible hold for a reason — review, lien, dispute. The money is still yours; the question is when and how it’s released. This is the entire subject of this page.
• Banned / closed / forfeited (permanent operator action). The operator terminated the account under its terms — usually multi-accounting, fraud, or a mod-APK — and may claim the balance. This is not a hold you wait out; it’s a closure you contest (deposit-only recovery at best) or accept. The tell is wording like “permanently closed,” “terminated,” “in breach of terms.”
• Dormant / inactive (you stopped logging in). Some operators flag long-idle accounts and require re-verification before releasing a balance. This looks like a freeze but clears with a fresh login and KYC re-check — no grievance needed. The tell is “account inactive / dormant, please re-verify.”
• Self-excluded (you opted out). If you ever set a self-exclusion or cooling-off period under a responsible-gaming feature, the account is locked by your own request for the period you chose. The balance is safe; the lock lifts when the period ends. The tell is “self-exclusion active until [date].”

The practical sort: a dormant or self-excluded account needs no fight — re-verify or wait out the period. A frozen account needs the six-cause diagnostic above. A banned/forfeited account needs the contest-or-accept calculus in Cause 2. Reading a self-exclusion as theft, or a temporary review as a permanent ban, wastes the days you’d spend on the real route. Check the exact wording of the message before you decide which fight you’re in.

A second confusion worth killing: “frozen” versus “the app isn’t loading.” A genuine freeze comes with a status message about your account. An app that simply won’t open, crashes, or shows a network error is a technical problem — reinstall (your balance is tied to your registered number, not the app file), check for an official update, and only treat it as a freeze if a clear account-status message appears after you get back in. Many “my account is frozen” reports are really a broken install or an outdated build, which resolve with a clean reinstall and cost you nothing.

What a freeze actually does to your money, mechanically

To act fast you need a mental model of where your money physically sits during each freeze type, because that’s what decides who can release it. A freeze is not one mechanism — it’s four different things happening in four different places.

An operator-side hold. Your balance never leaves the operator’s books. The number you see in the app is a ledger entry the operator controls, and a risk hold simply flips a flag that blocks the “withdraw” action against that ledger. Nothing has moved to a bank or a rail. That’s why an operator hold is purely a contract matter — only the operator can flip the flag back, which is why the written-reason demand and the grievance officer are your levers, and why the RBI Ombudsman has no purchase here (no regulated payment entity is holding the money yet).

A settlement / escrow hold. Here the money has left the operator and sits in the payment aggregator’s escrow account at a scheduled commercial bank, waiting to settle to you. It’s in a regulated intermediary’s hands, governed by the RBI’s T+1 settlement rule. That’s why this hold does fall under RBI’s reach — the aggregator is a regulated entity, and a settlement stuck past T+1 is escalatable as a payment deficiency, not just an app complaint.

A bank lien. The money is in your bank account, but the bank has placed a debit freeze on a specific amount on the instruction of a police/cyber authority. The bank is a custodian executing a lawful (or sometimes unlawful) order; it can’t release the lien on its own — it needs the NOC from the Investigating Officer or a court direction. That’s why you chase the officer, not the bank, for a defreeze, and why the I4C GRM exists when the officer is silent.

A PMLA attachment. The money may be in your account or already moved into ED custody, and it’s held as suspected proceeds of crime under a provisional order that the Adjudicating Authority must confirm within 180 days. Neither the bank nor the operator can touch it; only the Adjudicating Authority or the Appellate Tribunal can release it. That’s why it’s lawyer territory.

The single insight that ties this together: the party that can unfreeze your money is the party currently holding it, and the four freeze types put your money in four different hands — operator ledger, aggregator escrow, bank custody, or ED/court custody. Spend your effort on the holder, not on whoever you can reach fastest. Emailing the operator about a bank lien wastes a week; calling your bank about an operator hold wastes another. Map money-location to the right authority and the freeze becomes a solvable sequence instead of a wall.

How to keep an account from getting frozen in the first place

Five of the six freeze causes are preventable by habit, and a player who never trips them rarely sees a hold. These are the concrete behaviours that keep an account clean, drawn from the trigger patterns each cause keys on.

1. One account, one identity, one device — forever. The multi-account flag (Cause 2) is the most punishing and the most self-inflicted. Never open a second account, never let a family member play on your device under their own login, and avoid shared/public Wi-Fi for cash sessions where you can. A single PAN tied to a single account is the cleanest signal a risk engine can read.
2. Match every name exactly before your first withdrawal. A PAN that reads “Rahul Kumar,” a bank account that reads “RAHUL K,” and a UPI handle that reads something else is the single most common reason a first payout gets parked into review — and review is where holds escalate. Fix the mismatch before you ever try to cash out, per the KYC-rejected steps.
3. Withdraw in steady, modest amounts, not one giant spike. The win-spike review (Cause 1) keys on transactions that don’t fit your profile. A player who builds a history of regular small withdrawals trips it far less often than one who plays for months and then pulls a single large sum, which reads as an anomaly to the AML system.
4. Never chargeback a deposit to recover a loss. It freezes the account (Cause 3), can get you blacklisted, and post-PROGA the deposit was illegal anyway. Dispute a card transaction only when it’s genuine fraud you didn’t authorise.
5. Use the same, live, own-name bank account for deposit and withdrawal. Routing money through someone else’s account, a closed account, or a constantly-changing handle is exactly the pattern that draws both operator risk flags and bank cyber-fraud attention. Keep it boring and consistent.

The sixth cause — a court/LEA freeze you didn’t earn because a counterparty turned out to be a fraud “mule” — is the one you can’t fully prevent, since it depends on whose money touched yours. But even there, keeping clean, consistent, single-identity records is your best defence: when the Investigating Officer reviews your account, a transparent history of legitimate gaming withdrawals is what earns the NOC fastest. Prevention and recovery use the same hygiene.

Editor’s verdict on prevention: freezes are mostly earned by patterns, not bad luck. One account, exact name-matching, steady withdrawal sizes, no chargebacks, and a single own-name bank account eliminate five of the six causes before they start. The discipline that keeps you unfrozen is the same discipline that gets you defrozen fast if it ever happens.

Frozen-account scam red flags that change your strategy

Most freezes are real and procedural. But the freeze itself is now a magnet for a second scam — fake “unblock” services that prey on panicked players. Spot these and your strategy shifts from “recover” to “report and protect”:

• An “account-recovery agent” or “unblock specialist” found on Google, YouTube, or Telegram who asks for a fee. No legitimate unblock costs a fee paid to a third party. These exist to take a fee and phish your credentials. Report to 1930.
• “Pay a clearance / verification / unblock fee to release your frozen balance.” No operator, bank, or authority unfreezes an account for a fee you pay them. The freeze process is free — the I4C GRM and consumer routes cost nothing.
• A “customer care number” that asks for your OTP, UPI PIN, or remote-access (AnyDesk/TeamViewer). Real support and real police never ask for these. This is the single clearest theft pattern.
• “Deposit ₹X to unlock your withdrawal.” Never legitimate, and post-PROGA the deposit is illegal too. Stop, document, report.
• A clone app or a “mod / unlimited chips” APK that froze your balance. Modified builds void the operator’s terms and can freeze the balance with no recourse under those terms — the money you’re fighting for may already be gone by the operator’s own rules.

If two or more of these are present, lower your expectation of recovering money held inside that operator, pursue any rail loss through the bank/UPI dispute, and file the cybercrime report. Feeding a frozen account another rupee — to an operator or a “recovery agent” — never unfreezes it.

Related fixes (go deeper on your exact case)

This is the freeze hub for the KYC cluster. For the case that matches your symptom, these go step-by-step:

• KYC/account-recovery overview → KYC and account recovery hub — the full account-recovery map and where each freeze fits.
• KYC rejected / name mismatch → Teen Patti KYC rejected — the document-level fixes that clear a verification freeze.
• Withdrawal stuck / processing → withdrawal stuck fix — the pending-state countdown for a payout-only hold.
• Withdrawal not received / rail failure → 3 Patti withdrawal hub — the T+1 auto-reversal, ₹100/day claim, and 194BA tax math.

FAQ

1. Why is my Teen Patti account frozen? One of six reasons: an AML/win-spike review (most common, clears in hours to ~48h), a multi-account flag, a chargeback, a payment-aggregator settlement hold (clears by T+1), a bank cyber-fraud lien under Section 106/107 BNSS, or a PMLA/ED freeze. The cause decides the duration — from 24 hours to 180 days — so find out who froze it and why before escalating.

2. How long does a frozen RMG account stay frozen? It depends on the cause: a win-spike review is hours to ~48 hours; a bank cyber-fraud lien should be removed after 90 days without a continuation direction under the MHA/I4C SOP; and a PMLA provisional freeze ceases after 180 days unless the Adjudicating Authority confirms it.

3. Can a gaming app legally freeze my winnings? Yes, temporarily, for a genuine reason — an AML review, a multi-account flag, or a terms breach. As a Reporting Entity under PMLA Section 2(1)(wa), an operator must monitor and can hold a payout pending review. But it must give a written reason, and freezing a clean, KYC-verified balance indefinitely with no cause is a deficiency of service you can take to the consumer forum.

4. My account was frozen after a big win — is that normal? Yes. A sudden large win is a classic win-spike trigger: it doesn’t match your prior profile, so the AML system parks the payout for manual review. A clean account usually clears in hours to a couple of days. The operator may also file a Suspicious Transaction Report with FIU-IND within 7 working days, but that’s a report about the transaction, not an indefinite freeze.

5. The app says “multiple accounts detected” — will I lose my money? Possibly. Operator terms commonly allow suspension of all linked accounts and forfeiture of winnings earned across them. If you genuinely have one account and the flag is a false positive (shared device/IP), argue that hard and early with a single clean PAN. If a second account truly exists, your realistic recovery shrinks to your deposits, not winnings. Never open a new account to escape it.

6. My bank account — not the app — is frozen over a gaming transaction. What law is that? Almost always a cyber-fraud complaint routed through the NCRP. The police power moved from old Section 102 CrPC to Section 106 BNSS on 1 July 2024, but a debit-freeze/attachment needs Section 107 BNSS and a magistrate’s order. The lien should be limited to the disputed amount, not your whole balance.

7. How do I unfreeze a bank account that has a cyber-fraud lien? Get the freezing-authority details from your bank (police station + complaint reference), then approach the Investigating Officer for a No-Objection Certificate (NOC) — defreezing happens when the IO issues an NOC to your branch. If the officer is silent past 15 days, file on the I4C GRM module, which auto-escalates.

8. Can the police freeze my entire bank account over a small disputed amount? No — not lawfully. The MHA/I4C SOP caps the lien at the disputed sum: if ₹5,000 is disputed on a ₹1,00,000 balance, only ₹5,000 should be blocked. The Kerala and Madras High Courts have held that freezing an entire account without quantifying the amount is manifestly arbitrary and violates Article 19(1)(g) and 21.

9. What’s the difference between a BNSS freeze and a PMLA freeze? A BNSS freeze (Section 106/107) comes from the police/cyber cell in a fraud investigation and has a 90-day SOP-removal expectation. A PMLA freeze comes from the Enforcement Directorate under Section 17(1A) for suspected money-laundering proceeds, must be confirmed by the Adjudicating Authority within 180 days or it ceases, and is appealable to the Appellate Tribunal within 45 days.

10. The app I used shut down — is my balance frozen or lost? Usually neither. The cash games stopped under PROGA, but withdrawals were kept open so users could recover existing balances. The blocker is normally incomplete KYC or a hard-to-find recovery flow, not a legal freeze. Complete KYC, run the recovery flow, expect 30% TDS on net winnings, and never re-deposit.

11. Will I get my frozen money back if it’s genuinely mine? In most cases that aren’t trapped inside an unreachable operator, yes. A freeze on your money is time-bound and proportionate under Indian law: a bank lien has a 90-day removal rule, a PMLA freeze a 180-day confirmation ceiling, and an operator owes you a written reason plus a consumer-forum route. Match the remedy to the freezing party and hold them to the clock.

12. Someone offered to “unblock” my account for a fee — is that safe? No. No legitimate unblock charges a fee paid to a third party, and the official routes — I4C GRM, consumer helpline 1915, operator grievance — are free. “Pay ₹X to unlock,” OTP/PIN requests, or remote-access demands are scams; report to 1930 / cybercrime.gov.in.

13. My withdrawal is frozen but login works — is that a real freeze? That’s a payout hold, not a full account freeze — usually an AML review (Cause 1) or a KYC gate, the most reversible kind. Demand a written reason, fix any KYC name mismatch, and follow the withdrawal-stuck countdown. Past 72 hours with no reason, escalate to the grievance officer.

14. Can I still use a bank account that’s under a PMLA freeze? Sometimes, with permission. Courts have allowed operation of PMLA-frozen accounts for limited purposes like salary payments under Section 17(1A). The freeze isn’t absolute, and a provisional attachment that the Adjudicating Authority doesn’t confirm within 180 days is automatically released.

15. Where do I complain if an operator freezes my balance and won’t explain? For an operator refusing to return a clean, KYC-complete balance, file with the National Consumer Helpline 1915 / consumerhelpline.gov.in for service deficiency, and run the operator’s grievance officer in parallel. For any payment-rail failure, after 30 days use the RBI Integrated Ombudsman at cms.rbi.org.in. For fraud, cybercrime 1930.

Sources & method. Freeze causes, durations, and unblock steps on this page are built from primary legal and regulatory sources and named operator behaviour — not personal account tests. Key references: the BNSS replacing the CrPC on 1 July 2024 and the Section 106 vs 107 distinction; the Kerala HC and Madras HC proportionality rulings; the MHA/I4C account-freeze SOP, its lien-cap and 15-day/90-day timelines, and the sub-₹50,000 no-court-order refund; the I4C GRM module; PMLA Section 17(1A) freezing, the 180-day Section 8 confirmation ceiling, and the Gameskraft ED matter; FIU-IND gaming reporting / STR within 7 working days and online gaming under PMLA; the RBI Payment Aggregator T+1/escrow framework and LEA hold handling; operator multi-account forfeiture practice; the Promotion and Regulation of Online Gaming Act, 2025, its Rules effective 1 May 2026, and the wind-down balance recovery; the RBI Integrated Ombudsman Scheme 2021; 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, your bank’s policy, and current law.