Teen Patti Refund Process: When You Get Money Back

The 30-second answer

A Teen Patti refund is money returned to you when you paid but got nothing for it — a failed deposit, a duplicate charge, or an unauthorised transaction. A lost game or buyer’s remorse is not refundable. There is no statutory 180-day gaming-refund right: that draft PROGA rule was dropped from the final 2026 Rules, so refunds fall back to RBI rail rules, consumer law, and the operator → OGAI (within 30 days) → MeitY ladder. Start at the master map: gaming refund decision tree.

Editor’s verdict, up front. The word “refund” carries two completely different meanings on a card-game app, and confusing them is why most refund requests fail before they start. There is the rail refund — your bank or UPI auto-returns money that left your account but never reached its destination — and there is the operator refund — the app voluntarily putting chips or rupees back into your wallet. The first is governed by hard RBI rules with timelines and compensation attached. The second is governed by the operator’s own policy plus general consumer law, and it is much weaker. The single most important skill on this page is sorting your situation into “I am owed a refund” versus “I am not,” because a wrongly-aimed refund request burns the days you’d need for a real one. This page is the process page: the exact entitlement test, each operator’s stated refund pattern, the request flow step by step, realistic timelines per scenario, and copy-paste templates. For the wider four-loss money-recovery map, the hub is the refund-dispute-recovery decision tree.

2026 reality you must read first. The legal ground shifted hard, and one detail matters enormously for refunds. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) banned all online money games — skill or chance — where you stake money for a return, and its operating Rules came into force on 1 May 2026. A draft Rule would have given platforms and banks a 180-day window to return user funds without that counting as “facilitating” a banned game. That provision was omitted from the final notified Rules. So there is no statutory gaming-refund clock, and the burden of recovering trapped balances shifted from platforms to users. What survived: the RBI/NPCI rail protections, the Consumer Protection Act, 2019, ordinary contract law, and the new OGAI grievance ladder — operator first, then the Online Gaming Authority of India within 30 days, then MeitY. Do not read this page as “you have a 180-day right to a refund.” You don’t. You have specific refund grounds and a specific ladder, and that distinction is the whole game.

What a “Teen Patti refund” actually means

When someone searches “teen patti refund,” “3 patti refund,” or “gaming app refund process,” they are usually holding one of five very different situations in their head and calling all of them the same word. The first job is to name yours, because a refund is not one thing.

A refund, precisely, is money returned to you for a transaction where you did not receive what you paid for. That definition does a lot of work. It immediately includes a deposit that failed (you paid, no chips arrived) and immediately excludes a lost hand (you paid to play, you played, you lost — the service was rendered). Everything below hangs on that line.

There are five distinct objects people call a “Teen Patti refund,” and they split cleanly into two columns:

• Refundable — service not rendered or money taken wrongly:
  1. Failed deposit — you were debited but the chips never credited to your wallet.
  2. Duplicate / double charge — the same deposit was billed twice.
  3. Unauthorised transaction — someone used your card/UPI without permission, or a child made a payment.
  4. Service-not-rendered — you paid for a specific thing (a tournament entry, a pass) the app never delivered.
• Not refundable — service was rendered: 5. A lost game, or buyer’s remorse — you deposited, played, and lost, or you deposited and changed your mind after playing. The chips were delivered; the outcome of the game is not a defect.

That split is not the operator being mean. It mirrors how Indian consumer law itself defines a refundable failure. Under the Consumer Protection Act, 2019, an unfair trade practice includes refusing to refund money paid for a service that is deficient or not delivered as agreed — but losing a game you chose to play is neither deficient nor undelivered. The service (a fair game of cards) was supplied. You can dispute rigging or a technical failure mid-game, but you cannot dispute losing.

One more distinction shapes the entire process: a refund is not the same as a withdrawal. A withdrawal is you cashing out a balance you legitimately hold; a refund is you reversing a payment that shouldn’t stand. They use different rules, different counterparties, and different escalation doors. If your problem is “my winnings won’t come out,” that’s a withdrawal problem — go to the 3 Patti withdrawal hub. If your problem is “I paid and got nothing back,” that’s a refund, and you’re on the right page.

Why naming your object decides everything

A failed deposit and a lost game can feel identical from the inside — in both cases, money is gone and your wallet is lighter than you expected. But they are legal opposites. The failed deposit has the RBI failed-transaction rulebook behind it and an automatic reversal coming; the lost game has nothing behind it because nothing went wrong. A player who files a “refund” for a lost game is, in card-network terms, attempting a friendly-fraud chargeback — disputing a legitimate transaction — which can get the card blacklisted across operators and even flagged by the bank. So before you touch a refund button, settle the object. The entitlement test in the next section does exactly that.

The entitlement test: are you actually owed a refund?

Run this before anything else. It is six questions, and your honest answers route you to either “yes, pursue it” or “no, stand down.” Getting this right saves the days you’d otherwise waste filing a doomed dispute.

1. Did money leave your bank/card/UPI? If nothing was debited, there is nothing to refund — this is a display glitch, not a payment one. Stop here.
2. Did you receive what that money bought? If you deposited ₹500 and ₹500 of chips arrived, the transaction worked. Whatever happened after (you lost it) is gameplay, not a refund ground. If the chips never arrived, you have a failed deposit — refundable.
3. Was the charge a duplicate? If the same deposit shows twice on your statement but credited once, the second one is refundable as a duplicate.
4. Did you authorise it? If a payment went out that you never approved — a stolen card, a saved UPI used by someone else, a child tapping “buy” — it’s an unauthorised transaction, refundable, with a 3-working-day reporting window for zero liability.
5. Did you pay for a specific deliverable the app didn’t deliver? A tournament entry where the tournament never ran, a paid pass that never activated — service-not-rendered, refundable.
6. Are you simply unhappy you lost, or changed your mind after playing? Then no refund is owed. The service was rendered. Pursuing it as a chargeback is friendly fraud.

