RMG Customer Care & Complaint Escalation: The India Map

The 30-second answer

Indian real-money gaming (RMG) apps almost never run a public phone helpline. Real support is in-app first, then official email, then a grievance / nodal officer. The moment money left the payment rail, it becomes a bank + NPCI UDIR dispute, then the RBI Ombudsman after 30 days of no resolution. For a clean balance an app simply won’t pay, run the National Consumer Helpline 1915 in parallel. For any fraud — a fake “care number,” an OTP you shared — call cybercrime 1930 inside the golden hour and file at cybercrime.gov.in. Pick the rung that matches your problem; don’t climb past it.

Editor’s verdict, up front. Almost every “how do I contact RMG customer care” search starts from the wrong instinct — that there’s a phone number, that a human will pick up, that one call fixes it. For these apps, that’s rarely true, and the gap between what you expect and what exists is exactly where scammers and wasted days live. So this page is not a list of numbers. It’s a routing map: six escalation rungs, each aimed at a different authority, each with its own clock, its own evidence requirement, and its own realistic turnaround. The single most useful skill here isn’t persistence — it’s diagnosis. Sort your problem into the right rung and you’ll often clear it in days. Send it to the wrong door — RBI on day one, a “care number” off YouTube, a consumer forum for a fraud — and you’ll burn weeks or your savings. This is the hub for the whole complaint cluster; the deep, app-specific pages link out from each rung.

2026 reality you must read first. The legal ground shifted 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, with Rules in force from 1 May 2026. India’s biggest operators suspended cash play from late August 2025. Two consequences run through this whole page. First, support is now thinner than ever — wound-down operators cut staff, so the escalation chain to your bank, NPCI and RBI matters more, because those don’t depend on the app answering. Second, a new deposit into a money game is now illegal, so any “support agent” who tells you to pay a fee to release your balance is committing a crime and you hang up. Every rung below reads two ways: for a still-live app, and for a wound-down balance recovery.

Why “customer care number” is the wrong starting point

Fix the wrong assumption before you climb anything, because it’s the assumption that wastes your first week. The mental model most people carry — a problem means you call a toll-free line and a human solves it — was built by banks, telecoms and airlines over forty years. It does not map onto an app like a Teen Patti build, a rummy app, or any informal-brand card game. The mismatch is the whole problem.

Here’s the structural reality. Most RMG apps in India are not single companies with call centres. Many are informal brand names worn by several builds and skins, distributed largely outside the Google Play Store (Play restricts real-money gambling apps in India), with the operating entity often unclear from inside the app. There is usually no published, verified toll-free helpline — support, where it exists, runs through an in-app ticket / chat system and an email address. That’s normal for digital-first apps worldwide: tickets scale, phone lines don’t, and a phone line for millions of users is expensive and slow.

So when you search the app’s name plus “customer care number,” you are usually searching for a thing that does not exist as a public phone line. And a vacuum invites fraud. Scammers pour fabricated numbers into that empty space because the search demand is large and the searchers are pre-qualified victims — upset, money stuck, ready to do what a confident stranger says. The fix is not to find the “right” number. The fix is to stop looking for a number and use the channels that actually exist, in order: in-app support, verified official email, the grievance officer, and — when the app fails — the bank/NPCI/RBI payment chain that has legal teeth.

This hub keeps the fake-number warning brief on purpose, because one sibling page already covers it in depth for the highest-risk search. If your specific worry is a “Teen Patti Master customer care number,” the full threat model, the four scam scripts, the minute-by-minute call breakdown and the golden-hour fraud response all live there: Teen Patti Master customer care. What this page gives you instead is the universal map — the escalation chain that applies to any Indian RMG support problem, whichever app it is.

The reframe that protects you: a “customer care number” you found on a search result, a video, or a social post is not a support channel — it is an unverified phone number a stranger published. Treat it like a stranger on the street who says “give me your bank PIN and I’ll fix it.” That instinct is correct. Keep it, and use the map instead.

The six-rung escalation map, in one view

Every Indian RMG support problem routes through the same six rungs. The art is matching your problem to a rung and climbing in order — not skipping (you get bounced back) and not leaping (RBI on day one rejects you). Here is the whole map before the detail. Read down the rows until you find your problem, then go to that rung’s section.

The colour-coding to keep in your head is simpler than the table looks. Rungs 1 and 2 are operator rungs — you’re asking the app to do its job. Rungs 3 and 4 are rail rungs — RBI-regulated banks and payment systems, which is where legal force lives. Rung 5 is the consumer rung — for a service refusal, run in parallel. Rung 6 is the emergency rung — for fraud, it overrides everything and you jump straight to it. Most genuine delays die at Rung 1 or 3. The rest of this page is each rung in full.

First, diagnose: which problem do you actually have?

You cannot pick the right rung until you name the problem, because the same word — “stuck” — covers five completely different situations that escalate completely differently. Spend two minutes here and you save two weeks later.

The five problem types

Type A — Pending / processing (sitting in the app’s queue). The app shows “processing,” “pending,” or “under review.” No UTR yet. The money left your withdrawable balance but hasn’t hit the payment rail. This is an operator problem: auto-approval didn’t fire, or a manual review / daily-limit / batch delay is holding it. Route: Rung 1, then Rung 2. The deep page is withdrawal stuck.

Type B — “Paid / success” in the app, but nothing in your bank. The app marks it completed, maybe shows a UTR, but your account never received it. Either a genuine rail failure that hasn’t reflected, a stale/wrong handle, or the app’s status running ahead of reality. This is a rail problem the moment a UTR exists. Route: Rung 3 (trace the UTR through your bank), then Rung 4.

Type C — Failed, but money debited. The screen says “failed,” yet the amount left somewhere. This is the most consumer-protected state in the whole chain. Route: Rung 3 — it’s the T+1 auto-reversal case under the RBI TAT circular, with ₹100/day after.

Type D — KYC rejected / account blocked or frozen. Withdrawal blocked with a verification or restriction message. This is a verification problem, not a payment one — name mismatch, blurry document, risk freeze. Route: fix KYC first, then Rung 1–2; the deep cluster is KYC & account recovery.

