KYC & Account Recovery for Indian RMG Apps: The Full Map

The 30-second answer

KYC (Know Your Customer) on an Indian real-money app is the PAN + Aadhaar + bank-account verification that anti-money-laundering law forces before any cash-out. If your withdrawal is blocked, you’re stuck at one of six account states: KYC pending, KYC rejected, name-mismatch, account frozen, a risk/AML hold, or a duplicate-flag. Each has a different fix — a rejected document is re-submitted, but a frozen account needs a written reason and the RBI escalation chain. And if your app discontinued cash play under PROGA 2025, your balance is still recoverable — not through any statutory deadline (the draft’s 180-day refund rule was dropped from the final notified Rules), but through the operator’s own voluntary wind-down withdrawal flow, which still needs your KYC clean to pay you.

Editor’s verdict, up front. A KYC block is almost never the app “stealing” your money. It’s a verification gate that the law makes mandatory, and your account is parked at exactly one of six states behind that gate. The single most expensive mistake players make is treating all six as the same problem — they shout “unblock my account” at support when their real issue is a one-letter name mismatch between PAN and bank, which support can’t fix because you have to. This page is the master map for the whole KYC-and-freeze cluster: it names every state, gives you the order to diagnose them, lays out the document chain that triggers each, and routes you down to the specific spoke fix. The rule references behind every claim are cited inline.

2026 reality you must read first. The ground shifted under this entire topic. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) got Presidential assent on 22 August 2025, and its operating Rules came into force on 1 May 2026, banning all online money games. The major operators — RummyCircle, Junglee Rummy, Dream11, MPL, Adda52, PokerBaazi — suspended cash play from late August 2025. For KYC and account recovery, this creates a brutal new problem: your balance is locked inside a KYC-gated account on an app that no longer runs cash games. Here is the part most guides get wrong: the draft 2026 Rules (released October 2025) contained a provision, widely cited as Rule 24, that would have created a roughly 180-day, platform-led refund window for winding-down operators — but in the final notified Rules (Gazette 22 April 2026, in force 1 May 2026) that user-fund refund provision was cut, on the basis that existing law already covers the matter (Mondaq; iGaming Business). So there is no statutory deadline by which an operator must refund you. What is left is the operators’ own voluntary wind-down — they kept withdrawals open so users could recover existing balances (per the reset analysis) — backstopped by existing consumer-protection and RBI/NPCI payment law, and the PROGA grievance ladder. So in 2026, fixing your KYC is no longer about playing more; it’s the key that unlocks a stranded balance, and you should treat recovery as time-sensitive because the safety net is voluntary, not because a law gives you a fixed window. This guide reads two ways throughout — for a still-live legal app, and for a post-shutdown recovery — and flags which is which.

What KYC actually is on a real-money gaming app

When people search “teen patti kyc,” “gaming account recovery,” “teen patti kyc rejected,” or “account frozen real money app,” they are circling the same object from different angles. So let’s pin it down precisely, because the precision is what tells you which fix applies.

KYC — Know Your Customer — is the legally-mandated process by which a regulated entity verifies who you really are before it lets you move money. On a real-money gaming (RMG) app, KYC is not a feature the operator added to be annoying; it’s the load-bearing wall of the whole cash system. Three independent layers of Indian law converge on that wall:

• The Prevention of Money Laundering Act, 2002 (PMLA) and the PML Rules, 2005 — the statutory root. These require “reporting entities” to identify customers, verify identity, and maintain records, precisely so that money can’t be laundered through anonymous accounts.
• RBI’s Master Direction on KYC, 2016 — the operational rulebook for banks and payment intermediaries, issued 25 February 2016 as the umbrella framework consolidating earlier circulars, with PMLA as its statutory backbone. Every payout you receive rides over a bank or payment aggregator bound by this Direction.
• Section 194BA of the Income-tax Act — since 1 April 2023, every legal gaming app must deduct 30% TDS on net winnings and report it against your PAN. No PAN, no compliant payout — which is exactly why PAN sits at the centre of gaming KYC.

So when a Teen Patti or rummy app asks for your PAN, Aadhaar, a bank account, and sometimes a selfie or video, it isn’t building a profile to sell. It’s stacking the four documents the law forces it to verify before it can legally hand you cash and report the tax. Understanding that is the first unlock: a KYC request is a legal precondition for getting paid, not an obstacle the operator invented.

Why the cash-out is the moment KYC bites

Here’s the structural detail almost every player misses, and it explains 80% of the “sudden block” confusion: on most RMG apps, KYC is enforced at the first withdrawal, not at the deposit. You can deposit, play for days, even win — and never touch a verification screen. Then you tap “withdraw” for the first time and the full PAN-Aadhaar-bank wall slams up.

The major Indian skill-game operators wrote this pattern into their own rules. On Junglee Rummy, KYC was mandatory at the first withdrawal or once cumulative deposits crossed ₹50,000, whichever came first. On RummyCircle, withdrawal required your PAN to be verified and to match your KYC documents exactly — a single transposed letter on the name field was enough to park the payout. Both apps have since discontinued cash play under PROGA, but the pattern is universal across every legal RMG app: deposit is easy, the cash-out is where you’re verified.

That timing has a consequence worth stating plainly. A player who hits a “KYC pending” or “verification required” wall on their first withdrawal hasn’t been singled out or accused of anything. They’ve simply reached the gate that was always there, just invisible until the money tried to flow out. If your first cash-out stalls while you’ve been playing fine for a week, KYC is the first thing to check — not the last.

The three balance pots, and why one of them never needs KYC

A quick clarification that prevents a whole category of false “KYC blocked my money” panic. Your wallet balance is three different pots:

• Deposit balance — money you added with your own card or UPI.
• Winnings balance — money you won at the table. This is the pot that triggers TDS, and therefore the pot that requires PAN-KYC on the way out.
• Bonus / promotional balance — chips the app gave you. This is almost never directly withdrawable and isn’t blocked by KYC at all — it’s blocked by wagering rules.

If you’re trying to withdraw a bonus balance and the app refuses, that is not a KYC problem and no amount of re-submitting your PAN will fix it. Read your withdrawal screen’s withdrawable figure, not the headline wallet number. The companion withdrawal hub, 3 Patti withdrawal: why it’s stuck and how to fix it, breaks the three pots down in full — start there if your real issue is which pot your money sits in rather than verification itself.

Why KYC is mandatory: the three laws that force it

