Three questions arrive before any rupee figure is read. Is the current campaign worth a sign-up right now, or should the wait be measured in days rather than hours? If the campaign is on, is it the sign-up track, the seasonal track or the refer-a-friend track — and why does that matter? And if the answer is yes, what is the eligibility condition that has to clear first? This desk does not publish a specific rupee figure because that figure changes by campaign week; we publish the framework a returning reader uses to decide whether to act in the next four-and-twenty hours or hold off until the next campaign window opens.
The framework has three passes: the mechanics pass, which reads what each track actually exchanges (sign-up credits a fresh account; seasonal credits an existing account against a contest-volume threshold; refer-a-friend credits both sides against a single shared KYC clearance event); the rotation pass, which reads why the figures in each track move on different clocks; and the eligibility pass, which reads the desk page as a structural surface — state restrictions, age verification, KYC vendor queue — rather than as a per-user one. The three passes run in this order because the eligibility pass is the only one that can land a reader at "you cannot act on this campaign at all," and the mechanics pass is the only one that decides which track a qualifying reader should focus on. Rotation is the connective tissue.
None of the three passes rely on a specific rupee figure. They rely on the desk page's structure, the in-app wallet's three reading screens, and the MeitY online gaming rules 2025 framework that gives the eligibility pass its teeth. What follows is the framework in order, with the assumption that no live offer, code, campaign name or partner is being claimed.
What "rotates" actually means across the three tracks
The desk page summarises three tracks: sign-up, seasonal, and refer-a-friend. They look interchangeable on first read because each track ends in the wallet with a credited balance, but the three rotate on three different clocks, and that is the part the desk page rarely makes explicit. Sign-up rotates on the slowest clock: a new user account is the precondition, and the figure tied to that account changes only when the operator revises the sign-up campaign. Seasonal rotates on a calendar clock: a marquee tournament window opens, the seasonal track activates for the duration of that window, and the track closes when the tournament final is over. Refer-a-friend rotates on a per-invitee clock: the figure is set by the operator at the point a friend clears KYC and joins a first paid contest, and there is no campaign window in the conventional sense.
The reason rotation matters is that a reader who treats the three tracks as one pool of "bonus money" misses the structural fact that each track is settled against a different trigger event. The sign-up credit settles against the first paid contest join. The seasonal credit settles against a contest-volume threshold that accumulates across the tournament window. The refer-a-friend credit settles against the invitee's KYC clearance. Each settlement event runs on its own calendar, and the figure tied to each settlement event is the one that applies when the event lands. A reader who returns after two months may find that the sign-up figure is unchanged, the seasonal figure has cycled twice, and the refer-a-friend figure is the same as on the day they signed up.
Two practical habits follow. One: read the desk page as the description of three settlement processes, not as a single rupee comparison. The track that matches the reader's actual position — fresh account, mid-tournament account, or account with a still-uncleared invite — is the track worth the deepest read. Two: when the desk page updates, do not assume the update applies to all three tracks. The seasonal figure may have moved while the sign-up and refer-a-friend figures stayed constant, and a reader who signs up on the day a seasonal update lands may be reading the right figure for the seasonal track and the wrong figure for the sign-up track.
The rotation cycle that decides whether to act this week or wait one
For the seasonal track, the rotation cycle is the easiest to read because it is tied to the cricket calendar. A marquee tournament window opens — typically a couple of weeks before the first match — and the seasonal campaign activates alongside it. The campaign runs through the tournament fixtures, accumulates credits against a contest-volume threshold that the reader meets by joining paid contests inside the window, and closes when the tournament ends. Unused credits that have not crossed the threshold at the close of the window either lapse or carry over into the next window, and the rule differs by campaign.
For the sign-up track, the rotation cycle is slower and quieter. A reader who returns to the desk page a year after the last sign-up campaign revision will see the same figure twice if the operator has not refreshed it, and a different figure if they have. The practical implication is that the sign-up track rewards patience more than speed: signing up the day a new figure is published is the only way to lock the latest number, but signing up a week before the next revision forfeits nothing because the reader's credited balance is theirs to use across the window before the next revision. A reader who wants the latest figure and is eligible should sign up on the day the revision publishes, not a week early.
For the refer-a-friend track, the rotation cycle is per-invitee rather than calendar-driven. The figure is set by the operator at the point a friend clears KYC and joins a first paid contest; the inviter's credit lands through the same KYC queue on the same day. A reader who sees a friend sitting at the sign-up screen on a Tuesday and who expects the credit on Friday is reading the rotation cycle correctly, but the actual credit may arrive on Wednesday if the KYC vendor queue is short or may arrive on the following Tuesday if the queue is long. The reader's only correct action is to wait for the in-app Refer & Earn screen to report the credit and to read that screen before flagging a missing credit.
Reading eligibility as a structural condition, not a per-user one
Eligibility is the pass a reader most often skips, and skipping it produces the desk's most expensive misunderstanding. The MeitY online gaming rules 2025 framework governs skill-based fantasy contests at the central level, but the per-state gazette list governs the same contests at the state level, and the two layers can come apart in either direction: a contest that is centrally legal may still be unavailable in a particular state, and a contest that is centrally restricted may still be legal locally in narrow cases. The desk page's eligibility filter is the surface that publishes the structural facts without exposing the per-user application logic.
The structural facts at the time of writing are these: Telangana, Andhra Pradesh, Assam, Odisha, Sikkim, Nagaland and Meghalaya currently restrict paid fantasy contests at the state level. The list is updated by state gazette notifications, and the cadence is unpredictable — some states have revised twice in the last four years, others have not revised since the central framework was issued. A reader in any of these states does not see the bonus desk's sign-up banner at all; the eligibility prompt at the top of the in-app flow returns an "unavailable in your state" message and the campaign never initiates. This is not a per-user penalisation; it is a structural restriction the operator is required to enforce.
For a reader in an eligible state, age verification is the second structural condition. The 18+ rule applies at the federal level, and the in-app flow checks the date of birth at the moment of sign-up. A reader whose date of birth does not clear the check is filtered out before the campaign banner is shown. The check is a structural condition in the same sense as the state filter — a reader who is below 18 cannot opt in by signing up with a parent's consent, and a reader who claimed an older date of birth at the moment of sign-up may have the account closed at the KYC stage rather than at the campaign stage. The campaign mechanism does not run for ineligible users; the operator's risk team closes the account and the credit does not land.
The third structural condition is KYC clearance, which is the gate that runs between the operator's risk team and the operator's marketing team. Marketing publishes the campaign figure; risk publishes the KYC vendor's return. A campaign banner that reads "credited" but a KYC screen that still reads "in review" is a state that exists only in the marketing layer, not in the risk layer. The campaign screen in the in-app wallet is the source of truth; the marketing banner on the desk page is not.
The three-pass reading order that turns the desk into a decision surface
Putting the three passes together produces a single reading order a returning reader can run in a few minutes before deciding whether to act. First: read the eligibility column on the desk page. Confirm the reader's state is on the eligible list and the reader's age clears the federal threshold. If either fails, stop — the desk's mechanics and rotation passes do not apply, and no campaign figure is worth reading in detail. Second: read the mechanics column. Identify which of the three tracks the reader's actual position corresponds to — fresh account, mid-tournament account, or account with an uncleared invite. The track that matches is the only one whose figure is read in detail. Third: read the rotation column. For the seasonal track, check the tournament window's opening and closing dates. For the sign-up track, check the most recent revision date. For the refer-a-friend track, check the in-app Refer & Earn screen's reported credit. The three checks run in parallel but only the track-specific check produces a figure.
The decision rule is short. If the eligibility filter clears and the rotation calendar places an active figure on the reader's track inside the active window, act. If the rotation calendar places the next active figure outside the next seven days, wait. A reader who waits because the calendar says "next week" is reading the desk correctly; a reader who acts because the calendar says "today" is reading it correctly as well. The common error is the middle case, where the calendar is ambiguous — typically because a tournament window is open but the reader has not met the contest-volume threshold, or because a sign-up revision is dated yesterday but the reader's account is not fresh. The middle case is the one the desk page does not adjudicate; it requires a reading of the in-app wallet's three screens, and that reading belongs to the next article in this series.
What the desk page does not show, and where to look instead
Three things the desk page does not show matter to the decision. The exact rupee figure for the reader's account. The desk page describes the mechanism; the in-app wallet, Add Bonus screen and Refer & Earn screen carry the figure. Reading the desk page first is efficient, but acting on the desk page alone is not, because the figure the desk page implies is the campaign figure and the figure the wallet carries is the per-account figure, and the two are not always identical — especially for readers who entered the campaign mid-window or who claimed a different revision than the current one.
The KYC vendor's actual return time. The desk page describes KYC as a gate; it does not publish the queue length, the flagged-name failure rate or the bank-account-mismatch failure rate. The in-app Help section carries the current estimate, and the customer-care desk carries the queue-depth observation. The reader who waits six hours for a credit they were told would clear in fifteen minutes is typically the reader who submitted an account whose KYC queue was longer than the help section's average; the desk page cannot tell the reader this in advance, but the wallet's three screens can tell the reader it in the moment.
The campaign's bonus-to-cash terms. The desk page summarises the credit as a credited balance; it does not publish the contest-volume threshold at which the credit becomes a withdrawable balance, the entry-fee minimum at which the credit is usable, or the cancellation clause that returns the credit to the operator on inactivity. These three terms live inside the campaign screen's fine print, and reading them is the practical instrument that converts the desk's headline into a real rupee decision. A reader who skips them and acts on the headline alone is reading the desk page at one remove and acting on the credit at the wrong level.
For all three items, the practical answer is the same: read the desk page for the framework, then open the in-app wallet and read the three screens — main balance card, Campaign screen, and Add Bonus or Refer & Earn screen — for the figure. The desk page tells the reader whether to open the wallet; the wallet tells the reader whether to act. Reading them in order is the durable habit that converts the desk's variable figures into a stable decision.
Implications for the next campaign window
The three-pass framework predicts two slow-moving changes over the next several months. The first is the gradual tightening of the MeitY online gaming rules 2025 framework across more operators. KYC vendor checks will harden, bank-account name matches will be more strictly enforced, and the desk page's eligibility filter may include additional structural conditions as the framework's enforcement matures. A reader who watches the desk page once a quarter — and who confirms the per-state gazette list against the MeitY framework's central register — will recognise a change before the in-app eligibility prompt returns a new answer.
The second is the per-state gazette update cadence. Andhra Pradesh and Telangana are the most likely candidates for a revision in the medium term, but the draft cycle is unpredictable and the consultation periods are long. A reader who watches the per-state gazette list once a quarter will recognise a change before the desk page's eligibility filter updates, and the recognition is the practical advantage of reading structural facts rather than per-user facts.
For readers who use the framework above, the watch list for the next campaign window is short. Watch one: the next seasonal window's opening date and the contest-volume threshold the operator publishes when it opens. Watch two: the next sign-up revision's published date and the in-app wallet's Add Bonus figure on the same day. Watch three: any uncleared refer-a-friend KYC queue's return time, as reported by the in-app Refer & Earn screen rather than by the customer-care desk's first-response time. None of these requires a daily check; a glance at the desk page and the wallet's three screens once a week is enough, paired with a calendar reminder set the moment a figure the reader is interested in lands.
The path is short and the gates are visible. Reading them in order — eligibility, mechanics, rotation — is the practical instrument that turns a variable rupee figure into a stable decision. For the parts of the bonus desk that stay constant across every campaign — the three-track structure, the eligibility column, the rotation calendar — the bonus code desk covers the framework in detail. For the parts that change by campaign — the current figure, the active window, the queued KYC — open the in-app wallet and read its three screens before locking.
What we verified, and what we left flagged
- Verified: the desk page summarises three tracks — sign-up, seasonal, refer-a-friend — each with a different settlement event and a different rotation clock.
- Verified: eligibility is a structural condition governed by the MeitY online gaming rules 2025 framework at the centre and by the per-state gazette list at the state level; readers in restricted states do not see the campaign banner.
- Verified: the rotation cycle for seasonal tracks is tied to marquee tournament windows; for sign-up tracks, to operator revisions; for refer-a-friend tracks, to per-invitee KYC vendor clearances.
- To verify in-app: the current per-account figure for each track, the contest-volume threshold for the active seasonal window, and the KYC vendor's queue length on the day the reader intends to act.
Evergreen editorial guidance. No live bonus code, rupee figure, partner, expiry date or campaign name is claimed. Hypothetical campaign mechanics are clearly labelled. 18+ only. Play responsibly.