If you answered “yes” to any of questions 2-through-failure (chips didn’t arrive), 3, 4, or 5, you have a genuine refund ground — proceed to the request flow. If your situation is only question 6, the honest answer is that no counterparty owes you money, and the productive move is to stop, not to escalate.

The entitlement test in one line: you are owed a refund when money moved but value did not — a failed deposit, a duplicate, an unauthorised charge, or an undelivered paid item. You are not owed one for the outcome of a game you chose to play. Roughly four in five “the app cheated me” refund attempts collapse on question 6, and the four legitimate grounds are where all your energy should go.

The grey-zone cases worth calling out

Three situations sit on the line and deserve a sharper read, because operators and players genuinely disagree on them.

• Mid-game disconnection / app crash that cost you a hand. You were in a winning position, the app froze, and you lost the pot. This is arguably a service defect, but it is hard to prove and operators almost universally treat the hand as completed. Realistically: raise it with support for a goodwill chip refund, but don’t expect a rail-level remedy — there’s no UTR to dispute, because the deposit itself worked.
• Bonus you couldn’t withdraw. You feel you’re “owed a refund” of a bonus the app gave you and then locked behind wagering. This is not a refund situation at all — a bonus is promotional credit, not money you paid, so there’s nothing to return. The terms govern it.
• Deposit made to a now-banned operator after PROGA. You deposited into a money game in 2026 — which is itself illegal post-ban — and now want it back. The deposit may be reversible as a failed or unauthorised transaction if it never credited, but a successful deposit into an illegal game is a genuinely hard recovery, and you should never have been able to make it. Pursue the rail leg; expect friction on the rest. The master decision tree covers this trapped-balance case in depth.

The four refundable scenarios, one by one

Each refundable ground has its own counterparty, its own evidence, and its own clock. Treating them as one generic “refund” is the most common process error. Here is each, with what proves it and who owes it.

Scenario 1 — Failed deposit (debited, chips never credited)

What it is: you initiated a deposit, your bank debited the amount, but the chips never appeared in your wallet. The most common and most protected refund ground.

Who owes it: primarily the payment rail (your bank / UPI), not the app — because the failure is that the money never reached the operator, or reached it but the credit instruction failed. Under RBI’s failed-transaction TAT circular, a UPI debit that isn’t completed must be auto-reversed by T+1, with ₹100/day compensation after that. A deposit to a merchant (the operator) that fails confirmation has a T+5 auto-reversal window before the same ₹100/day kicks in.

What proves it: the UTR (12-digit reference) of the debit, the bank SMS/statement showing the debit, and the in-app wallet showing no credit. With those three, the rail must reverse it.

Realistic timeline: most failed UPI deposits self-reverse within T+1 with no action needed. If it doesn’t, you raise a UPI dispute (it routes into NPCI UDIR) and claim the ₹100/day. The screen-by-screen version of this exact dispute is on the UPI failed, money debited page.

Scenario 2 — Duplicate / double charge

What it is: the same deposit was billed twice — two debits, one chip credit. Often a retry after a “failed” screen that actually went through.

Who owes it: the rail again, because the second debit has no matching service. The operator may also reverse it goodwill-style if it sees the double credit on its side, but the bank dispute is the reliable lever.

What proves it: two UTRs for what should be one transaction, debited within seconds/minutes of each other, with only one wallet credit. That pattern is unambiguous and banks reverse it routinely.

Realistic timeline: a clean duplicate, disputed with both UTRs, is typically reversed within the bank’s failed-transaction cycle — days, not weeks. If it rode a card rather than UPI, it follows the card chargeback timeline, which can run 30–120 days at the outer edge but usually resolves far faster for an obvious duplicate.

Scenario 3 — Unauthorised transaction

What it is: a payment you never approved — a stolen/cloned card, a saved UPI mandate misused, or (extremely common) a minor making in-app payments on a parent’s phone.

Who owes it: the bank/card issuer, under RBI’s customer-liability framework. The critical number: if you report within 3 working days, your liability for an unauthorised electronic transaction is zero, and the bank must investigate and reverse it (RBI rules). Delay past that window and your liability can rise.

What proves it: the transaction details, your statement that you didn’t authorise it, and (for a minor’s spend) the account context. Speed is the whole game — the 3-day clock is unforgiving.

Realistic timeline: report immediately (same day), in writing. The bank opens a fraud/unauthorised-transaction case; reversal follows its investigation, but reporting inside 3 working days is what caps your liability at zero. Note: a gambling loss dressed up as “unauthorised” is friendly fraud and will be contested — this ground is for genuinely unapproved payments only.

Scenario 4 — Service-not-rendered

What it is: you paid for a specific deliverable — a tournament buy-in, a paid pass, a feature unlock — and the operator never delivered it. Distinct from a failed deposit (where chips didn’t arrive) because here a named service didn’t materialise.

Who owes it: the operator, and this is the one ground where the operator (not the rail) is the primary counterparty, backed by the Consumer Protection Act, 2019 — refusing to refund for an undelivered service is a defined deficiency in service / unfair trade practice.

What proves it: proof of the specific purchase (receipt, order ID), and evidence the deliverable never came (the tournament that didn’t run, the pass that stayed locked).

Realistic timeline: operator-led, so slower and policy-dependent. Raise it with the operator first; if denied, the consumer-law route (National Consumer Helpline 1915, then the consumer forum) applies, and post-PROGA the OGAI grievance ladder is the gaming-specific door. There’s no rail auto-reversal here because the deposit itself worked — the dispute is about what you got for it.

Scenario map in one line: Scenarios 1, 2, 3 are payment-rail / bank refunds (strong rights, RBI-backed, UTR is everything), while Scenario 4 is an operator/consumer-law refund (weaker, policy-dependent, no auto-reversal). Knowing which one you’re in tells you the first door to knock on — bank for 1/2/3, operator for 4.