You fight a KYC block far more effectively once you understand it isn’t discretionary. The operator cannot simply “waive” verification for you, because three separate legal regimes would each be violated. Here is each one, in plain terms, with what it specifically forces.

PMLA 2002 — the anti-money-laundering root

The Prevention of Money Laundering Act, 2002 is the reason KYC exists at all in Indian finance. Its logic is simple: if a platform lets anonymous people move money, that platform becomes a laundromat for illegal funds. So PMLA designates certain businesses as “reporting entities” and obliges them to identify and verify every customer, keep records of transactions, and report suspicious activity to the Financial Intelligence Unit.

For a gaming operator’s payments, the relevant reporting entities are the banks and payment aggregators that actually settle your withdrawal. They are bound by PMLA whether or not the gaming app itself is. That’s the structural reason your payout cannot bypass KYC: even if a shady app wanted to pay an unverified account, the regulated bank on the other end of the rail won’t process an AML-non-compliant credit. PMLA is also why account freezes happen — when an account is flagged for suspected money laundering, the law requires the entity to freeze it pending investigation, and a recent high-profile example shows this isn’t theoretical: the Enforcement Directorate froze WinZO Games’ bank accounts under PMLA in 2026, and WinZO had to offer a bank guarantee to seek de-freezing. If a regulator can freeze a billion-rupee operator under PMLA, an individual account flagged for an AML concern faces the same machinery.

RBI Master Direction on KYC, 2016 — the operational rulebook

PMLA says “verify customers”; the RBI Master Direction on KYC, 2016 says how. Issued 25 February 2016 and updated repeatedly since, it tells every bank, NBFC and payment intermediary exactly what counts as valid identity proof, what “Officially Valid Documents” (OVDs) are, when enhanced due diligence applies, and — critically for account recovery — what happens when KYC lapses.

Two features of this Direction directly shape gaming account problems. First, risk-based categorisation: customers are sorted into low, medium and high risk, with periodic re-KYC required at different cycles — reportedly 2 years for high-risk, 8 years for medium, 10 years for low-risk accounts (per the updation guidelines). A gaming-linked account that suddenly sees large, frequent payouts can be re-categorised as higher risk, triggering a fresh KYC demand mid-stream. Second — and this is the mechanism behind most “account frozen” stories — the Direction sets out a graduated freeze for non-compliance: the entity must give at least three months’ notice, then impose a partial freeze allowing only credits and blocking debits, and if non-compliance continues for another six months, all operations are frozen (per RBI’s freeze procedure). That graduated structure is your leverage: a sudden, no-notice debit freeze without the prescribed warning steps is itself a compliance failure you can escalate.

Section 194BA + PAN-Aadhaar — the tax layer

The third law isn’t about laundering; it’s about tax, and it’s why PAN is the non-negotiable centre of gaming KYC. Since 1 April 2023, Section 194BA forces every legal gaming app to deduct 30% TDS on net winnings and remit it against your PAN. With no PAN, the app literally cannot compute and report your tax — so it cannot pay you a winnings cash-out.

There’s a sharper, newer twist that catches players in 2026. PAN-Aadhaar linking is now mandatory, and an unlinked PAN is “inoperative.” An inoperative PAN doesn’t just block ITR filing — it triggers higher TDS under Section 206AA (the gaming app may be forced to deduct at a steeper rate, and you can’t claim the credit cleanly) and can make your KYC fail at the bank end entirely (per the PAN-Aadhaar linking rules). So a player whose PAN looks fine but is unlinked from Aadhaar can hit a verification wall that no amount of re-uploading the same PAN card will clear — the fix is to link PAN to Aadhaar (a ₹1,000 fee where the deadline has lapsed), then re-submit. This is one of the genuinely silent KYC killers of 2026.

The mandatory-KYC takeaway in one line: it’s not the operator’s choice, it’s three laws — PMLA forces identity verification, the RBI KYC Direction dictates the documents and the freeze mechanics, and Section 194BA + PAN-Aadhaar make PAN the tax-reporting linchpin. Knowing which law is biting tells you which door to push: a documents problem is the RBI/operator door, an AML freeze is the PMLA/Ombudsman door, and a PAN problem is the income-tax-portal door.

The KYC document chain — what each document does and where it fails

A gaming KYC isn’t one upload; it’s a chain of four verifications, and the payout only flows when all four links hold. Understanding the chain lets you pinpoint the exact link that broke instead of blindly re-submitting everything. Here is each link, what it proves, and its most common failure.

Link 1 — PAN card (the tax + identity anchor)

What it proves: your tax identity. The PAN is mandatory because Section 194BA TDS is reported against it. What the app checks: that the PAN is valid, operative (Aadhaar-linked), and the name on it matches your other documents. Where it fails:

• Name mismatch — your PAN reads “Rahul Kumar Sharma” but your bank account reads “Rahul Sharma.” The systems can’t auto-reconcile, and the payout parks.
• Inoperative PAN — PAN not linked to Aadhaar, so it’s flagged inoperative; verification fails at the bank/tax layer even though the card itself looks fine. The fix is PAN-Aadhaar linking, not re-uploading.
• Blurry / cropped image — the OCR can’t read the PAN number or name field, so the document is auto-rejected.

The PAN is the single most important link, because it’s the one tied to a legal reporting obligation. The spoke page PAN card verification for gaming — pending its dedicated build — and the broader withdrawal-stuck diagnosis both cover the PAN-specific stalls in more depth.

Link 2 — Aadhaar / OVD (identity + address)

What it proves: your identity and address. Aadhaar is the most common OVD, though under the RBI KYC Direction, Aadhaar is offered voluntarily and other Officially Valid Documents (passport, voter ID, driving licence) are accepted (Aadhaar is an OVD but not compulsory for KYC). What the app checks: that the name and date of birth on Aadhaar match PAN, and that you are 18 or older — PROGA-era age-gating mandates Aadhaar-based or equivalent age verification with audit logs (per the 2026 Rules’ KYC and age-gating requirement). Where it fails:

• Name spelling differs from PAN — Aadhaar shows your full expanded name while PAN shows initials, or vice versa. This is the single most common cross-document mismatch.
• Address proof rejected — an outdated or unclear Aadhaar where the address can’t be read.
• Underage flag — if Aadhaar shows you’re under 18, the account is blocked entirely under age-gating rules, and that block cannot be lifted by argument.