Type E — Fraud. You shared an OTP/PIN, paid a “fee,” scanned a fraudulent QR, or installed a remote app at a “care number’s” instruction. Route: jump straight to Rung 6 — 1930, golden hour, now. Skip every other rung.

The one-line decision rule

If nobody phished you and the money is just slow inside the app, you’re a patient Rungs 1–2 case. If the money genuinely left the rail and vanished, you’re a Rungs 3–4 case with real legal force. If the app is flatly refusing a clean, owed balance, add Rung 5 in parallel. And if any credential, fee, or remote app crossed the line, you’re a Rung 6 emergency — the only situation where speed beats process. Diagnose first; everything downstream depends on getting this sort right.

A blunt accuracy note on amounts: Type C (failed-but-debited) is the best stuck state to be in, because the refund is rule-mandated and largely automatic. Type B (paid-but-not-received) is worse — the money supposedly went somewhere, so you need the UTR to prove it didn’t reach you. And Type A (pending in the queue) is an operator problem until the app actually hands the payout to the rail — escalating it to your bank on day one just gets you told “we have no transaction to trace.”

Rung 1 — The in-app ticket (the real first move)

Almost every legitimate RMG app routes first-line support inside the app, and it does so for a reason that also makes it the safest channel: the in-app ticket is the only surface that can verify you are actually you. It’s tied to your logged-in, registered account, it can see your transaction history, and nobody can impersonate “support” inside your own logged-in session. A phone line — even a real one — is the channel a scammer can most easily imitate. The ticket is the one they can’t.

How to file it

Look for Settings → Help / Support / Customer Service, or a headset / chat icon, usually on the profile or wallet screen. Raise a ticket describing the stuck withdrawal with three things the app can verify against its own records:

• The amount and the date/time you requested it.
• The status the app is currently showing (“processing,” “under review,” “paid”).
• The UTR / reference number if one was shown (a 12-digit reference; capture it the moment it appears).

Then get a ticket / complaint ID in writing. That ID is not a formality — it timestamps your complaint, which is what later starts the 30-day Ombudsman clock and proves to a consumer forum that you exhausted the operator’s internal process. A ticket without an ID is a conversation you can’t prove happened.

The realistic turnaround at this rung

Most legitimate apps publish or imply a first-response SLA in the 24–72 hour band, with payout windows often stated as 1–3 working days. So the honest advice for Rung 1 is patience with a clock. If this is a first-ever withdrawal, many apps run a stricter manual review on it — even a clean ₹100 test payout — before they trust the account, so a first payout taking longer than later ones is normal, not a red flag by itself. Don’t escalate inside the app’s own stated window; you’ll just be told to wait. Do escalate the moment you cross it.

What clears at this rung — and what doesn’t

Type A (pending) and Type D (KYC/blocked) problems frequently resolve right here, because they’re operator-side by nature. A pending payout was usually waiting on a manual approval the ticket nudges along; a KYC block needs you to resubmit clean documents the ticket tells you how to fix. Type B and Type C — money genuinely gone on the rail — often won’t clear here, because the operator’s honest answer is “we paid it, the UTR is X, talk to your bank.” That answer isn’t a brush-off; it’s the handoff to Rung 3. For the full payout-recovery detail behind a stuck or not-received withdrawal, the hub page maps it Day-0 to Day-30: 3 Patti withdrawal.

Rung 1 in one line: raise the in-app ticket, capture a ticket ID and any UTR, give it the app’s stated 24–72h / 1–3 working-day window, and treat its honest “we paid it, see your bank” answer not as a dead end but as the signed handoff to the rail rungs.

Rung 2 — The grievance / nodal officer

When the first-line ticket stalls past its SLA, the next operator rung is a grievance officer (sometimes called a nodal officer for complaints). This isn’t a courtesy — for regulated payment intermediaries it’s a legal requirement, and even informal RMG operators that take Indian payments sit downstream of one. Understanding why this officer exists tells you how to use them.

Where the grievance-officer requirement comes from

Every payment that moves between you and an RMG app passes through a payment aggregator (PA) — the regulated entity that actually carries the rupees. Under RBI’s framework for payment aggregators, a PA must appoint a nodal/grievance officer and publish an escalation matrix, displaying the officer’s contact details prominently, and that officer must send a final response within defined timelines — the RBI’s payment-aggregator directions set a 20-business-day target for the grievance officer and up to 30 business days for the nodal officer in the older PA-PG framework. So even if the gaming app itself is informal, the payment rail behind it has a named, accountable escalation officer by regulation. That’s leverage most players never use.

How to write the grievance-officer escalation

Two officers may matter: the app’s own grievance officer (if the app publishes one — well-run operators do), and the payment aggregator’s grievance officer (reachable via the PA whose name appears on your transaction or deposit receipt). Write to whichever you can reach, in writing, citing the unresolved first-line ticket. The letter must do three jobs:

• Establish the timeline. State the original ticket ID, the date you raised it, the app’s stated payout window, and how many days you’re now past it.
• State the exact relief. Either credit the payout, or provide the UTR and a written reason for the delay, within a deadline you set (48 hours is standard).
• Signal the next rung. Name where you’ll go next — your bank’s UPI dispute, NPCI UDIR, the RBI Ombudsman, the consumer helpline. A complainant who clearly knows the process is unstuck more often than one who pleads.

The grievance-officer letter does double duty: beyond chasing the payout, it is the document that proves you exhausted the operator’s internal process. That proof is the entry ticket for the consumer-forum and Ombudsman rungs, both of which expect you to have tried the entity first. So even if the officer ignores you, the dated letter you sent is not wasted — it’s evidence.

The realistic turnaround at this rung

By the RBI norms above, a regulated intermediary’s grievance officer owes a final response within roughly 20–30 business days. In practice a well-run operator answers faster, and a wound-down or offshore one may not answer at all. Either outcome is useful: a response that resolves it ends your problem, and silence past the deadline is exactly the “no resolution from the regulated entity” condition that unlocks the RBI Ombudsman at Rung 4. The deep page on the grievance-officer mechanism across Indian RMG operators lives in this cluster; for now, treat Rung 2 as the bridge that converts an ignored ticket into a documented, escalatable case.

