RBI Ombudsman for Gaming Payments: File and Win

The 40-second answer

The RBI Integrated Ombudsman (RB-IOS 2021) hears free complaints against regulated entities — your bank, wallet, or payment aggregator — not gaming operators. So you win by framing a stuck payout as a payment-service failure. You qualify 30 days after first complaining to that entity (start here), file within one year at cms.rbi.org.in, and can win up to ₹20 lakh plus ₹1 lakh.

Editor’s verdict, up front. Most people who reach for “the RBI Ombudsman” for a gaming problem aim it at the wrong target and get bounced. The Ombudsman cannot order a Teen Patti app, a rummy operator, or an offshore casino to pay you — those are not RBI-regulated. What it can do is hold your bank, wallet provider, or the payment aggregator that botched a UPI/IMPS/NEFT credit to account for that failure. That reframing — from “the app cheated me” to “my regulated payment provider failed to deliver a transfer” — is the entire game. This page shows you exactly which disputes qualify, the 30-day gate you must clear first, the cms.rbi.org.in flow step by step, the evidence that actually wins, what the Ombudsman can and cannot order for gaming money, the appeal path when it rejects you, and the realistic timelines. Your first move, before any of this, is the prior complaint — start at customer-care escalation.

2026 reality you must read first. The legal ground shifted hard in 2025. 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; its operating Rules came into force on 1 May 2026. This does not kill your Ombudsman route. A payment failure on a UPI or bank transfer is a banking grievance no matter what the money was for, and banks were instructed to keep processing withdrawals so users could recover existing balances. So in mid-2026 the live question is rarely “is my game legal” — it’s “my bank/wallet failed to credit a transfer and won’t fix it,” which is squarely an RB-IOS matter. The one thing PROGA changes: never deposit again “to unlock” a payout. A new deposit into a money game is now illegal, and the Ombudsman will not help you recover a deliberate, illegal deposit.

Why the Ombudsman is for your bank, not the gaming app

This single distinction decides whether your complaint is heard or rejected at the door, so it gets the most space on this page.

The RB-IOS 2021 is a scheme run by the Reserve Bank of India to redress grievances against the entities RBI itself regulates. The official scheme names them: commercial banks, Non-Banking Financial Companies (NBFCs), Payment System Participants, and Credit Information Companies, plus larger urban and co-operative banks. That list is exhaustive in spirit — if an entity is not on it, the Ombudsman has no jurisdiction over that entity.

A gaming operator — RummyCircle, a Teen Patti skin, an offshore betting site — is not on that list. RBI does not license or supervise gaming companies; that’s MeitY’s domain under PROGA, and the states’ under their gambling laws. So a complaint that says “the app refused to pay my winnings” names a party the Ombudsman cannot touch. It will be closed as outside jurisdiction — and worse, you’ll have burned a 30-day clock pointing at the wrong door.

Now flip it. The money in a gaming payout does not travel through the gaming company’s own pipes. It rides one of three regulated channels:

• Your bank (the one debited, and the one that should credit you).
• A wallet / prepaid instrument provider (a PPI licensee — a Payment System Participant).
• A payment aggregator (PA) like Razorpay or Cashfree, both of which hold final RBI authorisation as payment aggregators (granted in December 2022). A PA that collects or disburses for a merchant is a regulated entity under the RBI PA-PG Guidelines of 17 March 2020, and it must appoint a Nodal Officer for customer grievances.

Every one of those is a regulated entity the Ombudsman can order to act. So the winning frame is: “A regulated payment provider failed to deliver a transfer I was entitled to receive.” Not “the casino stole my money” — “my bank debited a UPI transfer and never credited it,” or “the payment aggregator that disbursed my withdrawal sent it to a dead handle and won’t trace it.” Same rupees, completely different — and admissible — complaint.

A clean test for “is my complaint in scope?”

Ask one question: did a regulated payment entity fail at a payment task it owed me? If yes, you’re in scope. Three worked examples:

• In scope. You withdrew ₹8,000; the app marked it “paid” with a UTR; your bank has no credit against that UTR and won’t trace it after 30 days. The failure is the bank’s (a deficiency in a payment service). ✅
• In scope. A wallet (PPI) debited your withdrawal request, the transfer “failed,” and the wallet provider hasn’t reversed it after 30 days despite the T+1 auto-reversal rule. The failure is the PPI’s. ✅
• Out of scope. The app says your ₹5,000 is a non-withdrawable bonus and refuses to release it. No regulated payment entity has failed — the operator is enforcing its terms. The Ombudsman can’t help; that’s a consumer-forum / operator matter. ❌

Hold that test in your head through everything below. The 1-line version: the Ombudsman fixes broken transfers, not broken games.

The anatomy of a gaming payout — and where the regulated entity sits

To frame a complaint correctly you have to know which regulated party touched your money and when. A typical winnings payout from an Indian gaming app passes through four hands before it lands in your account, and only the last three are entities the Ombudsman can act against. Trace yours.

1. The operator’s own ledger. Your winnings sit as a balance number inside the app. This is not a payment yet — it’s a database entry. No regulated entity is involved. If your money is stuck here (pending, under review, locked bonus), the Ombudsman has nothing to act on, because nothing has been handed to a payment rail.
2. The payment aggregator / payout processor. When you withdraw, the operator instructs a payment aggregator — frequently Razorpay or Cashfree, both RBI-authorised PAs — or a bank’s payout API to disburse funds. The moment the operator hands the instruction over, a regulated entity is in the chain. Under the PA-PG Guidelines of 17 March 2020, that PA owes you grievance redressal through a published Nodal Officer.
3. The remitting bank. The PA’s escrow bank (PA settlements run through a single scheduled commercial bank escrow by RBI rule) pushes the actual UPI/IMPS/NEFT credit. That bank is a regulated entity.
4. Your receiving bank. Your own bank must credit your account. It’s a regulated entity too, and it’s the one most directly answerable to you for a missing credit, because you hold the account.

The practical upshot: a payout that has reached hands 2, 3, or 4 and failed there is an in-scope Ombudsman matter, and you name whichever regulated entity failed — usually your receiving bank (simplest, since you bank with them) or the PA (if the disbursement itself was botched). A payout still sitting in hand 1 is not yet a payment at all, so it’s an operator problem first; the 3 Patti withdrawal hub explains how to push it out of hand 1 before you ever reach for the Ombudsman.

