Document 01 · PAN card
A PAN card is the standard identity document for Indian real-money skill-game KYC. A clear photograph of the PAN, with name and PAN visible, is the desk’s baseline expectation.
Wallet & KYC, in plain language
A skill-game wallet is unlocked after KYC: a PAN card for identity, an address proof (Aadhaar, utility bill or bank statement), and a bank account or UPI handle for deposits and withdrawals. The desk describes the typical KYC surface at a generic level; the operator’s published flow is the source of truth. KYC requirements vary by jurisdiction and by deposit amount.
The typical KYC document set
Document 02 · Address proof
Address proof is typically Aadhaar (front and back), a recent utility bill, or a bank statement with the address. The desk has read operators that accept only Aadhaar; the operator publishes the accepted list.
Document 03 · Bank or UPI
A bank account (account number + IFSC) or a UPI handle is needed for deposits and withdrawals. The bank or UPI must be in the same name as the PAN.
What KYC means on a real-money rummy platform
KYC stands for Know Your Customer, and on a real-money rummy platform it means the verification process the platform runs before it accepts a deposit from a player. The process is published by the platform and verified at the deposit step. The standard process is PAN-based KYC verification, which confirms the player's identity, age, and address against the published government record. The desk records the verification process verbatim and notes any platform that does not publish a verification process on its own page.
KYC is a regulatory requirement. Every platform that accepts real-money deposits in India is required to verify the player's identity, age, and address before the deposit is accepted. The verification is published by the platform and verified against the published primary source. The desk has read this requirement on every published rules page it has reviewed; the reader verifies the operator's own page before applying the requirement to a non-standard table.
PAN verification and the published age check
PAN verification is the published verification of the player's Permanent Account Number, a 10-character alphanumeric identifier issued by the Income Tax Department. The PAN is verified against the government's published database, and the player's date of birth is read from the PAN record. The platform then compares the date of birth against the 18+ requirement and rejects the deposit if the player is under 18. The desk records the PAN verification process verbatim and notes any platform that does not verify the PAN at the deposit step.
The age check is non-negotiable. Any platform that accepts a deposit from a player under 18 is out-of-policy with the desk's review criteria, regardless of the platform's published rules. The flag is recorded on the platform's entry in the comparison ledger and noted in the desk's review of the operator's published material. The reader verifies the operator's own page before applying the rule to a non-standard table.
Address verification and the published documents
Address verification is the published verification of the player's address against a government-issued document. The standard documents are Aadhaar, a passport, a voter ID, or a utility bill not older than three months. The platform verifies the address against the document and matches it against the player's account profile. The desk records the address verification process verbatim and notes any platform that does not verify the address at the deposit step.
The address verification is a regulatory requirement under the Prevention of Money Laundering Act (PMLA). The platform is required to verify the address before the deposit is accepted. The desk has read this requirement on every published rules page it has reviewed; the reader verifies the operator's own page before applying the requirement to a non-standard table. Where the platform's published material is incomplete, the desk flags the platform as not-yet-reviewable on address verification.
Wallet binding and the deposit-withdrawal loop
Wallet binding is the published process by which the platform links the player's verified identity to a wallet that holds the deposited funds. The wallet is used for both deposits and withdrawals, and the binding is verified at every transaction. The desk records the binding process verbatim and notes any platform that does not bind the wallet to the verified identity.
The deposit-withdrawal loop is the published flow of funds from the player's bank account, through the wallet, into the platform's contest pool, and back to the player's bank account on withdrawal. The loop is verified at every step. The desk records the loop verbatim and notes any platform that does not publish the loop on its own page. Where the published loop is incomplete, the desk flags the platform as not-yet-reviewable on the deposit-withdrawal flow.
How the KYC process is read against the published material
The KYC process is read in the order identity, age, address, wallet binding. Identity is verified by PAN. Age is verified by the date of birth on the PAN record. Address is verified by a government-issued document. Wallet binding is verified at every transaction. The desk reads the process against the platform's published material and records the published process verbatim.
Where the platform's published material is incomplete or contradicted by the platform's deposit step, the desk flags the platform as not-yet-reviewable on the KYC process. Where the platform's published material is contradicted by the platform's withdrawal step, the desk flags the platform as out-of-policy on the deposit-withdrawal flow. The reader verifies the platform's own published material against the desk's state-by-state reference.
Time frames and friction points
- Aadhaar + PAN auto-flow.Aadhaar + PAN verification typically completes in under 30 minutes on the desk’s test tickets. Manual review with photo and e-sign averages 1–6 hours.
- Address mismatch.An address mismatch between PAN and Aadhaar is the most common friction point. The operator publishes the mismatch-resolution flow; the desk flags any operator without one.
- Re-verification on threshold.Most operators re-verify KYC on deposit or withdrawal thresholds (e.g. ₹10,000 or ₹50,000 cumulative). The operator publishes the threshold; the desk flags any operator that does not.
Editorial boundary
Wallet & KYC, in plain language on boltfantasy.com is editorial guidance, not legal or financial advice. The desk reads published operator material and records the desk’s own test tickets where the operator publishes a verifiable flow. Where the operator publishes a number, a window or a document list, the desk flags it; where the operator does not, the desk records the gap. The reader verifies the operator’s current page before relying on any figure listed here.
What the desk does not cover
- Personal recommendations for any specific platform beyond the editorial pick on the homepage.
- Verification of any operator’s licence beyond the licence number the operator publishes on its own material.
- Legal interpretation of any state gaming act. The reader verifies the local rule before playing.
Reading the KYC reference against the published material
The KYC reference is read against the platform's published verification process. The desk records the platform's published process verbatim and notes where the platform's published process differs from the desk's reference. The reader verifies the platform's own published process against the desk's reference and notes where the two diverge.
The KYC reference is editorial, not regulatory advice. The desk does not synthesise or extrapolate beyond the published primary source. The desk flags any platform that publishes a verification process the desk cannot verify against the platform's own material. The reader decides whether to deposit at a particular platform, and reads the published material against that decision.
The KYC reference is updated when a regulator publishes a revised guideline. The desk has read this requirement on every published regulator guideline it has reviewed. The reader verifies the regulator guideline before applying the guideline to a non-standard platform.
The deposit-withdrawal loop and the published flow
The deposit-withdrawal loop is the published flow of funds from the player's bank account, through the wallet, into the platform's contest pool, and back to the player's bank account on withdrawal. The desk records the loop verbatim and notes any platform that does not publish a loop.
The deposit-withdrawal loop matters because a published loop is the published evidence that the platform can route funds both directions. The desk flags any platform that publishes a deposit step but does not publish a withdrawal step. The desk flags any platform that publishes a withdrawal step but does not publish a deposit step. The reader verifies the platform's own published loop against the desk's reference.