Rung 2 in one line: escalate the dead ticket in writing to a grievance / nodal officer (the app’s and/or the payment aggregator’s, who exists by RBI regulation with a 20–30 business-day response duty), set a deadline, name your next rung — and keep the dated letter, because it’s the proof of “internal process exhausted” that the consumer forum and Ombudsman demand.

Rung 3 — The bank + NPCI UDIR dispute (the rail rung with teeth)

This is the rung where leverage changes hands. The moment your money left your bank or the app’s wallet and never reached you, the problem stops being a “gaming app” matter and becomes a payment-system matter — and the payment system is RBI-regulated with hard, mandated timelines and a real dispute machine behind it. That single shift is your strongest weapon, so understand it precisely.

Why a failed payout is the best stuck state to be in

“UPI is instant” is true for the successful path. The failure path runs on reconciliation cycles, which is why a failed payout can sit in limbo before it bounces back. When a UPI payout is initiated, money is debited at the sending side and a credit instruction goes to your bank. If your bank doesn’t confirm the credit — it was down, the handle didn’t resolve, a timeout — the transaction sits in a deemed-failed / pending state and is reconciled in cycles, not instantly. The rule that governs the outcome is RBI’s Harmonisation of Turn Around Time (TAT) circular.

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: the transaction must be auto-reversed by T+1 (the day after the transaction). If it isn’t, the bank owes you ₹100 per day of delay beyond T+1, credited automatically — you don’t have to ask.
• The ₹100/day compensation applies to technical/system failures, not to your mistakes (sending to a wrong handle), but a stuck app-to-you payout is a system path, so it’s covered.

So a Type C “failed but debited” payout is already obligated to reverse, usually within one working day, automatically. The correct first move is often wait through T+1, then dispute — not panic-spam support on hour one.

How UDIR actually processes the dispute

The machine that handles these is NPCI’s Unified Dispute and Issue Resolution (UDIR) system, surfaced for consumers at the NPCI UPI Help portal (upihelp.npci.org.in). UDIR replaced slow, manual, file-based dispute handling with an automated, API-driven flow, and it auto-converts an unresolved complaint into a chargeback once the prescribed TAT lapses. The current chargeback auto-conversion windows, per NPCI’s UDIR framework, are T+1 for person-to-person (P2P) transactions and T+3 for person-to-merchant (P2M) — and from 15 February 2025, NPCI moved to automatic acceptance or rejection of chargebacks in the next settlement cycle based on the beneficiary bank’s response, per the new UPI chargeback rule. NPCI’s stated UDIR resolution window for a consumer complaint is 3–5 working days, the complaint line is 1800-120-1740, and the help email is upihelp@npci.org.in.

How to raise the dispute, step by step

1. Capture the UTR on Day 0. You cannot trace or dispute a “paid but not received” payout without the UTR (also shown as a 12-digit reference / RRN). It’s in your UPI app’s transaction history, your bank SMS, and the app’s payout record. Every UPI app labels it differently — “UPI Reference No.” (PhonePe), “Bank Reference ID / UPI transaction ID” (Google Pay), “UPI Ref No.” (Paytm), “Transaction ID” (BHIM) — but it’s the same number, the single thread tying your debit to a missing credit. Capture it before the failed transaction ages out of the app’s quick view.
2. Raise the in-app “raise complaint / dispute” on that transaction. This feeds UDIR. Choose the issue (“money debited but not received” / “payment failed”) and submit.
3. Or call your bank and lodge a failed-transaction complaint with the UTR. Ask explicitly for the ₹100/day compensation if you’re past T+1 — the RBI TAT circular entitles you to it on system failures.
4. Or go straight to the NPCI UPI Help portal “Dispute Redressal” page and file with the transaction ID, bank, amount, date and email — or call 1800-120-1740 — if the in-app route stalls (common when the app no longer recognises the beneficiary).

Which rail, which door

Knowing the rail tells you who to complain to. UPI failures go to the UPI app / NPCI UDIR first. IMPS and NEFT failures go to your bank’s failed-transaction desk first, with the RRN/UTR, because there’s no consumer UPI app in that loop. A NEFT delay of up to a couple of hours is normal batch timing (NEFT settles in half-hourly batches), not a failure — don’t escalate a NEFT payout inside the first two hours. All of these ultimately escalate to the same place — your bank’s grievance officer, then the RBI Ombudsman — but the first door differs. The screen-by-screen version of this whole dispute, per UPI app, lives on the hub: 3 Patti withdrawal.

Rung 3 in one line: a failed rail payout is your strongest case, because RBI’s TAT circular forces a T+1 auto-reversal with ₹100/day after, and NPCI UDIR auto-converts an unresolved complaint into a chargeback (T+1 P2P / T+3 P2M, resolution 3–5 working days, line 1800-120-1740) — so capture the UTR on Day 0, dispute, and don’t escalate a queued (Type A) payout here, because there’s no rail transaction to trace yet.

Rung 4 — The RBI Integrated Ombudsman (RB-IOS 2021)

When a regulated entity — your bank, or the payment-system participant carrying the payout — hasn’t resolved a payment failure, the rung with the most teeth in the entire chain is the RBI Integrated Ombudsman. It’s free, it’s binding on the entity, and it exists precisely for “the bank/payment system didn’t fix my digital-payment problem.” Knowing its exact eligibility gate is what stops your complaint from being rejected on day one.

What RB-IOS 2021 actually covers

The Reserve Bank – Integrated Ombudsman Scheme, 2021 (RB-IOS) came into effect on 12 November 2021 and provides cost-free redress of customer complaints about deficiency in services by RBI-regulated entities — including banks, NBFCs, and Payment System Participants — per the RB-IOS 2021 FAQs. That “Payment System Participants” scope is the key: it’s what lets a digital-payment failure (a UPI withdrawal that was debited and never credited) reach the Ombudsman, even though the gaming app itself is not RBI-regulated. You’re not complaining about the game; you’re complaining about the rail that failed to deliver your money.

The 30-day eligibility gate