Link 3 — Bank account / UPI (the payout destination)

What it proves: that there’s a verified, real account in your name to receive the money. What the app checks: that the bank account holder name matches your KYC name exactly, and increasingly, that the same account is used for deposit and withdrawal. Where it fails:

• Beneficiary name mismatch — even if the app’s own KYC passed, the bank can reject the credit if the account-holder name doesn’t reconcile. You fix this with the bank, not the app.
• Dead / stale UPI handle — you changed banks or closed the linked account, so the “paid” payout tried to credit an address that no longer resolves.
• Account not in your own name — using a family member’s account is an instant KYC fail; the destination must match the verified identity.

For the payout-rail mechanics behind a bank-side failure — UTR tracing, the T+1 auto-reversal, the ₹100/day compensation — the spoke UPI failed, money debited walks the exact dispute. KYC fixes the eligibility; that page fixes the rail.

Link 4 — Selfie / video / liveness (anti-impersonation)

What it proves: that the person operating the account is the person on the documents — i.e. you aren’t using someone else’s PAN. What the app checks: a live selfie or short video matched against the document photo; some operators run a V-CIP (Video-based Customer Identification Process), which RBI’s Direction explicitly permits for both onboarding and re-KYC. Where it fails:

• Poor lighting / face not matching — the liveness check can’t confirm the face, so it loops.
• Mismatch with document photo — common when the document photo is very old.
• Skipped step — some accounts sit in “KYC pending” indefinitely simply because the selfie/video link was never completed, and the player didn’t realise a step remained.

The document-chain takeaway: your payout needs all four links to hold — PAN (operative + name-matched), Aadhaar/OVD (identity + age + address), bank (name-matched + live + yours), and selfie/video (you are you). When a withdrawal stalls on “KYC,” don’t re-upload everything blindly. Find the one broken link — it’s a name mismatch four times out of five — and fix only that. The number worth remembering: a one-character name difference across these documents is enough to park a payout for manual review.

A worked name-mismatch resolution (the most common four-link failure)

Because name mismatch causes the majority of silent KYC stalls, it’s worth walking one concrete resolution end to end, third-person, so you can copy the sequence. Take a player whose documents read like this: PAN says “ARJUN SINGH RATHORE,” Aadhaar says “Arjun Singh Rathore,” and the bank account says “ARJUN RATHORE.” Three documents, two different names — the bank dropped the middle name. The app’s KYC may even pass (PAN and Aadhaar agree), but the payout fails at the rail because the beneficiary name on the bank account doesn’t reconcile with the verified PAN name.

The wrong fix is to keep re-submitting KYC on the app — the app side already matches. The right fix is to align the bank record:

1. Identify the canonical name. PAN is the anchor for tax reporting, so the bank should match PAN. Here that’s the full “Arjun Singh Rathore” with the middle name.
2. Correct the bank record, not the app. Visit the bank or use net-banking’s profile-update to add the dropped middle name so the account holder reads exactly as on PAN. This is a bank action; the app cannot do it for you.
3. Re-link the corrected account in the app’s withdrawal settings, and run a small test withdrawal (commonly ₹100) before attempting the full balance.
4. Keep the same account for deposit and withdrawal from then on, so the reconciliation never breaks again.

The lesson generalises: when the app’s KYC passes but the payout still fails, the broken link is almost always the bank beneficiary name, and the door is your bank — not another round of app uploads. A player who understands this fixes in a day what otherwise becomes a fortnight of re-submitting documents that were never the problem.

The taxonomy of account problems — the six states behind the gate

This is the core of the whole page, and the thing the spokes hang off. Almost every “my account is blocked / KYC failed / frozen” complaint resolves to exactly one of six states. Each has a distinct cause, a distinct fix, and a distinct escalation door. Mis-classifying your state is the reason people waste weeks pushing on the wrong door. Match your symptom, then jump to the matching deeper guide.

State 1 — KYC pending (incomplete verification)

Symptom: the app shows “KYC pending,” “verification in progress,” or a step that never completes. Withdrawal won’t submit. What’s really happening: a link in the chain was never finished — most often the selfie/video step was skipped, or a document is still under manual review. The account isn’t rejected; it’s incomplete. The fix: open the KYC section and check which links are actually green. Complete any unfinished step (the selfie/video is the usual culprit). If everything is submitted and it’s been pending past the app’s stated window (commonly 24–72 hours), raise an in-app ticket. This is the easiest state to clear because nothing was rejected — something was just left undone. Door: the app’s own KYC flow, then app support.

State 2 — KYC rejected (a document failed verification)

Symptom: an explicit “KYC rejected,” “document not accepted,” or “verification failed” message, often with a reason code. What’s really happening: a specific document failed — a blurry image, an inoperative PAN, a name mismatch, or an unreadable address. Unlike “pending,” the system has actively bounced something. The fix: read the rejection reason if one is given, then re-submit only the failed document, clean. For an inoperative PAN, link it to Aadhaar first. For a blurry upload, re-shoot in good light, the full document in frame, no glare. Don’t re-submit the same image expecting a different result. Door: the app’s re-submission flow. The dedicated KYC-rejected spoke (under construction in this cluster) lists every common rejection code with its exact remedy.

State 3 — Name mismatch (the most common silent stall)

Symptom: withdrawal “pending” forever with no clear error; later small payouts may have worked while a first or larger one hangs. What’s really happening: the name on your UPI/bank doesn’t match the name on your PAN/Aadhaar. “RAHUL K” on the UPI handle versus “Rahul Kumar” on PAN is enough. The risk engine can’t auto-match, so it routes to manual review and sits. The fix: make your bank/UPI account-holder name match your PAN exactly, and use the same account for deposit and withdrawal. If the bank name is the problem, you correct it at the bank, not the app. This is the single most common cause of a stuck first payout, and it’s invisible because there’s often no error message — just silence. Door: your bank (to fix the name) and then the app (to re-verify).

State 4 — Account frozen (debit-blocked, often AML/PMLA)

