Gaming Refund India: The Money-Dispute Recovery Decision Tree

The 30-second answer

A gaming refund in India turns on which of four losses you have. A rail failure (debited, not credited) auto-reverses by T+1 under RBI rules. A deposit dispute may use a chargeback. A trapped balance is user-led recovery after PROGA dropped its 180-day refund rule. A fraud loss goes to 1930. Strong rights against the bank, weak against an operator.

Editor’s verdict, up front. Almost every “I want my money back from a gaming app” search is one of four distinct losses wearing the same shirt, and people lose weeks because they pick the wrong door. A rail loss is the easy one — the RBI rulebook forces a refund and your bank is on the hook. A deposit dispute is winnable through a chargeback but can get your card blacklisted across a hundred operators, so it’s a last resort, not a first move. A trapped balance after the 2025 ban is the genuinely hard case, made harder because the government quietly removed the rule that would have forced platforms to refund you. A fraud loss is a race against the clock, where the first hour decides whether you ever see the money again. This page is the master map: classify the loss, read its section, follow the link to the spoke that goes deep. Pour no more deposits into a stalled or frozen account while you sort this out — post-PROGA, that deposit is also illegal.

2026 reality you must read first. The legal ground moved hard. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) received Presidential assent on 22 August 2025 and prohibits all online money games — skill or chance — where you stake money for a return. The operating Rules came into force on 1 May 2026. India’s biggest operators — RummyCircle, Junglee Rummy, Dream11, MPL, Adda52, PokerBaazi — suspended cash formats from late August 2025. The cruel twist for refunds: a draft Rule 24 would have given platforms and banks a 180-day window to return user funds without it counting as “facilitating” a banned game — but that provision was omitted from the final notified rules, shifting the burden of recovering stuck balances from platforms to users. So in mid-2026 the common problem is no longer “my live app is slow” — it’s “a discontinued app holds my balance and nobody is obliged to push it back to me.” The good news: banks kept processing withdrawals so users could pull existing balances out, and the RBI/NPCI rail protections still cover any rail-side leg of that recovery. This guide reads for all four loss types, and flags which door each one opens.

Why classifying the loss is 90% of the recovery

Most refund advice on the internet is generic — “contact support, then escalate” — and it fails because it treats four different problems as one. The single decision that determines whether you get paid is not how hard you fight. It is which kind of loss you have, because each kind has a different counterparty, a different rulebook, and a wildly different probability of success.

Here is the distinction the whole page turns on: you have strong, enforceable rights against the bank and the payment rail, and weak rights against the operator — especially an unlicensed or offshore one. The rail (UPI, IMPS, NEFT) is run by banks and aggregators regulated by the Reserve Bank of India (RBI), with hard timelines, a free ombudsman, and ₹100/day penalties built into the law. The operator is a gaming company you signed a terms-of-service contract with, and post-PROGA many of them are winding down, offshore, or simply gone. When your money is on the rail, you have leverage. When your money is inside the operator’s wallet, you mostly have a contract claim and a grievance form.

So the very first thing to find out is where your money actually is right now — and the four-way classification below answers exactly that. Get this right and an easy case resolves in three days; get it wrong and you spend a month shouting at the operator about money the rail already owes you, or filing a chargeback that gets your card blacklisted when a simple bank dispute would have worked.

The four classes in one table

Read that table top to bottom as a difficulty gradient. Class (a) is the recoverable one; class (d) is the one where speed matters more than anything. Find your row, then read its full section below — each one names the channel, the realistic odds, and the spoke that goes screen-by-screen.

How to classify your own loss in 60 seconds

Before the deep sections, run this short triage. Answer four questions in order and you’ll land in exactly one class.

1. Did money leave your bank or wallet and simply never arrive where it was supposed to go? If a payout was debited from the app and never hit your bank, or a deposit was debited from your bank and never showed as chips, and the screen says “failed” or “pending” — that’s a rail failure (class a). The rail owes you a refund. This is the best case.
2. Did the deposit go through correctly, but you now want it reversed — because you deposited by mistake, the amount was wrong, you were charged twice, or you’ve decided you shouldn’t have? That’s a deposit dispute (class b), and the tool is a chargeback. Read the warnings before you fire it.
3. Is the money sitting inside the app — a balance you won or deposited that you can see but can’t withdraw, because the account is frozen, under review, or the operator has wound down? That’s a trapped balance (class c). Your leverage is the operator’s grievance process and, for any rail leg, the bank.
4. Did you send money to someone because of a scam — a fake customer-care number, a “deposit to unlock your withdrawal” demand, a phishing link, a clone app, an OTP/PIN you shared? That’s a fraud loss (class d). Call 1930 now, before you finish reading.

If two seem to fit, pick the one earliest in this list — it has the strongest recovery path. A “failed deposit” that’s really a rail failure (class a) is far easier to recover than treating it as a trapped balance (class c). The whole point of classifying first is to claim the strongest right available to you.

One number to anchor on: the RBI failed-transaction circular forces a refund within T+1 for class (a), automatically. No other class has a guarantee that strong. So if there’s any chance your loss is a rail failure, test that first — it’s the one door that’s legally obligated to open.

Class (a): Rail failure — debited but not credited (the recoverable one)

This is the class with the strongest consumer protection in the entire chain, and it’s the one most worth getting right, because the rules already force a refund. A “rail failure” means the money left somewhere — your bank account on a deposit, or the app’s wallet on a payout — and the matching credit never confirmed. The transaction sits in a deemed-failed / pending state, and the rail’s own rules govern the bounce-back.

What is actually happening on the rail

“UPI is instant” is true only for the successful path. The failure path runs on reconciliation cycles, which is why a failed transaction can sit in limbo for up to a day before it reverses. When a UPI transfer is initiated, money is debited at the sending side and a credit instruction goes to the receiving bank. If that bank doesn’t confirm the credit — it was down, the handle didn’t resolve, the session timed out — the transaction is now failed-but-unreversed. It does not reverse the instant the screen says “failed.” The banks reconcile these in cycles, governed by RBI’s Harmonisation of Turn Around Time (TAT) circular.