Why “deficiency in service” is the magic phrase

The scheme doesn’t redress “I’m owed money” in the abstract. It redresses a deficiency in service by a regulated entity. So your complaint must establish that one of hands 2–4 fell short of a service it owed you. Concrete deficiencies that qualify:

• A UPI credit was debited but not credited and not auto-reversed by T+1, breaching the RBI TAT circular. That’s a textbook service failure by the remitting/receiving bank.
• The bank marked a transaction successful when no credit reached you, and then refused or failed to trace the UTR within 30 days. Failing to investigate a disputed transaction is itself a deficiency.
• A payment aggregator disbursed to a stale or wrong handle despite holding correct details, or its Nodal Officer ignored a documented grievance. Both are service failures by a regulated PA.
• The entity failed to pay the ₹100/day compensation it automatically owed under the TAT rule. Non-payment of mandated compensation is a deficiency in its own right.

Notice none of those mentions the game. Each is a sentence about a bank or PA failing a payment task. Write your complaint in that grammar and you stay in the in-scope, awardable column; drift into “the casino kept my winnings” and you hand the Ombudsman a reason to close you out.

The anatomy lesson in one line: money becomes an Ombudsman matter only once a regulated payment entity touches it and fails — hands 2, 3 or 4. While it’s still a number inside the operator’s ledger (hand 1), no amount of RBI escalation will move it, because no regulated entity has done anything yet. Find which hand dropped your money, then name that hand.

Exact eligibility: the four gates you must clear

RB-IOS has hard admissibility gates. Miss any one and your complaint is rejected without a hearing, often after you’ve already waited weeks. Clear all four and it’s heard. Here they are, with the precise rule behind each.

Gate 1 — A regulated entity is the respondent

Covered in depth above: name a bank, NBFC, PPI/wallet, payment aggregator, or other Payment System Participant, never the gaming operator. If your only grievance is with the operator itself, this gate fails and nothing else matters. One number to remember: there are 22 Ombudsman offices historically, but under RB-IOS you no longer pick one by geography — it’s a single centralised scheme, and the system routes your complaint.

Gate 2 — The 30-day prior-complaint gate

You must first complain to the regulated entity and give it 30 days. Per the scheme, a complaint is not maintainable if it is filed with the Ombudsman before 30 days have elapsed from your complaint to the entity — unless the entity has already sent you a reply you’re dissatisfied with, in which case you can file immediately. So your sequence is fixed:

1. Lodge a written complaint with the bank / wallet / PA and get a complaint reference number.
2. Wait 30 days (or until you receive a rejection/unsatisfactory reply, whichever is first).
3. Then file with the Ombudsman.

This is why the very first thing you do — long before any Ombudsman talk — is open that prior complaint and capture its reference. The whole customer-care escalation ladder exists to get you a clean, dated, reference-numbered prior complaint that starts this 30-day clock correctly.

Gate 3 — The one-year time limit

You cannot sit on it forever. A complaint is not admissible if it’s filed:

• more than one year after you received the entity’s reply, or
• where no reply came, more than one year and 30 days after the date of your representation to the entity.

So the outer window is roughly one year (plus the 30-day grace where no reply came) from the entity’s response. Practically: don’t let a stuck payout drift past a year of inaction. The clock that matters is the date of the entity’s reply (or your representation if it never replied), not the date the transaction failed.

Gate 4 — Not on the “non-maintainable” exclusion list (Clause 10)

Even a correctly-targeted, timely complaint is thrown out if it falls under the scheme’s exclusions. The Ombudsman will not entertain a complaint that:

• has not first been raised with the regulated entity (Gate 2 restated);
• is already pending before, or has been decided by, a court, tribunal, arbitrator, or any other forum;
• relates to a commercial judgement / business decision of the entity (e.g. a lending decision) — not your case, but worth knowing;
• is about a service not within the Ombudsman’s scope, or against an unregulated party;
• is frivolous, vexatious, or without sufficient cause, or where no loss was caused;
• is filed by an advocate on the complainant’s behalf (unless the advocate is the aggrieved party).

For a gaming-payment dispute, the two exclusions that actually bite are (a) targeting an unregulated operator (Gate 1) and (b) the matter already being in another forum. If you’ve also filed the same dispute in a consumer court, disclose it — overlapping forums can get the Ombudsman complaint closed.

The eligibility checklist in one breath: regulated entity named + 30 days given to it + within one year of its reply + not already in court / not excluded. Tick all four before you touch cms.rbi.org.in. Missing the 30-day gate is the single most common reason a gaming-payment complaint bounces — there were tens of thousands of complaints closed annually as non-maintainable across the scheme, and “premature filing” is a leading cause.

What the Ombudsman can — and cannot — order for gaming money

Set your expectations precisely, because the limits are sharp and asymmetric.

What it CAN do

• Order the regulated entity to reverse / credit a failed payment. If your bank or PPI failed a transfer you were owed and the Ombudsman finds a deficiency in service, it can direct the entity to make good — i.e. actually pay you the stuck amount.
• Award compensation up to ₹20 lakh. The Ombudsman can pass an Award directing the entity to pay you the actual loss you suffered as a direct consequence of the deficiency, capped at ₹20 lakh. For most gaming-payout disputes the “actual loss” is simply the un-credited amount, which sits far below that ceiling.
• Add up to ₹1 lakh for time, expense, harassment and mental anguish. Separately and on top of the ₹20 lakh, the Ombudsman may award up to ₹1 lakh for the loss of your time, the expenses you incurred, and the harassment / mental anguish suffered. This is the rung that punishes an entity for stonewalling you.
• Direct the ₹100/day TAT compensation be paid. Where your case is a UPI debited-but-not-credited failure under the RBI failed-transaction circular, the Ombudsman can direct the entity to pay the ₹100-per-day delay compensation it already owed automatically. The deep mechanics of that auto-reversal are on the UPI failed, money debited fix page.

What it CANNOT do