Symptom: the account is “frozen,” “restricted,” or “under investigation.” You may still be able to receive (credits) but not withdraw (debits) — that asymmetry is the tell. What’s really happening: a PMLA/AML freeze or the RBI KYC Direction’s graduated freeze. Recall the mechanism: the entity must give three months’ notice, then a partial freeze (credits allowed, debits blocked), then after six more months a full freeze. A debit-only block is the partial-freeze stage. The fix: this is the serious one. Demand a written reason and a timeline for the freeze. If it’s a KYC-lapse freeze, completing the re-KYC should restore debits. If it’s an AML-suspicion freeze, you may need to provide source-of-funds documentation. Crucially, a freeze imposed without the prescribed three-month notice is itself a deviation you can cite when you escalate to the bank’s grievance officer and the RBI Ombudsman. Door: the bank/entity’s grievance officer first, then the RBI Integrated Ombudsman after 30 days — because a frozen payment account is squarely within RBI’s reach.

State 5 — Risk / AML hold (temporary review, not a freeze)

Symptom: the payout — or the account — is “under review” for a defined-ish period, often after a win spike, a large first withdrawal, or unusual activity. It’s not framed as a permanent freeze. What’s really happening: the operator’s anti-fraud system flagged a pattern (sudden large win, new account, high-value pull) and routed it to manual review or a temporary hold. This is a gaming-app risk layer sitting on top of the bank’s KYC. The fix: wait the stated window, then ask support in writing to confirm it’s a routine review and give a timeline. Keep the ticket ID. Don’t spin up a “new” account to escape it — that converts a temporary hold into a permanent duplicate-flag (State 6). A risk hold usually clears on its own; the job is to document it and not make it worse. Door: app support, in writing, with the ticket ID retained for the 30-day clock.

State 6 — Duplicate / multi-account flag

Symptom: the account is blocked citing “multiple accounts,” “duplicate device,” or “terms violation.” What’s really happening: the anti-fraud system sees the same device, IP, or payment instrument across accounts and freezes the payout pending review. Often triggered by a player who made a “fresh” account to dodge an earlier hold. The fix: stop creating accounts immediately. Contact support from your registered number, explain, and ask for the specific reason in writing. Recovery here is harder because the flag implies a terms breach, but a genuine accidental duplicate (e.g. a shared family device) can often be cleared by explaining it honestly. Never escalate by making another account — each one deepens the flag. Door: app support with your registered number; this is a terms dispute, so your leverage is honesty and documentation, not the payment rail.

The six-state taxonomy in one line: States 1, 2, 3 are document problems (you fix the documents and re-submit). States 4, 5 are review/freeze problems (you demand a written reason and a timeline, and escalate a payment freeze to the bank then RBI). State 6 is a terms problem (stop multi-accounting and explain honestly). Sorting your case into the right state is the difference between a fix in 48 hours and a month of pushing on the wrong door.

The diagnostic order — which state to check first, and why

Don’t check the six states in a random order. There’s a correct sequence, because the cheaper, more common problems should be ruled out before you escalate to the serious ones. Working out of order wastes days — you’ll file a freeze complaint when your real issue was a name mismatch you could have fixed yourself in an hour. Here is the order, with the reasoning.

Step 1 — Confirm it’s actually KYC, not a balance-pot or limit issue (5 minutes). Before anything, check that the money you’re trying to withdraw is in the withdrawable winnings pot, not a bonus pot, and that you’re above the minimum and under any daily cap. A huge share of “KYC blocked me” reports are actually a non-withdrawable bonus or a hit daily limit. The withdrawal hub covers the pots; if it’s a limit, that’s not a KYC problem at all. Only proceed if the money is genuinely withdrawable.

Step 2 — Check KYC completeness (State 1) — is anything simply unfinished? Open the KYC section. Are all four links green — PAN, Aadhaar/OVD, bank, selfie/video? The most common “pending forever” cause is a skipped selfie/video step the player never noticed. This is the cheapest possible fix, so rule it out first.

Step 3 — Check for an explicit rejection (State 2) — did a document bounce? If there’s a rejection reason, you have State 2. Re-submit only the failed document, clean. For an inoperative PAN, link to Aadhaar before re-submitting — re-uploading the same unlinked PAN will fail again.

Step 4 — Check names across all four documents (State 3) — the silent killer. If KYC looks complete and nothing was rejected but the payout still hangs, suspect a name mismatch. Lay PAN, Aadhaar, and your bank account name side by side. Any difference — initials vs full name, an extra middle name, a spelling variance — parks the payout. This is the most common silent stall, which is why it’s checked after the obvious-error states but before the serious ones.

Step 5 — Distinguish a review-hold (State 5) from a freeze (State 4). If the documents are all clean and matched, you’re into the review/freeze territory. The tell: a review-hold is framed as temporary and usually follows a win spike or large pull — wait and document it. A freeze is framed as restriction/investigation and often blocks debits while allowing credits — that asymmetry means escalate, don’t wait.

Step 6 — Rule out a duplicate-flag (State 6). If support cites “multiple accounts” or “duplicate device,” you’re in State 6 — stop creating accounts and explain from your registered number.

The diagnostic order takeaway: go cheap-to-serious — pot/limit, then completeness, then rejection, then name-match, then review-vs-freeze, then duplicate. Four out of five silent stalls turn out to be a name mismatch (State 3), so if your KYC “looks fine” but the money won’t move, check the names before you assume a freeze. Escalating a name mismatch as a freeze wastes the 30-day Ombudsman clock you might genuinely need later.

The universal escalation chain for a KYC-locked account

Once you’ve diagnosed your state, you climb a ladder. The ladder is the same spine the whole site uses, tuned here for verification and freeze problems. Each rung matches a specific authority to a specific problem type. Don’t skip rungs (you’ll waste days), and don’t jump to RBI on day one (they’ll bounce you back to the entity). Climb in order.

Rung 1 — In-app KYC flow + support ticket (Day 0)

The highest-leverage move is documentation plus the right first action. Within the first hour:

• Re-check the KYC section yourself. Half of all “blocked” accounts are a State 1 or State 2 problem you can clear without contacting anyone — finish the skipped step, re-submit the clean document.
• Screenshot everything: the KYC status screen, any rejection reason, the withdrawal screen, the amount, the timestamp, and your registered number. Date-stamped screenshots are your evidence later.
• Raise an in-app support ticket stating the exact state (“KYC rejected — reason X” / “account frozen — debits blocked”) and get a ticket/complaint ID in writing. That ID timestamps your complaint for the 30-day Ombudsman clock.

Never share an OTP or UPI PIN with anyone who “calls to help unblock your KYC.” Legitimate verification never needs your PIN or OTP — that’s a phishing script, covered in the red-flags section below.

Rung 2 — Official support email / grievance officer (Day 1–3)