The rule that forces your refund

Per RBI Circular DPSS.CO.PD No.629/02.01.014/2019-20, dated 20 September 2019, the binding numbers are:

• Account-to-account UPI where you were debited but the beneficiary wasn’t credited: auto-reversal is due by T+1 (the day after). If the bank misses that, it owes you ₹100 per day of delay beyond T+1, credited automatically — you don’t have to ask.
• UPI to a merchant where confirmation failed: the auto-reversal window is up to T+5 before the same ₹100/day compensation begins.

The RBI’s own description of the circular is explicit that it covers failures “not directly attributable to the customer” — communication-link disruption, session time-outs, non-credit to the beneficiary’s account, and similar system causes. A stuck app-to-you payout, or a deposit debited that never became chips, is precisely a system path, so it’s covered. (The ₹100/day does not apply to your own mistakes, like sending to a wrong handle — but a stuck operator-side transfer is a system failure.)

The channel and the realistic odds

The mechanism that processes these is NPCI’s Unified Dispute and Issue Resolution (UDIR) system. UDIR is an automated, single-channel redressal platform launched in 2020 that resolves disputes through API calls rather than manual files, and — this is the key feature — it can auto-convert an unresolved complaint into a chargeback once the prescribed TAT lapses. NPCI’s revised dispute TAT keeps transaction data in URCS for 45 days, so you must raise the dispute within 45 days — beyond that, the transaction can no longer be searched. From February 2025, NPCI’s Transaction Credit Confirmation (TCC) rule automates chargeback approval/denial so disputes settle faster without manual bank review.

The realistic odds here are high. This is a rule-mandated, largely automatic refund. You surface it at the NPCI UPI Help portal (upihelp.npci.org.in), via your UPI app’s “raise complaint” button, or at the NPCI UPI line 1800-120-1740. NPCI’s stated UDIR resolution window is 3–5 working days.

The move, in order

1. Capture the UTR on Day 0. The 12-digit reference is the single thread tying your debit to a missing credit. No UTR, no trace.
2. Wait through T+1 if the screen says “failed” — the auto-reversal may run on its own.
3. Past T+1, raise the UPI dispute on that transaction (it feeds UDIR), or call your bank’s failed-transaction desk with the UTR and ask explicitly for the ₹100/day if you’re past the window.
4. Past the rail’s TAT with no resolution, escalate to the bank’s grievance officer, then the RBI Ombudsman after 30 days.

The screen-by-screen version of this dispute — exact UTR location per app, exact UDIR path — is in the spoke: UPI failed, money debited. For the broader payout-stuck context, the 3 Patti withdrawal hub maps the full Day-0-to-30 ladder.

The takeaway for class (a): a failed transaction is the best loss to have, because the refund is rule-mandated and the bank is the counterparty. Your job is to name the UTR and start the clock — the rules do the rest.

Class (b): Deposit dispute — the chargeback option and its real risks

A deposit dispute is different from a rail failure in one way that changes everything: the deposit usually worked. The money left your bank, the operator received it, your chips appeared. You want it reversed anyway — because you deposited by mistake, the amount was wrong, you were double-charged, the chips didn’t credit at the value you expected, or you’ve simply decided you shouldn’t have played. The tool people reach for is a chargeback, and it works — but it is a loaded weapon, so understand it before you pull the trigger.

What a chargeback actually is

A chargeback is a forced reversal of a card transaction by the issuing bank, a consumer-protection mechanism against fraud, merchant error, or undelivered service. In India you typically have 60–120 days from the transaction date to file one, through your bank’s helpline, net banking, or a branch with evidence, and resolution takes 30–120 days depending on the bank and the network (Visa / Mastercard / RuPay). The merchant gets a chance to contest with evidence — and if they can’t show you got what you paid for, you win by default.

Where the chargeback is genuinely right

A chargeback is the correct tool when the deposit was genuinely unauthorised or defective:

• A truly unauthorised charge — your card was used without your consent. Under RBI rules, if you report a fraudulent transaction within 3 working days, your liability is zero.
• A double charge — you were debited twice for one deposit.
• A deposit that never credited as chips at all and the operator won’t fix it — though note this is often really a rail failure (class a), which is cleaner to dispute than a chargeback.

Where the chargeback is a trap

Here’s the part most “how to get gambling money back” articles skip. Disputing a deposit you did authorise and did play — because you lost, or had second thoughts — is friendly fraud, and it carries consequences that can outlast the refund:

• Account closure and cross-network blacklisting. If an operator deems a chargeback invalid, it can close your account and add you to shared blacklists across partner networks. Third-party risk-mitigation platforms compile global lists of high-risk users and share them in real time — one flagged profile can lock you out of hundreds of operators and, in some cases, the payment processors behind them.
• Bank-side consequences. Misusing chargebacks to refund standard losing bets can lead to your own bank account closure or being blacklisted by payment providers, and a chargeback the bank finds fraudulent can invite further action.
• You usually lose anyway. Operators keep gameplay records, IP and device matches, and login logs — compelling evidence that you received the service. On a deposit you genuinely played, the merchant’s evidence typically wins.

The realistic odds

For a genuinely unauthorised or double charge, odds are medium-to-good — the rules favour you and the merchant can’t prove a legitimate service. For buyer’s remorse on a played deposit, odds are low and the downside is high — you’ll likely lose the dispute and get blacklisted. The honest verdict: use a chargeback for fraud and billing errors, not for losses you regret. And if the real problem is a deposit that didn’t credit, route it through the class (a) rail dispute first — it’s cleaner and doesn’t risk your card.

Chargeback vs rail dispute: which tool wins which deposit problem