This is the gate people trip on. Under RB-IOS, you can file with the Ombudsman only after one of these is true: the regulated entity did not respond within 30 days of your complaint, rejected it wholly or partly, or you’re unsatisfied with its response. File before that 30-day window closes, with no prior complaint to the entity, and it’s rejected — which is exactly why Rungs 1–3 come first, and why the dated ticket/grievance letters you kept matter. They prove you complained to the entity and waited the 30 days. The complaint must also be filed within one year of the entity’s reply (or within one year and 30 days of your original complaint if there was no reply).

How to file with the Ombudsman

A complaint can be filed three ways, per the RBI Complaint Management System:

• Online on the CMS portal at cms.rbi.org.in — the fastest route, with automatic acknowledgement, real-time status tracking and online document upload.
• By email to cpc@rbi.org.in.
• In writing / physically to the Centralised Receipt and Processing Centre (CRPC), 4th Floor, Sector 17, Chandigarh – 160017.

After registration you get a complaint number with an SMS acknowledgement, and you can track it in real time on the portal. If the Ombudsman issues an award you disagree with — or rejects your complaint — you can appeal within 30 days to the Appellate Authority (the Executive Director-in-Charge at RBI), via the same CMS portal or by email to aaos@rbi.org.in.

The honest limit of this rung

The Ombudsman is powerful against the rail — banks and payment-system participants are RBI-regulated and must answer it. It is weak against a shady offshore or unlicensed gaming operator that simply ignores everyone, because that operator may sit outside Indian regulatory reach. So Rung 4 is your best lever for Type B and Type C (money lost on the rail), and a much weaker one for Type A (a payout still sitting inside an unresponsive app that never handed it to the rail). That asymmetry is the single strongest argument for only ever playing where payouts are clean — and, post-PROGA, for treating any new deposit into a money game as off-limits entirely.

Rung 4 in one line: after 30 days of no resolution from a regulated entity (your bank or the payment-system participant — not the gaming app), file free with the RBI Integrated Ombudsman at cms.rbi.org.in (or email cpc@rbi.org.in, or CRPC Chandigarh), get a complaint number, and appeal within 30 days if you disagree — knowing it bites the rail hard and an offshore operator barely at all.

Rung 5 — National Consumer Helpline 1915 and the consumer commissions

The rail rungs (3 and 4) fix a payment that failed. But some problems aren’t payment failures at all — they’re a service refusal: an app that holds a clean, KYC-complete, clearly-owed balance and simply won’t release it, while the rail never even got a transaction to fail. For that, the right authority is the consumer-protection system, and you run it in parallel with the rail route, because they reach different obligations through different doors.

Start with the National Consumer Helpline (1915)

The National Consumer Helpline (NCH) is the entry point. Call 1915 (or 1800-11-4000), or register online at consumerhelpline.gov.in, which runs on the INGRAM (Integrated Grievance Redress Mechanism) platform that brings consumers, companies and regulators onto one system, per the NCH about page. NCH is a mediation-first mechanism: it logs your grievance, takes it up with the company, and pushes for a resolution. It’s free, it’s available in multiple languages, and for a straightforward “the app owes me a verified balance and won’t pay” complaint it’s the fastest formal pressure you can apply that isn’t the rail.

What to have ready: the operator/app name, your registered mobile, the amount owed, the date you requested the withdrawal, the in-app ticket ID, and your KYC status (completed, PAN matching your bank account name). NCH issues a docket/complaint number — keep it.

Escalate to a consumer commission via e-Daakhil

If NCH’s mediation fails — the company ignores it or refuses — the next rung is a formal consumer complaint to a Consumer Disputes Redressal Commission, filed online through the e-Daakhil portal (edaakhil.nic.in). The right commission depends on the value of the consideration (what you paid / the amount in dispute), under the Consumer Protection Act, 2019:

• District Commission — value of goods/services up to ₹50 lakh, per the pecuniary-jurisdiction rules.
• State Commission — above ₹50 lakh up to ₹2 crore.
• National Commission — above ₹2 crore.

For the rupee amounts in a typical RMG payout dispute, that’s the District Commission, and e-Daakhil makes filing genuinely accessible: it’s free for district claims up to ₹5 lakh, then a modest fee (roughly ₹200–₹7,500) above that. The catch is time — a consumer-commission case runs in weeks to months, not days, so it’s the rung for a principled, owed balance the app has refused, not for a payout that’s merely slow. For systemic violations (mass refund denial, dark-pattern conduct across many users), the Central Consumer Protection Authority (CCPA) is the regulator-level escalation above the commissions.

When Rung 5 is the right door — and when it isn’t

Use the consumer route when the problem is service deficiency: a clean balance refused, no reachable support, an operator failing its service obligation to you. Don’t use it for a rail failure (that’s Rungs 3–4, faster and free) or for fraud (that’s Rung 6, and it overrides everything). The consumer angle reaches the operator’s service duty; the RBI angle reaches the payment rail. Run them together when both apply — the app refused you and a payout failed on the rail — and let whichever moves first carry the day.

Rung 5 in one line: for an app refusing a clean, owed balance (a service deficiency, not a rail failure), start the National Consumer Helpline 1915 mediation, and if that fails, file a formal complaint at the District Consumer Commission via e-Daakhil (free up to ₹5 lakh; District ≤₹50 lakh) — running it in parallel with the rail route, never instead of the 1930 sprint for fraud.

Rung 6 — Cybercrime 1930 / NCRP (the emergency override)

This rung is different from all the others, and the difference is the most important rule on the page: if any fraud is involved, you do not climb the ladder — you jump straight here, immediately. A fake “care number,” an OTP you read out, a “fee” you paid, a remote app you installed: the moment any of those happened, the slow operator-and-rail ladder is the wrong tool, because fraud loss is measured in minutes, not days.

The golden hour and how 1930 works

The golden hour is not a figure of speech. The instant your money lands in a fraudster’s first “mule” account, a countdown starts — the criminal is splitting and forwarding it onward, and a bank can only freeze what’s still sitting in front of it. Call 1930, the National Cyber Crime Helpline, run by the Indian Cyber Crime Coordination Centre (I4C) under the Ministry of Home Affairs — it’s free from any Indian mobile network, staffed 24×7 in Hindi, English and major regional languages, and wired into the Citizen Financial Cyber Fraud Reporting and Management System (CFCFRMS) that connects banks and payment intermediaries so the beneficiary bank can place a hold on the mule account while the money is still parked there, per I4C / NCRP. The system’s impact is real: by 31 December 2025, over ₹8,189 crore had been saved across more than 23.61 lakh complaints, and national recovery rates rose from 10–11% in 2024 to about 24% in 2025 — driven almost entirely by speed of reporting. Reports lodged within the first hours dramatically raise the odds.