• It cannot order a gaming operator to pay you. Zero jurisdiction over the operator. If the money never left the operator’s wallet onto a payment rail (it’s still “pending” inside the app at Gate 3 of a normal payout), there is no regulated-entity failure yet — the Ombudsman has nothing to act on.
• It cannot award “winnings” the operator is withholding under its terms. A locked bonus, an unmet wagering requirement, a balance the operator says is non-withdrawable — none of that is a payment-service deficiency, so it’s outside scope.
• It cannot rule on the legality of your gambling. It won’t decide whether your game was legal under PROGA or your state law. It only looks at whether a payment was mishandled by a regulated party.
• It cannot recover an illegal deposit. Money you deposited into a now-prohibited money game post-PROGA is, by your own action, an illegal transaction — the Ombudsman is not a route to claw that back.
• It is capped at the actual loss + ₹20 lakh + ₹1 lakh. No punitive damages beyond the harassment head, no interest beyond what restores you.

The capability summary in one number pair: it can move up to ₹20 lakh + ₹1 lakh of a regulated entity’s money to you for a payment failure, and ₹0 of a gaming operator’s money — because it has no power over the operator at all. Aim every word of your complaint at the regulated entity’s failure, and you stay inside the powerful column.

The cms.rbi.org.in complaint — step by step

The Ombudsman runs on a single online portal, the Complaint Management System (CMS) at cms.rbi.org.in, open 24×7. Filing is free — there is no fee, and you don’t need a lawyer (in fact a lawyer can’t file for you under the exclusion above). Here is the exact flow.

Step 1 — Confirm you’ve cleared the 30-day gate

Before you open the portal, have in hand: your prior complaint reference with the bank/wallet/PA, the date you raised it, and proof that 30 days passed (or that you got an unsatisfactory reply). Without this, CMS will let you file but the Ombudsman will reject it as premature. This is the most common own-goal — don’t make it.

Step 2 — Register / log in on CMS

Go to cms.rbi.org.in. You authenticate with your mobile number and email via OTP. There’s no lengthy account creation; the OTP is the login. Keep the same mobile and email you used with the bank, so the records line up.

Step 3 — “File a Complaint” → against a regulated entity

Choose File a Complaint, then select that it’s against a regulated entity (a bank / NBFC / PPI / Payment System Participant). You’ll search for and pick the specific entity — your bank, your wallet provider, or the payment aggregator. Picking the right respondent here is Gate 1 in action: select the payment provider, never the gaming app (the app won’t even be selectable, which is the system telling you it’s out of scope).

Step 4 — Enter the transaction and grievance details

Fill in the structured fields:

• Category of complaint — choose the closest fit, typically under “Mobile/Electronic banking” or “UPI / digital payment” deficiency.
• Transaction details — the UTR / RRN (12-digit reference), amount, date and time, and the account / UPI handle involved. The UTR is non-negotiable; the UPI failed page shows exactly where each app hides it.
• Prior complaint details — the reference number and date of your complaint to the entity, and what reply (if any) you got. This is what proves Gate 2.
• Nature of grievance — a short factual statement: a UPI/bank transfer I was entitled to receive was debited but not credited (or was failed and not reversed), and the entity has not resolved it within 30 days.

Step 5 — Upload your evidence

Attach the documents in the evidence section (the next major section lists exactly what wins). At minimum: the bank statement / transaction screenshot showing the UTR and the missing credit, your prior complaint and the entity’s reply, and the app’s payout record showing it marked the payment “paid.”

Step 6 — Submit and capture the complaint reference

On submission you get an immediate online acknowledgement with a unique complaint reference number. Save that number — it’s how you track everything. RBI screens new complaints (broadly within ~48 hours) for completeness and eligibility before assigning them. You can later track status at the same portal under “Track your Complaint” using your mobile OTP and that reference number.

If you can’t use the portal

You don’t have to file online. You can also:

• Email the complaint to [email protected], or post it to the Centralised Receipt and Processing Centre (CRPC), Reserve Bank of India, Sector 17, Chandigarh 160017 in the prescribed form.
• Call the toll-free 14448 contact centre (multilingual, working-hours) — staff help you file and clarify, but they cannot lodge the complaint for you over the phone; the actual filing is still via CMS/email/post.

One trap on the portal: CMS will happily accept a premature or mis-targeted complaint and only reject it later. The system does not enforce the 30-day gate or the regulated-entity rule for you. You are the eligibility check. Run the four-gate list above one more time before you hit submit, and you’ll clear the ~48-hour screening cleanly.

What evidence actually wins an Ombudsman gaming-payment case

An Ombudsman complaint is decided on documents, not feelings. The complaints that win share the same evidence spine: they prove a regulated entity failed a specific, identifiable transfer, and they prove you gave it 30 days first. Here’s the exact pack, in order of weight.

Tier 1 — The transaction proof (this is the case)

• The UTR / RRN. The single most important artefact. It’s the 12-digit reference that ties your debit to the (missing) credit. No UTR, no traceable failure — the Ombudsman cannot order a refund of a transfer it can’t identify. Capture it on Day 0; the UPI failed page shows where PhonePe, GPay, Paytm and BHIM each hide it.
• Bank statement (PDF, from the bank — not a screenshot) covering the dates, showing either the debit with no matching credit, or the failed/un-reversed entry. An official statement carries far more weight than an app screenshot.
• The app’s payout record showing the withdrawal marked “paid / success” with that UTR. This is what converts “the app didn’t pay me” into “the payment provider handled this transfer and it failed to reach me” — the in-scope frame.

Tier 2 — The prior-complaint proof (this clears Gate 2)

• Your written complaint to the bank/wallet/PA with its date and reference number.
• The entity’s reply (or proof that 30 days passed with no reply). A screenshot of an unresolved ticket plus the 30-day lapse is enough where no formal reply came.
• The grievance / nodal-officer escalation, if you went that far — a payment aggregator must publish a Nodal Officer, and an unanswered escalation to that officer is strong evidence of deficiency.

Tier 3 — Context and quantum

• KYC confirmation (PAN + bank name match), to pre-empt the entity’s “name mismatch” defence and show the failure wasn’t your error.
• A timeline document — a simple dated list: transaction → app “paid” → bank shows no credit → complaint raised (ref, date) → 30 days lapsed → filing. The Ombudsman reads cleanly-laid-out timelines fastest.
• Evidence of harassment / time lost — the chain of unanswered emails, the hours on hold — if you want the ₹1 lakh time/harassment head, you have to show the harassment, not just claim it.