People conflate these two, and picking the wrong one either fails or backfires. The quick decision: if the deposit’s money moved wrongly on the rail, use the rail dispute; if the deposit’s money moved correctly but the charge itself is bad, use the chargeback.

The pattern: the rail dispute is the safer, stronger first move for anything that looks like a money-movement failure, and the chargeback is the narrower tool for a charge that is genuinely defective or unauthorised. A chargeback is never the right opener for “I changed my mind.” And for a deposit you simply made in error and haven’t played, talk to the operator before nuking the charge — many will reverse an un-played deposit without the blacklist exposure a chargeback carries.

For escalating a deposit-credit problem with the operator before any chargeback, the customer-care escalation spoke has the templates and the order of doors.

Chargeback in one line: it’s a real right for fraud and billing errors, and a self-inflicted wound for regretted losses. Reach for the rail dispute (class a) first; reserve the chargeback for the cases where you genuinely never authorised or never received what you paid for.

Class (c): Trapped balance — the post-PROGA recovery reality

This is the hard class, and 2026 made it harder. A “trapped balance” is money you can see in the app — winnings you earned, or deposits you never played — that you cannot withdraw, because the account is frozen, under review, or the operator has wound down its cash product. Your counterparty is the operator, not the rail, which is exactly why this is the weak-rights case.

Why the ground shifted under your feet

Before PROGA, a trapped balance was usually a temporary operator hold you could grind through with KYC and grievance escalation. The 2025 ban changed the picture in two ways.

First, the major operators discontinued cash play from late August 2025, so for a huge share of players the live question is no longer “why is my withdrawal slow” but “how do I get my balance out of an app that no longer runs cash games.” Banks were instructed to keep processing withdrawals so users could recover existing balances, which is the lifeline — the cash product stopped, but the withdrawal/recovery flow generally remained.

Second, and this is the part that hurts: the government removed the rule that would have forced platforms to refund you. A draft Rule 24 in the October 2025 rules would have given gaming companies, banks, and financial institutions a 180-day window to return user funds without those transactions being treated as “facilitating” prohibited gaming. That provision was omitted from the final notified rules, which lawyers describe as creating a regulatory “no man’s land” around pre-ban deposits and shifting the burden of recovering stuck balances from the platform to the user. There is, today, no proactive platform-led refund obligation — recovery is reactive and complaint-driven.

The channel that does exist: OGAI grievance

What replaced the missing refund mandate is a grievance ladder. The PROGA Rules 2026 establish a multi-tier complaint mechanism, and on 1 May 2026 the government constituted the Online Gaming Authority of India (OGAI) — a digital-first regulator and attached office of MeitY that handles grievances and enforces compliance. The ladder runs:

1. Operator’s internal grievance mechanism (Tier 1). Every service provider must maintain a functional internal grievance redressal channel. This is your first written demand for your balance.
2. Appeal to OGAI within 30 days. A user aggrieved by the operator’s grievance outcome may approach the OGAI within thirty days, and the Authority must dispose of the appeal within a further 30 days.
3. Second appeal to the Appellate Authority — the Secretary, MeitY — within the prescribed window. Penalty proceedings before the OGAI must conclude within 90 days of a complaint.

So the path for a trapped balance is: written grievance to the operator → OGAI appeal at 30 days → MeitY appeal. It is slower and less certain than a rail dispute, because OGAI is a regulator handling a complaint, not a bank reversing a transaction under a hard clock.

The realistic odds, honestly

For a legitimate, KYC-clean balance in a winding-down but still-reachable Indian operator, odds are medium — the operator generally still processes recovery withdrawals, and OGAI gives you an escalation lever. For a balance held inside an unlicensed, offshore, or vanished operator, odds are low — that entity may be outside Indian regulatory reach, and no Indian authority can compel an offshore wallet to pay you. The asymmetry is brutal and it’s the whole argument for never having played there.

Two rules for this class that aren’t optional:

• Complete KYC first. No balance — winnings or deposit — releases without PAN-matched KYC. A name mismatch between your bank/UPI and your PAN is the single most common silent stall; fix it before you escalate anything.
• Never deposit again to “unlock” a withdrawal. No legal app requires a deposit to withdraw, and post-PROGA a new deposit into a money game is illegal. This is the clearest theft pattern there is.

For the full anatomy of a frozen or blocked account — the six freeze types, who froze it, and the matching unblock path — the spoke goes deep: account frozen or blocked on an RMG app.

Trapped-balance verdict: the law that would have forced your refund was dropped, so recovery is now on you. Work the operator-grievance → OGAI ladder for an Indian operator, lean on the bank for any rail leg, and accept that money inside an offshore wallet may simply be unreachable. The lesson is preventive: clean KYC, a reachable operator, and never a top-up to “release” your own money.

Class (d): Fraud / scam loss — the golden-hour race

A fraud loss is a different universe from the other three, and it has one rule above all: speed. This is money you sent — or that was taken from you — because of a scam: a fake “customer care number” you found on Google or YouTube, a “deposit ₹X to release your withdrawal” demand, a phishing link, a clone app, or an OTP/UPI PIN you shared with someone pretending to help. The money has usually moved to a fraudster’s account, and your only real shot at recovery is to freeze it before it splinters across mule accounts.

The channel: 1930 and the golden hour

The instrument here is the National Cyber Crime Helpline 1930, run by the Indian Cyber Crime Coordination Centre (I4C) under the Ministry of Home Affairs. It is staffed 24×7, free from any Indian mobile network, and — this is the part that matters — it is the only number in India that can ask a beneficiary bank to place a temporary lien on a fraudster’s account within minutes of your call. That intermediate hold lasts up to 7 working days if the funds are still parked there, buying time for the investigation.

The “golden hour” is not a metaphor. Early reporting triggers the national rails that can freeze inflows before they scatter. Reporting within the first few hours initiates a freeze on the mule accounts; reporting within roughly 6 hours sharply increases recovery odds. Your complaint feeds directly into the NCRP portal at cybercrime.gov.in, where you get a complaint number and status tracking.