Keep the call tight — every minute on hold is a minute the money moves. Have ready before you dial: the amount, the date and time, your bank/UPI used, and the transaction reference (UTR/RRN) if you have it. You’ll get an acknowledgement number — write it down.

File the NCRP complaint and lock everything down

After (or alongside) the call, lodge the full written complaint at cybercrime.gov.in from your registered mobile number, attaching the SMS and transaction screenshots, your bank statement showing the debit, and a one-page typed narrative in time order. You’ll receive an NCRP acknowledgement PDF with a complaint number — the document that ties your phone report, your bank dispute and any later police follow-up into one case file. In parallel: uninstall any remote app (AnyDesk, TeamViewer, QuickSupport) and cut Wi-Fi/data to kill the session; call your bank’s official fraud line (the number on your card or in your real banking app, never one you searched for) to block cards/UPI and flag the transaction; and report the unauthorised transaction in writing within 3 working days, because under RBI’s zero-liability circular (06 Jul 2017), reporting inside 3 working days caps your liability at zero, with provisional credit within 10 working days and resolution within 90 days.

The universal fake-number principle

Here is the general rule that protects you across every RMG app, kept brief because the sibling page covers it in depth: a “customer care number” you found on a search result, video, blog, ad or comment is not support — it is an unverified number a stranger published, and for these apps it is far more likely a scam than a help line. No legitimate support ever needs a secret from you (OTP/PIN), a payment from you (a “fee” to release your own money), or control of your device (a remote app). Any one of those three asks ends the call. The full threat model — the four scam scripts, the minute-by-minute anatomy of a fake-support call, the publisher disambiguation, and the complete golden-hour fraud response — is on the dedicated page: Teen Patti Master customer care. Treat that page as the deep dive; treat this rung as the routing rule that sends you there the instant fraud appears.

Rung 6 in one line: the moment any fraud is involved — fake number, shared OTP/PIN, paid “fee,” installed remote app — skip every other rung and call 1930 in the golden hour (banks can freeze a still-parked mule account; reporting within 3 working days caps liability at zero), file at cybercrime.gov.in, and remember the universal rule that real support never needs a secret, a payment, or control of your device.

Climbing the map in order: a Day-0-to-30+ timeline

The six rungs aren’t just a menu — they’re a sequence on a clock, and matching each action to its rule-clock is what makes the whole thing work. Here is the universal timeline, the spine you climb for any non-fraud RMG support problem. (For fraud, ignore all of this and run Rung 6 now.)

Day 0 — Freeze the evidence and open the ticket

The single highest-leverage thing you do is on Day 0, and it isn’t complaining — it’s documentation. Within the first hour: screenshot everything (the withdrawal request, the status screen, the amount, the timestamp, your wallet balance before and after — date-stamped); capture the UTR / transaction reference the moment one appears (no UTR means you can’t trace a “paid” payout later); and raise the in-app ticket (Rung 1) with the amount, timestamp and UTR, getting a ticket ID in writing. That ID timestamps your complaint for the 30-day Ombudsman clock. Do not start a second account, do not deposit more “to unlock” the payout, and never share an OTP or UPI PIN with anyone who “calls to help.”

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

Send the same complaint by the app’s verified official support email (from its genuine listing/site, not a search ad), referencing the ticket ID — email creates a paper trail an in-app chat can’t. If this is a Type C failed/debited UPI case, this is the T+1 window; let the auto-reversal run before you dispute. If the app publishes a 1–3 working-day SLA, you’re still inside it — be firm but patient.

Day 4–10 — Grievance officer + open the rail dispute

If the operator’s first line has gone quiet past its SLA, escalate to the grievance / nodal officer (Rung 2) in writing. In parallel, if the money genuinely left the rail (Type B or C), open the bank / NPCI UDIR dispute (Rung 3) with the UTR — call your bank, raise the in-app dispute, or file at the NPCI portal / 1800-120-1740, and claim the ₹100/day if you’re past T+1.

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

Escalate the bank complaint to a written formal complaint if the helpline did nothing, and get a complaint reference number. Send the app a final-notice email: restate the facts, the ticket ID, the UTR, the days elapsed, and state you’ll escalate to the RBI Ombudsman and a consumer forum if it isn’t resolved. A clear, dated final notice often unsticks a payout, because it signals you know the process.

Day 16–30+ — RBI Ombudsman and consumer forum

After 30 days without resolution from the regulated entity, file with the RBI Ombudsman at cms.rbi.org.in (Rung 4). In parallel, for a service refusal, run National Consumer Helpline 1915 and, if needed, e-Daakhil (Rung 5). And the instant any fraud appears at any point in this timeline, drop the ladder and go to 1930 (Rung 6).

The timeline in one line: Day 0 document + ticket; Day 1–3 email + wait the T+1 TAT; Day 4–10 grievance officer + open the NPCI UDIR dispute; Day 8–15 formal bank complaint + final-notice email; Day 16–30+ RBI Ombudsman + consumer 1915 — with 1930 overriding the whole sequence the moment fraud is involved.

Per-rung realistic turnaround table

Forget vague promises. Here is what is actually normal versus slow versus a “now escalate” signal, per rung, with the rule reference where one exists. Timings marked with a rule are RBI/NPCI-mandated; the rest are typical behaviour and should be read as planning estimates, not guarantees.

Read that table as a clock. The moment you cross from “slow” into “escalate now” for your row is the moment you climb to the next rung. Don’t escalate early (you’ll annoy support and they’ll tell you to wait), and don’t escalate late (you’ll blow past a TAT and lose the easy refund or the Ombudsman window).

The PROGA wind-down: escalating when the app has gone

A growing share of people searching for RMG support in 2026 face the hardest version of this problem — the cash product they used has been discontinued under PROGA, the app may be gone from its source, and a balance is still trapped inside. This situation has its own rules, and, critically, it’s the one scammers exploit most aggressively, because a person whose app “disappeared” is primed to believe a stranger who claims they can “recover” it.