The non-refundable cases — and why fighting them backfires

It is worth being blunt about the cases where no refund is owed, because attempting one doesn’t just fail — it can cost you. The two big ones:

A lost game. You deposited, the chips arrived, you played Teen Patti, and you lost. The service — a game of cards — was delivered exactly as advertised. There is no defect to refund. This is the single most common “refund” attempt, and it has no legal ground in India: a genuinely lost gambling stake is not a deficiency in service, it’s the agreed outcome of a transaction you entered voluntarily.

Buyer’s remorse. You deposited, started playing, and then wished you hadn’t. Changing your mind after the service began is not a refund ground. A deposit that’s already been (partly) played through has been consumed.

Here’s why fighting these backfires rather than merely failing. Disputing a legitimate transaction with your card issuer is first-party misuse — “friendly fraud.” The card networks treat it as fraud, and iGaming sits at the top of every chargeback risk table. The concrete consequences, documented by the card networks themselves:

• The operator blacklists you. It submits its evidence — IP logs, gameplay records, KYC — to your bank, and on a clear gambling loss the chargeback is reversed and your account closed.
• Cross-platform blacklisting. Operators share fraud signals; a friendly-fraud flag can follow you across partner platforms.
• Your bank can flag you. Banks terminate or restrict accounts of cardholders known to file false chargebacks. You can lose the payment instrument, not just the dispute.

So the cost of a wrongful refund attempt isn’t zero — it’s a damaged payment profile to chase money you were never owed. The discipline of the entitlement test exists precisely to keep you off this rock.

The non-refundable rule in one line: you cannot refund the outcome of a game you chose to play, and trying to is friendly fraud — which risks blacklisting and account closure, not just a “no.” Spend the energy on the four real grounds instead.

The legal ground: what governs gaming refunds in India after PROGA

This is the part most explainers get wrong in 2026, and getting it wrong wastes weeks. There is a widely-repeated myth that India introduced a 180-day platform refund right for stranded gaming balances. It did not become law. Here is the actual stack of rules that governs a Teen Patti refund.

There is no statutory 180-day gaming refund window

A draft version of the PROGA Rules contained a provision that would have let platforms and banks return user funds within 180 days without that being treated as “facilitating” a banned money game. It was a safe harbour for refunds, not a right — but it would at least have created a clear platform obligation and timeline. It was dropped from the final notified Rules. The result, as the legal commentary on the 2026 rules reset makes clear, is that there is no PROGA-mandated refund clock at all, and the burden of recovering a trapped balance fell back onto users and onto pre-existing law. Anyone telling you “you have 180 days to claim your refund under the gaming rules” is citing a rule that was never notified. Don’t build your strategy on it.

What actually governs refunds, in order of strength

With the 180-day rule gone, a Teen Patti refund rests on four pre-existing pillars:

1. RBI / NPCI rail rules — the strongest. For any failed deposit, duplicate, or unauthorised payment, the RBI failed-transaction TAT circular forces a T+1 (account) or T+5 (merchant) auto-reversal with ₹100/day compensation, and the 3-working-day zero-liability rule covers unauthorised transactions. These bind your bank, which is RBI-regulated — real teeth.
2. Consumer Protection Act, 2019 — moderate. Refusing to refund for a deficient or undelivered service is a defined deficiency in service / unfair trade practice. The E-commerce Rules, 2020 reinforce that an entity cannot refuse to refund for a service “not as agreed.” This reaches the operator, via the National Consumer Helpline and consumer forums.
3. Contract law — case-by-case. The operator’s own published refund policy and Terms are a contract; where they promise a refund for failed deposits or duplicates, that promise is enforceable. Where they (lawfully) say “deposits are non-refundable once played,” that binds too.
4. The OGAI grievance ladder — the new gaming-specific door. Post-PROGA, an aggrieved user complains to the operator first, and if unsatisfied may approach the Online Gaming Authority of India (OGAI) within 30 days, with a final appeal to the Secretary, MeitY — each stage with its own 30-day resolution expectation.

The OGAI grievance ladder, precisely

Because the 180-day shortcut is gone, the OGAI ladder is now the gaming-specific escalation spine, and its timings are worth memorising:

• Stage 1 — Operator’s grievance officer. Raise the refund complaint with the operator first. The service provider is expected to resolve grievances within 30 days.
• Stage 2 — OGAI. A user aggrieved by the operator’s outcome may approach the OGAI directly within thirty days of that outcome. (Note: the draft Rules had a Grievance Appellate Committee as a buffer layer; the final Rules removed it, so it’s operator → OGAI directly.)
• Stage 3 — Secretary, MeitY. A final appeal lies to the Secretary, MeitY, again on a 30-day cycle.

The legal bottom line in two facts: (1) there is no 180-day statutory gaming refund — that draft rule was dropped; (2) your real leverage is the RBI rail rules (for failed/duplicate/unauthorised payments) and, for an undelivered service, the Consumer Protection Act plus the operator → OGAI (30 days) → MeitY ladder. Aim your refund at the right one of those, not at a rule that doesn’t exist.

Operator refund vs bank/rail reversal — the distinction that decides your speed

This is the single most useful mental model on the page. Every refund you might pursue is either an operator refund or a rail reversal, and they behave so differently that mixing them up can cost you a month.

The practical reading:

• If your refund is a failed deposit, duplicate, or unauthorised charge, you want the rail reversal — it’s faster, rule-backed, and carries compensation. The operator is almost a bystander; your lever is the bank/UPI dispute with the UTR. Don’t waste a week emailing the app when the rail must reverse it anyway.
• If your refund is for an undelivered service (the deposit worked, but a paid tournament/pass didn’t), there’s nothing for the rail to reverse — the money correctly reached the operator. Here the operator refund is your only path, slower and policy-bound, escalating through consumer law and OGAI.
• A subtle trap: people whose failed deposit should be a fast rail reversal instead spend weeks chasing the operator for a “refund,” because the app is the visible party. Flip it. A failed deposit is a payment problem first — go to the bank/UPI, and the UPI failed money debited page walks the exact dispute.

