18+ only. Fantasy cricket involves financial risk. Play responsibly and within your means. The PROG Act 2025 governs online real-money gaming in India.
CrickBet Wallet and KYC: Document Safety, Name Matching and Verification
KYC should establish identity without scattering documents across chats. Name matching, secure upload, purpose limitation and a retention answer all matter.
Related desk files
withdrawal walkthrough · account deletion checklist · responsible-play limits
Confirm who is collecting the document
Before uploading PAN, Aadhaar, passport, address proof, or a selfie, identify the legal operator and data controller. Read why each item is required, which processor receives it, where it is stored, how long it is retained, and how access or deletion requests work. Use only the authenticated upload flow on the verified domain or app. The desk has not verified a CrickBet-operated wallet or KYC processor. Do not email documents to an address copied from comments, send them to a messaging number, or permit a stranger to capture them through screen sharing.
Name matching across four records
The account profile, tax record, identity document, and bank beneficiary should describe the same person. Common differences include initials, middle names, maiden or married surnames, transliteration, reversed order, spacing, and honorifics. Do not alter a document image to force agreement. Use the operator’s correction route and provide a lawful supporting record when required. Record the old and requested names, ticket number, and decision. A nickname acceptable on a team sheet may be unacceptable in a regulated payment trail.
PAN handling
PAN may be requested for tax identity, duplicate-account controls, or reporting. Check that the form asks only for data relevant to the stated purpose and that the connection is secure. Upload a clear image or use a permitted verification service; do not annotate away required details or expose the file in an open gallery. Never share an OTP associated with a tax or identity service with support. If the PAN status, name, or date of birth differs from the account, resolve the authoritative record first rather than repeating failed submissions.
Aadhaar and alternative identity routes
Aadhaar use should follow the lawful mode offered by the operator, such as masked copy, offline verification, or another permitted process. Check whether an alternative document is available and avoid sharing a full Aadhaar copy when a masked version satisfies the stated requirement. Do not reveal biometric information or an authentication OTP to an agent. Store downloaded identity files carefully and remove temporary copies from shared devices. If consent language is unclear, pause and seek a written explanation of purpose, processor, retention, and grievance route.
Passport and address proof
A passport can establish identity and sometimes address, but the operator should state accepted documents and validity conditions. Address proof may include a bank statement, utility record, or government document depending on the policy. Redact only what the instructions permit; over-redaction can make a document unusable, while no redaction can expose unrelated transactions or account numbers. Check issue date limits and address spelling. Upload from a private network, confirm receipt in the account, and delete unsecured scans after the case closes while retaining the submission record.
Video KYC boundaries
Video verification may ask the account holder to appear live, show an original document, answer basic questions, or perform a liveness action. Confirm that the session begins inside the verified operator workflow and that the interviewer identity or vendor is disclosed. The agent should not ask for banking PINs, remote-control software, unrelated room footage, or another person’s presence to operate the account. Use a neutral background, close other documents, and note the date and case reference. Ask how the recording is retained and how a failed attempt can be reviewed.
Common failure causes
Blurred images, glare, cropped corners, expired documents, unsupported file types, oversized files, mismatched names, mismatched dates of birth, bank accounts in another person’s name, duplicate profiles, unreadable address, and failed liveness checks can all trigger review. Repeatedly uploading different records without understanding the error can create fraud flags. Capture the exact rejection reason and submit one corrected item through the same case. If support uses a vague “verification failed,” request the field that did not match and the correction process without asking them to expose security logic.
Wallet labels and privacy after approval
Cash deposit, winnings, bonus, refundable amount, tax deduction, and withdrawable balance may be separate. Keep the ledger and do not assume the headline wallet amount is withdrawable. After KYC approval, remove unneeded camera and photo permissions, check connected devices, and retain the approval reference. A later account-deletion request should ask what identity and transaction data must remain under law, the retention period, and which processors receive the deletion instruction. Approval is not permission for indefinite undocumented reuse.
Closing field note
If identity theft is suspected, stop uploads, secure the email and phone account, review bank activity, and use verified reporting channels. A KYC rejection should never be solved by sending more documents to an unsolicited helper.
Questions in the desk ledger
Should KYC files be sent through chat?
No. Use only a verified, authenticated upload process.
Can a nickname cause failure?
Yes, if it differs from PAN, identity, or bank-beneficiary records.
Is a full Aadhaar copy always necessary?
No. Check whether a masked or alternative lawful route is accepted.
What should follow a vague rejection?
Ask which field failed and use the documented correction route.
Does KYC approval make the whole wallet withdrawable?
No. Cash, winnings, bonus, and tax treatment can remain separate.
Field-notes appendix
After KYC approval, a quick review helps. Confirm that no permission is left in the operator app beyond what is necessary. Confirm that no device session is still active. Confirm that the saved payment method is the one the user expects. Confirm that the KYC file is not duplicated in cloud storage. If any of these is wrong, the operator's settings should let the reader revoke, edit, or remove the item. A short KYC hygiene habit is worth the effort because the next KYC request will not be obvious. The desk's role is not to do that for the reader, but to remind the reader that an unchecked KYC file can outlast a positive experience with the contest platform.
Field-notes appendix
After a successful KYC, a one-month review helps. The reader can ask: are the saved documents still current? has the address changed? has the bank account changed? has the phone number changed? has the KYC vendor changed? is the deletion route documented? is the retention period documented? If any item has changed, the operator should be notified before the next withdrawal. A KYC document that is out of date at the time of a withdrawal is a common cause of withdrawal delays. A monthly review takes five minutes and saves hours of escalation. The desk recommends a calendar reminder the day after the first withdrawal of every quarter, and a paper trail of the review. A reader who maintains the review is unlikely to be surprised by a rejected payout.
Editorial appendix
After a successful KYC, a one-month review helps. The reader can ask: are the saved documents still current? has the address changed? has the bank account changed? has the phone number changed? has the KYC vendor changed? is the deletion route documented? is the retention period documented? If any item has changed, the operator should be notified before the next withdrawal. A KYC document that is out of date at the time of a withdrawal is a common cause of withdrawal delays. A monthly review takes five minutes and saves hours of escalation. The desk recommends a calendar reminder the day after the first withdrawal of every quarter, and a paper trail of the review. A reader who maintains the review is unlikely to be surprised by a rejected payout. A surprise payout rejection is rarely the operator's first rejection. The reader's review is the first defence. A reader without a review will be told the rejection is the operator's first. The reader's review proves the assertion false, and the proof is a quiet authority the operator cannot ignore. The quiet authority is more useful than a noisy complaint. A noisy complaint is a sign of distress. A documented review is a sign of method. Method wins more often than distress.
The desk's pre-submission checklist
The desk walks a pre-submission checklist that takes ten minutes and prevents most KYC stalls. The checklist covers the documents, the metadata, the format, and the upload environment.
PAN
Photograph the PAN card under daylight, no flash, with the card on a dark non-reflective surface. Confirm the name spelling matches your Aadhaar and bank account. Confirm the PAN number is readable in the photograph. Save as JPEG at 1-2 MB; do not upload screenshots taken from a mobile banking app.
Aadhaar
Use the Aadhaar PDF download from UIDAI rather than a photograph of the physical card. The PDF has higher resolution and is accepted by all operators. If you must photograph the physical card, photograph both sides under daylight; the back side contains the address and the QR code.
Address proof
Address proof options: Aadhaar, passport, voter ID, utility bill (less than 3 months old), bank statement (less than 3 months old). The address on the proof must match the address you entered at signup. The desk's note: utility bills are accepted by some operators but not all; verify against the operator's accepted list.
Live capture
The live capture is the most-likely-to-fail KYC step. The desk's protocol: face centred in the frame, neutral expression, no glasses, no hat, no face mask, daylight or well-lit room. The operator's face-matching algorithm compares the live capture against the Aadhaar photo; large discrepancies in age, weight, or facial hair will trigger a manual review.
The upload environment
Use the operator's verified app or verified domain for upload. Do not email KYC documents to any address, no matter how official the address looks. Do not share Aadhaar OTP over the phone. The operator's verified upload screen is the only acceptable upload route.
Disclaimer. CrickBet is an editorial notebook about fantasy cricket. The site does not operate a real-money gaming platform and does not process deposits or withdrawals. References to fantasy contests describe publicly known contest formats from licensed operators. Fantasy cricket involves financial risk; only individuals aged 18+ and resident in eligible Indian states should participate. Please refer to the Public Online Gaming Act 2025 and your state's rules for current eligibility.