Wallet & KYC. The verification step that unlocks withdrawals.

The wallet-and-KYC experience on a legitimate Indian rummy platform is, in 2026, a fairly standard checklist: PAN card for identity, Aadhaar or a recent utility bill for address, a cancelled cheque or bank statement for the bank account that will receive withdrawals, and a live photograph at signup to anchor the KYC record to a real person. Each document is collected once, verified against a third-party database, and stored encrypted. The desk's editorial note is to submit the documents at signup, not at withdrawal — the platforms that respect the rule also tend to respect the player.

The PAN is the most important document in the file. It is the document that the Income Tax Department uses to track high-value transactions, and a winning withdrawal above ₹10,000 will be reported by the platform to the IT department under TDS rules. The reader should know that TDS will be deducted at the source (typically 30% without a PAN, 1% with PAN for net winnings above a threshold in skill-game formats). The desk has a working note on TDS thresholds in the and updates it whenever the IT department publishes a new circular.

The bank account for withdrawals should be in the reader's own name, in an Indian scheduled bank, and active. The platform will not withdraw to a third-party account, to a wallet that does not match the KYC name, or to a bank account that has been closed. The most common cause of a delayed withdrawal is a name mismatch between the KYC PAN and the bank account; the reader should double-check both before submitting the first withdrawal request.

The deposit rails vary by platform, but the most common in 2026 are UPI, netbanking, debit card and a small number of licensed wallets. Each rail has its own settlement time and its own KYC requirement; UPI is the fastest, netbanking the most universal, debit card the most familiar, and the wallets the most variable. The desk's reviews stack ranks the platforms by withdrawal speed and is the working reference for which platform honours which rail.

For readers who want a single document checklist they can save on their phone: PAN card (front image), Aadhaar card or passport (address proof), cancelled cheque (bank account proof), a live photograph taken in good light, and a working email address. The list is short on purpose; the desk has not found a legitimate use case for a longer list, and any platform that asks for more than these five items is a platform whose KYC process the desk has not yet verified.

The desk has been tracking reader correspondence on wallet and KYC experiences since Issue 01. The pattern is consistent across the five issues: the most common cause of a delayed withdrawal is a name mismatch between the KYC PAN and the bank account; the second most common is a withdrawal request to a closed bank account; the third most common is a bonus that the reader did not realise carried a turnover requirement. None of these is a deal-breaker on its own; each is fixable in a single support ticket if the reader has kept the relevant screenshot in the device folder.

The first mistake, name mismatch, is the most common because it is the most avoidable. The reader signs up with the name on the PAN, then enters a bank account in a slightly different name (a middle initial that the bank account does not have, a hyphen that the PAN does not, a spelling that varies between documents). The fix is to double-check both names before submitting the first withdrawal; the desk's recommendation is to take a screenshot of both names and keep the screenshot in the device folder for comparison.

The second mistake, closed bank account, is less common but more frustrating. The reader closes a bank account and forgets to update the platform, then submits a withdrawal to the closed account. The platform rejects the withdrawal, the reader opens a support ticket, and the support function is the test of the platform. The fix is to update the bank account on the platform before closing any bank account; the fix is also to keep a record of which bank account is registered on which platform.

The third mistake, untracked bonus, is the most expensive of the three. The reader accepts a bonus without reading the turnover requirement, then plays through the bonus and is surprised to find the bonus is not withdrawable until the turnover is met. The fix is to read the bonus terms before accepting any bonus, and to decline the bonus if the terms cannot be read in plain language. The desk's editorial line on bonuses is unchanged across issues: a bonus that cannot be read in plain language is a bonus the reader should not accept.

The desk's editorial recommendation, in plain language: keep a screenshot of the KYC PAN, a screenshot of the bank account name, and a screenshot of the bonus terms in the device folder before the first deposit. The folder is the part the reader controls; the withdrawal queue is the part the platform controls. A reader who has the folder is a reader who can resolve a name mismatch in a single support ticket. A reader who does not have the folder is a reader who has to send the documents again.