Operator vs rail in one line: a rail reversal is fast, rule-backed, and carries ₹100/day for delay; an operator refund is slow, policy-bound, and carries nothing. Match your scenario to the right one — failed/duplicate/unauthorised go to the bank, undelivered-service goes to the operator — and you cut weeks off the process.

Three worked refund walkthroughs (so you can see the whole arc)

Abstract rules are hard to act on. Here are three concrete cases, start to finish, each a different scenario, so you can see exactly which door, which clock, and which outcome applies. The amounts are illustrative, not a record of any real account.

Walkthrough A — a ₹500 failed deposit that self-reverses

You tap “Add ₹500” in a Teen Patti app, your bank debits ₹500, and the app shows “payment failed — please retry.” Your wallet still reads zero. This is Scenario 1, a failed deposit, and it’s the textbook fast refund.

• Day 0, hour 0: you screenshot the failed screen and the bank debit SMS, and you open your UPI app’s transaction detail to copy the UTR (a 12-digit number). You do not retry the deposit — a retry is how duplicates happen.
• Day 0–1: you wait. Under the RBI TAT circular, a debited-but-not-completed UPI transaction must auto-reverse by T+1. Most do.
• Day 1, morning: ₹500 lands back in your bank account (not the app wallet). The refund is done, with zero effort beyond capturing the UTR.

If it hadn’t reversed by T+1, the next move would be a UPI dispute (it routes into NPCI UDIR) plus a ₹100/day compensation claim. Total realistic timeline: one working day, sometimes hours. This is why a failed deposit is the best refund to have.

Walkthrough B — a ₹2,000 duplicate charge

You add ₹2,000, the screen lags, you tap again, and your statement shows two ₹2,000 debits seconds apart — but your wallet credited ₹2,000 once. The second debit bought nothing. This is Scenario 2, a duplicate.

• Day 0: you capture both UTRs and the wallet history showing a single ₹2,000 credit. That pattern — two debits, one credit — is unambiguous, and banks reverse it routinely.
• Day 0: you raise a dispute with your bank (Template B below), quoting both UTRs and noting only one credit. You do not chase the operator first — the operator received ₹2,000 once and may not even see the duplicate; the bank is the lever.
• Day 2–7: for a UPI duplicate, the bank’s failed-transaction cycle reverses the second ₹2,000 to your bank account. Had it ridden a card, it would follow the chargeback timeline — usually a week or two for a clear duplicate, up to 120 days at the outer edge.

Outcome: ₹2,000 back to the source. Realistic timeline: days. Note the discipline — you disputed the duplicate, not the underlying ₹2,000 that correctly bought chips.

Walkthrough C — a ₹1,500 charge a child made

Your statement shows a ₹1,500 deposit to a card-game app you didn’t make. It turns out a minor used your saved UPI. This is Scenario 3, unauthorised — and the clock is brutal.

• The moment you discover it: you call your bank and report an unauthorised electronic transaction. Under RBI’s customer-liability framework, reporting within 3 working days caps your liability at zero. You follow up in writing (Template C) with the transaction reference and the discovery date.
• Same day: the bank opens a fraud/unauthorised-transaction case. You secure the saved payment method so it can’t recur.
• Investigation window: the bank reverses ₹1,500 after verifying it was unauthorised. The credit returns to your account/card.

Outcome: recoverable if you reported inside 3 working days. The critical variable here isn’t the amount — it’s speed. A week’s delay can move your liability off zero. This is the one refund where the clock starts the instant you notice, not the instant it happens.

The three walkthroughs in one line: a failed deposit is a one-day, near-automatic rail reversal; a duplicate is a days-long bank dispute with both UTRs; an unauthorised charge is a same-day fraud report racing a 3-working-day clock. Different scenarios, different doors, very different speeds — which is the whole reason to classify first.

What evidence a refund actually needs (and why Day 0 capture wins it)

A refund is won or lost on documentation, not on how upset you are. Each scenario needs a specific evidence set, and almost all of it has to be captured on Day 0, because references age out of an app’s quick view and a bank can’t trace a credit you can’t name. Here is the exact evidence per ground.

• Failed deposit: the UTR of the debit, the bank SMS/statement showing money left, and a screenshot of the wallet showing no credit. Those three prove “money out, value not in” — the entire claim.
• Duplicate: two UTRs debited close together, plus the wallet history showing a single credit. The proof is the mismatch between two debits and one credit.
• Unauthorised: the transaction reference, your statement, and a clear note of the date/time you discovered it (the 3-day clock anchors there). For a minor’s spend, the account context.
• Service-not-rendered: the order ID / receipt for the specific deliverable, and evidence it never came — the tournament that didn’t run, the pass that stayed locked, a screenshot of the unfulfilled purchase.

A few rules about that evidence that decide cases:

• The UTR is one number, labelled differently everywhere. PhonePe calls it “UPI Reference No.,” Google Pay “Bank Reference ID,” Paytm “UPI Ref No.,” BHIM “Transaction ID” — all the same 12-digit thread tying your debit to a missing credit. Capture whichever your app shows.
• Screenshots must be date-stamped. A wallet screenshot with no timestamp proves little. The status screen, the amount, and the time together build the timeline a dispute officer reads.
• Written beats verbal, every time. An in-app chat can vanish; an email to the grievance officer and a bank complaint reference number create a paper trail you can cite to the Ombudsman or OGAI later. Always convert a phone call into a written follow-up with the reference number.
• Keep the “before and after” wallet balance. For a failed deposit especially, showing the wallet unchanged across a debit is the cleanest proof the value never arrived.