The realistic odds

Honestly, low-but-rising, and entirely dependent on speed. National recovery rates improved from 10–11% in 2024 to 24% in 2025, and the MHA’s expanded refund system and upgraded 1930 helpline are pushing them higher — but a quarter of cases recovering means three-quarters do not, and the ones that recover are overwhelmingly the ones reported fast. Every minute the money sits un-frozen is a minute it can move.

The move, in order

1. Call 1930 immediately — before you finish documenting, before you call the “support number” back, before anything. Give them the transaction details and the beneficiary account if you have it.
2. File on cybercrime.gov.in to lock in the complaint number.
3. Tell your bank to flag and dispute the transaction in parallel.
4. Report the fraudulent payment entity on RBI’s Sachet portal.
5. Preserve everything — the fake number, the chat, the screenshots, the URL of the clone app.

What you do not do: call the scammer back, share any further OTP or PIN, or deposit anything to “verify” or “release” funds. Legitimate support never needs your PIN or OTP, and most legal apps have no public phone helpline at all — they route support in-app, which is why a “care number” from a search result is a red flag by itself.

The spoke that covers official contact channels and the scam-number warning in detail is customer-care escalation.

Fraud-loss verdict: this class is won or lost in the first hour. Dial 1930 the instant you realise it’s a scam — the 7-day lien and the rising 24% recovery rate only help the people who call fast. After that, document, report on the NCRP and Sachet portals, and never feed the scam another rupee.

The rail-vs-operator distinction, made concrete

Everything above hangs on one line: strong rights against the rail, weak rights against the operator. It’s worth making this concrete, because it’s the mental model that tells you which door to knock on first.

The practical consequence: whenever any part of your loss touched the rail — a debit that never credited, a deposit that vanished, a payout that “succeeded” but never landed — fight that part as a rail dispute first. It’s the leg with statutory teeth. Reserve the operator-grievance and OGAI route for the part of the loss that is genuinely inside the operator’s wallet, where the rail can’t help you.

This is also the single best argument against unlicensed and offshore apps: not the morality, but the plumbing. When the operator is outside Indian regulatory reach, you keep your rail rights but lose your operator rights entirely — so a balance trapped inside it may simply be gone, while the same rupees lost on a rail failure would have been refundable. Where you play decides which rights you keep.

Four worked scenarios: the same ₹5,000, four different outcomes

The classification is easier to feel than to memorise, so here is the same amount — ₹5,000 — lost four ways, each routed through its class. These are illustrative walk-throughs built from the rules, not real individuals.

Scenario A — the rail failure (the clean recovery)

You request a ₹5,000 payout from a still-legal app. The app debits its wallet, the screen says “processing,” then “failed.” Your bank account stays empty. This is class (a). On Day 0 you screenshot the failed screen and capture the UTR from the app’s payout record. You wait through T+1 — the auto-reversal doesn’t fire. On Day 2 you open your UPI app’s “raise complaint” on that transaction, which feeds NPCI UDIR, and you call your bank’s failed-transaction desk with the UTR, asking for the ₹100/day owed past T+1. UDIR resolves in 3–5 working days; the ₹5,000 reverses and a small compensation lands. Total time: under a week. This is what “high odds” looks like — the rules did the work, the bank was the counterparty, and you never argued with the operator at all.

Scenario B — the deposit dispute (the loaded weapon)

You deposited ₹5,000, played, and lost it. You regret it and want it back. This is class (b), but the friendly-fraud trap. A chargeback here would force you to claim the charge was unauthorised — which it wasn’t. The operator’s evidence (your login, device, IP, gameplay logs) defeats the dispute, and you risk account closure plus a cross-operator blacklist. The correct read: there is no refund for a deposit you genuinely played and lost. Now change one fact — the ₹5,000 was a double charge, debited twice for one deposit. That is a legitimate class (b) chargeback: you file within the 60–120 day window for the duplicate, the operator can’t show two services were delivered, and the duplicate reverses. Same amount, same class, opposite outcome — decided entirely by whether the charge was genuinely defective.

Scenario C — the trapped balance (the hard, post-PROGA case)

You have ₹5,000 of winnings sitting in an app that discontinued cash play after the 2025 ban. You can see it; you can’t withdraw it. This is class (c). First you complete KYC and check the name on your bank account matches your PAN exactly — the most common silent block. The in-app recovery/withdrawal flow still exists (banks were told to keep processing recovery), so you try it. If the operator stalls, you file its internal grievance in writing, then appeal to OGAI within 30 days. There is no rule forcing the platform to push the money — Rule 24 was dropped — so this is slower and less certain than Scenario A. For a reachable Indian operator your odds are medium; if the same ₹5,000 sat in an offshore wallet that ignores you, the realistic odds drop toward zero, and the bank can only help with a rail leg of the transfer, not the trapped balance itself.

Scenario D — the fraud loss (the clock)

Someone called claiming to be “Teen Patti customer care,” said your ₹5,000 withdrawal was “stuck,” and walked you through an OTP that moved ₹5,000 out of your account. This is class (d). The right action is not to document first — it’s to call 1930 immediately, within the golden hour, so the beneficiary bank can place a 7-day lien before the money splinters across mule accounts. Then you file on cybercrime.gov.in, tell your bank, and report the entity on Sachet. If you called within the hour, you’re in the ~24% of cases that recover; if you waited a day, you’re likely in the three-quarters that don’t. Same ₹5,000 — and here the only variable that mattered was speed.

Four scenarios, one lesson: the class and the clock decide the outcome, not how loudly you complain. Scenario A recovered because the rail owed it; Scenario D recovered (or didn’t) on the first hour; Scenario C is a grind because the platform isn’t obliged to pay; and Scenario B is only winnable when the charge was genuinely defective.

A short timeline of why 2025–26 broke the old refund playbook

