About and contact · state eligibility

Is real-money rummy legal in your state: the desk's state-by-state read against the MeitY/PROG Act 2025

A reference for the state-by-state eligibility read. The desk reads the MeitY/PROG Act 2025 notice, the state high-court rulings, and the operator's geolocation block list, and refuses to publish a single national answer because the eligibility decision is state-by-state.

Reading time · 9 min Last reviewed · 2026-08-10 Source-led

Section 01 · Verified facts

01

Why the desk refuses to publish a national answer

The betinia editorial desk refuses to publish a single national answer to the question of whether real-money rummy is legal. The MeitY/PROG Act 2025 notice frames rummy as a skill game, but the state high-court rulings and the state government notifications vary, and the operator's geolocation block list is the only enforceable layer.

The desk reads three sources in order: the MeitY/PROG Act 2025 notice, the state high-court rulings on rummy (Tamil Nadu, Karnataka, Kerala, Andhra Pradesh, Telangana), and the operator's geolocation block list. The desk refuses to publish a per-state verdict because the operator's block list changes faster than the editorial publication cycle; the verified answer is the operator's geolocation check at sign-in.

Detail block

Three sources the desk reads in order

  1. MeitY/PROG Act 2025 — the central notice framing rummy as a skill game and removing the prior omnibus "gaming" classification.
  2. State high-court rulings — the rulings on rummy in Tamil Nadu, Karnataka, Kerala, Andhra Pradesh and Telangana.
  3. Operator geolocation block list — the operator's enforced block at sign-in; the verified answer for the reader's state.

Reader checklist

Five items the reader runs before signing in

  • Statethe reader's state of residence and the operator's block list
  • High-court rulingthe state high-court ruling on rummy
  • Operator geolocationthe operator's geolocation check at sign-in
  • Agethe reader is 18 or older per the MeitY/PROG Act 2025
  • Editorialthe editorial recommendation is independent of the operator

State-by-state deep read

How the desk reads each state's published position on real-money rummy

The desk reads each state's published position against three sources: the state government's official gaming or home-department notice, the MeitY/PROG Act 2025 framework as the federal umbrella, and the operator's own state-eligibility block. A state's published position is treated as canonical only when the three sources agree; a state whose official notice contradicts the operator's published block is flagged in the desk's review shelf with a dated changelog row.

The desk refuses to publish a "yes/no" line per state. The desk's standing rule is that the state's published position is a moving target: a state that publishes a permissive position can publish a restrictive update with a 30-day notice, and a reader who treats the desk's last reading as a permanent line will read past a change. The desk's changelog rows are dated, not versioned, so a reader can read across the row without depending on the desk's internal schema.

The desk's verification step before a deposit is the same for every state: confirm the operator's state-eligibility block on the lobby page, confirm the operator publishes a grievance officer contact, and confirm the operator's geolocation check at sign-in matches the reader's location. A reader who cannot confirm all three should not deposit at the operator, regardless of the state's published position.

The desk also publishes a non-rummy position: most states that allow real-money rummy do not allow real-money fantasy sports under the same notice, and vice versa. The MeitY/PROG Act 2025 framework covers both, but the state-by-state blocks differ. The desk's walks through the per-state position against the framework in the longer form.

For an adult reader who has not yet confirmed the state block on the operator they intend to use, the desk's standing recommendation is a free-practice table at the same operator before any real-money deposit. The state-eligibility block on the practice table is the same block the cash table reads; the difference is the stake unit, which is zero on a practice table.

Continue reading

Three pages the desk suggests after this read

Hub · Safety

Safety and KYC explainer

The canonical safety explainer with the MeitY/PROG Act 2025 citation and RBI payment-aggregator direction.

Continue →
Hub · Owner

Owner and operator record

The owner and operator record the desk cites for the geolocation block list.

Continue →
Hub · Responsible play

Responsible play toolkit

Limit-setting, deposit caps and the verified support channels.

Continue →