What does NOT help (and can hurt)

• Emotional narrative without a UTR. “I’m a poor student and they robbed me” moves no Award; a traced, un-credited UTR does.
• Documents about the game (your win history, the operator’s terms). These pull the case toward the out-of-scope “operator dispute” frame. Keep the file focused on the payment.
• A parallel court / consumer-forum filing you don’t disclose. If the same matter is pending elsewhere, the complaint can be closed under the exclusions — disclose, or pick one forum.

The evidence rule in one line: a winning Ombudsman gaming-payment file is 80% one document — the UTR-bearing bank statement showing a debit with no credit — plus a dated prior complaint that proves you waited 30 days. Everything else is supporting cast. If you have those two, you have a real case; if you don’t, fix that before filing.

Perfecting the prior complaint — the step that decides everything

The Ombudsman complaint is downstream of the prior complaint to the regulated entity, and the quality of that prior complaint quietly determines whether your Ombudsman case is strong or hollow. Spend real care here; it’s the 30 days you’ll spend anyway, so make them count.

A prior complaint that sets up a winning Ombudsman case does four things:

• Names the deficiency in writing. Don’t tell the bank “I didn’t get my money.” Tell it: “UPI transaction UTR [X], ₹[amount], dated [date], was debited and not credited to my account; it was not auto-reversed by T+1 as required under RBI circular DPSS.CO.PD No.629. Please reverse it and pay the ₹100/day compensation.” That sentence, on the entity’s record, is your future evidence of a clearly-stated, ignored service failure.
• Gets a reference number and a date. The reference + date is what proves Gate 2 to the Ombudsman. A chat with no ticket number is worthless here. If the app or bank won’t give a reference, escalate to the grievance / nodal officer in writing (email), which always generates a trail.
• Asks for the specific relief you’ll later seek from the Ombudsman. Ask the entity for the refund and the ₹100/day and a written reason for delay. When the entity ignores or refuses, you carry that exact unmet demand straight into the CMS “relief sought” field.
• Creates a 30-day countdown you can prove. Date everything. The Ombudsman’s first eligibility check is “did 30 days pass since a complaint to the entity?” — a dated email answers it instantly.

The full mechanics of building this prior complaint — which channel, which officer, how to phrase it, how to escalate when ignored — are the entire subject of the customer-care escalation page. Treat that page as step one and this page as step two; they’re a single pipeline.

A field-by-field annotation of the CMS form

When you reach cms.rbi.org.in, the structured fields trip people up. Here’s what each one really wants:

• “Regulated entity” / respondent. Your receiving bank is usually the cleanest pick — you hold the account, so its duty to credit you is direct and undeniable. Pick the payment aggregator instead only if the disbursement itself was the failure and you can name the PA. Never the operator (it won’t be listed).
• “Category of complaint.” Choose the digital/mobile-banking or UPI category — the deficiency lives in the payment channel, not in “gaming.” Mis-categorising as a generic grievance slows routing.
• “Transaction details.” UTR, amount, date/time, account/handle. Treat the UTR as mandatory; a blank UTR is the field most likely to get your complaint screened out as untraceable.
• “Have you complained to the entity?” + reference/date. Answer yes, give the reference and date, and confirm 30 days elapsed (or that you got an unsatisfactory reply). This is the Gate-2 self-certification — get it right or the ~48-hour screening kicks it back.
• “Nature of complaint” free text. Paste the copy-paste complaint framed as a regulated-entity payment failure. Keep it factual and UTR-anchored.
• “Relief sought.” State three lines: credit the amount, pay the ₹100/day where applicable, compensate for time/harassment. Concrete relief is easier for an Ombudsman to grant than a vague “please help.”
• Declarations. You’ll confirm the matter isn’t pending in another forum and that you’re filing yourself (not via advocate). Both are Gate-4 exclusions — tick them honestly.

The prior-complaint truth: a sloppy first complaint to the bank produces a weak Ombudsman case no matter how good your CMS filing looks, because the Ombudsman judges whether the entity failed to act on a clearly-stated grievance. Spend the 30-day wait turning a vague ticket into a dated, reference-numbered, deficiency-named paper trail — that’s the work that actually wins.

The realistic timeline, end to end

People expect the Ombudsman to be fast. It isn’t instant, but it’s predictable. Here’s the honest clock from problem to outcome, with the rule-backed checkpoints marked.

Read it as a sequence of gates, not a guarantee of speed. The 30-day entity window is mandatory and unskippable — it’s the price of admission. After filing, a large share of complaints settle by facilitation within weeks once the regulated entity sees a documented, in-scope file; the matters that go all the way to a contested Award take longer. The end-to-end realistic expectation for a clean, well-evidenced gaming-payment complaint is roughly one to three months from filing — faster if the entity settles, slower if it fights to an Award and appeal.

The timeline takeaway: you cannot compress the 30-day prior window, so start the prior complaint the instant a payout fails — that 30 days runs whether or not you’re paying attention. Everything after filing is mostly out of your hands, but a tight evidence pack is what pushes a case to settle in weeks rather than grind to a contested Award in months.

The appeal path when the Ombudsman rejects you

An Ombudsman decision is not the end of the road — but the appeal rules are specific, and one carve-out catches a lot of gaming-payment complainants. Know it before you file, because it shapes how you frame the complaint.

If you get an Award you’re unhappy with (or the entity does)

Either side can appeal. The appeal goes to the Appellate Authority, which under RB-IOS 2021 is the Executive Director-in-Charge of the Consumer Education and Protection Department (CEPD) at RBI, Mumbai — note this is not the old “Deputy Governor” of the pre-2021 scheme; the authority changed. The appeal must be filed within 30 days of the date you received the Award or the decision. The Appellate Authority can dismiss the appeal, allow it, set aside the Award, remand the matter back, or modify the Award.

The carve-out that bites gaming-payment cases — “no deficiency in service”

Here’s the trap. If the Ombudsman closes your complaint on the ground that there was “no deficiency in service” (a specific sub-clause of the closure provisions), that closure is not appealable to the Appellate Authority. So if your complaint is weak on the payment-failure framing — if it reads like an operator dispute and the Ombudsman concludes the bank did nothing wrong — you get closed, and you can’t appeal that particular closure.