What still works when the operator winds down

First, the reassuring mechanics. A genuine app’s balance is tied to your registered mobile number and account, not to the installed file — a reinstall from the official source doesn’t wipe it. And when the big legal operators wound down cash play, banks and payment intermediaries kept processing withdrawals so users could pull existing balances out, per the PROGA wind-down explainer. So a wind-down balance is often recoverable through the remaining in-app withdrawal flow, with normal rail timing and the usual 30% TDS on net winnings applied — not lost just because cash games stopped.

Which rungs the wind-down changes

The escalation map still applies, but the weight shifts. Rung 1–2 (operator rungs) get thinner — wound-down operators cut support staff, ticket replies slow, and if a specific informal-brand build genuinely vanished with no successor, there may be no operator left to email. That’s the hard case, and the honest answer is that recovery of a balance held inside a vanished, unlicensed operator is not guaranteed, because that entity may sit outside Indian regulatory reach. But the rail rungs (3–4) and the fraud rung (6) don’t depend on the operator at all — and that’s the whole point of the map:

• Any money lost on the payment rail — a withdrawal debited but never credited — is recoverable through your bank / NPCI / RBI chain regardless of the app’s status, because that’s a payment-system problem, not a gaming one.
• Fraud reporting still applies in full: if a “recovery agent” defrauded you, that’s a 1930 / cybercrime case independent of the app.

The one thing never to do

The move that turns a recoverable situation into a permanent loss: depositing more money “to recover” or “to unlock” your balance. Post-PROGA a new deposit into a money game is illegal, every “recovery fee” demand is a scam, and adding money to a dead app is throwing good money after lost. If support is unreachable because the operator wound down, your lever is the payment-side dispute, not a payment to the operator. The full discontinued-app recovery process is mapped end-to-end from the hub: 3 Patti withdrawal.

Wind-down reality in two numbers: a legitimate wound-down balance is usually still withdrawable via the in-app flow with 30% TDS on net winnings, but a balance inside a vanished unlicensed operator has no guaranteed recovery — so lean on the rail rungs (3–4), report any “recovery fee” demand as fraud (Rung 6), and never deposit a rupee to “unlock” anything.

State and identity friction that can block a payout (and how to escalate it)

Sometimes the reason a payout won’t move isn’t a queue, a rail failure or fraud — it’s who you are or where you are, and these need a slightly different escalation read because they look like a payment problem but aren’t.

The KYC / identity block

The single most common silent reason a first withdrawal stalls is a KYC name mismatch: your UPI handle reads “RAHUL K,” your PAN reads “Rahul Kumar,” and the app’s risk system can’t auto-match, so it parks the payout for manual review instead of paying it. This is a Type D problem — a verification issue, not a payment one — and escalating it to your bank or NPCI is pointless, because the rail never got a transaction to fail. The fix is to make your bank/UPI account name match your PAN exactly, resubmit clean KYC, use the same account for deposit and withdrawal, and chase it through Rung 1 (in-app ticket), demanding a written reason and timeline if the account is held for “investigation.” The document-level fixes for every KYC stall — name mismatch, PAN failure, blurry document, duplicate-account flags, frozen accounts — are the whole subject of the KYC cluster: KYC & account recovery.

The state-legality block

Where you are can also matter. Historically, some states banned staked play entirely — Telangana and Andhra Pradesh imposed blanket prohibitions on all staked games including skill games — so an operator might legally decline to pay out or onboard a player there. Post-PROGA, the cash product is centrally prohibited regardless of state, so the only payout that should still flow anywhere is a balance recovery. The escalation read: if an operator refuses even to return your existing balance citing your state, that’s a consumer-grievance and bank-dispute matter (Rungs 3–5), not a gaming dispute — push it as a payment/service deficiency, not as an argument about whether you were allowed to play. Don’t get lost in the skill-vs-chance philosophy; for getting your money, PROGA made it irrelevant, and your lever is the rail and consumer rungs that don’t care about the operator’s goodwill.

Identity/state friction in one line: a KYC name mismatch (Type D) is a verification block — fix it through Rung 1 and the KYC cluster, not the rail — while a state-legality refusal to return an existing balance is a payment/service deficiency you push through Rungs 3–5, never a skill-vs-chance debate.

Copy-paste escalation templates

Fill in the bracketed parts. Keep every message factual, dated and ID-stamped — emotion doesn’t move a payout, a UTR does. There are six here, one per rung, so you can lift the exact one your situation needs.

Template 1 — In-app support ticket (Rung 1, Day 0)

Subject: Withdrawal not received — ticket request

My withdrawal of ₹[AMOUNT] requested on [DATE, TIME] is showing
"[STATUS shown in app]" and has not reached my account.
Registered mobile: [NUMBER]
UPI ID / bank used: [HANDLE / A/C]
UTR / reference (if shown): [UTR]
KYC status: completed (PAN + Aadhaar verified)
Please confirm the payout status and the UTR, and resolve within your
stated payout window. Please share a complaint/ticket ID for this request.

Template 2 — Grievance / nodal officer escalation (Rung 2)

Subject: [Ticket ID] Withdrawal of ₹[AMOUNT] not credited — grievance escalation

To: Grievance / Nodal Officer, [operator] / [payment aggregator on receipt]

I raised in-app ticket [TICKET ID] on [DATE] for a withdrawal of
₹[AMOUNT] not credited to [UPI/bank]. It is now [N] days, past your
stated payout window of [X working days], with no resolution.

- Amount: ₹[AMOUNT]   Requested: [DATE, TIME]
- Status in app: [STATUS]   UTR / reference: [UTR]
- Registered number: [NUMBER]   KYC: completed (PAN matches bank name)

Per the RBI requirement for a grievance officer and escalation matrix,
please credit the payout or provide the UTR and a written reason within
48 hours. Failing that, I will escalate to my bank's UPI dispute, NPCI
UDIR, the RBI Ombudsman (RB-IOS 2021), and the National Consumer
Helpline (1915).

Template 3 — Bank / NPCI failed-transaction dispute (Rung 3)

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