Detail block · state-by-state breakdown

  1. Permitted federal — states without a state-specific override; the operator's lobby surfaces the state as permitted at sign-in.
  2. Permitted state-licensed — states with a state-specific licence requirement; the operator's lobby surfaces the state as permitted only where the operator holds the state licence.
  3. Restricted federal — states with a federal restriction but no state-level block; the operator's lobby surfaces the state as restricted at sign-in.
  4. Restricted state-licensed — states with a state-specific licence ceiling; the operator's lobby surfaces the state as restricted where the operator does not hold the state licence.
  5. Blocked state — states with an explicit state-level block; the operator's lobby surfaces a hard stop before deposit.
  6. Federal territory — federal territories that follow the federal rule; the operator's lobby surfaces the territory as permitted or restricted per the federal rule.

Section 02 · How the desk verifies a state-eligibility decision

02

The desk treats a state-eligibility decision as a four-row check. The first row is the operator's published state table; the desk reads the table against the most recent MeitY notice and the most recent state-block update. The second row is the operator's licence register; the desk confirms that the licence number on the register matches the licence number on the operator's state table.

The third row is the operator's deposit rail list; the desk confirms that the rail the reader intends to use is listed as available in the reader's state and not just listed at the federal level. The fourth row is the operator's responsible-play surface; the desk confirms that the responsible-play block is reachable from the lobby and not buried in a help-center article.

The desk's standing rule is that no state is recorded as permitted without all four rows passing. The desk refuses to combine the four rows into a single number; the operator is recorded as permitted in a state when all four pass and as friction-observed when any one fails. The state-by-state check is re-run on every cadence and the changelog row records the date, the rows the desk ran, and the verdict chip issued at the close of the check.

Reader questions

Is the operator's state table the same as the MeitY notice?

No. The MeitY notice sets the federal rule for online real-money gaming; the operator's state table is the operator's application of the federal rule plus any state-level overrides. Where the two diverge, the operator's state table is the source the reader must verify against at sign-in, and the desk records the operator's state table as the canonical row.

What does the desk record when the operator's state table is older than twelve months?

The desk records the operator as friction-observed against the state-table row and stamps the verdict chip with the date of the check. The desk asks the reader to verify the state table against the operator's most recent update and to escalate to the operator's grievance officer where the table remains older than twelve months across two separate checks.

Can a reader join from a federal territory?

Yes. The federal territories follow the federal rule; the desk confirms the operator's federal territory list and asks the reader to verify against the operator's most recent territory list. The desk records the territory as permitted where the operator lists the territory as permitted and as restricted where the operator lists the territory as restricted.

What happens when a reader moves between states?

The operator's state table is enforced at KYC. Where the reader moves from a permitted state to a restricted state, the operator re-runs the KYC step and may refuse the login if the reader's new state is not on the operator's state table. The desk asks the reader to confirm the operator's state table before logging in from a new state.

\n
\n
\n
\n
\n

Reading cadence

\n \n
\n
\n

The desk re-issues the state-eligibility surface on three cadences. The first cadence is per quarter: the desk reads the operator's state table against the four-row reference and re-issues the verdict chip on the operator's state table. The second cadence is per half: the desk reads the operator's state table against the most recent MeitY notice and the most recent state-block update, and re-issues the verdict chip on the operator's state table.

\n

The third cadence is per incident: where a reader reports a state-eligibility event that crosses the desk's incident threshold, the desk verifies the event against the operator's published record and re-issues the verdict chip only when the operator's record changes. The desk refuses to combine the three cadences into a single "last updated" line; the changelog records the date, the row the desk re-scored, and the verdict chip issued at the close of the check.

\n

For the per-row verification, the desk asks the reader to confirm the operator's state table against the four-row reference and to refuse any operator that lists a reader's state as permitted but does not list the rail the reader intends to use. The desk's standing rule is that no operator passes the state-eligibility criterion without all four rows being visible in-app; the desk records a buried row as a friction observation and stamps the verdict chip with the date of the check.

\n
\n
\n