The lesson runs backwards into your filing: make the deficiency-in-service of the regulated entity unmissable. Don’t let the file look like a complaint about a game; make it a complaint about a bank that debited and failed to credit, then ignored you for 30 days. That framing both wins on the merits and keeps the appeal door open if it doesn’t.

What’s left if the Ombudsman door closes

If you’re closed on “no deficiency” with no appeal, or you exhaust the appeal, the Ombudsman route is done — but other doors remain:

• Consumer forum / National Consumer Helpline 1915 for a service-deficiency claim against the entity (or, in scope, the operator’s service obligation) — see how to complain about RMG in India.
• Cybercrime 1930 / cybercrime.gov.in the instant any fraud, phishing, or fake “customer care number” is involved.
• The RBI Sachet portal to report a suspicious or unauthorised payment entity.

The appeal rule in one line: you have 30 days to appeal an Award to RBI’s CEPD Executive Director, but a closure for “no deficiency in service” is final and un-appealable — which is exactly why you must build the file around the regulated entity’s payment failure, not the game, from the very first sentence.

How this slots into the Day-0-to-30 escalation ladder

The Ombudsman is the top rung of a fixed ladder, not a first move. Climb it in order — jumping to RBI on Day 1 just gets you bounced back to the entity, and skipping the prior complaint forfeits the whole route. Here’s where the Ombudsman sits relative to everything before it.

Day 0 — Freeze evidence, capture the UTR, open the prior complaint

Within the first hour: screenshot the withdrawal request, status, amount, timestamp; capture the UTR the moment it appears; and open the in-app / bank ticket with the amount, time and UTR, getting a reference number. That reference starts the 30-day Ombudsman clock. The full first-hour drill is the heart of the customer-care escalation page.

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

Send the same complaint by official email to the bank/wallet/PA, referencing the ticket. If it’s a UPI debited-but-not-credited case, this is the T+1 window — let the auto-reversal run. The 3 Patti withdrawal hub maps which failure type you’re in.

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

If the money is genuinely gone on the rail, open the UPI app’s “raise complaint / dispute” (feeds NPCI UDIR) or lodge a bank failed-transaction complaint with the UTR, claiming the ₹100/day if you’re past T+1. The screen-by-screen version is on the UPI failed, money debited page.

Day 8–29 — Formal written complaint + the 30-day wait

Escalate to a written formal complaint to the entity’s grievance / nodal officer, get a reference, and let the 30 days run. This is the dead-time that earns your Ombudsman eligibility. Don’t waste it — use it to assemble the evidence pack above.

Day 30+ — File with the Ombudsman

Thirty days after the prior complaint (or on an unsatisfactory reply), file free at cms.rbi.org.in with the full pack. Run National Consumer Helpline 1915 in parallel for any operator-side service deficiency, and cybercrime 1930 immediately if fraud is involved. The broader complaint map is on how to complain about RMG in India.

The ladder’s logic: each rung matches the rule-clock. You can’t file the Ombudsman before day 30 (clause 10), so the only way to reach it sooner in elapsed time is to start the prior complaint on day 0. People who lose weeks are the ones who spent the first month arguing with the app instead of putting a dated, reference-numbered complaint on the regulated entity’s record.

Copy-paste CMS complaint

Use this as the body of your CMS “nature of grievance” field (and as the email to [email protected] if you file by email). Fill in the bracketed parts. Keep it factual, dated, UTR-stamped, and framed as a regulated-entity payment failure — not a gaming dispute.

Nature of complaint: Deficiency in service by a regulated entity —
failed digital payment (UPI/bank transfer debited but not credited /
not reversed), unresolved after 30 days.

Regulated entity (respondent): [BANK / WALLET / PAYMENT AGGREGATOR NAME]
Complainant: [YOUR NAME], registered mobile [NUMBER], email [EMAIL]

Transaction details:
- Type: [UPI / IMPS / NEFT] credit to my account
- Amount: ₹[AMOUNT]
- Date / time: [DATE, TIME]
- UTR / RRN (12-digit reference): [UTR]
- My account / UPI ID: [A/C or HANDLE]
- KYC: completed; PAN matches my bank account name

What happened:
A payout I was entitled to receive was [debited but not credited /
shown as "paid" by the disbursing system but never credited / failed
and not auto-reversed]. My bank statement shows no credit against UTR
[UTR]. This is a deficiency in the regulated entity's payment service.

Prior complaint to the regulated entity (mandatory 30-day step):
- Complaint reference: [ENTITY COMPLAINT REF]
- Raised on: [DATE]
- Entity's response: [no reply within 30 days / reply received on
  [DATE] which did not resolve the issue]
- 30 days have elapsed since [DATE] without resolution.

Relief sought:
1. Credit of ₹[AMOUNT] to my registered account.
2. ₹100/day compensation for delay beyond T+1 per RBI circular
   DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019), where applicable.
3. Compensation for time lost, expenses, and harassment/mental anguish
   caused by the entity's failure to resolve (up to ₹1 lakh).

I confirm this matter is not pending before any court, tribunal or
other forum, and I am filing it myself (not through an advocate).

Attachments: bank statement (PDF) showing the debit/failed entry and
the missing credit against UTR [UTR]; the app's payout record marked
"paid" with that UTR; my prior complaint and the entity's reply;
KYC confirmation; a dated timeline.

Why this template wins where a homemade one fails: every line points the blame at the regulated entity’s payment failure, names a specific traceable UTR, and proves the 30-day gate up front — the three things the screening and the Ombudsman look for first. It deliberately avoids any “the game cheated me” language that would invite a “no deficiency in service” closure you couldn’t appeal.

Wallets, prepaid instruments and the ₹1 lakh harassment head

Two parts of the scheme get overlooked in gaming-payment cases and quietly decide whether you recover the full amount you’re owed: how wallets/PPIs fit, and how to actually unlock the separate ₹1 lakh harassment award. Both are worth getting right.

When the failure is a wallet, not a bank