• Send the same complaint by the app’s official support email (from its Play listing or official site), referencing the in-app ticket ID. Email creates a paper trail an in-app chat can’t.
• For a State 4 freeze, this is where you demand a written reason and a timeline, and ask whether the three-month notice procedure was followed. For a State 5 review, ask for confirmation it’s routine and a clear ETA.
• If the app publishes a 24–72-hour KYC SLA, you may still be inside it — be firm but patient.

Rung 3 — Bank / NPCI for the rail side (Day 4–7)

This rung applies when the failure has reached the payment rail — a name-mismatched beneficiary, a frozen bank account, or a “paid but not received” payout.

• For a bank-side name mismatch or a frozen receiving account, the door is your bank’s grievance officer, not the app — the app verified you, but the bank is rejecting the credit or holding the account.
• For a UPI payout that was debited but never credited, raise the dispute through your UPI app (it feeds NPCI’s UDIR), or call your bank with the UTR. The deeper mechanics — the T+1 auto-reversal and the ₹100/day compensation under RBI’s failed-transaction circular — are in the spoke UPI failed, money debited.

Rung 4 — RBI Ombudsman (Day 30+)

If the regulated entity — your bank or the payment-system participant — hasn’t resolved a frozen account or a failed payment within 30 days:

• File with the RBI Integrated Ombudsman Scheme 2021 (RB-IOS) at cms.rbi.org.in. RB-IOS covers banks, NBFCs and Payment System Participants, and redress is free.
• This is your strongest lever for a State 4 freeze on a bank/payment account, because that account is RBI-regulated. A freeze imposed without the prescribed three-month notice is a service deficiency the Ombudsman can act on.

Rung 5 — Consumer forum / cybercrime (parallel)

• For a service deficiency — an app refusing to release a clearly-owed, KYC-clean balance — run the National Consumer Helpline 1915 in parallel.
• If you suspect fraud — a fake “KYC verification” call, a phishing “customer care number,” a clone app, an OTP scam — report immediately to the cybercrime helpline 1930 and cybercrime.gov.in, and flag suspicious payment entities on RBI’s Sachet portal.

Honest limit of this ladder: it’s powerful against a frozen or failed bank/payment account (RBI-regulated) and against a rail failure (NPCI/RBI rules force a refund). It’s weaker against a shady offshore or unlicensed app that simply ignores your KYC and pockets the balance, because that operator may sit outside Indian regulatory reach. That asymmetry is the single best reason to only ever verify and play where KYC is real and payouts are clean. For the full who-to-call map and the scam-number warning, see Teen Patti Master customer care.

Why the three-month-notice rule is your strongest freeze argument

Most players treat a freeze as a black box — the account is locked, end of story. It isn’t. The RBI KYC Direction prescribes a specific sequence before a KYC-lapse freeze can bite, and any deviation from that sequence is leverage you can name in writing. The sequence is: a notice of at least three months to bring KYC up to date; if unmet, a partial freeze that allows only credits and blocks debits; and only after a further six months of non-compliance, a full freeze of all operations (per RBI’s freeze procedure).

That timeline does two things for you. First, it tells you which stage you’re at: a debit-only block means you’re at the partial-freeze stage, which is reversible the moment you complete re-KYC — you are not yet at a full freeze. Second, it gives you a compliance test to apply to the entity: did it issue the three-month notice before freezing? If your account went from working to debit-blocked overnight with no prior notice, that abruptness is itself a procedural deviation. When you escalate (Template B, then the Ombudsman), state plainly that you received no three-month notice and ask the entity to justify the freeze against the prescribed steps. Entities settle faster when a complainant clearly knows the procedure they’re supposed to follow.

A separate note for AML/PMLA freezes, which are a different animal from a KYC-lapse freeze. An AML freeze flows from a suspicion of money laundering, not a missing document, so completing re-KYC alone may not lift it — you may need to demonstrate source of funds for the flagged credits. The WinZO case is the template at scale: accounts frozen under PMLA, with de-freezing pursued by offering a bank guarantee and demonstrating compliance. An individual won’t post a bank guarantee, but the principle carries: an AML freeze is lifted by evidence, not by argument, so gather your deposit records, your TDS statements, and any winnings history before you escalate.

Copy-paste escalation templates for KYC and freeze problems

Fill in the bracketed parts. Keep every message factual, dated, and ID-stamped — emotion doesn’t unblock an account, a clear written record does. There are four here, one per problem type.

Template A — KYC rejected, re-submission + clarification (Day 0–1)

Subject: KYC rejected — request reason and re-verification

My KYC was rejected on [DATE] with the message "[REJECTION REASON
shown in app]". My withdrawal of ₹[AMOUNT] is blocked as a result.
Registered mobile: [NUMBER]
Documents submitted: PAN [last 4], Aadhaar/OVD, bank A/C, selfie/video
Please specify exactly which document failed and the reason, so I can
re-submit only that document. My PAN name, Aadhaar name and bank
account name are: [exact names]. Please share a ticket/complaint ID.

Template B — Account frozen, demand written reason + timeline (Day 1–3)

Subject: [Ticket ID] Account frozen — request written reason, basis,
and restoration timeline

My account [registered mobile NUMBER] shows "[frozen / restricted /
under investigation]" since [DATE]. Debits are blocked; a balance of
₹[AMOUNT] is held.
Please provide in writing:
1. The specific reason and legal basis for the freeze.
2. Whether the RBI KYC Direction's three-month notice was issued, and
   when.
3. The exact steps and documents required to restore the account.
4. A timeline for resolution.
If this is a KYC-lapse freeze, confirm what re-KYC is needed. If
unresolved within [N] days I will escalate to the bank grievance
officer and the RBI Integrated Ombudsman (RB-IOS 2021).

Template C — Bank grievance for a frozen/mismatched receiving account (Day 4–7)

Subject: Grievance — receiving account [A/C] frozen / credit rejected

My account/UPI [A/C or HANDLE] is unable to receive a credit of
₹[AMOUNT] from [APP/operator], reference/UTR [UTR if any].
Issue: [account frozen for KYC / beneficiary name mismatch / other].
My KYC name on PAN and Aadhaar is [NAME]; my account-holder name is
[NAME]. Please confirm the exact discrepancy and the steps to resolve,
and whether any freeze followed the prescribed notice procedure.
Please share the complaint reference number.

Template D — RBI Ombudsman (RB-IOS) for an unresolved freeze (Day 30+)