The reason Day 0 capture matters so much: a “failed” transaction drops out of an app’s recent-activity view quickly, and once it does, digging the UTR back out is far harder. A refund you could have won in a day by screenshotting a reference becomes a week of back-and-forth because the number is buried. Five minutes of documentation in the first hour is the highest-leverage thing you do in the whole process.

The evidence rule in one line: capture the UTR and a date-stamped before/after screenshot on Day 0, and put every escalation in writing — a refund is proved by references, not by frustration, and the references are easiest to grab in the first hour.

The exact refund-request flow, step by step

Here is the process, sequenced. Don’t skip the documentation step — a refund stands or falls on whether you captured the reference on Day 0.

Step 1 — Freeze the evidence (within the first hour)

Before you click any “refund” or “dispute” button:

• Screenshot the transaction: the deposit attempt, the amount, the timestamp, the error/“failed” screen if any, and your wallet balance before and after. For a duplicate, capture both debit SMS/statements. Date-stamped screenshots are your case.
• Capture the UTR / RRN — the 12-digit reference for the debit. It’s in your UPI app’s transaction detail, the bank SMS, and your statement. No UTR means you cannot trace or dispute a rail transaction. For an unauthorised charge, capture the transaction details and note the date/time you discovered it (the 3-day clock starts there).
• Note which scenario you’re in (failed deposit / duplicate / unauthorised / service-not-rendered) — it decides Step 2’s door.

Step 2 — Knock on the right first door

• Failed deposit, duplicate, unauthorised (Scenarios 1–3): go to your bank / UPI app first. In your UPI app, open the transaction → “raise complaint / dispute” (this feeds NPCI UDIR). For an unauthorised charge, also call the bank immediately to report fraud — the 3-day window is what caps liability at zero. Use Template B below.
• Service-not-rendered (Scenario 4): go to the operator’s grievance officer / in-app support first, with the order ID and proof of non-delivery. Use Template A. The rail has nothing to reverse here.

Step 3 — Wait the correct clock (don’t escalate early)

• Failed UPI deposit: wait through T+1 — the auto-reversal usually fires by then. Merchant-confirmation failures get T+5. Escalate only after the window.
• Duplicate: allow the bank’s failed-transaction cycle; a card duplicate may run on the chargeback timeline.
• Unauthorised: no waiting — report same-day; the bank investigates.
• Operator refund: the operator’s stated grievance window, up to 30 days under the OGAI ladder.

Step 4 — Escalate if the window passes

• Rail cases still unresolved: push the NPCI UDIR complaint, claim ₹100/day past T+1, and after 30 days without resolution from the bank, file free with the RBI Integrated Ombudsman. Use Template C / D.
• Operator cases denied: escalate to the National Consumer Helpline 1915, and via the OGAI ladder — operator → OGAI within 30 days → MeitY. Use Template E. The deeper escalation playbook is on the customer-care escalation page.

Step 5 — Report fraud in parallel, if relevant

If the “refund” is actually a scam (a fake “refund agent” who calls asking for your OTP/UPI PIN to “process your refund”), that’s fraud — report it immediately to cybercrime 1930 and cybercrime.gov.in. No legitimate refund ever requires you to share an OTP or PIN, or to deposit money “to release a refund.” Both are theft patterns.

The flow in one line: document the UTR on Day 0 → bank-first for failed/duplicate/unauthorised, operator-first for undelivered-service → wait the correct clock (T+1/T+5/30 days) → escalate to NPCI/RBI or NCH/OGAI → report any “refund agent” asking for an OTP to 1930.

Each operator’s stated refund-policy pattern

Operator refund policies follow a recognisable pattern across Indian RMG apps, even though the informal Teen Patti brands publish less than the licensed rummy operators did. Below is the pattern, framed third-person from published policies — not a personal test — split into the deposit side (where refunds are sometimes possible) and the gameplay side (where they generally aren’t). A blunt 2026 caveat: RummyCircle and Junglee Rummy discontinued cash play under PROGA, so their rows describe how the policies worked and how a wind-down recovery still behaves.

The universal pattern

Almost every Indian RMG refund policy says the same three things, in different words:

• Failed/unsuccessful deposits are reversed — money debited without chips credited is returned, typically on the rail’s own timeline (the operator points you to the bank for the auto-reversal). This is the refund operators do honour, because the rail forces it anyway.
• Deposits, once successfully credited, are largely non-refundable — because the chips were delivered. Some operators allow a refund of an unused, never-played deposit at their discretion; most require play-through first.
• Game outcomes are final — a lost game is never refunded. This is stated explicitly in nearly every policy.

Teen Patti Gold / Teen Patti Master (informal brands)

These are multi-skin informal brands, so a single authoritative refund table doesn’t exist — judge by the exact build you installed, and for the contact/escalation side see customer-care escalation.

RummyCircle / Junglee Rummy (cash discontinued under PROGA — wind-down)

The operator-policy reading in one line: every legitimate operator refunds a failed deposit (the rail forces it) and refuses to refund a lost game (the service was delivered) — the only grey zone is an unused, never-played deposit, which some refund at discretion. Don’t expect a policy refund for anything you actually played.

Realistic refund timelines per scenario

“How long will my refund take” has no single answer, because each scenario rides a different clock. Timings marked with a rule reference are RBI/NPCI-mandated; the rest are typical behaviour and should be read as estimates.

Read that table as a set of clocks, one per scenario. The mistake to avoid is escalating before your row’s window closes (the bank tells you to wait, and you’ve burned goodwill) or after a TAT lapses (you’ve lost the easy ₹100/day claim). The failed-deposit row is the fastest and most protected; the operator-service row is the slowest and weakest. That asymmetry should shape how much patience you bring to each.

Where the refund money actually comes back to

A surprising number of “I never got my refund” complaints are actually refunds that did arrive — just not where the person was looking. Three things to check before you re-escalate:

• A rail reversal returns to the source. A failed-deposit auto-reversal goes back to the bank account or UPI handle the deposit left from, not into your app wallet. If you deposited from your SBI account, check that account’s statement, not the Teen Patti balance.
• An operator refund usually returns to your wallet. A goodwill or service-not-rendered refund from the operator typically lands as chips/balance in the app, which you then have to withdraw — converting it back into a separate withdrawal process. (That’s why some “refunds” feel incomplete: the operator refunded the wallet, but you still have to cash it out.)
• A card chargeback returns to the card. A disputed card transaction reverses to the card statement as a credit, on the issuer’s cycle.

So before declaring a refund missing, confirm which mechanism you used and where that mechanism returns money, and check the right place. A failed-deposit reversal you’re hunting for in your app wallet will never show up there — it went back to your bank.

The “where’s my refund” rule in one line: rail reversals go back to your bank/card (the source); operator refunds go into your app wallet (and then you must withdraw them). Check the source for Scenarios 1–3, the wallet for Scenario 4.

How the refund differs by payment rail you deposited with

The rail you deposited with shapes how the refund behaves and which door you knock on, because each rail has its own dispute mechanism and its own clock. Four rails cover almost every Indian gaming deposit.

• UPI deposit. The most common and the most protected. A failed UPI debit gets the T+1 auto-reversal under the RBI TAT circular, and the in-app “raise complaint” feeds NPCI UDIR with a stated 3–5 working-day resolution. The refund returns to the bank account linked to your UPI. This is the easiest rail to recover from.
• Card (debit/credit) deposit. A card deposit gone wrong is disputed through your card issuer’s chargeback process, which runs on the card timeline — often days for a clear duplicate, up to 120 days at the outer edge with arbitration. The refund credits your card statement. Caution: card chargebacks are exactly where the friendly-fraud trap lives — only dispute genuine failed/duplicate/unauthorised charges, never a lost game.
• Net banking deposit. A failed net-banking debit reverses through your bank’s failed-transaction process; you raise it with the bank using the transaction reference, and it returns to the same account. Timelines track the bank’s own reconciliation cycle rather than UPI’s T+1.
• Wallet (Paytm/other) deposit. A failed wallet-funded deposit may reverse to the wallet balance first, not your bank, so check the wallet’s passbook before declaring it missing. The wallet provider’s grievance flow is the door here.

The cross-rail lesson: identify how you funded the deposit before you pick a dispute channel, because chasing a card chargeback for a UPI failure (or vice versa) wastes days at the wrong desk. The reference number’s home is the rail you used. For the UPI-specific dispute, screen by screen, the UPI failed money debited page is the deep version.

The rail rule in one line: UPI failures reverse fastest (T+1, via NPCI UDIR), card disputes are slowest and carry the friendly-fraud risk, net-banking and wallet failures route through the bank or wallet provider respectively — match your dispute to the rail you actually deposited with.

When a legitimate refund is denied: the escalation ladder

You ran the entitlement test, you had a real ground, you requested it the right way — and you were denied or ignored. Here is the climb, matched to the scenario, because a denied rail refund and a denied operator refund escalate through different authorities.

For a denied rail refund (failed deposit, duplicate, unauthorised)

1. Re-raise the UPI/bank dispute with the UTR, explicitly citing the RBI TAT circular and demanding the ₹100/day if you’re past T+1. Get a complaint reference number.
2. NPCI UDIR — escalate the specific UTR through the NPCI UPI Help portal or 1800-120-1740; UDIR can auto-convert to a chargeback once the TAT lapses. Stated resolution: 3–5 working days.
3. RBI Integrated Ombudsman — after 30 days without resolution from your bank (a regulated entity), file free at cms.rbi.org.in under RB-IOS 2021, which covers banks and Payment System Participants.

For a denied operator refund (service-not-rendered, wrongly refused)

1. Operator’s grievance officer — a formal written complaint (not just in-app chat), referencing the Consumer Protection Act 2019 deficiency-in-service ground. The operator is expected to resolve within 30 days.
2. OGAI — if the operator’s outcome is unsatisfactory, approach the OGAI within 30 days of that outcome.
3. Secretary, MeitY — the final appeal in the gaming ladder, again on a 30-day cycle.
4. National Consumer Helpline 1915 / consumer forum — in parallel, for the service-deficiency angle, since the operator owes a consumer-law duty independent of the gaming rules.

For a fraud-flavoured loss (fake refund agent, clone app)

Report immediately to cybercrime 1930 and cybercrime.gov.in, and flag suspicious payment entities on the RBI Sachet portal. A “refund agent” who calls asking for your OTP/PIN, or who tells you to deposit to “release” your refund, is a scammer — and the fraud report, not a refund dispute, is the right channel.

The denial-escalation in one line: a denied rail refund climbs bank → NPCI UDIR → RBI Ombudsman (after 30 days); a denied operator refund climbs grievance officer → OGAI (within 30 days) → MeitY, with NCH 1915 in parallel — and any OTP-asking “refund agent” goes straight to 1930. The deeper, channel-by-channel version is on customer-care escalation.

The honest limit of this ladder

Be realistic about reach. The RBI/bank route is powerful against the payment rail (Scenarios 1–3), because banks and PSPs are RBI-regulated and must comply. It is weaker against an unlicensed or offshore operator that simply ignores you. The OGAI route is new and its enforcement muscle against a discontinued or non-compliant operator is still being tested. So a refund for money lost on the rail is the recoverable kind; a balance trapped inside a wound-down or shady operator is the genuinely hard kind — pursue it through the chain above, but never deposit more “to unlock” it. Post-PROGA, that deposit is both throwing good money after bad and illegal. The refund-dispute-recovery decision tree lays out the odds for each loss type.

Copy-paste refund-request templates

Fill in the bracketed parts. Keep every message factual, dated, and reference-stamped — a UTR and a clear scenario move a refund; emotion doesn’t. Six templates, one per door.

Template A — Operator refund request (failed deposit / service-not-rendered)