Many gaming apps disburse to or through a prepaid payment instrument (PPI) — a wallet like the ones operated under RBI’s PPI licensing. A PPI issuer is a Payment System Participant, which means it is squarely a regulated entity under RB-IOS. So if your withdrawal landed in (or got stuck against) a wallet that then failed to credit your bank, or debited a load/transfer and never reversed it, the wallet provider is a valid respondent. The same logic as a bank applies: name the wallet, prove the failed transfer with its reference, prove you gave it 30 days. A wallet that ignores a documented grievance is committing the same deficiency a bank would.

The one twist: wallet balances have their own KYC and load limits, and a “stuck in wallet” amount can sometimes be a limit problem rather than a failure. Check whether the wallet flagged a KYC or load-cap issue before you frame it as a deficiency — if the wallet correctly declined a transfer because you breached a limit, that’s not a failure you can pin on it. But a wallet that accepted the transfer, debited it, and failed to deliver is fully in scope.

Unlocking the separate ₹1 lakh for time and harassment

The headline ₹20 lakh ceiling covers your actual loss — for most gaming payouts, just the un-credited amount. The separate ₹1 lakh is a different animal: it compensates the loss of your time, the expenses you incurred, and the harassment / mental anguish the entity’s conduct caused you. It’s discretionary, and the Ombudsman only grants it when you evidence the harassment — a bare claim earns nothing.

So if the entity stonewalled you, build the harassment record deliberately:

• Keep the full chain of unanswered emails and chat transcripts, dated, showing repeated unresolved follow-ups.
• Log call attempts — dates, durations, hold times, dropped calls to a helpline that went nowhere.
• Note expenses — travel to a branch, repeated paid SMS/printouts, anything you spent chasing the entity.
• Describe the concrete impact — money locked for weeks, the time lost, the distress — factually, not melodramatically.

The Ombudsman reads a documented pattern of an entity ignoring a customer as exactly the kind of conduct the ₹1 lakh head exists to discourage. A complainant who hands over a tidy log of twelve ignored emails over a month is far more likely to get the harassment award than one who simply writes “they harassed me.” For a few-thousand-rupee gaming payout, the harassment head can actually exceed the principal — which is precisely why a stonewalling entity should fear it.

The under-used lever in one line: the ₹1 lakh harassment award is separate from and on top of the refund, and it’s the part that makes ignoring you expensive for the entity — but only if you document the ignoring. Save every dated, unanswered message from day one; that log is what converts “they were slow” into a compensable deficiency.

How the Ombudsman actually decides your case

Knowing what happens inside the office after you file removes the anxiety of the silent weeks and tells you when to chase. The process is structured, not a black box.

After your ~48-hour eligibility screening, an admitted complaint moves through a predictable sequence:

1. Forwarding to the regulated entity. The Ombudsman office sends your complaint to the named entity and asks it to respond / file its written submission. This alone resolves a large share of cases: an entity that ignored you directly often pays up fast once RBI is the one asking, because a contested Award is a regulatory black mark it would rather avoid.
2. Facilitation / conciliation. The Ombudsman tries to broker a settlement between you and the entity. If the entity offers to credit the amount (and any compensation), and you accept, the matter closes by agreement — no Award needed. Most resolved gaming-payment complaints end here, in weeks, not months.
3. Examination on the merits. If no settlement comes, the Ombudsman examines the documents — your UTR-backed bank statement, the entity’s submission, the prior-complaint trail — to decide whether there was a deficiency in service. This is purely document-driven for a payment dispute; there’s rarely an oral hearing for a straightforward un-credited transfer.
4. Award or closure. If a deficiency is found, the Ombudsman issues an Award directing the entity to credit you and pay any compensation, within a stated period. If no deficiency is found, the complaint is closed — and if that closure is specifically “no deficiency in service,” remember it’s not appealable.
5. Implementation and compliance. A regulated entity that doesn’t appeal must comply with the Award within its stated period — credit the money, pay the compensation. RBI tracks compliance; an entity that flouts Awards invites supervisory attention.

Your job during this is light but real: respond promptly to any clarification the office requests, don’t open a parallel forum that would trigger the pending-elsewhere exclusion, and track status at cms.rbi.org.in using your reference number. If weeks pass with no movement and no request from the office, a polite status follow-up via the portal or 14448 is reasonable — but the structured sequence above means silence usually just means “with the entity for its response,” not “lost.”

A realistic read on outcomes: a clean, in-scope, well-evidenced gaming-payment complaint — a traceable UTR, a bank statement showing no credit, a dated 30-day prior complaint — has a genuinely strong shot, and most resolve by facilitation before any Award. A complaint that’s really an operator dispute in disguise — locked balance, withheld bonus, an unlicensed app — tends to close at the merits stage for “no deficiency” by the bank, with no appeal. The decisive variable is, again, which hand dropped your money and whether you framed the file around that regulated hand’s failure.

The decision process in one line: most winning cases never reach an Award — they settle at the facilitation stage once RBI forwards a documented, in-scope file to the entity, because the entity would rather pay than carry a contested Award. Your filing’s job is simply to make settling the entity’s cheapest option.

Worked scenarios: what realistically happens

Abstract rules are hard to act on, so here are four concrete cases mapped to outcomes — built from how the scheme’s rules apply, not from anyone’s personal filing.

Scenario A — UPI debited-but-not-credited, bank stonewalls (strong case)

You withdrew ₹12,000; your bank debited a UPI credit instruction that never reached you, the screen said “failed,” and no auto-reversal came. You complained to the bank on day 0 with the UTR; 30 days passed with a brush-off. Outcome: this is the textbook in-scope case. The T+1 rule was already breached, so the deficiency is clear. Most such cases settle by facilitation once the Ombudsman forwards the file — the bank pays the ₹12,000 plus the ₹100/day it already owed. If it fights, an Award restoring the ₹12,000 (well under the ₹20 lakh cap) plus a harassment sum is the realistic ceiling. Strong.

Scenario B — App says “paid” with a UTR, bank shows no credit (strong, with the UTR)

The app marked an ₹8,000 withdrawal “paid” and gave a UTR; your bank statement has no credit against it. You raised a bank trace request, waited 30 days, got nothing. Outcome: the UTR is everything here. With a bank statement proving no credit against that exact reference, you’ve shown the disbursing/receiving payment provider failed — in scope. Without the UTR you have no traceable failure and the case collapses to “the app says it paid; you say you didn’t get it,” which the Ombudsman can’t adjudicate against the bank. Strong only if you have the UTR.

