Grievance Officer & Nodal Officer: The RMG Escalation You Skip

The 40-second answer

A grievance officer (and the closely related nodal officer) is the named, legally mandated person an Indian operator must appoint to handle your complaint — not a chatbot, a person with a deadline. Under the IT Rules 2021 they must acknowledge within 24 hours and resolve within 15 days. Under the Consumer Protection e-commerce rules it’s 48 hours and one month. An RBI payment-aggregator nodal officer must be named on the website. Miss those clocks and after 30 days you file free with the RBI Ombudsman. This page is the rung most people skip between “support ignored me” and “I gave up.” For the full ladder, the hub is RMG customer-care escalation.

Editor’s verdict, up front. Ninety percent of stuck-payout complainers never invoke a grievance officer. They spam in-app chat, get a canned reply, and quit — or jump straight to the RBI Ombudsman, who bounces them back for skipping a rung. The grievance officer is the legal pressure point in between: a real person, with a statutory deadline, whose inaction itself becomes the basis for your next escalation. The trick is three things most people get wrong. First, find the right officer — gaming apps, payment apps, and marketplaces each fall under a different law with a different officer and a different clock. Second, write a grievance, not a complaint — the structure that triggers the statutory duty looks nothing like an angry chat message. Third, time-stamp everything, because the day the officer received your grievance is the day the 30-day Ombudsman clock starts. This page maps all three, with the exact legal citations and copy-paste letters.

2026 reality you must read first. The legal ground shifted hard. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) got Presidential assent on 22 August 2025, and its Rules came into force on 1 May 2026, banning all online money games. India’s biggest cash operators — RummyCircle, Junglee Rummy, Dream11, MPL — suspended cash play from late August 2025. So in mid-2026 your problem is usually not “my live app is slow,” it’s “a discontinued app still holds my balance and won’t release it.” The grievance officer route still works for that recovery, because banks were instructed to keep processing withdrawals. But never deposit again to “unlock” a payout — that’s illegal now. This guide reads two ways: for a still-live channel and for a wind-down recovery, and it flags which is which.

Run the diagnostic first, then read the section that fits you

At the top of this page is the Payout Diagnostic Wizard. Pick your operator type (gaming app / payment app / marketplace / bank), pick what you’re seeing, and enter how many days you’ve waited. It tells you which grievance officer your case falls under — because the law that governs the officer, and therefore your deadline, depends entirely on which kind of entity you’re fighting. The wizard’s timings are the statutory deadlines cited on this page (IT Rules 24h/15d, e-commerce 48h/1mo, RBI 30d), not anyone’s personal experience.

If you’d rather read, the rest of this guide is the manual version. It is long on purpose, because the grievance-officer system is genuinely a maze of three overlapping laws, and the value is in knowing which one is your lever.

What a grievance officer actually is (and the nodal officer next to it)

When people search “grievance officer online gaming,” “nodal officer complaint,” or “how to escalate to a grievance officer,” they’re usually circling the same frustration: support won’t help, and they’ve heard there’s a “higher authority” they can email. There is. But the term covers three different legally-mandated roles, and confusing them is why so many escalations go nowhere. Let’s be precise about the object.

A grievance officer is a named individual an entity is required by statute to appoint, whose job is to receive, acknowledge, and resolve user complaints within a fixed timeline. The key word is statute. This isn’t a customer-service tier the company invented; it’s a legal post with legal duties, and the failure to perform those duties is itself actionable. Three different Indian laws create such a post:

• The Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 require every “intermediary” — which includes most app-based platforms — to appoint a Grievance Officer who acknowledges in 24 hours and resolves in 15 days.
• The Consumer Protection (E-Commerce) Rules, 2020 require every “e-commerce entity” to appoint a Grievance Officer who acknowledges in 48 hours and redresses in one month.
• The RBI Payment Aggregator Directions require every payment aggregator (the company that actually moves your withdrawal) to appoint a Nodal Officer for customer grievances, whose name and contact must be prominently displayed on the website, plus a documented escalation matrix.

A nodal officer is the variant used in the banking and payments world. The word “nodal” just means the single point of contact the regulator expects an entity to designate so complaints don’t get lost between departments. In payments, the nodal officer is the rung you escalate to after the first-line grievance officer, and the person whose silence eventually qualifies you for the RBI Ombudsman.

A grievance appellate authority is the third tier, and it only exists in some frameworks. Under PROGA’s 2026 Rules, for example, an unresolved gaming complaint escalates from the operator to a Grievance Appellate Committee, then to the Online Gaming Authority of India — each with a 30-day window. Under the IT Rules, an unhappy user can appeal a social-media intermediary’s decision to a government Grievance Appellate Committee within 30 days. You rarely reach these tiers, but knowing they exist changes how you write the first grievance — because you want to set up the appeal cleanly.

Why this distinction decides whether you win

A player who emails “the grievance officer” without knowing which law applies is firing in the dark. The deadline you can demand, the language that triggers a statutory duty, and the authority you escalate to next are all different depending on whether you’re treating the operator as an intermediary (IT Rules), an e-commerce entity (Consumer Protection Rules), or your money as a payment-rail failure (RBI). The single most useful thing you can do before writing a word is decide which hat your opponent is wearing — and often it’s more than one, which is your advantage, because you can invoke multiple clocks at once.

A worked example makes the stakes concrete. Say a discontinued rummy app is sitting on your ₹8,000 balance. You can simultaneously: treat the app as an intermediary and demand a 24-hour acknowledgment under the IT Rules; treat it as an e-commerce entity providing a paid service and cite the 48-hour/one-month e-commerce duty; and, if the money already left a payment rail, treat that leg as an RBI payment-system matter with the 30-day Ombudsman backstop. Three deadlines, three escalation paths, one ₹8,000. The operator that ignores a generic “please help” email finds it much harder to ignore a letter that names all three statutory duties and the specific consequence of breaching each.

The legal basis, law by law (this is your leverage)

Everything that makes a grievance officer answer their email comes from one of the four frameworks below. Skim the one that fits your operator; the citations are what you quote in the letter.

IT Rules 2021 — the intermediary grievance officer (24 hours / 15 days)