If you last tried to get money out of a gaming app before 2025, the rules you remember are partly obsolete. Here’s the compressed timeline of what changed, because each step shifted the odds for one of the four classes.

• 1 April 2023 — Section 194BA arrives. Flat 30% TDS on net winnings, no minimum threshold. This is why so many “the app cheated me” complaints are actually tax, not a refund case — it carved a permanent slice out of every payout and created the “I got less than I withdrew” confusion that this page tells you not to dispute.
• 1 October 2023 — 28% GST on deposits. Deposits now carry a 28% tax on full face value, so ₹100 deposited buys fewer chips. Another non-refund shortfall people mistake for a bug.
• 22 August 2025 — PROGA gets Presidential assent. The Act bans all online money games, skill or chance. Within days, the major operators suspend cash play — turning a wave of “slow withdrawal” cases into “wound-down operator holds my balance” cases overnight. Class (c) is born at scale.
• October 2025 — draft rules include Rule 24. The draft would have given platforms and banks a 180-day window to refund user funds without it counting as facilitating banned gaming. For a few weeks, it looked like trapped balances had a guaranteed exit.
• Ahead of 1 May 2026 — Rule 24 is dropped. The final notified rules omit the refund window, shifting recovery from platforms to users — the single biggest blow to class (c) odds.
• 1 May 2026 — Rules in force; OGAI constituted. The grievance ladder (operator → OGAI in 30 days → MeitY) replaces the missing refund mandate. It’s a complaint route, not an automatic refund — better than nothing, weaker than Rule 24 would have been.

The net effect: the rail classes (a and legitimate b) are essentially unchanged — RBI’s 2019 TAT circular still forces those refunds — while the operator class (c) got materially harder, and the fraud class (d) got slightly better as the 1930/I4C machinery improved. Knowing which way each class moved tells you where to spend your energy: lean hard on the rail rights that didn’t change, and be realistic about the operator rights that eroded.

The evidence file: what to capture before you do anything

Across all four classes, the difference between a won and a lost case is often a single artefact you failed to save on Day 0. Build this evidence file in the first hour, because some of it ages out fast — a “failed” transaction drops out of an app’s quick view, and NPCI’s URCS only holds the record for 45 days.

• The UTR / RRN — the 12-digit reference, the spine of any class (a) or (b) dispute. It’s in your UPI app’s transaction detail (labelled “UPI Reference No.” on PhonePe, “Bank Reference ID” on Google Pay, “UPI Ref No.” on Paytm, “Transaction ID” on BHIM — all the same number) and in the bank SMS.
• Date-stamped screenshots — the transaction, the status screen, the amount, and your balance before and after. For a class (c) trapped balance, screenshot the withdrawable figure specifically, not just the headline wallet number.
• The ticket/complaint ID — every in-app or operator complaint, in writing. This timestamps your grievance, which matters for the 30-day RBI Ombudsman and OGAI clocks.
• For a fraud loss (d) — the fake number, the full chat, the URL of the clone app or phishing page, and the beneficiary account/UPI the money went to. This is what 1930 needs to place the lien.
• For KYC stalls — a clear photo of your PAN and the exact spelling of your bank account name, so you can prove (or fix) a name mismatch.

A practical rule: capture first, escalate second. The instinct is to start complaining; the discipline is to spend the first ten minutes building a file you can attach to every door you’ll knock on. A complaint with a UTR, a timestamp, and a ticket ID moves; a complaint that says “the app took my money” does not.

The 30-second answer is wrong for one case: when not to chase a refund

A short honest note, because chasing the wrong refund wastes the days you’d need for a real one. If your “loss” is actually TDS, there is no refund to chase — and disputing it is a mistake. Every legal RMG app deducts 30% TDS on net winnings under Section 194BA, with no minimum threshold, since 1 April 2023. So a payout that arrives smaller than you withdrew is usually tax, not theft. On a ₹25,000 withdrawal where your net winnings were ₹15,000, that’s a ₹4,500 cut — reported against your PAN in Form 26AS / AIS and creditable when you file your return. You don’t dispute it; you reclaim it at filing.

Likewise, a deposit that bought fewer chips than you expected is usually the 28% GST on deposits (since 1 October 2023), not a “deposit not credited” bug. On a ₹1,000 deposit, the 28% GST is computed on the face value, so a chunk of that ₹1,000 is tax before it ever becomes playable balance — a gap players routinely misread as “₹1,000 deposited but only ₹780-ish credited.” It isn’t a shortfall to dispute; it’s the deposit-side tax doing exactly what the law requires.

Neither of these is a recoverable loss in the refund sense. Sort them out of your case before you classify it as (a), (b), (c), or (d) — otherwise you’ll spend a week filing a dispute against the tax department’s own rules and lose, while the 45-day clock on a real rail dispute quietly runs out. A simple test: if your shortfall is roughly 30% of your net winnings, it’s TDS; if it’s roughly 28% of a deposit, it’s GST; anything else is a genuine loss worth classifying. The full tax arithmetic, with worked examples, lives in the withdrawal hub: 3 Patti withdrawal.

The non-refund cases in one line: a 30% shortfall on net winnings is TDS, and a deposit buying fewer chips is 28% GST — both are tax, both are yours to reconcile at filing, and neither is a refund to pursue. Strip them out first so your real loss is the only thing left on the table.

The universal Day-0-to-30 recovery ladder (all four classes)

Whichever class you’re in, the sequence of escalation is the same spine — only the door you start at differs. Climb in order; don’t skip rungs (you’ll waste days proving you tried), and don’t jump to the regulator on Day 1 (they’ll bounce you back to the entity).

Day 0 — Freeze the evidence and start the right clock

The highest-leverage hour is the first one, and it’s not complaining — it’s documentation, plus the one class-specific action that’s time-critical.