A UPI transaction was debited but not credited to my account.
- UTR / reference (RRN): [UTR]
- Amount: ₹[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 ₹100/day compensation for delay beyond T+1. It has now been
[N] days. Please reverse the amount, credit the applicable compensation,
and share the complaint reference number. NPCI UDIR helpline: 1800-120-1740.

Template 4 — RBI Ombudsman (RB-IOS) grievance (Rung 4, Day 30+)

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

- Regulated entity complained of: [your bank / payment system participant]
- Original complaint to entity: [ref] on [DATE] — no resolution in 30 days
- Amount: ₹[AMOUNT]   Date/time: [DATE, TIME]   UTR/RRN: [UTR]
- My account / UPI ID: [A/C or HANDLE]
- Relief sought: credit of ₹[AMOUNT] plus ₹100/day TAT compensation
  from T+1, and resolution of the deficiency.

Filed under RB-IOS 2021 via cms.rbi.org.in. Supporting documents
(screenshots, bank statement, entity complaint reference) attached.

Template 5 — National Consumer Helpline (Rung 5, service deficiency)

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

Complaint: Service deficiency — gaming app failing to pay a verified,
KYC-complete withdrawal and providing no reachable support channel.

- Operator / app: [APP NAME]   Registered mobile: [NUMBER]
- Withdrawal amount owed: ₹[AMOUNT]
- Requested on: [DATE]; in-app ticket [TICKET ID] raised [DATE]
- App's status / response: [STATUS / no response after N days]
- KYC: completed; PAN matches bank account name
Relief sought: release of ₹[AMOUNT] to my registered account, and a
written reason for the delay. If unresolved, I will file before the
District Consumer Commission via e-Daakhil.

Template 6 — Cybercrime / fake-number report (Rung 6, fraud)

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

Complaint: Fraudulent "customer care number" / impersonation of
[APP NAME] support used to attempt or commit financial fraud.

- Fraudulent number / channel: [NUMBER or URL where I found it]
- Where it was published: [search result / video / blog / comment]
- What was requested: [OTP / UPI PIN / "refundable fee" of ₹[X] /
  install AnyDesk-TeamViewer / scan QR]
- Amount lost (if any): ₹[AMOUNT] on [DATE, TIME]
- My bank / UPI used: [A/C or HANDLE]; transaction ref/UTR: [UTR]
Relief sought: registration of the cyber-fraud complaint, freeze of the
beneficiary/mule account, and recovery of ₹[AMOUNT].

Use Template 6 the instant any fraud is involved (and call 1930 first), Template 3 within the T+1 window for a debited-but-not-credited payout, and Templates 1/2/4/5 to climb the non-fraud ladder in order.

The full contact-and-escalation reference block

The whole map in one place. Notice that not one legitimate first door is a “customer care number” you found on a search result — because, for these apps, that door usually doesn’t exist.

Order of doors, in one line: in-app ticket → verified email → grievance officer → bank/NPCI UDIR → RBI Ombudsman after 30 days, with consumer 1915 in parallel for app-side deficiency and cybercrime 1930 the instant any fraud is involved.

How this hub routes to its spokes

This page is deliberately the map, not the territory. Each rung touches a problem that has its own deep page, and routing you to the right one is half the job. Here’s the routing logic in plain terms, so you land on the page that actually fixes your case rather than re-reading the overview.

• If your money is stuck or “not received” and you want the full payout-recovery detail — the per-app reality tables, the UTR-finding menu paths for every UPI app, the screen-by-screen UDIR dispute, the tax math behind a “smaller than expected” payout — start at the payout hub: 3 Patti withdrawal.
• If your specific worry is a “customer care number” and whether it’s safe to call — the fake-number threat model, the four scam scripts, the minute-by-minute anatomy of a fraud call, the publisher disambiguation, and the golden-hour response — go to the depth page: Teen Patti Master customer care.
• If the block is verification — KYC rejected, name mismatch, account frozen or flagged — the document-level fixes live in the KYC cluster: KYC & account recovery.
• If the payout is sitting at “pending / processing” and you need the per-status waiting limits — the state-machine of a stuck payout, which gate it’s at and the next step for each — is the stuck-withdrawal page: withdrawal stuck.

The unifying idea across all four: diagnose the problem type, climb the matching rung, and route to the matching spoke. Get those three right and the overwhelming complaint cluster collapses into a single, walkable path.

Frequently asked questions

1. What is the customer care number for RMG apps like Teen Patti or rummy?

For most Indian RMG apps there is no public phone customer care number — support runs in-app and by official email, not a phone line. Many of these apps are informal brands distributed outside the Play Store, with no single verified helpline. Treat any “customer care number” you find on a search result, video or comment as an unverified number a stranger published, and far more likely a scam than support, since no legitimate support ever asks for your OTP, PIN, a fee, or remote access. The full warning is on Teen Patti Master customer care.

2. How do I actually contact RMG support if there’s no phone number?

In this order: (1) in-app ticket (Settings → Help/Support — get a ticket ID), (2) verified official email taken from the genuine app screen or site, (3) the operator’s grievance / nodal officer. These are the only three legitimate operator channels. If the money left the rail, the contact then shifts entirely to your bank and NPCI UDIR, not the app. The realistic first-reply window for an in-app ticket is 24–72 hours.

3. What is a grievance officer and how do I escalate to one?

A grievance / nodal officer is the named escalation contact a regulated payment intermediary must publish by RBI rule, with a duty to send a final response within roughly 20–30 business days, per RBI’s payment-aggregator directions. Escalate to one in writing, citing your unresolved ticket ID, the days elapsed, and the exact relief you want. The letter also serves as proof you exhausted the operator’s internal process, which the consumer forum and Ombudsman both require.

4. When can I complain to the RBI Ombudsman about a gaming payout?

Only after the regulated entity (your bank or the payment-system participant — not the gaming app) has had 30 days and failed to resolve, rejected, or unsatisfactorily answered your complaint. The RB-IOS 2021 scheme is free, covers Payment System Participants, and you file at cms.rbi.org.in (or email cpc@rbi.org.in, or write to CRPC Chandigarh). File before the 30-day gate and it’s rejected.

5. The app says “paid” but I never got the money — what do I do?

Get the UTR (12-digit reference) from the app, then ask your bank to trace that UTR. If the bank has no record of a credit against it, you have proof the money didn’t reach you, and you raise a failed-transaction dispute through your bank or NPCI UDIR (line 1800-120-1740), which resolves in a stated 3–5 working days. This is a rail problem, not a gaming one — the UTR is everything.

6. My UPI withdrawal failed but money was debited — am I getting it back?

Almost certainly yes, and largely automatically. Under RBI’s TAT circular, a debited-but-not-credited UPI transaction must be auto-reversed by T+1, and if it isn’t, the bank owes you ₹100 per day beyond T+1. NPCI’s UDIR auto-converts an unresolved complaint into a chargeback (T+1 for P2P, T+3 for P2M). Capture the UTR, wait through T+1, and dispute if it’s still missing — this is the most consumer-protected stuck state there is.

7. The app won’t pay a clean balance it clearly owes me — which rung is that?

That’s a service deficiency, so run Rung 5: start the National Consumer Helpline 1915 (consumerhelpline.gov.in) mediation, and if it fails, file a formal complaint at the District Consumer Commission via e-Daakhil (free for claims up to ₹5 lakh; District jurisdiction covers up to ₹50 lakh). Run it in parallel with the bank/RBI route if a payout also failed on the rail — different doors, same goal.

8. I shared an OTP / paid a “fee” / installed AnyDesk for a “support agent” — now what?

Stop climbing the ladder and go straight to Rung 6: call 1930 immediately (the golden hour is when a bank can still freeze the mule account), uninstall the remote app and cut data, block your cards/UPI via your bank’s official fraud line, and report the unauthorised transaction in writing within 3 working days to cap your liability at zero under RBI’s 2017 circular. Then file at cybercrime.gov.in. India saved over ₹8,189 crore across 23.61 lakh complaints by 31 Dec 2025 — speed is everything.

9. How long does each escalation rung realistically take?

In-app ticket reply: 24–72 hours. NPCI UDIR resolution: 3–5 working days. UPI auto-reversal: T+1. Grievance officer final response: 20–30 business days. RBI Ombudsman eligibility: after 30 days of no entity resolution. Fraud zero-liability: report within 3 working days for provisional credit within 10 working days. Consumer commission cases run weeks to months. Match your action to the slowest rule-clock on your row before escalating.

10. Does the RBI Ombudsman work against an offshore or shut-down gaming app?

Only weakly. The Ombudsman is powerful against the rail — your bank and the payment-system participant are RBI-regulated and must answer it — but it’s weak against a shady offshore or unlicensed operator that sits outside Indian regulatory reach. So for money lost on the rail (a debited, never-credited payout) it’s a strong lever; for a balance trapped inside a vanished, unlicensed app, recovery is not guaranteed. That’s the single best reason never to deposit where payouts aren’t clean.

11. My app shut down under PROGA — can I still get support and my balance?

Often yes for the balance, less so for the support. A balance is tied to your registered account, not the app file, and banks were instructed to keep processing withdrawals so users could recover existing balances, per the PROGA wind-down explainer — usually via the remaining in-app flow with 30% TDS on net winnings. But support is thinner, and a vanished unlicensed operator may have no one to email — in which case lean on the bank/NPCI/RBI rungs. Never deposit to “unlock” a balance — that’s illegal and a scam.

12. Should I file an FIR or go to the police for a stuck gaming payout?

For a plain delayed payout (no fraud), no — that’s the operator/rail/Ombudsman ladder, not a police matter. For fraud (a fake number, a shared OTP, a paid “fee”), yes — your 1930 call and cybercrime.gov.in complaint can be converted into an FIR at a cyber police station, and an FIR becomes effectively mandatory for losses over ₹10 lakh or where a bank requires it for recovery. The NCRP acknowledgement PDF is the document that ties your case together.

13. Can I claim compensation for the delay, not just the missing money?

For a rail failure, yes — the RBI TAT circular gives you ₹100 per day of delay beyond T+1 on a debited-but-not-credited transaction, credited automatically. For a service deficiency taken to a consumer commission, compensation for deficiency and mental agony is possible but discretionary and slow. The reliable, rule-backed money is the ₹100/day TAT compensation on the rail — claim it explicitly when you raise the bank dispute.

14. Which rung do I use if I just don’t know what kind of problem I have?

Start by diagnosing the type: pending in the app (Type A → Rung 1–2), paid-but-not-received (Type B → Rung 3), failed-but-debited (Type C → Rung 3, T+1), KYC/blocked (Type D → fix KYC, then Rung 1), or fraud (Type E → Rung 6 now). When in genuine doubt and no fraud is involved, raise the in-app ticket and capture the UTR — Rung 1 costs nothing, timestamps your complaint, and the operator’s reply (“we paid it, see your bank” vs “it’s under review”) tells you which rung is next.

15. Is it ever safe to call a number I found for RMG support?

Only if it appears on the app’s own in-product support screen or a website you reached by typing the address yourself — and even then, prefer the in-app ticket, which is authenticated and can’t be impersonated. A number from a YouTube title, Google ad, blog, Telegram channel or comment is presumed hostile. The meta-rule that never fails: real support needs your registered number and a ticket, never a secret (OTP/PIN), a payment (a “fee”), or control of your device. Any of those three asks ends the call — full depth on Teen Patti Master customer care.

The bottom line

Strip away the panic and an RMG support problem is a routing exercise. There is no magic phone number; there is a six-rung map, and your only real job is to drop your problem onto the right rung and climb in order. A pending payout is an operator problem — work the in-app ticket and grievance officer. A payout that left the rail and vanished is a payment-system problem with real legal force — work your bank, NPCI UDIR, and the RBI Ombudsman after 30 days, with T+1 reversals and ₹100/day compensation on your side. A flat refusal of a clean balance is a consumer problem — run National Consumer Helpline 1915 and, if needed, e-Daakhil. And the instant any fraud touches the case — a fake “care number,” a shared OTP, a paid “fee” — you abandon the ladder entirely and sprint to 1930 in the golden hour. Diagnose first, escalate in order, route to the right spoke, and never deposit a rupee to “unlock” your own money.