This is the broadest and most useful framework, because nearly every app that lets users transact qualifies as an intermediary. Under Rule 3(2) of the IT (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, every intermediary must:

• Appoint a Grievance Officer based in India and publish that officer’s name and contact details on its website or app, along with the complaint mechanism.
• Acknowledge any complaint within 24 hours.
• Dispose of (resolve) the complaint within 15 days of receipt.

That 15-day resolution window is a sharp improvement on the old 2011 rules, which gave intermediaries 30 days, per the Trilegal summary of the 2021 Rules. The 24-hour acknowledgment clock is the one you’ll lean on most, because it’s the easiest breach to prove: if you have a time-stamped grievance and no acknowledgment 24 hours later, the entity is already in default of a statutory duty, and you say so in your follow-up.

A nuance worth knowing: a Significant Social Media Intermediary (a platform above a user threshold) must additionally appoint a resident Chief Compliance Officer, a Grievance Redressal Officer, and a nodal contact person, all Indian residents, per the Mondaq highlights of the Rules. Most gaming apps aren’t “significant social media intermediaries,” but the base grievance-officer duty under Rule 3(2) applies to virtually all of them regardless of size.

The honest limit: the IT Rules grievance officer is built to handle content and conduct complaints (defamation, impersonation, unlawful content) more than money complaints. You can still invoke it for a withheld payout — a refusal to release your own money is plausibly a grievance about the platform’s conduct — but if your real injury is a payment failure, the RBI framework below has sharper teeth. Use the IT Rules to force an acknowledgment and a 15-day clock; use RBI to force a refund.

Consumer Protection (E-Commerce) Rules 2020 — the e-commerce grievance officer (48 hours / one month)

If the operator sold you a service for money, it’s an e-commerce entity, and the Consumer Protection (E-Commerce) Rules, 2020 apply on top of everything else. Rule 4 requires every e-commerce entity to:

• Appoint a Grievance Officer and display that officer’s name, contact details and designation on the platform, per the consumerprotection.in summary of Rule 4.
• Acknowledge a consumer complaint within 48 hours.
• Redress the complaint within one month from the date of receipt.

The reach of this framework is wider than it first looks. Per the AKM compliance analysis, sellers on a marketplace must also appoint a grievance officer with the same timelines — so if you bought a service through a platform, both the platform and the underlying seller can carry the duty. And the Rules apply even to foreign e-commerce entities that offer goods or services to Indian consumers, which matters for offshore operators that think Indian law can’t reach them.

The angle most useful for a stuck balance: the e-commerce framework treats a deficiency in service as the injury. A KYC-clean, clearly-owed payout that the operator simply won’t release is a textbook service deficiency, and the one-month redressal duty plus the consumer-forum backstop is your path. Where the IT Rules give you a fast acknowledgment clock, the e-commerce Rules give you a consumer-court endgame (the National Consumer Helpline and the e-daakhil forum), which is exactly the lever for an operator that isn’t an RBI-regulated payments company.

RBI Payment Aggregator Directions — the payments nodal officer (displayed + escalation matrix)

When your withdrawal actually moves, it moves through a payment aggregator (PA) — a regulated company that collects and settles payments. The RBI Payment Aggregator Directions, consolidated in the 2025 master directions issued 15 September 2025 per the Khaitan & Co note, require every PA to:

• Designate a Nodal Officer for customer grievances and prominently display that officer’s name and contact details on its website, per the AuthBridge analysis of the 2025 directions.
• Appoint a grievance redressal officer and publish an escalation matrix so a complaint can climb in order, per the Lexology overhaul summary.
• Ensure the dispute-resolution process complies with RBI’s turnaround-time (TAT) rules for failed transactions — the same RBI failed-transaction circular that forces a T+1 auto-reversal and ₹100/day compensation on a debited-but-not-credited UPI payout.
• Disclose merchant policies and customer-complaint information on its site or app.

This is the framework with the most enforcement weight, because a PA is an RBI-regulated entity, and an RBI-regulated entity that doesn’t resolve your complaint in 30 days drops you straight into the RBI Integrated Ombudsman Scheme — a free, binding redress mechanism. The catch is that you have to identify the PA. Your money usually leaves the gaming app and travels through a named payment company (you’ll see it on the payout screen, the bank narration, or the UTR trail). That company’s nodal officer is your highest-leverage target for a money complaint, and the section below on finding the officer covers how to surface it.

PROGA 2026 — the gaming-specific grievance tier (operator → committee → authority, 30 days each)

For online gaming specifically, the Promotion and Regulation of Online Gaming Rules, 2026 (in force 1 May 2026) add a dedicated grievance ladder. Per the Mondaq summary of the 2026 Rules, a registered game provider must run a functional grievance mechanism, and an unresolved complaint escalates in three tiers:

1. The online game service provider — the first point of contact, which must maintain an internal grievance system.
2. The Grievance Appellate Committee — if unresolved, the user may appeal within 30 days, and the committee endeavours to resolve within 30 days.
3. The Online Gaming Authority of India — if still unsatisfied, the user may approach within 30 days of the committee’s order, and the Authority endeavours to resolve within 30 days, with a final appeal to the Secretary, MeitY.

The practical caveat for 2026: because PROGA banned online money games, most of the big operators discontinued cash play, so the live use of this ladder is narrower than the law implies. But it’s the right framework if a registered provider (or a wind-down operation) is mishandling your balance recovery — and citing the PROGA grievance duty in your letter signals you know the gaming-specific law, not just the generic ones.

The four-framework cheat-sheet, in one line: invoke IT Rules to start a 24-hour clock on any app; invoke e-commerce Rules to frame an owed balance as a service deficiency with a one-month duty; invoke RBI PA Directions to reach a regulated payments nodal officer with a 30-day Ombudsman backstop; invoke PROGA when a registered gaming provider mishandles a recovery. The strongest letters cite more than one, because more than one usually applies.

Support ticket vs formal grievance: the difference that changes the clock

Here’s the distinction almost everyone misses, and it’s the difference between a reply in 15 days and no reply ever. A support ticket and a formal grievance are not the same thing, and only one of them starts a statutory clock.

A support ticket is what you open in the app’s help chat. It goes to first-line support — often outsourced, often scripted — and there is no legal deadline attached to it. The company can take as long as it likes, send canned replies, and close it as “resolved” without resolving anything. A support ticket is a customer-service interaction. Useful as a first step and as evidence that you tried, but toothless on its own.

A formal grievance is a complaint addressed to the named grievance/nodal officer, framed as a grievance, that invokes the statutory duty. The moment a properly-formed grievance reaches that officer, the legal clock starts: 24 hours to acknowledge under the IT Rules, 48 hours under the e-commerce Rules. The officer’s failure to meet that clock is now a breach, not just bad service — and a breach is what you carry up to the Ombudsman or the consumer forum.

Four things turn a toothless ticket into a clock-starting grievance:

1. It’s addressed to the grievance/nodal officer by title (or name, if published), not to “support.” You’re invoking a legal post, so you address the post.
2. It uses the word “grievance” and references the relevant rule. “I am submitting a formal grievance under the IT Rules 2021 / Consumer Protection (E-Commerce) Rules 2020” tells the recipient which duty they’re now on the hook for.
3. It states a specific, dated demand — the amount, the date, the relief sought, and the deadline you expect (their statutory one).
4. It’s sent on a channel that creates a record — the published grievance email, not an ephemeral in-app chat. You need to be able to prove when it was received, because that date anchors every downstream clock.

The sequence that works is therefore: open the support ticket first (it’s evidence you used the front door and gives you a ticket ID), then, if first-line support stalls or fobs you off, escalate to a formal grievance addressed to the officer. The ticket establishes you tried; the grievance starts the clock. Skipping straight to the grievance officer on hour one sometimes works, but operators occasionally bounce it back asking you to “use support first,” so leading with a documented ticket closes that door.

The one-line test: if your message went to “support” and has no statutory deadline, it’s a ticket. If it went to the named grievance/nodal officer, used the word grievance, and cited a rule, it’s a grievance — and the clock is now running. Only the second kind builds toward the Ombudsman.

How to find an operator’s grievance or nodal officer

You cannot escalate to an officer you can’t name an address for. The good news is the law requires the officer’s details to be published, so they’re almost always findable — just buried. Here is where to look, in the order most likely to pay off.

1. The Terms & Conditions / Terms of Service

The single most reliable location. Because the IT Rules, the e-commerce Rules, and the RBI directions all require the officer’s details to be disclosed, a compliant operator puts them in the legal documents. Open the app’s or website’s Terms & Conditions, Terms of Use, or a linked Grievance Redressal Policy, and search the page (Ctrl+F / browser find) for these terms:

• “grievance officer”, “grievance redressal officer”, “GRO”
• “nodal officer” (this is the one for the payments side)
• “grievance@”, “nodal@”, “compliance@” (the email is often a dedicated alias)
• “Rule 3(2)” or “IT Rules” (intermediaries often quote the rule they’re complying with, and the officer’s name sits right beside it)

A compliant grievance policy typically lists the officer’s name, designation, email, postal address, and the acknowledgment/resolution timeline in one block. That block is your target address, and the published timeline is the deadline you’ll hold them to.

2. The website footer and a dedicated “Grievance Redressal” page

Many operators keep a footer link labelled “Grievance Redressal,” “Contact / Grievance,” “Customer Grievance Policy,” or “Legal.” Payment companies in particular run a standalone grievance page because RBI requires the nodal officer to be prominently displayed — not buried in a PDF. Scroll to the very bottom of the site and look for it. On a payment aggregator’s site, the nodal officer details are frequently on a page titled “Grievance Redressal Mechanism” or “Customer Grievance Policy,” often with an escalation matrix (Level 1: support → Level 2: grievance officer → Level 3: nodal officer).

3. Inside the app

In the app itself, the officer’s details may live under Settings → Legal, Help → Grievance, Profile → About → Terms, or a “Grievance Officer” entry in the help centre. Some apps surface a “raise a grievance” or “escalate” button distinct from the normal support chat — that’s the channel that routes to the officer. If you can’t find it, the app’s Terms (reachable from the install listing or the website) is the fallback.

4. The payment aggregator behind your withdrawal

For a money complaint, the gaming app’s grievance officer is often less powerful than the payment aggregator’s nodal officer, because the PA is RBI-regulated. To find the PA:

• Look at the payout / withdrawal screen — it sometimes names the payment partner.
• Check the bank narration / statement for the failed or successful payout; the merchant string usually contains the PA’s name.
• The UTR trail and any payment receipt email will reference the settling entity.

Once you have the PA’s name, go to that company’s website footer and find its nodal officer on its grievance page. This is the highest-leverage target for a debited-but-not-credited payout, because that company answers to RBI.

5. When the operator hides the officer (the offshore/clone problem)

Some operators — especially unlicensed, offshore, or clone apps — publish no grievance officer at all, which is itself a violation. If you genuinely cannot find an officer after checking the Terms, footer, app, and payment partner, you have two moves. First, treat the absence as evidence of non-compliance and skip to the external authorities (your bank’s nodal officer for the payment leg, the National Consumer Helpline for the service deficiency, the RBI Ombudsman for the payment-rail failure). Second, if money was lost on the rail, your bank’s grievance/nodal officer is always findable and always RBI-regulated — so even a faceless app can’t block that path. The cluster page on how to complain about an Indian gaming or payment problem maps every external channel for exactly this case.

The finding shortcut: open the Terms & Conditions and Ctrl+F for “grievance officer” and “nodal officer.” If it’s a money complaint, also find the payment aggregator’s name from your bank narration and look up its nodal officer. If neither exists, the operator is non-compliant — go straight to your bank’s nodal officer and the external authorities, because they’re always reachable.

What the officer is actually obligated to do (and the clocks, side by side)

Knowing the exact duty lets you quote it. Here is every grievance-officer obligation across the four frameworks in one table. Timings marked with a rule reference are statutory; treat them as the deadline you can demand, not a courtesy.

Read that table as a set of clocks you start. The IT Rules 24-hour clock is your fastest breach to prove. The e-commerce one-month clock is your service-deficiency endgame. The RBI 30-day clock is your route to a free, binding Ombudsman ruling. You can run all of them at once.

A subtle but important point on the RBI 30-day rule: per the RB-IOS 2021 FAQ, you become eligible to file with the Ombudsman if you received no reply within 30 days after the regulated entity received your complaint, or if the reply was unsatisfactory. That’s why the date the officer received your grievance is the single most important fact to capture — it’s the start of the 30-day eligibility window. A grievance with no provable receipt date is a grievance you can’t escalate cleanly.

How to write an effective grievance-officer escalation (the structure)

A grievance that works reads nothing like a support chat. Support chat is conversational and emotional; a grievance is a structured legal demand. The structure below is what triggers the statutory duty and sets up the appeal. Use it for any of the four frameworks — only the cited rule changes.

The seven required parts

1. Address it to the officer by post. “To: The Grievance Officer / Nodal Officer, [Operator].” You’re invoking a legal role, so name the role. If the published name is available, use it.
2. State that it’s a formal grievance and cite the rule. One sentence: “I am submitting a formal grievance under [IT Rules 2021, Rule 3(2) / Consumer Protection (E-Commerce) Rules 2020, Rule 4 / the RBI Payment Aggregator Directions].” This is the line that converts a ticket into a clock-starting grievance.
3. Give the facts, dated and numbered. Amount, date and time of the withdrawal, current status shown in the app, the UTR/reference if money left a rail, your registered mobile number, and your KYC status. Numbers, not adjectives. The reader needs to act, not to feel.
4. Reference the prior support attempt. “I first raised this via in-app ticket [ID] on [date]; it remains unresolved after [N] days.” This proves you used the front door and dates the failure.
5. State the relief you demand, specifically. Not “please help” — “Credit ₹[amount] to my registered account” and, if a rail failed, “plus ₹100/day compensation per the RBI TAT circular.” Vague demands get vague non-answers.
6. Demand it in writing, and set the statutory deadline. “Please acknowledge within 24 hours and resolve within 15 days as required under the Rule cited. Please provide the UTR and a written reason for any delay.” Asking for a written reason is deliberate — a written refusal is far more useful to you than silence.
7. State the next rung. “If unresolved within the statutory period, I will escalate to the RBI Integrated Ombudsman (RB-IOS 2021), the National Consumer Helpline (1915), and the relevant grievance appellate authority.” This isn’t a threat; it’s notice, and notice often unsticks the case because it signals you know the process.

What to cite, depending on the operator

• Any app withholding your money: cite the IT Rules 2021, Rule 3(2) for the 24-hour/15-day clock — it applies to almost every app and is the easiest breach to prove.
• A paid service that won’t deliver (an owed balance): add the Consumer Protection (E-Commerce) Rules 2020, Rule 4 for the 48-hour/one-month service-deficiency duty and the consumer-forum backstop.
• A debited-but-not-credited payout: cite the RBI failed-transaction TAT circular (DPSS.CO.PD No.629, 20 Sep 2019) for the T+1 auto-reversal and ₹100/day, and address the payment aggregator’s nodal officer.
• A registered gaming operator mishandling a recovery: add the PROGA 2026 grievance-mechanism duty and the appeal path to the Grievance Appellate Committee.

What to demand in writing (and why “in writing” matters)

Demand four things in writing every time: (a) the status of your payout and its UTR; (b) a written reason for any hold or delay; (c) a resolution date; and (d) a complaint/grievance reference number. The reason “in writing” matters is the appeal: the RBI Ombudsman and the consumer forum decide on documents, not feelings. A written refusal — “we are holding your balance because X” — is evidence you can attack, while a phone call that says the same thing leaves no trace. If support tells you anything material verbally, email them to “confirm in writing what was discussed,” which converts the verbal into a record.

The grievance-writing rule in one line: address the officer by title, say the word grievance and cite the rule, give dated numbered facts and a specific demand, set the statutory deadline, and demand a written reason — because the next rung decides on paper, and a paper trail is the whole game.

The universal escalation ladder with the grievance officer in the middle

The grievance officer isn’t the start or the end of escalation — it’s the load-bearing middle rung, the one that converts “support ignored me” into “a regulated entity breached a statutory duty.” Here’s the full ladder with the officer in its correct place, matched to the clocks above.

Day 0 — Freeze evidence and open the support ticket

The highest-leverage Day-0 action is documentation, not complaining. Within the first hour:

• Screenshot everything: the withdrawal request, the status screen, the amount, the timestamp, your wallet balance before and after. Date-stamped screenshots are your evidence.
• Capture the UTR / reference the moment one appears. Without it you can’t trace a “paid” payout. (For exactly where each UPI app hides the UTR, the withdrawal hub 3 Patti withdrawal fix lists the per-app menu paths.)
• Open the in-app support ticket and get a ticket ID. This is the front door, and the ID dates your first attempt.

Never deposit more “to unlock” a payout, never start a second account, and never share an OTP or UPI PIN with anyone who “calls to help.” Real support never needs your PIN.

Day 1–3 — Escalate to the formal grievance officer

If first-line support stalls, this is the rung this whole page is about:

• Send a formal grievance to the published grievance/nodal officer email, structured as in the section above, referencing the ticket ID and citing the relevant rule.
• This starts the statutory clock — 24 hours to acknowledge under the IT Rules, 48 hours under the e-commerce Rules.
• If it’s a failed/debited UPI payout, this is also the T+1 window — let the rail’s auto-reversal run before you treat it as theft, but the grievance can go in parallel.

Day 4–15 — Hold the officer to the clock + open the payment dispute

• If the officer missed the acknowledgment deadline, send a one-line follow-up noting the breach (“No acknowledgment received within the 24 hours required under Rule 3(2)”) — that breach is now part of your record.
• If money is genuinely gone on the rail, open your UPI app’s “raise complaint / dispute” on the transaction (it routes into NPCI UDIR), or lodge a bank failed-transaction complaint with the UTR and claim the ₹100/day if you’re past T+1.
• Escalate from the first-line grievance officer to the nodal officer if the operator’s escalation matrix has that tier.

Day 16–30 — Final notice + parallel consumer channel

• Send the operator a final-notice grievance: restate the facts, the ticket ID, the UTR, the days elapsed, every statutory breach so far, and the exact next steps you’ll take. A clear, dated final notice frequently unsticks a payout.
• Run the National Consumer Helpline 1915 in parallel for the service-deficiency angle if the operator is sitting on a clean, owed balance.

Day 30+ — RBI Ombudsman and the appellate tiers

• After 30 days of no resolution from a regulated entity (your bank or the payment aggregator), file free with the RBI Integrated Ombudsman Scheme 2021 at cms.rbi.org.in. RB-IOS covers banks, NBFCs and Payment System Participants, and redress is free.
• For a gaming-specific complaint against a registered provider, appeal to the Grievance Appellate Committee under PROGA within 30 days.
• For suspected fraud — a fake “care number,” a clone app, an OTP scam — report immediately to the cybercrime helpline 1930 and cybercrime.gov.in, and flag suspicious payment entities on RBI’s Sachet portal.

Honest limit of this ladder: it’s powerful against regulated entities — a payment aggregator or your bank, who answer to RBI, and a registered gaming provider, who answers to the Authority. It’s weaker against an unlicensed offshore clone that publishes no officer and ignores everything, because that operator may sit outside Indian reach. For any money that touched the rail, though, your bank’s nodal officer is always reachable, which is why a rail loss is always the more recoverable kind.

Copy-paste grievance-officer letters

Fill in the bracketed parts. Keep every message factual, dated, and ID-stamped — emotion doesn’t move a grievance officer, a cited rule and a UTR do. There are six here, one for each situation you’ll face.

Letter A — Formal grievance to the grievance officer (IT Rules, any app)

To: The Grievance Officer, [Operator name]
Subject: Formal grievance under IT Rules 2021, Rule 3(2) —
withdrawal of Rs.[AMOUNT] not credited

Dear Grievance Officer,

I am submitting a formal grievance under Rule 3(2) of the Information
Technology (Intermediary Guidelines and Digital Media Ethics Code)
Rules, 2021.

Facts:
- Amount: Rs.[AMOUNT]
- Withdrawal requested: [DATE, TIME]
- Status shown in app: [STATUS]
- UTR / reference (if shown): [UTR]
- Registered mobile: [NUMBER]
- KYC: completed (PAN + Aadhaar verified, name matches bank account)
- Prior in-app ticket: [TICKET ID], raised [DATE], unresolved after
  [N] days.

I request that you (1) acknowledge this grievance within 24 hours and
(2) resolve it within 15 days, as required under Rule 3(2). Please
credit the payout, or provide the UTR and a written reason for the
delay. Please also share a grievance reference number.

If unresolved within the statutory period, I will escalate to the
relevant grievance appellate authority, the National Consumer
Helpline (1915), and — for any payment-rail failure — the RBI
Integrated Ombudsman (RB-IOS 2021).

[Name] / [Registered mobile] / [Email]

Letter B — Grievance as a service deficiency (Consumer Protection e-commerce Rules)

To: The Grievance Officer, [Operator name]
Subject: Formal grievance under Consumer Protection (E-Commerce)
Rules 2020, Rule 4 — deficiency in service

Dear Grievance Officer,

I am submitting a formal grievance under Rule 4 of the Consumer
Protection (E-Commerce) Rules, 2020. The operator is holding a
verified, KYC-complete balance owed to me and has not released it,
which is a deficiency in service.

- Operator / service: [APP NAME]
- Balance owed: Rs.[AMOUNT]
- Withdrawal requested: [DATE]
- In-app ticket: [TICKET ID], raised [DATE], unresolved after [N] days
- KYC: completed; PAN matches bank account name

Per Rule 4, please acknowledge this grievance within 48 hours and
redress it within one month. I require, in writing: the status of the
balance, a reason for any hold, a resolution date, and a grievance
reference number.

If unresolved, I will file with the National Consumer Helpline (1915)
and the consumer forum via e-daakhil.

[Name] / [Registered mobile] / [Email]

Letter C — Grievance to the payment aggregator’s nodal officer (debited-but-not-credited)

To: The Nodal Officer, [Payment Aggregator name]
Subject: Grievance — UPI debited but not credited — UTR [UTR] —
refund + TAT compensation

Dear Nodal Officer,

A payout settled through your platform was debited but not credited
to my account.

- UTR / RRN: [UTR]
- Amount: Rs.[AMOUNT]
- Date / time: [DATE, TIME]
- My account / UPI ID: [A/C or HANDLE]
- Merchant / app: [APP NAME]

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

If unresolved within 30 days, I will file with the RBI Integrated
Ombudsman (RB-IOS 2021) at cms.rbi.org.in.

[Name] / [Registered mobile] / [Email]

Letter D — Follow-up noting a missed acknowledgment deadline

To: The Grievance Officer / Nodal Officer, [Operator name]
Subject: [Grievance ref / Ticket ID] — no acknowledgment within the
statutory period

Dear Officer,

My formal grievance dated [DATE] (ref [REF]) regarding a withdrawal
of Rs.[AMOUNT] has not been acknowledged within the [24 hours / 48
hours] required under [Rule 3(2), IT Rules 2021 / Rule 4, Consumer
Protection (E-Commerce) Rules 2020].

This non-acknowledgment is itself a breach of the cited Rule. Please
treat this as a final notice. If I do not receive resolution and a
grievance reference number within [N] days, I will escalate to the
RBI Integrated Ombudsman, the National Consumer Helpline (1915), and
the relevant grievance appellate authority, citing both the original
issue and this failure to acknowledge.

[Name] / [Registered mobile] / [Email]

Letter E — Grievance to a registered gaming provider (PROGA 2026 recovery)

To: The Grievance Officer, [Registered game provider]
Subject: Grievance — balance recovery — Rs.[AMOUNT] withheld

Dear Grievance Officer,

I am submitting a grievance regarding an existing balance you have
not released. As a registered online game service provider, you are
required to maintain a functional grievance redressal mechanism under
the Promotion and Regulation of Online Gaming Rules, 2026.

- Balance owed: Rs.[AMOUNT]
- Recovery requested: [DATE]
- Registered mobile: [NUMBER]
- KYC: completed; PAN matches bank account
- In-app ticket: [TICKET ID], raised [DATE]

Please release my balance to my registered account and provide a
grievance reference number and written status. If unresolved, I will
appeal to the Grievance Appellate Committee within 30 days and, if
necessary, the Online Gaming Authority of India.

[Name] / [Registered mobile] / [Email]

Letter F — RBI Ombudsman grievance (after 30 days)

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

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

File Letter F at cms.rbi.org.in only after 30 days have passed without resolution from the entity, since that 30-day rule is the eligibility gate for the RB-IOS 2021.

When the grievance officer fails to respond: the next rung

A grievance officer’s silence is not a dead end — it’s the trigger for the next rung, and the framework tells you which rung. Match the silence to the door.

If the officer ignores a payment-rail failure → bank nodal officer, then RBI Ombudsman

If your money left a rail (debited-but-not-credited, or “paid” but never arrived) and the operator’s grievance officer is silent:

• Escalate to your own bank’s nodal officer — always reachable, always RBI-regulated — with the UTR and the failed-transaction details.
• If 30 days pass from when the regulated entity received your complaint with no reply or an unsatisfactory one, file free with the RBI Integrated Ombudsman at cms.rbi.org.in. RB-IOS covers banks and Payment System Participants, so the payment aggregator and your bank are both in scope.

If the officer ignores an owed-balance service deficiency → NCH 1915, then e-daakhil

If the injury is a clean, owed balance the operator simply won’t pay (not a rail failure):

• File with the National Consumer Helpline (1915), which reaches the operator’s service obligation.
• If unresolved, file a consumer complaint via e-daakhil (the consumer-forum online portal). The Consumer Protection (E-Commerce) Rules give you standing here, and the operator’s failed one-month redressal duty is part of your case.
• The cluster page how to complain about an Indian gaming or payment problem walks every external channel step-by-step.

If the officer ignores a registered gaming provider’s recovery → Grievance Appellate Committee → Authority

Under PROGA 2026, if a registered provider’s internal grievance mechanism fails:

• Appeal to the Grievance Appellate Committee within 30 days; it endeavours to resolve within 30 days.
• If still unsatisfied, approach the Online Gaming Authority of India within 30 days of the committee’s order, with a final appeal to the Secretary, MeitY.

If the operator publishes no officer at all → treat the absence as non-compliance

A missing grievance officer is itself a violation of whichever rule applies. Don’t waste days hunting a ghost:

• Go straight to the external authorities — your bank’s nodal officer for any rail leg, NCH 1915 for the service deficiency, the RBI Ombudsman for the payment failure.
• For an unlicensed or suspicious entity, flag it on the RBI Sachet portal, and if any fraud is involved, call cybercrime 1930 and file at cybercrime.gov.in.
• An account that’s been frozen rather than merely unpaid follows a different path — the account frozen / blocked fix covers the AML, multi-account, and lien cases specifically.

The “no response” rule in one line: silence from the officer is the start of the next rung, not the end of the road. Send it up by category — rail failure → bank nodal officer → RBI Ombudsman after 30 days; owed balance → NCH 1915 → e-daakhil; registered gaming provider → Grievance Appellate Committee → Authority; no officer at all → straight to external authorities.

The grievance-channel reference block

Keep this handy; it’s the whole grievance map in one place. Use the door that matches your problem type.

Order of doors, in one line: support ticket → operator’s grievance/nodal officer → payment aggregator’s nodal officer / your bank’s nodal officer → RBI Ombudsman, with NCH 1915 in parallel for an app-side service deficiency and cybercrime 1930 the instant fraud is involved.

The escalation matrix inside one operator: Level 1, 2, 3

A compliant operator doesn’t have one grievance contact — it has a tiered escalation matrix, and the RBI Payment Aggregator Directions explicitly require payment companies to publish one. Knowing the tiers stops you wasting the highest-leverage contact on a problem the first tier should have solved, and stops you accepting a first-tier brush-off as final.

A typical three-level matrix looks like this:

• Level 1 — Customer support / help centre. The front door: in-app chat, support email, the ticketing system. No statutory deadline of its own, but it’s where you start and where you get a ticket ID. Most simple issues die here, resolved, and never need to climb.
• Level 2 — Grievance officer. The named officer under the IT Rules or the e-commerce Rules. This is where the statutory clock lives (24 or 48 hours to acknowledge). You escalate here when Level 1 stalls, fobs you off, or blows past its own stated window.
• Level 3 — Nodal officer / principal nodal officer. The senior single-point-of-contact, especially on the payments side, who answers to the regulator. For a bank, the principal nodal officer sits at the head office and coordinates with RBI. This is the last internal rung before the external authorities (the RBI Ombudsman, the consumer forum).

The reason this matters tactically: each climb up the matrix should be triggered by a specific failure, and you should name that failure when you climb. You don’t go to the nodal officer because you’re impatient; you go because “Level 1 gave no resolution in [N] days” and “the Level 2 grievance officer failed to acknowledge within the statutory 24 hours.” Naming the prior tier’s failure does two things: it shows the senior officer you followed the process (so they can’t bounce you back down), and it stacks the breaches you’ll later present to the Ombudsman. A complaint that climbed cleanly through three named tiers, each with a dated failure, is a far stronger Ombudsman filing than one that jumped straight to the top.

One more practical note on the matrix: when an operator publishes the matrix but not the individual officers’ emails, the matrix page itself usually carries a generic grievance alias (grievance@, nodal@) plus the timeline for each level. Use that alias and reference the level you’re invoking — “escalating to Level 2 (Grievance Officer) per your published escalation matrix” — so there’s no ambiguity about which clock you’ve started.

A worked walkthrough: a ₹6,000 stuck recovery, day by day

To make the whole sequence concrete, here is how the grievance route plays out over time for a representative case — described in the third person from the rules, not as anyone’s personal payout test. Assume a player owed ₹6,000 from a discontinued cash app that keeps showing “processing” with no UTR.

Day 0. The player screenshots the withdrawal screen, the ₹6,000 amount, the timestamp, and the “processing” status. No UTR has appeared, so there’s nothing to trace yet — but the wallet balance before and after is captured. An in-app support ticket goes in, and the player records the ticket ID and the date. Total time: ten minutes, and the front-door attempt is now documented.

Day 2. Support has replied with a canned “your request is being processed, please wait.” That’s not a resolution. The player opens the app’s Terms and Ctrl+Fs for “grievance officer,” finds a grievance@ alias and a line citing the IT Rules, and sends Letter A — a formal grievance under Rule 3(2), referencing the ticket ID, demanding acknowledgment within 24 hours and resolution within 15 days, and a written reason for the hold. The sent email is the provable receipt date that anchors the 30-day clock.

Day 4. No acknowledgment has arrived, which is now a breach of the 24-hour duty. The player sends Letter D, the missed-deadline follow-up, noting the non-acknowledgment in writing. Because the app is discontinued and the money never reached a rail, there’s no bank dispute to run yet — the balance is still sitting inside the operator.

Day 12. The grievance officer finally replies, asking the player to “re-verify KYC.” The player re-submits clean KYC matching the bank name exactly and emails to confirm, in writing, that KYC is now complete and the 15-day resolution clock continues to run.

Day 18. Still no payout. The player sends a final-notice grievance restating every fact, the ticket ID, the two statutory breaches (missed 24-hour acknowledgment, missed 15-day resolution), and the exact next steps. In parallel, the player files with the National Consumer Helpline 1915, framing the withheld ₹6,000 as a service deficiency.

Day 32. With 30 days elapsed since the operator received the formal grievance and no satisfactory resolution, the player is now eligible for the RBI Ombudsman if a regulated payment entity is in the chain — and for the consumer forum via e-daakhil regardless. The receipt date from Day 2 is what makes this eligibility clean. The case is now a documented, multi-breach filing rather than a one-line “they didn’t pay me,” which is exactly the difference that gets it heard.

The lesson the timeline teaches: the grievance officer rung rarely resolves on the first email, but it builds the record that the later rungs need. Every dated breach is a brick. By Day 32 the player isn’t begging — they’re presenting a file.

Common mistakes that kill a grievance (and the fix for each)

The grievance-officer route fails for predictable, avoidable reasons. Here are the ten that sink most cases, each with the one fix that saves it.

1. Sending it to “support,” not the officer. A message to the help chat has no statutory clock. Fix: address the named grievance/nodal officer by title on the published grievance email.
2. Never using the word “grievance.” If you don’t frame it as a grievance and cite a rule, the recipient treats it as a routine query. Fix: open with “I am submitting a formal grievance under [Rule].”
3. No provable receipt date. Without a record of when the officer received it, you can’t start the 30-day Ombudsman clock. Fix: send to the published email (not ephemeral chat) and keep the sent record.
4. Vague demand. “Please help” invites a vague non-answer. Fix: state the exact amount, the relief, and (if a rail failed) the ₹100/day claim.
5. No UTR on a money complaint. You can’t trace a “paid” payout without it. Fix: capture the UTR on Day 0 from your UPI app’s transaction history.
6. Skipping the support ticket. Some operators bounce a grievance back asking you to “use support first.” Fix: open the ticket first, get the ID, then escalate citing it.
7. Citing the wrong law. Demanding a 24-hour acknowledgment under the e-commerce Rules (which give 48) hands the operator an easy deflection. Fix: match the clock to the rule — 24h for IT Rules, 48h for e-commerce.
8. Going to the RBI Ombudsman on Day 1. They’ll reject it for skipping the 30-day rule. Fix: give the entity its 30 days, then file with the receipt date as proof.
9. Accepting verbal answers. A phone refusal leaves no evidence for the appeal. Fix: email to “confirm in writing what was discussed.”
10. Depositing to “unlock” the payout. No legal operator requires a deposit to withdraw, and post-PROGA a new deposit into a money game is illegal. Fix: never add money — document and escalate instead.

The pattern behind all ten: a grievance only works as a legal instrument, not a customer-service one. Address the officer, cite the rule, date the receipt, demand specifics in writing, and respect the 30-day gate. Get those five right and the rest is paperwork.

Is it a delay or a dead end? Red flags that change your strategy

Most stuck payouts on a regulated operator are delays the grievance route can fix. But some operators are unlicensed, offshore, or outright clones, and against those the officer route has limited teeth. Use these flags to decide how hard to fight.

• No grievance officer is published anywhere. A compliant operator must publish one. Its absence signals you’re not on a regulated platform, and your statutory leverage shrinks — pivot to your bank’s nodal officer and the external authorities.
• The “officer” email bounces or never replies, and the app has no Indian address. A genuine intermediary has a resident officer and a physical Indian contact. A foreign-only footprint with no reachable officer is a warning to lower your recovery expectations for any balance held inside the app.
• You’re pushed to a “customer care number” from a random website or YouTube comment. These are overwhelmingly scams that phish your OTP and UPI PIN. Real operators route support in-app, and many have no public phone helpline at all. Report fake numbers to 1930 / cybercrime.gov.in.
• “Deposit ₹X to release your withdrawal.” No legal operator requires a deposit to withdraw, and post-PROGA the deposit itself is illegal. This is the clearest theft pattern — stop, document, report.
• The app vanished and pending payouts went dark. A legitimate PROGA wind-down stops cash games but should still let you withdraw an existing balance. A disappeared operator is a worse problem — pursue any rail loss through your bank, but lower expectations on balance held inside.

If two or more are true, the realistic read is harsh: pursue the bank/rail dispute and the cybercrime report for any rail loss, but lower your expectation of recovering balance held inside an unlicensed operator — and never feed it another rupee.

Where to get real, official help

There is no “faster app” or magic escalation that beats the official grievance chain, used in order with the paper trail intact. After PROGA 2025 (Rules in force 1 May 2026), moving to another online money-gaming service isn’t a legal option in India anyway. What actually recovers money is the ladder on this page, climbed in sequence:

• Operator’s grievance/nodal officer first. A formal grievance citing the right rule, with a provable receipt date.
• The payment aggregator’s nodal officer or your bank’s nodal officer for any rail leg, with the UTR and the ₹100/day TAT claim under the RBI failed-transaction circular.
• RBI Ombudsman (RB-IOS) if a regulated entity doesn’t resolve within 30 days — file free on the RBI CMS portal.
• National Consumer Helpline 1915 and, for fraud, cybercrime 1930 / cybercrime.gov.in plus the RBI Sachet portal.

Editor’s verdict. The grievance officer is the rung that converts a brush-off into a breach — and a breach is what the Ombudsman and the consumer forum act on. A rail failure (money left your bank, never reached you) is the recoverable kind, because the rules force a refund and your bank’s nodal officer is always reachable. A balance held inside a discontinued or unlicensed operator is harder: pursue it through the chain, but never deposit more “to unlock” it. Post-PROGA, that deposit is both throwing good money after bad and illegal.

Related fixes (go deeper on your exact case)

This page owns the grievance/nodal officer mechanism. For the surrounding cases, these go step-by-step:

• The full escalation map for any RMG support problem → RMG customer-care escalation — the hub this page sits under.
• A stuck Teen Patti / 3 Patti withdrawal → 3 Patti withdrawal fix — the four payout gates, the time table, and per-app UTR menu paths.
• Every official complaint channel → how to complain about an Indian gaming or payment problem — NCH 1915, cybercrime 1930, e-daakhil, and how to file each.
• A frozen or blocked account → account frozen / blocked fix — the AML, multi-account, chargeback, and lien cases.

FAQ

1. What is a grievance officer for an online gaming app? A grievance officer is the named person an Indian app must appoint by law to handle user complaints. Under the IT Rules 2021 (Rule 3(2)), that officer must acknowledge a complaint within 24 hours and resolve it within 15 days, and the app must publish the officer’s name and contact on its platform. It’s a statutory post, not a customer-service tier — its failure to meet the deadline is itself a breach you can escalate.

2. What’s the difference between a grievance officer and a nodal officer? They overlap. Grievance officer is the term in the IT Rules and the e-commerce Rules; nodal officer is the payments-world term for the single point of contact RBI requires. In practice the RBI Payment Aggregator Directions make a payment company display a nodal officer, while a gaming app displays a grievance officer under the IT Rules. For a money complaint, the payment aggregator’s nodal officer often has more weight, because that company answers to RBI.

3. How fast must a grievance officer respond by law? It depends on the law. Under the IT Rules 2021, 24 hours to acknowledge and 15 days to resolve. Under the Consumer Protection (E-Commerce) Rules 2020, 48 hours to acknowledge and one month to redress. A payment aggregator’s timeline follows its published policy and the RBI turnaround-time rules. Match your demand to the right clock — citing the wrong one hands the operator an easy deflection.

4. What is the difference between a support ticket and a formal grievance? A support ticket goes to first-line help and carries no legal deadline — the company can take as long as it likes. A formal grievance is addressed to the named grievance/nodal officer, uses the word “grievance,” cites the rule, and starts a statutory clock (24 or 48 hours to acknowledge). Only the grievance builds toward the RBI Ombudsman or a consumer forum, because only the grievance creates a breach when ignored.

5. How do I find an operator’s grievance or nodal officer? Start with the app’s Terms & Conditions and Ctrl+F for “grievance officer” and “nodal officer.” Check the website footer for a “Grievance Redressal” page, and look inside the app under Settings → Legal / Help → Grievance. For a money complaint, find the payment aggregator’s name from your bank narration or the UTR, then look up its nodal officer. The law requires these details to be published, so a compliant operator always has them somewhere.

6. What legal rules force an app to have a grievance officer? Three main ones. The IT Rules 2021, Rule 3(2) (intermediaries, 24h/15d); the Consumer Protection (E-Commerce) Rules 2020, Rule 4 (e-commerce entities, 48h/1mo); and the RBI Payment Aggregator Directions (payment companies, nodal officer displayed). For gaming specifically, the PROGA 2026 Rules add a Grievance Appellate Committee tier.

7. What should a grievance-officer letter actually contain? Seven parts: address the officer by title; state it’s a formal grievance and cite the rule; give dated, numbered facts (amount, date, status, UTR, mobile, KYC); reference the prior ticket; state a specific demand (the amount, plus ₹100/day if a rail failed); set the statutory deadline and demand a written reason; and state the next rung you’ll escalate to. Numbers and a cited rule move an officer; an angry paragraph doesn’t.

8. What if the grievance officer never responds? Silence is the trigger for the next rung. For a rail failure, escalate to your bank’s nodal officer, then file with the RBI Ombudsman after 30 days of no reply. For an owed balance, file with the National Consumer Helpline 1915, then a consumer forum via e-daakhil. For a registered gaming provider, appeal to the PROGA Grievance Appellate Committee within 30 days. The non-response itself becomes part of your case.

9. When can I escalate to the RBI Ombudsman? After 30 days from when the regulated entity received your complaint with no reply, or an unsatisfactory one, per the RB-IOS 2021 FAQ. The scheme covers banks, NBFCs and Payment System Participants, so your bank and the payment aggregator are both in scope, and redress is free. That 30-day gate is why the date the officer received your grievance is the single most important fact to capture.

10. Does the grievance officer route work for a debited-but-not-credited UPI payout? Yes, and it’s the strongest case. Address the payment aggregator’s nodal officer (and your bank’s), cite the RBI failed-transaction circular DPSS.CO.PD No.629 (20 Sep 2019), which forces a T+1 auto-reversal and ₹100/day compensation after that. The 3 Patti withdrawal fix covers where each UPI app hides the UTR you’ll need.

11. Can I cite more than one law in a single grievance? Yes, and the strongest letters do. One operator can be an intermediary (IT Rules, 24h), an e-commerce entity (e-commerce Rules, 48h), and the money leg can be an RBI payment-system matter (30-day Ombudsman backstop) — all at once. Citing all the duties that apply makes the grievance much harder to ignore than a generic “please help,” because each cited rule is a separate consequence the operator now faces.

12. Do these rules apply to foreign or offshore gaming operators? The Consumer Protection (E-Commerce) Rules 2020 apply even to foreign e-commerce entities offering services to Indian consumers, so an offshore operator isn’t automatically beyond reach. The practical limit is enforcement: a faceless offshore clone that publishes no officer and ignores everything is hard to compel. For any money that touched a rail, though, your bank’s nodal officer is always reachable, which is why a rail loss is the more recoverable kind.

13. Can I still escalate to a grievance officer at a discontinued app like RummyCircle? For a balance recovery, yes. Cash games are gone under PROGA 2025, but operators and banks kept processing withdrawals so users could recover existing balances. Send a formal grievance for the recovery, expect 30% TDS on net winnings in the payout, and never deposit again — a new deposit into a money game is now illegal. If a registered provider runs the wind-down, the PROGA Grievance Appellate Committee tier applies.

14. Is it worth contacting a grievance officer at all, or should I go straight to the Ombudsman? Contact the officer first — the Ombudsman rejects complaints that skip the 30-day rule. The grievance officer rung is what creates your eligibility: you need a provable grievance, a receipt date, and 30 days of no resolution before the Ombudsman will hear you. Skipping the officer doesn’t speed things up; it gets you bounced back to do the rung you skipped.

15. What if the operator publishes no grievance officer at all? That absence is itself a violation of whichever rule applies. Don’t hunt a ghost — go straight to the external authorities: your bank’s nodal officer for any rail leg, the National Consumer Helpline 1915 for the service deficiency, and the RBI Ombudsman for the payment failure. Flag an unlicensed entity on the RBI Sachet portal, and report any fraud to cybercrime 1930 and cybercrime.gov.in.

Sources & method. The grievance-officer duties, timelines, and escalation steps on this page are built from primary legal sources, not personal experience. Key references: the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 (Rule 3(2): 24-hour acknowledgment, 15-day resolution); the Consumer Protection (E-Commerce) Rules, 2020 (Rule 4: 48-hour acknowledgment, one-month redressal); the RBI Payment Aggregator Directions and the 2025 master directions analysis (nodal officer displayed, escalation matrix, TAT compliance); 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); the RBI Integrated Ombudsman Scheme 2021 and cms.rbi.org.in (30-day eligibility, free redress); the Promotion and Regulation of Online Gaming Rules, 2026 and the Mondaq summary (Grievance Appellate Committee, Online Gaming Authority, 30-day tiers); the Promotion and Regulation of Online Gaming Act, 2025; cybercrime reporting at cybercrime.gov.in / helpline 1930; the RBI Sachet portal; and the National Consumer Helpline 1915. This page is information, not legal advice — verify each step against your operator’s current Terms and the latest version of each Rule.