A copy of every KYC submission
Save a copy of the PAN, Aadhaar (masked) and address proof you submitted. If the platform requests re-verification, you can resubmit quickly.
A working explainer for adult Indian rummy readers covering PAN, masked Aadhaar, address proof and penny-drop verification, with a withdrawal processing window reference.
Tax-withholding obligations. Real-money winnings above a threshold are subject to TDS deduction; PAN is the identifier on which the deduction is recorded.
Identity and address verification. UIDAI consent rules allow a platform to verify the last four digits match the first eight without storing the full number.
State eligibility. A platform uses the address to confirm the player is in a state where real-money play is permitted.
Bank account ownership. The reference number returned by the platform confirms the player owns the receiving bank account.
| Payment method | Typical window | What the player sees |
|---|---|---|
| UPI | Minutes to a few hours | Funds land in the registered UPI handle. |
| IMPS | Minutes to a few hours | Funds land in the registered bank account. |
| NEFT | 1 to 3 business days | Funds land in the registered bank account via the NEFT batch window. |
| Bank draft | 5 to 10 business days | A physical draft is couriered to the registered address. |
Save a copy of the PAN, Aadhaar (masked) and address proof you submitted. If the platform requests re-verification, you can resubmit quickly.
Every withdrawal generates a reference number. Save the number with the date and amount. If a withdrawal is delayed, the reference number is the fastest path to resolution.
If the platform responds to a withdrawal delay in writing, save the response. A written response is evidence; a verbal response is not.
Most platforms run KYC on the first deposit or the first withdrawal, not on sign-up. The desk walks through the seven steps a reader takes from first deposit to verified withdrawal, the documents the platform asks for at each step, and the verification window each step carries.
The reader signs up with the platform's published sign-up form. The form asks for a mobile number, an email address and a password. The platform sends a one-time password to the mobile number and the email address. The reader enters the one-time password to confirm the contact details.
The platform runs the state-eligibility check at sign-up. The check asks the reader for the state they reside in. The platform confirms whether real-money play is permitted in that state. Where the reader is in a state where real-money play is not permitted, the platform does not accept the deposit.
The reader makes the first deposit via the platform's published payment methods. Most platforms support UPI, IMPS, NEFT and bank drafts. The reader notes the deposit reference number on file; the desk's wallet reference lists the reference numbers a reader should keep.
The platform asks the reader for the PAN. The platform verifies the PAN against the Income Tax Department's published register. The verification typically completes within a few minutes. Where the verification fails, the platform asks the reader to resubmit a clearer PAN image.
The platform asks the reader for the Aadhaar number. The platform masks the Aadhaar to the last four digits under UIDAI consent rules. The platform verifies the last four digits against the first eight digits via the UIDAI API. The verification typically completes within a few minutes.
Where the platform does not accept masked Aadhaar as address proof, the platform asks for a current utility bill, bank statement or rental agreement. The document must be dated within the last three months. The platform verifies the address against the document image.
The platform posts a small credit to the registered bank account. The reader notes the reference number on the bank statement and types the reference number into the platform. The platform confirms the bank account is owned by the reader. The verification typically completes within one business day.
Re-verification happens when the platform upgrades its compliance framework, when the reader changes the registered bank account, when the Aadhaar masked digits change (for example, after an Aadhaar re-issue), or when the regulator issues a new instruction. The platform publishes a re-verification notice on the reader's account page.
The desk recommends the reader keeps a copy of every KYC submission on file. The desk's wallet reference lists the documents the reader should keep. Where the platform asks for re-verification, the reader can resubmit from the on-file copy quickly.
The reader does not need to resubmit the PAN if the PAN has not changed. The reader does not need to resubmit the Aadhaar if the masked digits have not changed. The reader does need to resubmit the address proof if the address has changed since the last submission.
Where PAN verification fails, the reader resubmits a clearer PAN image. The image should be a flat scan of the PAN card, with no glare and no cropping. Where the resubmission fails a second time, the reader contacts the platform's in-app support inbox with the PAN reference number.
Where Aadhaar verification fails, the reader confirms the masked digits match the first eight digits. The reader resubmits with the corrected masked digits. Where the resubmission fails a second time, the reader contacts the platform's in-app support inbox with the Aadhaar reference number.
Where address proof fails, the reader resubmits a document dated within the last three months. The reader confirms the name on the document matches the name on the PAN. Where the resubmission fails a second time, the reader contacts the platform's in-app support inbox with the address reference number.
Where penny-drop verification fails, the reader confirms the bank account is active and accepts small credits. The reader resubmits the bank account number. Where the resubmission fails a second time, the reader contacts the platform's in-app support inbox with the penny-drop reference number.
The platform publishes a minimum withdrawal amount on the platform's terms page. The minimum is the smallest amount the reader can withdraw in a single transaction. Where the reader's balance is below the minimum, the platform holds the balance until the reader tops up to the minimum.
The platform publishes a maximum withdrawal amount on the platform's terms page. The maximum is the largest amount the reader can withdraw in a single transaction. Where the reader's withdrawal exceeds the maximum, the platform splits the withdrawal across multiple transactions over a published window.
The platform publishes a daily withdrawal limit on the platform's terms page. The daily limit is the maximum amount the reader can withdraw in a single calendar day. Where the reader's withdrawal exceeds the daily limit, the platform holds the excess until the next calendar day.
The platform publishes a monthly withdrawal limit on the platform's terms page. The monthly limit is the maximum amount the reader can withdraw in a single calendar month. Where the reader's withdrawal exceeds the monthly limit, the platform holds the excess until the next calendar month.
The reader reads the platform's published limits before the first deposit. The reader sets a daily deposit cap that fits within the platform's published withdrawal limits. The reader verifies the platform's published limits on the platform's terms page rather than relying on the desk's summary.
The reference above walks through the seven steps a reader takes from first deposit to verified withdrawal, the documents the platform asks for at each step, and the re-verification scenarios the reader may face. Verify each step on the platform's own published page.
The desk reads KYC questions sent to the editorial email. The desk does not act as an intermediary between a reader and a platform; the desk directs the reader to the platform's in-app support inbox for account-specific questions. Where the reader has a question about the regulatory framework behind the KYC step, the desk publishes the framework on this page.
The desk reads withdrawal questions sent to the editorial email. Where the reader's withdrawal is delayed beyond the platform's published window, the desk directs the reader to the platform's withdrawal-appeal inbox with the withdrawal reference number attached.
The desk reads re-verification questions sent to the editorial email. The desk does not publish the re-verification notice for any specific reader; the reader must log into the reader's account page to read the notice. The desk publishes the re-verification scenarios the reader may face.