Scenario C — Operator withholding a “bonus” balance (out of scope)

The app refuses to release ₹5,000 it labels a non-withdrawable bonus with unmet wagering. Outcome: no regulated payment entity failed — the operator is enforcing its terms. The Ombudsman closes this as outside scope (or for “no deficiency in service” by the bank, which you can’t appeal). The right door is the consumer-forum / NCH route, not RB-IOS. Out of scope.

Scenario D — Offshore/unlicensed app simply vanished (limited Ombudsman power)

An unlicensed app went dark holding your ₹20,000 balance. Outcome: the Ombudsman can do nothing against the operator. But trace the rail: if any deposit/withdrawal was a debited-but-not-credited failure by your regulated bank/PA, that specific transfer is in scope and recoverable. The balance held inside the dead operator is likely lost through this route — pursue cybercrime 1930 and the Sachet portal for the fraud angle. Limited.

The pattern across all four: you win to the exact extent a regulated payment entity failed a traceable transfer. Money stuck inside an operator — bonus, balance, a vanished app’s wallet — is outside the Ombudsman’s reach. Sort your case into A/B (rail failure → file) versus C/D-inside (operator hold → different door) before you spend a day on CMS.

Common mistakes that get gaming-payment complaints rejected

These are the avoidable own-goals. Each one ends a complaint at the screening stage or the first hearing.

• Naming the gaming operator as respondent. Instant out-of-scope. Name the bank / wallet / payment aggregator that handled the transfer.
• Filing before 30 days. Premature under clause 10 — the most common rejection. Start the prior complaint early, then wait the full 30 days.
• No UTR. Without the 12-digit reference there’s no traceable failure to pin on the entity. Capture it on day 0.
• Letting it age past one year from the entity’s reply (or one year + 30 days where none came). The window closes.
• Filing the same matter in court/consumer forum simultaneously without disclosing it. Triggers the “pending before another forum” exclusion.
• Using a lawyer to file. The scheme bars advocate-filed complaints unless the advocate is the aggrieved party. File it yourself — it’s designed to be filed by you.
• Framing it as a gambling dispute. Invites a “no deficiency in service” closure that you cannot appeal. Frame it as a payment failure.
• Submitting screenshots instead of a bank statement. Get the official PDF statement showing the debit with no credit — it’s far harder for the entity to dispute.

The mistakes reduce to one root error: aiming at the operator instead of the regulated payment provider. Fix that and most of the others fix themselves — the right respondent, the right framing, the right evidence, and the appeal door stays open.

The pre-filing checklist — run this before you submit

Print this, or keep it open beside the CMS form. If every box is ticked, your complaint clears the ~48-hour screening and reaches a hearing. If any box is blank, fix it first — filing with a gap just burns time.

• Respondent is a regulated entity. You’re naming a bank, wallet/PPI, or payment aggregator — never the gaming operator. (Gate 1.)
• You have the UTR. The 12-digit reference for the failed transfer is in hand, copied exactly. (No UTR = untraceable = screened out.)
• You have an official bank statement (PDF) showing the debit and the missing credit against that UTR — not just an app screenshot.
• You raised a prior complaint with the entity and have its reference number and date. (Gate 2.)
• 30 days have elapsed since that prior complaint — or you have a dated unsatisfactory reply that lets you file sooner. (Gate 2.)
• You’re within one year of the entity’s reply (or one year + 30 days where no reply came). (Gate 3.)
• The matter is not pending in any court / consumer forum — or, if a parallel matter exists, you’re disclosing it. (Gate 4.)
• You’re filing yourself, not through an advocate. (Gate 4.)
• Your complaint text is framed as a payment-service deficiency, with the relief stated in three concrete lines: credit the amount, pay the ₹100/day where applicable, compensate for time/harassment.
• Your harassment log is attached if you’re seeking the ₹1 lakh head — dated unanswered emails, call attempts, expenses.

A complaint with all ten ticked is the strong kind that tends to settle by facilitation within weeks. A complaint missing the UTR or the 30-day proof is the weak kind that gets bounced at screening or closed for “no deficiency” — losing you not just the case but the month you waited. The few minutes this checklist costs are the cheapest insurance on the whole process.

The checklist’s purpose in one line: it forces you to confirm you’re suing the right party, with the right proof, at the right time — the three things every rejected gaming-payment complaint got wrong. Ten ticks before you submit beats ten weeks of waiting for a rejection.

Grievance contact reference block

Keep this handy; it’s the whole Ombudsman map in one place.

Order of doors, in one line: entity grievance → wait 30 days → RBI Ombudsman (cms.rbi.org.in), with NPCI/UDIR feeding the payment dispute beforehand, NCH 1915 in parallel for operator deficiency, and cybercrime 1930 the instant fraud appears.

Where the Ombudsman fits versus the other doors

It’s not the only complaint authority, and using the wrong one wastes weeks. Here’s the clean division of labour.

• RBI Ombudsman (RB-IOS) — for a payment-service failure by a regulated entity (bank/wallet/PA). Powerful: can order a refund + up to ₹20 lakh + ₹1 lakh. Slow gate: 30 days. Use it when the rail failed.
• NPCI UDIR — the UPI-specific dispute that you raise before the Ombudsman, often resolving the failure within its 3–5 working-day window so you never need the Ombudsman. Use it first for any UPI failure.
• National Consumer Helpline 1915 / consumer forum — for the operator’s service deficiency (it won’t release a clean, owed balance). Reaches the operator’s consumer-service obligation, which the Ombudsman can’t. Use it when the operator, not the rail, is the problem — detailed on how to complain about RMG in India.
• Cybercrime 1930 / cybercrime.gov.in + Sachet — for fraud: fake care numbers, phishing, clone apps, vanished operators. Use it the instant deception is involved.

The honest limit, restated: the Ombudsman and bank disputes are strong against the payment rail (a regulated entity failed), and weak against a shady or offshore operator that simply ignores you — that operator may sit outside Indian regulatory reach entirely. That asymmetry is the best argument for only ever using payment methods and operators where the money path is clean and KYC is real.

FAQ

