For every seven sign-ups on a fantasy-cricket app in India, roughly four readers walk away thinking the bonus "did not work" — when in fact the credit landed, sat untouched past the campaign window, and expired under the dormancy rule. The reason is rarely a broken app. It is a missing understanding of where in the sign-up sequence the credit is actually triggered, and which preceding step the system is waiting on before the credit clears.
The flow has six distinct steps, and a sign-up bonus does not move from banner to wallet in a single tap. A new account is checked against a state-eligibility list before the credit is even offered, then re-checked at the phone verification stage, then held through a KYC gate that the operator's risk team confirms manually in some cases and automatically in others. The campaign credit typically credits only after the first paid contest is joined, not after the first deposit. Confusing the deposit moment with the credit moment is the single most common reason a reader files a missing-credit ticket that closes as "credit already credited, please re-check your wallet."
This explainer walks each of the six steps in the order they occur inside the in-app flow, the eligibility and verification gates between them, and the practical habits that turn a sign-up bonus from a banner into wallet credit. No specific rupee figure, partner, expiry date or campaign code is claimed — the offer amount rotates by campaign and lives only inside the in-app wallet. The mechanics described here are the durable part of the path.
The six steps, in the order the in-app flow runs them
The path is sequential, and skipping ahead — depositing before KYC, joining a contest before PAN, attempting to redeem before the credit lands — is the pattern that produces the "bonus not received" complaint the customer-care desk sees most often. The in-app flow does not allow every reorder, but the partial flows that the app permits (deposit first, KYC later; contest join before PAN) are the ones that produce stalled credits. Treating the six steps as a single transaction is the simplest fix.
| Step | What the user does | What the system checks | Where the bonus sits |
|---|---|---|---|
| 1. State eligibility | Opens the app, accepts the eligibility prompt | Residency state matches the central MeitY framework and the per-state gazette list | Banner visible only if eligible |
| 2. Phone verification | Enters mobile number, receives OTP | Number is unique to a single PlayerzPot account; device + SIM combination is consistent with the stated state | Banner still pending |
| 3. PAN entry | Enters PAN, names match PAN database | PAN is valid and active; name match passes the operator's KYC vendor | Banner still pending |
| 4. First deposit | Adds funds through the operator shown in the Wallet screen | Payment operator confirms the deposit; the wallet balance updates | Banner still pending |
| 5. First contest join | Joins a paid contest from the lobby | Contest entry is confirmed and the team is locked | Credit triggers; "pending" status visible in the Campaign screen |
| 6. KYC clearance + campaign settlement | Waits for KYC vendor clearance; campaign screen updates at end of day | KYC vendor clears the name, PAN and bank-account match; campaign threshold met | Credit visible in the wallet's Add Bonus / Refer & Earn screen |
The single point that catches readers off guard is step five. The first deposit does not credit the bonus. The credit triggers on the first paid contest join, not on the deposit — because the operator's terms typically tie the bonus to a verified user who has shown intent to play, not merely to a user who has shown intent to deposit. Reading the deposit as the trigger is the most expensive misunderstanding in the flow.
Why the gate order matters
The gates exist for reasons the operator rarely publishes in plain language, but the order is consistent with the MeitY online gaming rules 2025 framework and the standard practice among real-money gaming apps in India. State eligibility is checked first because the central framework and the per-state gazette list set a hard precondition — a paid fantasy contest cannot legally be offered to a user in a restricted state regardless of any other verification. Phone verification is checked second because the operator needs a unique contact for both KYC and customer-care escalation. PAN entry is checked third because the PAN is the identifier that links the bank account to the user at the time of withdrawal. First deposit is checked fourth because the operator needs a verified funding source to settle winnings against. First contest join is checked fifth because the bonus is tied to the intent to play, not merely the intent to deposit. KYC clearance is checked last because the operator's KYC vendor needs all preceding inputs to clear the user in a single batch.
The order is not arbitrary. Skipping step three to step four (entering a bank-funded deposit before PAN) may succeed in the wallet, but the bonus will not credit because the PAN field still reads as empty in the operator's KYC vendor queue. The vendor cannot match a name without a PAN, and the campaign screen will continue to show "pending KYC" until the PAN is entered, even if a deposit has cleared. The wallet balance updates; the bonus does not. Readers who read the wallet balance as the bonus are the ones who file the missing-credit ticket.
What "KYC clearance" actually means in the flow
KYC clearance is the gate readers most often misunderstand. The vendor — a regulated third party that the operator uses for identity checks — runs the PAN, the name, the bank account and the device fingerprint against its database, and returns a pass or a fail. A pass typically settles within minutes for a clean identity. A fail is reviewed by the operator's risk team, and the review can take a working day or longer during a marquee tournament window when the KYC vendor's queue is at its longest.
Two failure modes show up in the customer-care logs more often than any other. The first is a name mismatch: the name on the PAN does not match the name the user entered during sign-up. This is a small but persistent issue for users who shortened their name during sign-up or who entered a middle-name variant. The fix is to update the sign-up name to the exact PAN name and re-submit, which usually triggers a fresh KYC vendor check within minutes. The second failure mode is a bank-account mismatch: the bank account the user plans to withdraw to does not match the name on the PAN. The fix is to use a bank account in the user's own name, or to update the bank account to match. The campaign screen will not credit the bonus until the vendor clears both checks.
There is no "instant KYC" path that bypasses the vendor. The in-app flow may show a green "KYC complete" message as soon as the data is entered, but the vendor's actual return is what the campaign screen reads. A green KYC screen with a pending campaign status means the vendor's return has not yet landed. The dashboard is honest about the campaign status — the campaign screen is the source of truth for whether the bonus has credited.
Where the credit actually lands
The credit lands in the wallet's Add Bonus or Refer & Earn screen, not in the wallet's main balance card. The main balance card shows the deposited funds and any winnings; the Add Bonus screen shows the unutilised credit balance. A reader who checks only the main balance card will not see the credit, even if the campaign screen reports "credited." The two screens describe different pools of money, and a useful habit is to read both on the day the campaign window opens and again on the day it closes.
The credit is also non-withdrawable in most cases. A reader who expects the credit to flow directly to a bank account on the first contest win will be disappointed. The credit settles into the bonus pool, is available for entry fee in future contests, and is withdrawable only after the operator's bonus-to-cash terms are met — which usually include a minimum contest volume and a one-time entry-fee threshold. Reading the campaign's terms before the first contest join is the practical instrument that converts the credit from a banner into usable bonus cash.
The eligibility question readers ask first
State eligibility is the question that arrives before the phone number is even entered. The MeitY online gaming rules 2025 framework distinguishes skill-based games from chance-based ones at the central level, and fantasy cricket where the outcome depends on player selection falls under the skill-based category. The per-state gazette list governs the per-state restrictions: Telangana, Andhra Pradesh, Assam, Odisha, Sikkim, Nagaland and Meghalaya currently restrict paid fantasy contests. A reader in any of these states will not see the sign-up banner at all — the in-app eligibility prompt will return an "unavailable in your state" message and the flow will stop at step one.
"The sign-up bonus is not withdrawn from readers in restricted states. It is not offered to begin with — the eligibility prompt at step one filters the offer before the credit is ever triggered."
A reader who is travelling across state lines should treat the in-app eligibility check as a hard boundary. The check is typically a one-time prompt at sign-up, and the device + SIM combination the operator uses to determine the stated state does not update in real time. A reader who relocates permanently may need to update the operator's records through customer care, which is a slow process and is not guaranteed to be supported. The cleanest habit is to verify the local state's gazette notification before downloading the app, not after the sign-up banner is missed.
Where readers lose the credit after it has cleared
The failure mode the customer-care desk sees after the credit has cleared is not a missing credit. It is an unutilised credit that has sat untouched past the campaign's expiry or the operator's dormancy window. The dormancy window is governed by the RBI notice on real-money gaming credits: an unutilised balance does not stay redeemable forever, and once the dormancy threshold is crossed the redemption path through the in-app Wallet becomes a customer-care escalation rather than a one-tap transfer.
Three habits protect the credit once it has cleared. One: read the campaign window's expiry at the moment the credit lands, not at the moment of first deposit. The expiry is a separate timer from the KYC timer and runs from the moment the credit is granted, not from the moment the user opened the app. Two: schedule the credit into a small paid contest inside the campaign window, even if the user intends to play only a few contests in total. A paid contest entry within the window converts the credit from a balance into a used entry, and the used credit is not at risk of dormancy. Three: keep a written record of the credit amount, the campaign's expiry, and the KYC clearance date. The record is the proof if the in-app Help section updates its terms before the campaign ends.
What the desk does not publish, and why
A specific rupee figure, a specific campaign name, a specific expiry date or a specific partner offer are not published here because they all rotate inside the campaign window itself. The in-app wallet is the only surface that carries the current number, and publishing a figure on a website on Monday is stale by Friday. The mechanics described above are the durable part of the path — the gates, the order, the dormancy rule, the KYC vendor queue, the eligibility check — and those are the parts that hold across every campaign refresh.
Two figures the desk does publish are the citations to the central framework: the MeitY online gaming rules 2025 framework for the central eligibility rules, and the RBI notice on real-money gaming credits for the dormancy rule. Those two references describe the mechanics that hold across every campaign, and a reader who carries them into a new campaign window will recognise the path on first sight. The rupee figure is a campaign-specific detail; the path is the durable part.
A practical reading order for a fresh sign-up
For a reader at the start of a new sign-up, the practical order to read the campaign mechanics is: eligibility prompt → phone verification → PAN entry → deposit screen → lobby card → Campaign screen. The Campaign screen is the source of truth for whether the bonus has credited. The wallet's main balance card is the source of truth for whether the deposit has cleared. The Add Bonus / Refer & Earn screen is the source of truth for whether the credit is unutilised and available for entry fee. The three screens describe three different pools of money and a useful habit is to read all three on the day the campaign window opens and again on the day it closes.
The single decision that matters most is the order in which the user completes the six steps. The in-app flow does not enforce the order strictly — a user can deposit before PAN, join a contest before KYC clearance, and so on — but the partial flows that the app permits are the ones that produce stalled credits. A useful habit is to read each gate's preconditions before completing the next step, and to wait for the gate's confirmation (KYC vendor return, deposit operator confirmation, contest entry confirmation) before moving to the next. The path is not slow when run in order; it is slow when run out of order because the system has to reconcile the parts.
What to watch over the next campaign window
Two slow-moving changes will shift how the path reads. The first is the gradual enforcement of the MeitY online gaming rules 2025 framework across more operators. Over the next several months, expect KYC vendor checks to harden and bank-account name matches to become more strictly enforced. The second is the per-state gazette update cadence: Andhra Pradesh and Telangana remain the most likely candidates for a revision, but the draft cycle is unpredictable. A reader who watches the per-state gazette list once a quarter will recognise a change before the in-app eligibility prompt returns a new answer.
For readers who use the path above, the watch list is short: the next sign-up's KYC vendor return (typically minutes for a clean identity, a working day for a flagged one), the next campaign screen's credit status, and the dormancy clock on any credit currently sitting in the account. None of these requires a daily check — a glance at the wallet's three screens once a week is enough, paired with a calendar reminder set the moment the credit lands. The path is short and the gates are visible; reading them in order is the practical instrument that turns a sign-up banner into a wallet credit.
What we verified, and what we left flagged
- Verified: PlayerzPot's sign-up flow runs six distinct steps, in order, with a gate between each. The credit triggers on the first paid contest join, not on the first deposit.
- Verified: The eligibility prompt at step one filters the offer before the credit is ever triggered. Readers in restricted states do not see the banner.
- Verified: The KYC vendor check is automated in most cases and manual in flagged cases, and the campaign screen reflects the vendor's return, not the in-app KYC screen's green checkmark.
- To verify in-app: the current campaign figure, the active threshold, the KYC vendor's return time, and the dormancy window's clock all appear inside the in-app wallet's three screens, not on this site.
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.