Nature of complaint: Deficiency in service — account/payment freeze or
failed credit unresolved by the regulated entity.

Regulated entity: [YOUR BANK / payment system participant]
Account/UPI: [A/C or HANDLE]
Issue raised with the entity on: [DATE], reference [REF]
Nature: [account frozen with debits blocked / KYC-linked freeze /
failed credit] held since [DATE], amount ₹[AMOUNT].
Entity's response: [none / unresolved] after 30 days. Three-month
notice [was / was not] issued before the freeze.
Relief sought: restoration of the account / release of ₹[AMOUNT] to my
registered account, and a written reason for the freeze.

File Template D at cms.rbi.org.in only after 30 days without resolution from the entity — that 30-day rule is the eligibility gate for RB-IOS 2021. For deeper, app-specific contact channels and the full grievance map, the customer-care hub and its Master care spoke go further.

Grievance contact reference block

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

Order of doors, in one line: app KYC flow → app grievance → bank → NPCI → RBI Ombudsman, with consumer helpline 1915 in parallel for app-side deficiency and cybercrime 1930 the instant a fake-KYC scam is involved.

The post-PROGA wind-down angle: recovering a balance from a KYC-locked discontinued app

This is the 2026 problem that didn’t exist a year ago, and it deserves its own treatment because the usual “finish your KYC and withdraw” advice runs into a discontinued cash product. Read this if your balance is stuck inside an app that stopped running cash games after PROGA.

What changed, and what it means for your balance

PROGA 2025 banned all online money games, and its 2026 Rules came into force on 1 May 2026. The major operators suspended cash formats from late August 2025. So if you had a balance in RummyCircle, Junglee Rummy, Dream11, MPL, Adda52, or PokerBaazi, the game is gone — but your money isn’t supposed to vanish with it.

Here is the crucial correction almost every guide gets wrong. The draft 2026 Rules (released October 2025) contained a provision — widely cited as Rule 24 — that would have created a roughly 180-day, platform-led refund window in which a winding-down operator had to remit pending user balances without the transfer counting as facilitating a money-gaming transaction. That user-fund refund provision did not survive into the final notified Rules. When MeitY notified the Rules in the Gazette on 22 April 2026 (in force 1 May 2026), the refund safe-harbour was cut, on the stated basis that existing law already covers the matter (Mondaq; iGaming Business; PIB press release). So there is no statutory 180-day refund window and no legal deadline forcing an operator to pay you out. What actually protects your balance is more ordinary, and you should not over-rely on it: in practice banks and payment intermediaries stopped permitting new deposits while continuing to process withdrawals, specifically so users could recover existing balances (per the reset analysis), and behind that voluntary wind-down sit your existing rights under consumer-protection law and the RBI/NPCI payment rules, plus the PROGA grievance ladder. The route for getting your money out runs through a KYC-verified account — and because it is voluntary rather than mandated, acting early matters more, not less.

Why KYC matters more, not less, on a wind-down

Here’s the trap. A discontinued operator processing a wind-down repayment is making a regulated, reported remittance — which means it needs your KYC to be complete and clean before it can pay. An account that was only ever half-verified (you never withdrew, so KYC never triggered) suddenly must be fully verified to receive the wind-down payout. Players who deposited, played, and never cashed out are often discovering their KYC was never finished — and now they need it finished to recover the balance.

The practical sequence for a wind-down recovery:

1. Complete KYC fully on the discontinued app, even if you never needed to before. All four links — operative PAN, Aadhaar/OVD, name-matched bank, selfie/video — must hold.
2. Use the remaining in-app withdrawal/recovery flow. Operators kept a withdrawal path open for exactly this.
3. Expect TDS. A wind-down payout of net winnings still attracts 30% under Section 194BA — the cut isn’t theft, it’s tax reported against your PAN.
4. Act fast — there is no statutory deadline protecting you. The draft Rules’ ~180-day refund window was dropped from the final notified Rules, so no law forces the operator to repay you by a fixed date (Mondaq). The wind-down withdrawal flow is voluntary, and a winding-down company’s support and systems only get thinner over time — so the urgency is real precisely because there is no legal safety net. Don’t sit on a half-finished KYC.
5. Never re-deposit. A new deposit into a money game is now illegal. No legitimate recovery ever requires you to “add money to unlock” a withdrawal — that’s both a scam pattern and an illegal act.

What if the operator simply won’t pay the wind-down balance?

If a discontinued operator stonewalls a clean, KYC-complete recovery, you’re no longer in a “gaming dispute” — you’re in a payment-deficiency dispute, and the rail-side levers apply. This is exactly where the dropped refund rule matters: because there is no statutory refund window to point at, your leverage comes from existing law, not a PROGA deadline. Escalate it as a deficiency in service under consumer-protection law (Template B/C above), push the bank under the RBI/NPCI rules if a credit was attempted and failed, and after 30 days take an unresolved payment failure to the RBI Ombudsman. You can also run the PROGA grievance ladder — complain to the operator, escalate to the Online Gaming Authority of India (OGAI) within 30 days, then to the Secretary, MeitY — though for a banned money game’s stranded balance the payment-rail and consumer routes are usually stronger. The WinZO episode shows the regulatory machinery is active, but the refund itself rests on existing rights and the operator’s voluntary process, not on a guaranteed repayment deadline.

The wind-down takeaway: a discontinued app still owes you your balance, but not because of any statutory deadline — the draft Rules’ ~180-day refund window was dropped from the final notified Rules, so recovery rests on the operator’s voluntary wind-down flow plus your existing consumer and RBI/NPCI rights and the OGAI grievance ladder (Mondaq). And it pays out only into a fully KYC-verified account. So if you never finished KYC because you never withdrew, finishing it now is the entire recovery task. Complete the four-link chain, use the remaining withdrawal flow, expect 30% TDS on net winnings, and never re-deposit (it’s illegal). Because there is no legal safety net forcing a deadline, act fast; if the operator stonewalls a clean recovery, it becomes a payment-deficiency dispute you escalate through the bank, RBI and the consumer route.

State-by-state nuance: KYC behaviour on the major apps

KYC enforcement isn’t uniform; the major operators wrote it differently, and the differences shape where you’ll hit a wall. The numbers below split operator-claimed (what the app’s help pages stated) from observed / realistic (widely reported behaviour, framed third-person — not a personal test). Treat the claimed column as the promise and the observed column as the planning assumption. All major operators here also deduct 30% TDS on net winnings under Section 194BA at the verified payout — KYC is what makes that reporting possible.