• Screenshot everything: the transaction, the status screen, the amount, the timestamp, your balance before and after. Date-stamped screenshots are your evidence.
• Capture the UTR / reference the moment one appears. For classes (a) and (b) it’s the thread that ties debit to missing credit; without it you can’t trace a “paid” transaction. It’s a 12-digit number in your UPI app’s history and the bank SMS.
• Open the right first door immediately: for class (d) fraud, call 1930 right now — that’s the golden-hour action that can’t wait. For classes (a)/(b)/(c), raise the in-app ticket and get a written complaint/ticket ID.

Do not start a second account, do not deposit more “to unlock” anything, and never share an OTP or UPI PIN with anyone who “calls to help.”

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

• Send the same complaint by the operator’s official support email (from its Play listing or official site), referencing the in-app ticket ID. Email creates a paper trail a chat can’t.
• For a class (a) failed transaction, this is the T+1 window — let the auto-reversal run before you dispute.
• If the operator publishes a 1–3 working-day SLA, you’re still inside it. Be firm but patient.

Day 4–7 — Open the payment-side dispute (UTR + NPCI), or file the chargeback

If money is genuinely gone on the rail (class a, or a class-b unauthorised charge) and hasn’t come back:

• Open your UPI app’s “raise complaint / dispute” on that transaction (feeds NPCI UDIR, which auto-converts to chargeback after the TAT), or call your bank’s failed-transaction desk with the UTR and claim the ₹100/day if past T+1.
• For a class (b) unauthorised card charge, file the chargeback through your bank within the 60–120 day window — but only if the charge was genuinely unauthorised, defective, or double-billed (re-read the chargeback risks above).
• You can also use the NPCI UPI Help portal or the line 1800-120-1740; UDIR’s stated window is 3–5 working days, and you must raise within 45 days while the transaction is still searchable in URCS.

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

• Escalate the bank complaint to a written formal complaint if the helpline did nothing; get a reference number.
• For a class (c) trapped balance, this is where you file the operator’s internal grievance in writing, and start the 30-day clock for an OGAI appeal.
• Send the operator a final-notice email: the facts, the ticket ID, the UTR, the days elapsed, and a clear statement that you’ll escalate to the RBI Ombudsman, OGAI, and the consumer forum. A dated final notice often unsticks a payout because it signals you know the process.

Day 16–30 — Regulator: RBI Ombudsman, OGAI, or consumer forum

If the matter is still unresolved, escalate to the authority that matches the class:

• Rail failure (a) still unresolved by your bank/PSP after 30 days → file free with the RBI Integrated Ombudsman Scheme 2021 (RB-IOS) at cms.rbi.org.in, which covers banks, NBFCs, and Payment System Participants.
• Trapped balance (c) with a failed operator grievance → appeal to OGAI within 30 days; OGAI must dispose within a further 30 days.
• App-side service deficiency (owed a clean, KYC-complete balance) → National Consumer Helpline 1915 and the consumer-forum route, in parallel.
• Fraud (d) → you’ve already called 1930; keep the NCRP complaint updated and report the entity on the Sachet portal.

Honest limit of this ladder: the RBI Ombudsman and bank disputes are powerful against the rail (classes a and the unauthorised part of b), because banks and PSPs are RBI-regulated. They’re weaker against a shady offshore or unlicensed operator (much of class c) that simply ignores you, because that operator may be beyond Indian reach. The OGAI route helps for Indian operators but is slower and reactive. That asymmetry is the whole reason to only play where payouts are clean — and to fight the rail leg of any loss first.

Copy-paste templates, one per class

Fill in the bracketed parts. Keep every message factual, dated, and ID-stamped — emotion doesn’t move a refund, a UTR does.

Template A — Class (a) rail dispute (bank / UPI, Day 4–7)

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

A UPI transaction was debited but not credited.
- UTR / reference (RRN): [UTR]
- Amount: Rs [AMOUNT]
- Date/time: [DATE, TIME]
- My account / UPI ID: [A/C or HANDLE]

Per RBI circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019),
a debited-but-not-credited transaction must be auto-reversed by T+1,
with Rs 100/day compensation for delay beyond T+1. It has now been
[N] days. Please reverse the amount and credit the applicable
compensation, and share the complaint reference number.

Template B — Class (b) chargeback request (card issuer)

Subject: Chargeback request - unauthorised/incorrect transaction [REF]

I am disputing a card transaction as [unauthorised / double-charged /
not delivered as described].
- Card last 4 digits: [XXXX]
- Merchant: [OPERATOR / PAYMENT DESCRIPTOR]
- Amount: Rs [AMOUNT]   Date: [DATE]
- Reason: [card used without consent / charged twice / deposit never
  credited and merchant will not resolve]

I report this within the dispute window. Please raise a chargeback
under the applicable Visa/Mastercard/RuPay rules, provide provisional
credit where due, and share the dispute reference number.

Template C — Class (c) operator grievance / OGAI escalation

Subject: Demand for release of my balance of Rs [AMOUNT] - [ACCOUNT ID]

My verified, KYC-complete account holds a balance of Rs [AMOUNT] that
I am unable to withdraw. Registered mobile: [NUMBER]. PAN matches my
bank account name.

- Balance owed: Rs [AMOUNT] (winnings/deposit, not bonus)
- KYC: completed (PAN + Aadhaar verified)
- In-app ticket [TICKET ID] raised [DATE]; status: [no response / unresolved]

Please release my balance to my registered account within 15 days, or
provide a written reason. If unresolved, I will appeal to the Online
Gaming Authority of India (OGAI) within the 30-day window under the
PROG Rules 2026, and approach the National Consumer Helpline (1915).

Template D — Class (d) cybercrime (after calling 1930)

To: National Cyber Crime Reporting Portal (cybercrime.gov.in / 1930)

Complaint: Online financial fraud - money obtained by [fake customer-
care number / phishing link / "deposit to unlock withdrawal" demand /
clone app / OTP-PIN scam].