Subject: Refund request — [failed deposit / undelivered service] — ₹[AMOUNT]

I am requesting a refund for a transaction where I did not receive what
I paid for.
- Type: [deposit debited but no chips credited / paid for TOURNAMENT/PASS
  that was not delivered]
- Amount: ₹[AMOUNT]
- Date/time: [DATE, TIME]
- UTR / order ID: [UTR or ORDER ID]
- Registered mobile: [NUMBER]
- Wallet credited? [No — chips never arrived / N/A]

The service paid for was not rendered, which is a deficiency in service
under the Consumer Protection Act, 2019. Please refund ₹[AMOUNT] to the
original source and share a complaint/ticket ID. If unresolved within
your 30-day grievance window, I will escalate to the OGAI and the
National Consumer Helpline (1915).

Template B — Bank / UPI failed-deposit or duplicate dispute (Scenarios 1, 2)

Subject: Failed/duplicate UPI debit — UTR [UTR] — request refund + TAT compensation

A UPI transaction was debited but [not completed / billed twice].
- UTR / RRN: [UTR]   (for a duplicate, also: second UTR [UTR2])
- Amount: ₹[AMOUNT]
- Date/time: [DATE, TIME]
- My account / UPI ID: [A/C or HANDLE]
- Service received: [none — chips not credited / only one credit for two debits]

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

Template C — Unauthorised transaction report (Scenario 3 — send same day)

Subject: URGENT — Unauthorised transaction — request immediate reversal

I am reporting an electronic transaction I did NOT authorise.
- Amount: ₹[AMOUNT]
- Date/time: [DATE, TIME]
- UTR / card reference: [UTR / last 4 of card]
- Discovered on: [DATE] (reporting within 3 working days)
- I did not authorise this payment [/ it was made by a minor without consent].

Per RBI's customer-liability framework, my liability for an unauthorised
electronic transaction reported within 3 working days is zero. Please
block the instrument if needed, investigate, and reverse ₹[AMOUNT].
Please confirm the complaint reference number.

Template D — RBI Ombudsman (RB-IOS) — rail refund, after 30 days

Nature of complaint: Deficiency in service — failed/unresolved digital
payment (gaming deposit debited but not credited / not refunded).

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

File Template D at cms.rbi.org.in only after 30 days without resolution from the entity — that 30-day rule is the eligibility gate for RB-IOS 2021.

Template E — National Consumer Helpline / OGAI escalation (operator refund denied)

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

Complaint: Service deficiency — gaming operator refused a legitimate
refund for a service not rendered.
- Operator / app: [APP NAME]
- Registered mobile: [NUMBER]
- Refund amount owed: ₹[AMOUNT] for [undelivered TOURNAMENT/PASS/etc.]
- Requested on: [DATE]; grievance ticket [TICKET ID] raised [DATE]
- Operator's response: [denied / no response after 30 days]
Relief sought: refund of ₹[AMOUNT] to my original source, and a written
reason for the refusal. I am also approaching the OGAI within 30 days
of the operator's grievance outcome.

The template rule in one line: aim Template A at the operator for an undelivered service, B/C at your bank for failed/duplicate/unauthorised payments, and D/E at the RBI Ombudsman and consumer/OGAI channels only after the 30-day windows lapse. Always quote the UTR and the specific scenario — a vague “give me my money back” gets a vague “no.”

Grievance contact reference block

Keep this handy. Use the door that matches your refund type.

Order of doors, in one line: for a rail refund, bank → NPCI → RBI Ombudsman; for an operator refund, grievance officer → OGAI → MeitY, with NCH 1915 in parallel and cybercrime 1930 the instant a “refund agent” asks for an OTP.

Is it a real refund process or a refund scam? Red flags

Refund scams in India specifically prey on people chasing a stuck gaming refund — the victim is already expecting money back, which makes the lie easy. Watch for these:

• A “refund agent” calls or messages you. Real refunds come through your bank or the in-app dispute flow, not from a person who contacts you first. A caller who “found your complaint” and offers to “process your refund” is almost always a scammer.
• They ask for an OTP, UPI PIN, or card CVV “to process the refund.” No refund anywhere requires you to enter your PIN — a PIN authorises money leaving your account, never arriving. This is the single clearest theft tell.
• “Deposit ₹X to release your refund / unlock your balance.” No legitimate refund requires a payment to receive it. Post-PROGA, that deposit into a money game is also illegal.
• A “refund link” or a screen-share app (AnyDesk/TeamViewer). Installing remote-access software at a “refund agent’s” request hands them your phone. Never do it.
• The number came from a Google search, YouTube comment, or random site. Most apps route support in-app and have no public refund hotline; numbers posted publicly are overwhelmingly scam bait.

If you see two or more of these, you’re not in a refund process — you’re in a scam attempt. Stop, share nothing, and report to 1930 and cybercrime.gov.in.

The scam test in one line: a real refund never requires your OTP/PIN, never requires a deposit to “release” it, and never comes from someone who contacts you first. If any of those is happening, it’s theft — report it, don’t engage.

Related fixes (go deeper on your exact case)

This is the refund-process spoke. For your specific case, these go step-by-step:

• The whole money-recovery map → gaming refund decision tree — classify the loss, see the odds per type, route to the right door.
• Failed deposit / debited-but-not-credited → UPI failed, money debited — the exact NPCI UDIR dispute, screen by screen, and the ₹100/day claim.
• Winnings won’t come out (not a refund — a withdrawal) → 3 Patti withdrawal hub — the four payout gates and the Day-0-to-30 ladder.
• Operator won’t respond / refund denied → customer-care escalation — the channel-by-channel escalation and the scam-number warning.

FAQ

1. How do I get a refund from a Teen Patti app? First decide if you’re owed one. You’re owed a refund only when money left your account but you got nothing for it — a failed deposit, a duplicate charge, an unauthorised transaction, or an undelivered paid service. For the first three, raise a dispute with your bank/UPI using the UTR; for the fourth, request it from the operator’s grievance officer. A lost game is not refundable.