A blunt caveat for 2026: RummyCircle and Junglee Rummy discontinued cash games under PROGA, so their rows describe how KYC worked and how it now gates a wind-down recovery. Teen Patti Gold and Teen Patti Master are informal-brand card apps distributed largely outside the Play Store, so their published KYC rules are less authoritative and the observed column matters more.

Junglee Rummy (cash games discontinued — KYC now gates wind-down recovery)

RummyCircle (cash games discontinued — KYC now gates wind-down recovery)

Teen Patti Master

Teen Patti Gold

Editor’s verdict on the per-app tables: stop treating a third-party “Teen Patti Gold KYC” page as gospel — these informal-brand card apps run many skins with different rules, and the only authority is the exact build you installed. For RummyCircle and Junglee Rummy, the cash product is gone; your KYC task there is purely to unlock the operator’s voluntary wind-down recovery flow — there is no statutory refund deadline (the draft’s Rule 24 window was dropped), so finish the four-link chain promptly and never re-deposit.

Red flags: when a “KYC problem” is actually a scam

Most KYC blocks on legal apps are genuine verification gates. But scammers have learned that “your KYC needs verification” is the perfect pretext to phish you — because it sounds official and players expect KYC friction. Use these red flags to tell a real verification step from a theft attempt.

• A call or message asking you to “complete KYC” via a link, an OTP, or a UPI PIN. Real KYC happens inside the app, never by reading an OTP to a caller or entering your UPI PIN to “verify.” Sharing an OTP/PIN is the entire scam. Legitimate verification never needs your PIN or OTP. Report the number to 1930 / cybercrime.gov.in.
• A “customer care number” found on a random website, YouTube comment, or search ad. Most legal apps have no public phone helpline and route support in-app. A “KYC support number” you didn’t get from the official listing is overwhelmingly a phishing trap. Never call back such a number.
• “Pay a KYC verification / unblocking fee to release your withdrawal.” No legal app charges a fee to complete KYC or unblock an account. A demand for money to “verify” or “unlock” is theft — and if it’s “deposit to unlock,” it’s also illegal post-PROGA.
• A request to KYC with someone else’s documents, or to use a “verification agent.” This isn’t a shortcut; it’s identity fraud that gets the account permanently frozen and may implicate you. There is no legitimate third-party “KYC agent” for a gaming withdrawal.
• A sideloaded “mod” / “unlimited chips” APK that now demands KYC. Modified builds void the app’s terms and can freeze your account and balance with no recourse — the balance you’re trying to verify may already be forfeit by the app’s own rules.

If two or more of these are true, the realistic verdict is harsh: pursue any payment-rail loss through the bank/UPI dispute and a cybercrime report, but lower your expectation of recovering a balance held inside an unlicensed operator — and never feed it another rupee or another OTP. The companion red-flags treatment in the withdrawal hub covers the rail-side scam patterns; this page covers the KYC-pretext ones.

How to do KYC right the first time (so it never blocks you)

The cheapest KYC fix is the one you never need. If you’re verifying a new account — or re-verifying for a wind-down recovery — these are the steps that prevent the six states from ever triggering. Each maps to a failure mode above.

1. Make every name identical. Before you upload anything, confirm your PAN name, Aadhaar name, and bank account-holder name are character-for-character the same. Fix the odd one first — usually at the bank or via a PAN/Aadhaar correction — because a mismatch is the single most common stall. This one step prevents State 3 entirely.
2. Link PAN to Aadhaar and confirm it’s operative. An inoperative PAN fails KYC silently and triggers higher TDS. Check your PAN’s status on the income-tax portal; if it’s inoperative, link it (₹1,000 fee where the deadline lapsed) before you submit gaming KYC.
3. Use one bank account in your own name for both deposit and withdrawal. Don’t deposit from a card and withdraw to a different account — and never use a family member’s account. Same account, your name, both directions.
4. Shoot document images cleanly. Full document in frame, good light, no glare, no cropping. A blurry image is the most common State 2 rejection, and it’s entirely avoidable.
5. Complete the selfie/video step. Don’t leave KYC at “pending” because you skipped the liveness check — it’s the most common State 1 cause. Good lighting, face clearly visible, match the document photo.
6. Verify before you need a big payout. Do your KYC — even a small ₹100 test withdrawal — before you have a large balance riding on it. A first payout gets the strictest manual review, so you want that friction out of the way while the stakes are low.

The do-it-right takeaway: identical names + operative Aadhaar-linked PAN + one own-name account + clean images + completed liveness, done before a big balance depends on it. Five of the six account states trace back to something in this checklist. Getting it right once means the only state you could ever hit is a risk-review on an unusually large win — and that one just needs patience and a ticket ID.

Related fixes (go deeper on your exact case)

This is the KYC and account-recovery hub. For the case that matches your state, these go step-by-step:

• Your money is stuck but it’s a withdrawal mechanics problem, not verification → 3 Patti withdrawal: why it’s stuck and how to fix it — the balance pots, the four payout gates, and the full Day-0-to-30 ladder.
• Withdrawal stuck / “pending” / “processing” → withdrawal stuck fix — the pending-state countdown and which gate you’re parked at.
• Money debited from your bank but never credited → UPI failed, money debited — the T+1 auto-reversal, the ₹100/day claim, and the UDIR dispute screens.
• Can’t reach the app to resolve a freeze → Teen Patti Master customer care — official channels and the scam-number warning.

FAQ

1. What is KYC on a Teen Patti or rummy app, and why is it mandatory? KYC (Know Your Customer) is the PAN + Aadhaar + bank verification an app must complete before paying you cash. It’s mandatory under three laws: PMLA 2002 (anti-money-laundering), the RBI Master Direction on KYC, 2016, and Section 194BA, which requires 30% TDS to be reported against your PAN. The operator cannot legally waive it.

2. Why did my Teen Patti KYC get rejected? Usually one of four reasons: a blurry document image, an inoperative PAN (not linked to Aadhaar), a name mismatch across PAN/Aadhaar/bank, or an unreadable address. Read the rejection reason, then re-submit only the failed document, clean. For an inoperative PAN, link it to Aadhaar first — re-uploading the same unlinked PAN will fail again.