- Amount lost: Rs [AMOUNT]   Date/time: [DATE, TIME]
- My account / UPI ID: [A/C or HANDLE]
- Beneficiary account / UPI / number used by fraudster: [DETAILS]
- UTR / reference of the transfer: [UTR]
- 1930 call made on: [DATE, TIME]; acknowledgement: [REF if any]

Request an immediate lien on the beneficiary account and recovery of
the amount. Evidence (screenshots, chat, fake number) attached.

Template E — RBI Ombudsman (RB-IOS), Day 30+ for an unresolved rail failure

Nature of complaint: Deficiency in service - failed/unresolved digital
payment (transaction debited, not credited/refunded).

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

File Template E at cms.rbi.org.in only after 30 days without resolution from the entity — that’s the eligibility gate for the RB-IOS 2021.

Grievance contact reference block

Keep this handy — it’s the whole escalation map in one place. Use the door that matches your loss class.

Order of doors by class, in one line: (a) bank/UPI → NPCI → RBI Ombudsman; (b) operator → card chargeback; (c) operator grievance → OGAI → consumer forum; (d) 1930 → NCRP → Sachet, immediately.

Realistic recovery odds, side by side

People want a straight answer on “will I actually get my money back,” so here it is, honest and per class. These are directional odds drawn from the rules and the published recovery data cited on this page — not a promise about your specific case.

Two patterns jump out of that table. First, the rail classes (a, and the legitimate part of b) are the recoverable ones, because the counterparty is a regulated bank with a hard clock. Second, the operator classes (c, and offshore fraud in d) are the hard ones, because the counterparty may be unreachable. That’s the rail-vs-operator distinction again — it’s not a side point, it’s the entire predictor of whether you get paid.

The one variable you fully control across all four: time. The UTR captured on Day 0, the 1930 call in the first hour, the dispute raised inside the 45-day URCS window, the OGAI appeal inside 30 days — every recoverable case is recoverable because someone acted fast. The slow cases are the lost cases.

Is it a delay, a refund-able loss, or a scam? Red flags that change your class

Sometimes the hardest part is knowing whether you even have a recoverable loss or a scam in progress. These red flags push your case toward class (d) fraud and change your strategy from “patient escalation” to “call 1930 now”:

• “Deposit ₹X to release your withdrawal.” No legal app requires a deposit to withdraw. This is the single clearest theft pattern — and post-PROGA, a new deposit into a money game is also illegal. Stop, document, report.
• A “customer care number” from a random website, YouTube comment, or search result. Most legal apps have no public phone helpline and route support in-app. These numbers overwhelmingly exist to phish your OTP and UPI PIN. Never call back a number you didn’t get from the official listing, and never share an OTP/PIN.
• No PAN/KYC was ever required to deposit or withdraw. A legal app must do KYC. Its absence means you’re likely not on a regulated platform — your rail leverage shrinks and class (c) odds drop toward zero.
• A sideloaded / “mod” / “unlimited chips” APK. Modified builds void the operator’s terms and can freeze your account and balance with no recourse — the money you’re chasing may already be forfeit by the app’s own rules.
• The “app” vanished and pending withdrawals went dark. A genuine reinstall keeps your balance (it’s tied to your registered number). A disappeared operator is a worse problem — though a legitimate PROGA wind-down is the opposite: it stopped cash games but should still let you withdraw an existing balance.

If two or more of these are true, treat the rail leg as a class (a)/(d) dispute (bank + 1930) and lower your expectation of recovering anything held inside the operator. The frozen-account spoke separates a recoverable hold from a lost balance: account frozen or blocked.

Where to get real, official help

There is no “faster app” that recovers a stuck refund, and after PROGA 2025 moving to another online money-gaming service is not a legal option in India. What actually recovers money is the official chain, used in the order that matches your class, with your paper trail intact:

• Your bank first, for any rail loss. A UPI/IMPS/NEFT debit that wasn’t credited gets auto-reversed by T+1 with ₹100/day after, under the RBI failed-transaction circular.
• NPCI UPI grievance / UDIR, raised within 45 days through your UPI app or NPCI UPI Help — the rail-level escalation that auto-converts to a chargeback after the TAT.
• OGAI, for a trapped balance an operator won’t release — appeal within 30 days of the operator’s grievance outcome under the PROG Rules 2026.
• RBI Ombudsman (RB-IOS) if a bank/PSP doesn’t resolve a rail failure within 30 days, free on the RBI CMS portal.
• National Consumer Helpline 1915, and for fraud, 1930 / cybercrime.gov.in plus the RBI Sachet portal — the latter the moment a scam is involved.

Editor’s verdict. A rail failure — money that left your bank but never arrived — is the recoverable kind; the rules force a refund and the bank is the counterparty. A balance held inside a wound-down or unlicensed operator is the hard kind, made harder because PROGA dropped the rule that would have forced platforms to refund you — pursue it through the operator-grievance → OGAI chain, but never deposit more “to unlock” it. And a fraud loss is the time-critical kind: 1930, first hour, no exceptions.

Related fixes (go deeper on your exact class)

This is the refund-and-recovery hub. For the loss class that matches you, these spokes go step-by-step:

• Rail failure — UPI debited but not credited → UPI failed, money debited — the exact NPCI UDIR dispute screens, UTR location per app, and the T+1 / ₹100/day claim.
• Trapped balance — frozen or blocked account → account frozen or blocked on an RMG app — the six freeze types, who froze it, and the matching unblock path.
• Can’t reach the operator at all → customer-care escalation — official channels, the scam-number warning, and the grievance-officer route.
• Withdrawal stuck or shrunk (and the tax math) → 3 Patti withdrawal — the full Day-0-to-30 payout ladder, TDS/GST examples, and per-app reality.

FAQ

1. What kinds of gaming refund actually exist in India? Four, and they don’t share a fix. A rail failure (debited not credited) is auto-reversed by T+1. A deposit dispute can use a chargeback within a 60–120 day window. A trapped balance in a wound-down operator is user-led recovery via OGAI grievance. A fraud loss goes to 1930. Classify yours first — it sets your odds.