2. Is there a 180-day refund window for gaming apps under the new rules? No. A draft PROGA rule would have allowed platforms 180 days to return user funds, but it was dropped from the final 2026 Rules. There is no statutory gaming-refund clock. Refunds fall back to RBI rail rules, the Consumer Protection Act, contract law, and the operator → OGAI (30 days) → MeitY ladder.

3. Can I get a refund for money I lost playing Teen Patti? No. A lost game is not a refundable transaction — the service (a fair game of cards) was delivered, and the outcome is the agreed result, not a defect. Disputing a genuine gambling loss with your card issuer is friendly fraud, which can get you blacklisted across operators and flagged by your bank.

4. My deposit was debited but no chips were credited — how do I get it back? That’s a failed deposit, the most protected refund ground. Under RBI’s failed-transaction circular, a debited-but-not-credited UPI transaction is auto-reversed by T+1 (T+5 for merchant-confirmation failures), with ₹100/day compensation after that. Capture the UTR, wait through T+1, then raise a UPI dispute if it hasn’t returned. The UPI failed money debited page has the screen-by-screen flow.

5. I was charged twice for one deposit — is that refundable? Yes. A duplicate charge — two debits, one chip credit — is refundable. Dispute it with your bank using both UTRs; a clear duplicate is usually reversed within the bank’s failed-transaction cycle. On a card, it follows the chargeback timeline, which can run up to 120 days at the outer edge but resolves faster for an obvious double charge.

6. Someone made a payment from my account without permission — what do I do? Report it to your bank immediately. Under RBI’s customer-liability rules, if you report an unauthorised electronic transaction within 3 working days, your liability is zero (source). The 3-day clock starts when you discover it, so speed is everything. This ground is for genuinely unapproved payments — including a minor’s spend — not for disguising a gambling loss.

7. What’s the difference between an operator refund and a bank reversal? A bank/rail reversal returns money that left your account but didn’t complete (failed deposit, duplicate, unauthorised) — it’s fast, RBI-backed, carries ₹100/day for delay, and goes back to your bank. An operator refund puts balance back in your app wallet (for an undelivered service) — it’s slower, policy-bound, and carries no mandated compensation. Match your scenario to the right one.

8. Where does the refund money actually come back to? A rail reversal returns to the source — the bank account or UPI the deposit left from, not your app wallet. An operator refund lands as balance in the app, which you then have to withdraw. A card chargeback credits your card statement. Many “missing refund” complaints are refunds the person was looking for in the wrong place.

9. How long should a Teen Patti refund take? It depends on the scenario. A failed UPI deposit auto-reverses by T+1; a merchant-confirmation failure by T+5; an unauthorised transaction is investigated after a same-day report; a duplicate takes days (UPI) to weeks (card); an operator service refund runs on the operator’s 30-day grievance window. There is no universal “gaming refund” timeline.

10. The app refuses to refund my deposit — what are my options? If it’s a failed/duplicate/unauthorised payment, you don’t need the app — go to your bank/UPI, then NPCI UDIR, then the RBI Ombudsman after 30 days. If it’s a service the app didn’t deliver, escalate through the operator grievance officer → OGAI (within 30 days) → MeitY, with the National Consumer Helpline 1915 in parallel.

11. What is the OGAI and when do I use it? The Online Gaming Authority of India (OGAI) is the body set up under the PROG Rules 2026 as an attached office of MeitY. For a refund the operator refused, you complain to the operator first (resolved within 30 days), then may approach the OGAI directly within 30 days of that outcome, with a final appeal to the Secretary, MeitY.

12. Someone called offering to “process my gaming refund” — is it real? Almost certainly not. Real refunds come through your bank or the in-app dispute flow, never from a stranger who contacts you first. If they ask for your OTP, UPI PIN, or CVV, or tell you to deposit money to “release” the refund, or to install a screen-share app, it’s a scam. A PIN only authorises money leaving your account. Report to cybercrime 1930 and cybercrime.gov.in.

13. Can I get a refund after PROGA banned the app I deposited into? A failed or unauthorised deposit that never credited may still be reversible on the rail, since the RBI protections survived. But a successful deposit into a now-banned money game is a hard recovery — and a new deposit in 2026 is illegal. For a trapped balance, follow the in-app recovery flow; the refund-dispute-recovery tree covers the odds.

14. Will disputing a charge with my bank cause problems? For a genuine failed deposit, duplicate, or unauthorised charge — no, that’s exactly what disputes are for. For a lost game dressed up as a dispute — yes. That’s friendly fraud: the operator submits its IP/gameplay/KYC evidence, the chargeback is reversed, your account is closed, and you risk being blacklisted across operators and flagged by your bank. Only dispute genuine grounds.

15. Is a refund the same as a withdrawal? No. A refund reverses a payment that shouldn’t stand (you paid, got nothing). A withdrawal cashes out a balance you legitimately hold (winnings you earned). They use different rules and different doors. If your winnings won’t come out, that’s a withdrawal problem — see the 3 Patti withdrawal hub, not this page.

Sources & method. Refund grounds, timelines, taxes, legality and escalation on this page are built from primary regulatory sources and named operator policies — not personal payout tests. Key references: RBI failed-transaction TAT circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019); RBI customer-liability / 3-day zero-liability framework via chargeback guidance; card chargeback timeline; RBI Integrated Ombudsman Scheme 2021 and cms.rbi.org.in; RBI Sachet portal; NPCI UPI Help / UDIR; the Consumer Protection Act, 2019 and E-commerce Rules, 2020; the Promotion and Regulation of Online Gaming Act, 2025 and the PROG Rules 2026 (in force 1 May 2026, the draft 180-day platform refund window omitted per the 2026 rules analysis); friendly-fraud risk via chargeback guidance and chargeback blacklisting; 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 dispute policy.