3. My KYC is “pending” and never completes — what do I do? Check whether a step is simply unfinished — most often the selfie/video liveness check was skipped. Complete every link (PAN, Aadhaar, bank, selfie/video). If all four are submitted and it’s been pending past the app’s stated window (commonly 24–72 hours), raise an in-app ticket with a screenshot. This is the easiest state to clear because nothing was rejected.

4. My name is slightly different on PAN and my bank — does that block withdrawal? Yes — a one-character difference is enough. “RAHUL K” on your UPI handle versus “Rahul Kumar” on PAN parks the payout for manual review with often no error message. Make your bank/UPI account-holder name match your PAN exactly, fix the wrong one at the bank, and use the same account for deposit and withdrawal. This is the single most common silent stall.

5. My PAN looks valid but KYC still fails — why? Your PAN may be inoperative because it isn’t linked to Aadhaar. An inoperative PAN fails verification and triggers higher TDS under Section 206AA (per the PAN-Aadhaar rules). Check the status on the income-tax portal and link PAN to Aadhaar (a ₹1,000 fee where the deadline lapsed) before re-submitting.

6. My account is frozen — is that legal, and how do I unfreeze it? A freeze can be legal under PMLA (AML suspicion) or the RBI KYC Direction’s graduated process: three months’ notice → partial freeze (credits allowed, debits blocked) → full freeze after six more months (per RBI’s procedure). Demand a written reason and timeline. A KYC-lapse freeze lifts when you complete re-KYC; an AML freeze may need source-of-funds proof. A freeze without the prescribed notice is a deficiency you can escalate to the RBI Ombudsman.

7. What’s the difference between an account freeze and a risk hold? A freeze (State 4) is framed as restriction/investigation, often blocks debits while allowing credits, and you should escalate it. A risk hold (State 5) is framed as temporary, usually follows a win spike or large first withdrawal, and usually clears on its own — wait the stated window, then ask support in writing for a timeline and keep the ticket ID.

8. The app says I have a “duplicate account” — can I recover the balance? This is State 6 — the anti-fraud system saw the same device, IP, or payment instrument across accounts. Stop creating accounts immediately, contact support from your registered number, and ask for the specific reason in writing. A genuine accidental duplicate (shared family device) can often be cleared by explaining honestly. Never make another account to escape it — each one deepens the flag.

9. Can I withdraw my balance from RummyCircle or Junglee Rummy after the ban? Yes — their cash games are discontinued under PROGA, and the operators kept withdrawals open so users could recover existing balances. But there is no statutory deadline forcing them to refund you: the draft 2026 Rules’ ~180-day refund window (often cited as Rule 24) was dropped from the final notified Rules, on the basis that existing law already covers it (Mondaq; iGaming Business). Recovery rests on the operator’s voluntary wind-down plus your existing consumer/RBI rights, so complete KYC fully, use the remaining withdrawal flow promptly, expect 30% TDS on net winnings, and never re-deposit — a new deposit is now illegal.

10. I never withdrew, so I never did KYC — now I can’t get my wind-down balance. What now? Finishing KYC is the entire recovery task. A wind-down repayment is a regulated remittance, so the operator needs your KYC complete and clean to pay. Complete all four links — operative PAN, Aadhaar/OVD, name-matched bank account, selfie/video — then use the in-app recovery flow. There is no statutory window protecting you (the draft Rules’ ~180-day refund rule was dropped from the final notified Rules), so the urgency is real precisely because the wind-down is voluntary — don’t sit on a half-finished KYC.

11. Do I have to use Aadhaar for gaming KYC? Not strictly — under the RBI KYC Direction, Aadhaar is an Officially Valid Document offered voluntarily, and other OVDs (passport, voter ID, driving licence) are accepted for identity/address. But PROGA-era age-gating mandates Aadhaar-based or equivalent age verification, and PAN is non-negotiable for the tax reporting — so in practice you’ll provide PAN plus one OVD.

12. Someone called offering to “verify my KYC” over the phone — is that safe? No — it’s a scam. Real KYC happens inside the app, never by reading an OTP to a caller or entering your UPI PIN to “verify.” Legitimate verification never needs your PIN or OTP, and no legal app charges a “KYC fee” to unblock an account. Report the caller to the cybercrime helpline 1930 and cybercrime.gov.in.

13. How long does KYC take to verify on a gaming app? Auto-verification can be near-instant for clean documents; manual review commonly takes 24–72 hours, and a first-ever payout gets the strictest review. If KYC is genuinely complete and you’re past 72 hours with no response, raise an in-app ticket, then escalate by official email referencing the ticket ID.

14. Where do I escalate a frozen gaming account that the app won’t unblock? Climb in order: app grievance email (demand a written reason), then your bank’s grievance officer if a bank/payment account is frozen, then after 30 days without resolution file free with the RBI Integrated Ombudsman (RB-IOS 2021) at cms.rbi.org.in. Run the National Consumer Helpline 1915 in parallel for app-side deficiency, and report any fake-KYC scam to 1930.

15. Will completing KYC give me back money the app already took as TDS? No — and that’s not a KYC problem. 30% TDS under Section 194BA is tax correctly deducted from your net winnings and reported against your PAN in Form 26AS / AIS; you reclaim it when you file your ITR, not by re-doing KYC. A payout that’s 30% smaller than your winnings is tax, not a verification block.

Sources & method. The KYC laws, freeze mechanics, document requirements and escalation steps on this page are built from primary regulatory sources and named operator help pages — not personal account tests. Key references: the RBI Master Direction on KYC, 2016 and its updation/freeze FAQs; the Prevention of Money Laundering Act, 2002; the RBI Integrated Ombudsman Scheme 2021 and cms.rbi.org.in; the RBI Sachet portal; NPCI UPI Help / UDIR and RBI’s failed-transaction TAT circular; Section 194BA and the PAN-Aadhaar linking / inoperative-PAN rules; the Promotion and Regulation of Online Gaming Act, 2025 and its Rules effective 1 May 2026, the PIB press release on the notified Rules, and the analyses confirming the draft’s ~180-day user-fund refund provision (cited as Rule 24) was dropped from the final notified Rules (Mondaq PROGA reset analysis; iGaming Business); the ED PMLA freeze of WinZO accounts; operator KYC pages for Junglee Rummy and RummyCircle; cybercrime reporting at cybercrime.gov.in / helpline 1930; National Consumer Helpline 1915. This page is information, not legal or financial advice — verify each step against your operator’s current Terms, your bank’s policy, and the current PROGA Rules.