2. My UPI deposit/payout was debited but never credited — can I get it back? Yes, this is the strongest case. Under RBI Circular DPSS.CO.PD No.629 (20 Sep 2019), a debited-but-not-credited transaction must be auto-reversed by T+1, and if it isn’t, your bank owes ₹100 per day of delay, credited automatically. Capture the UTR and raise the dispute within 45 days.

3. Can I chargeback a gaming deposit in India? You can, within 60–120 days of the transaction — but only do it for a genuinely unauthorised, double-charged, or undelivered deposit. Disputing a deposit you played and lost is friendly fraud: you’ll likely lose the dispute and can be blacklisted across operators and payment processors. For a deposit that simply never credited, use the cleaner rail dispute instead.

4. How long do I have to file a UPI dispute? You must raise it within 45 days. NPCI’s revised TAT keeps transaction data in URCS for 45 days; beyond that the transaction can’t be searched and the dispute can’t be raised. NPCI’s stated resolution window for a raised UDIR complaint is 3–5 working days.

5. My money is stuck inside an app that shut down after the ban — how do I get it out? Banks kept processing withdrawals so users could recover existing balances, so complete KYC and follow the in-app recovery flow. If the operator won’t release it, file the operator’s internal grievance, then appeal to OGAI within 30 days. Expect 30% TDS on net winnings, and never deposit again — that’s now illegal.

6. Doesn’t PROGA force the platforms to refund my balance? No — and this surprises people. A draft Rule 24 would have given platforms a 180-day window to return user funds, but it was dropped from the final rules, shifting recovery from platforms to users. There’s no proactive refund mandate; recovery is complaint-driven through the operator and then OGAI.

7. What is OGAI and how does its grievance route work? The Online Gaming Authority of India, constituted on 1 May 2026 as a MeitY-attached digital regulator. The ladder: operator’s internal grievance first, then an appeal to OGAI within 30 days (disposed within a further 30 days), then a second appeal to the Secretary, MeitY. Penalty proceedings must conclude within 90 days.

8. I sent money to a fake “customer care number” — what do I do? Call 1930 immediately — it’s the only number that can place a lien on the fraudster’s account within minutes, lasting up to 7 working days. The “golden hour” matters: reporting within ~6 hours sharply raises recovery odds. Then file on cybercrime.gov.in and tell your bank. Never share an OTP or PIN.

9. What are my realistic odds of recovering a fraud loss? Honestly, low but rising, and speed-dependent. National recovery rates improved from 10–11% in 2024 to 24% in 2025. The recovered cases are overwhelmingly the ones reported fast — every minute the money sits un-frozen, it can move to a mule account.

10. Why do I have stronger rights against my bank than against the gaming app? Because the rail (UPI/IMPS/NEFT) is run by RBI-regulated banks with statutory timelines, ₹100/day penalties, and a free ombudsman, while the operator is a private company you have only a contract claim against — and post-PROGA many are wound down, offshore, or unreachable. Fight the rail leg of any loss first.

11. I received less than I withdrew — is that a refund I should chase? No. That’s almost always 30% TDS on net winnings under Section 194BA (no threshold since 1 April 2023), reported against your PAN in Form 26AS / AIS and reclaimable at filing. A deposit buying fewer chips is 28% GST. Neither is a refund to pursue — strip them out before classifying your real loss.

12. The app says “paid / success” but nothing arrived — which class is that? That’s a rail failure (class a) in disguise. Get the UTR from the app and ask your bank to trace it; if there’s no credit against that UTR, you have proof the money didn’t reach you. Open a UPI dispute (NPCI UDIR) and escalate. The spoke walks it screen-by-screen.

13. Can I recover money from an offshore or unlicensed app? For any loss on the payment rail, yes — pursue the bank/UPI dispute, NPCI, RBI Ombudsman, and report fraud to 1930 and the Sachet portal. But a balance held inside an offshore or unlicensed operator that ignores you is not guaranteed to be recoverable, because it may sit outside Indian regulatory reach. That asymmetry is the strongest reason to never play there.

14. What’s the single biggest mistake people make trying to get a refund? Knocking on the wrong door. Treating a rail failure as an operator complaint (and missing the easy T+1 refund), firing a chargeback on a played deposit (and getting blacklisted), or reporting a fraud loss late (and missing the golden hour). Classify the loss first — it’s the one decision that determines whether you get paid.

15. Should I deposit more to “unlock” a withdrawal or “verify” my account? Never. No legal app requires a deposit to withdraw, and post-PROGA a new deposit into a money game is illegal. “Deposit ₹X to release your money” is the clearest theft pattern there is — it’s class (d) fraud. Stop, document, and report to 1930 and cybercrime.gov.in.

Sources & method. Refund classes, channels, odds and escalation on this page are built from primary regulatory sources and current reporting — not personal recovery tests. Key references: RBI failed-transaction TAT circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019); RBI Integrated Ombudsman Scheme 2021 and cms.rbi.org.in; RBI Sachet portal; NPCI UPI Help / UDIR and the NPCI revised disputes TAT (45 days); the Feb 2025 UPI chargeback / TCC rule; chargeback mechanics and friendly-fraud/blacklist risk via HonestGuide, Jupiter and gambling-chargeback guidance; the Promotion and Regulation of Online Gaming Act, 2025 and its Rules effective 1 May 2026; the dropped Rule 24 / refund-gap reporting; the OGAI grievance framework and wind-down recovery context; the 1930 cyber-fraud helpline and golden hour, 7-day lien and recovery rates, and MHA refund-system upgrade; cybercrime reporting at cybercrime.gov.in / helpline 1930; National Consumer Helpline 1915. This page is information, not legal or financial advice — verify each step against your operator’s current Terms and your bank’s UPI dispute policy.