Wallet and KYC verification.
A short explainer on how the wallet, KYC verification, deposits and withdrawals fit together, and where to escalate when the flow stalls.
How the wallet and KYC verification flow works.
The wallet is the user's account on a regulated platform. KYC verification confirms the wallet holder's identity. The two are linked; the wallet cannot send a withdrawal until KYC has cleared. The page below describes the flow and the timeline in plain language.
The wallet
The wallet is the on-platform account that holds a balance. The balance is funded by deposits and reduced by withdrawals. The wallet is closed only through the platform's published closure flow; an inactive wallet is dormant but not closed.
The KYC verification
KYC verification confirms the wallet holder's identity. The platform requests PAN, Aadhaar (or V-ID) and an address proof. The published turnaround is 24 to 72 hours. The verification is logged in the user dashboard with the document set reviewed and the date.
The wallet-to-bank flow
Deposits move from the user's bank rail to the wallet. Withdrawals move from the wallet to the same rail. The rail match is a regulatory protection. The safety chapter describes the rail-matching rule in greater detail.
If KYC does not clear
Most KYC issues are address mismatch or document quality. The platform's customer-care email is the cleanest first contact; the named grievance officer is the second-line escalation. Both contacts are published in the same Terms page.
What the wallet balance actually means.
The wallet balance is the on-platform record of funds held by the reader. The balance increases by deposits and decreases by withdrawals and by stakes placed in a hand. The balance is not a bank account; it is an on-platform position that cannot be withdrawn without the platform's published withdrawal procedure. The published procedure is the only authorised path from the wallet to the reader's bank rail.
The balance and the bonus balance
Where the reader has accepted a bonus offer, the wallet may show two balances: a cash balance and a bonus balance. The cash balance is the reader's own funds; the bonus balance is the platform's promotional credit. The wagering requirement is met by playing through the bonus balance a specified number of times before withdrawal. The two balances are settled separately at withdrawal.
The settlement and the rail
Withdrawal requests settle to the rail the reader originally deposited from. The platform may allow the reader to withdraw to a different rail if the platform's settlement partner supports it; the rail-to-rail change is documented in the platform's KYC or Terms page. A change of rail can extend the settlement window beyond the standard 24 to 72 hours.
Reading the wallet as a small ledger.
The wallet is a small ledger that records deposits and withdrawals. Each transaction is logged with a date, an amount and a rail. The wallet balance at any moment is the net of deposits minus withdrawals. The wallet's transaction history is available in the user dashboard for a published retention period (commonly 24 months).
The settlement and the rail
Deposits settle at the rail the reader used to fund the wallet. Withdrawals settle at the rail the platform supports for the reader's jurisdiction. The settlement window is published in the platform's withdrawal policy; common windows are 24 to 72 hours.
The wallet and bonus balances
Where the reader has accepted a bonus offer, the wallet may show two balances: a cash balance and a bonus balance. The cash balance is the reader's own funds; the bonus balance is the platform's promotional credit. The two balances are settled separately at withdrawal, with the cash balance withdrawable first under most rule variations.
Stalled withdrawal
A stalled withdrawal is a withdrawal request that has not settled within the published turnaround. The reader's first step is to check the published turnaround in the platform's withdrawal policy; the reader's second step is to confirm the wallet's KYC status has cleared; the reader's third step is to contact the platform's customer-care pathway in writing.
When the wallet is in negative
A wallet can show a negative balance after a wrong-show penalty is applied before the next deposit. The negative balance is settled by the reader's next deposit. The negative balance does not affect the reader's ability to sign in or to view prior history.
What the publication is not
The publication is not a wallet operator. The platform operates the wallet; the publication describes the wallet patterns an adult reader should expect. Where the platform's behaviour disagrees with the patterns, the reader should consult the platform's own documentation.
Reading the wallet as a small account.
The wallet is a small account that holds the reader's platform-side balance. The wallet has the same security expectations as any other account: a unique identifier, a recovery path, an audit trail and a set of restrictions. The reader should treat the wallet as an account, not as a tab of the platform's balance sheet.
What the wallet is not
The wallet is not a bank account. The wallet is not insured by a deposit insurer. The wallet is not a credit card. The wallet is an on-platform position that can grow or shrink based on the reader's deposits, withdrawals and play.
What the wallet offers
The wallet offers a single source of truth for the reader's platform-side balance. The wallet offers a transaction history for the published retention period. The wallet offers a withdrawal procedure that settles to the rail of deposit. The wallet does not offer interest, insurance or any banking-grade protections.
What to keep records of
Keep a copy of every deposit, every withdrawal and every KYC submission. The records should be stored locally on the reader's device, indexed by date. The records are the basis for any future dispute with the platform.
What this publication is not
The publication is not the wallet operator. The platform operates the wallet; the publication describes the wallet patterns. Where the platform's behaviour disagrees with the description, the reader should consult the platform's own documentation.
How KYC and the wallet interact.
The wallet and the KYC verification are linked but they operate independently. The wallet can be funded before KYC; the wallet cannot be withdrawn from until KYC has cleared. The reader who deposits before completing KYC will face a withdrawal-hold pattern until KYC clears.
Why the link exists
The link exists because regulators require the platform to know the customer's identity before settling withdrawals. The platform knows the identity via KYC; the platform settles withdrawals via the wallet. The two are linked but operationally separate.
How to complete KYC cleanly
The cleanest KYC submission includes a clear photo of each requested document, with the address legible and the photo matching the registered identifier. The address on the Aadhaar (or V-ID) should match the address on the bank account. A mismatched address is the most common cause of KYC delay.
How to read the KYC status
The KYC status is published in the user dashboard. The status is one of: not started, in review, cleared, or rejected. The cleared status enables withdrawal; the rejected status requires a re-submission with the platform's note on what was rejected.
What to do if KYC is rejected
If KYC is rejected, the platform's user dashboard should state the reason. The most common reasons are document quality, address mismatch or expired documents. The reader should correct the rejected element and re-submit. The re-submission is treated as a new KYC submission; the published turnaround applies from the re-submission date.
What this publication is not
The publication is not the platform. The publication describes the wallet-KYC patterns an adult reader should expect. Where the platform's behaviour disagrees, the reader should consult the platform's own documentation.