1. Can the RBI Ombudsman make a gaming app pay my winnings? No. The Ombudsman has zero jurisdiction over gaming operators — it only regulates banks, NBFCs, wallets, and Payment System Participants. It can order your bank or payment provider to fix a failed transfer, with awards up to ₹20 lakh + ₹1 lakh, but it cannot compel a Teen Patti or rummy operator to release a balance. Frame your complaint as a payment failure by your bank/PSP, not a dispute with the app.

2. Who exactly is a “regulated entity” I can complain about? Per RB-IOS 2021: all commercial banks, NBFCs, Payment System Participants (including wallets/PPIs and payment aggregators), and Credit Information Companies, plus larger urban/co-operative banks. Payment aggregators like Razorpay and Cashfree hold final RBI authorisation (since December 2022), so they count. A gaming operator does not — that’s the whole point of this page.

3. How long must I wait before filing with the Ombudsman? 30 days. You must first complain to the regulated entity and give it 30 days to resolve — filing earlier makes the complaint non-maintainable under clause 10. The only exception: if the entity already sent you a reply you’re dissatisfied with, you can file immediately without waiting out the full 30 days.

4. Is there a deadline by which I must file? Yes — within one year of receiving the entity’s reply, or, where no reply came, within one year and 30 days of your representation to it. Don’t let a stuck payout drift past roughly a year of the entity’s response or your complaint, or the matter becomes inadmissible.

5. How much compensation can the Ombudsman award? Up to ₹20 lakh for the actual loss caused by the deficiency, plus a separate ₹1 lakh for loss of your time, expenses, and harassment/mental anguish. For most gaming-payout disputes the “actual loss” is just the un-credited amount — often a few thousand rupees — which sits far below the ₹20 lakh ceiling.

6. Does it cost anything to file? No. Filing with the RBI Ombudsman via cms.rbi.org.in is completely free, and you do not need a lawyer. In fact the scheme bars an advocate from filing on your behalf unless the advocate is the aggrieved party — it’s designed for you to file yourself.

7. How do I file step by step? Go to cms.rbi.org.in, log in by mobile + email OTP, choose File a Complaint → against a regulated entity, pick your bank/wallet/PA, enter the UTR, amount, date and prior-complaint reference, upload your bank statement and prior complaint, and submit. You get an immediate complaint reference number; RBI screens it (broadly within ~48 hours) and assigns it.

8. What’s the single most important piece of evidence? The UTR / RRN — the 12-digit transaction reference — backed by an official bank statement showing the debit with no matching credit. That pair proves a regulated entity failed a specific, traceable transfer. Without the UTR there’s no identifiable failure for the Ombudsman to order reversed, and the case collapses.

9. The app marked my withdrawal “paid” but I never got it — is that an Ombudsman case? Yes, if you have the UTR. Get the UTR from the app, then ask your bank to trace it; if the bank shows no credit against that reference and won’t fix it within 30 days, the payment provider’s failure is in scope. Without the UTR it’s just your word against the app’s, which the Ombudsman can’t adjudicate against the bank.

10. My money is stuck inside the app as a bonus/locked balance — can the Ombudsman help? No. A locked bonus, unmet wagering, or any balance the operator holds under its terms is not a payment-service failure, so it’s outside RB-IOS scope. The right route is the National Consumer Helpline 1915 and the consumer-forum process — see how to complain about RMG in India.

11. What can I do if the Ombudsman rejects my complaint? If you got an Award you dislike, appeal within 30 days to the Appellate Authority (Executive Director, CEPD, RBI, Mumbai) — they can dismiss, allow, set aside, remand, or modify it. But a closure for “no deficiency in service” is final and cannot be appealed, which is why you must frame the complaint around the regulated entity’s payment failure from the start.

12. How long does the whole process take? Roughly one to three months from filing for a clean, well-evidenced case — many settle by facilitation within weeks once the entity sees a documented file, while contested cases that go to an Award take longer. The unskippable part is the 30-day prior-complaint window before you can even file, so start the prior complaint on day 0.

13. Does PROGA 2025 stop me from using the Ombudsman for a gaming payment? No. A payment failure by your bank or wallet is a banking grievance regardless of what the money was for, and banks kept processing withdrawals so users could recover existing balances. PROGA’s only impact: you cannot use the Ombudsman to recover a new deposit into a now-prohibited money game, because that deposit is itself illegal post-1 May 2026.

14. Can I call 14448 to lodge the complaint by phone? The 14448 contact centre helps you file and answers questions in multiple languages, but it cannot lodge the complaint for you over the phone. The actual filing must go through cms.rbi.org.in, email to [email protected], or post to the CRPC in Chandigarh.

15. Should I use NPCI UDIR or the Ombudsman first? NPCI UDIR first, for any UPI failure — its 3–5 working-day window often resolves the credit before you ever need the Ombudsman, and it’s a prerequisite step in the ladder. Escalate to the RBI Ombudsman only after 30 days of the regulated entity failing to resolve it. The full UPI-dispute walkthrough is on the UPI failed, money debited page.

Sources & method. Eligibility, compensation, filing, appeal and timeline facts on this page are built from primary RBI sources, not personal filings. Key references: the Reserve Bank – Integrated Ombudsman Scheme, 2021 FAQ and the RB-IOS 2021 notification (30-day gate, one-year limit, ₹20 lakh + ₹1 lakh awards, clause-10 exclusions, CEPD appellate authority, “no deficiency in service” non-appealability); the CMS complaint portal cms.rbi.org.in and the 14448 contact centre / [email protected] / CRPC Chandigarh filing channels; the RBI Guidelines on Regulation of Payment Aggregators and Payment Gateways (17 March 2020) and Razorpay/Cashfree final PA authorisation (who counts as a regulated payment entity); the RBI failed-transaction TAT circular DPSS.CO.PD No.629/02.01.014/2019-20 (20 Sep 2019) (T+1 auto-reversal, ₹100/day); NPCI UPI Help / UDIR; the Promotion and Regulation of Online Gaming Act, 2025; the RBI Sachet portal; and cybercrime reporting at cybercrime.gov.in / helpline 1930 and National Consumer Helpline 1915. This page is information, not legal or financial advice — verify each step against the current scheme text and your bank’s grievance policy.