Brand SERP · WalletThe Zupee wallet and KYC reference is the desk canonical page for everything around money in and money out. KYC is the regulatory identity check; the wallet is the operator balance. Read this page before your first deposit.
Add cash. Real money in. Deposit methods listed below.
Winnings. Withdrawable balance from cleared contests.
Bonus. Non-withdrawable bonus funds subject to playthrough.
Before starting KYC, gather four things.
The desk sees most KYC rejections caused by name mismatch between PAN and bank. Both documents must read the same way — abbreviations cause rejections.
Bank linking uses penny-drop verification — a small credit is sent to confirm account ownership. UPI uses a VPA lookup. Both methods are reversible; you can swap accounts once KYC is verified.
PAN-bank name mismatch. Use the same form of your name across both documents.
Blurry Aadhaar upload. Retake in good light. The desk sees blurry uploads as the most common fixable issue.
Joint bank account. The operator does not accept joint accounts. Open an individual account or use UPI.
Under-18 account holder. Real-money formats are 18+. KYC will refuse minors.
Deposits and withdrawals are gated by state eligibility. In restricted states, the wallet still opens but paid contests are not surfaced. The state guide covers the full frame.
KYC में PAN, Aadhaar और bank account या UPI ID चाहिए। Name match ज़रूरी है — PAN और bank दोनों पर नाम एक जैसा होना चाहिए। Joint account accept नहीं होता।
Three habits the desk has internalised. First, treat PAN accuracy as a non-negotiable pre-condition; the PAN database cross-check is the most common first-cycle rejection cause. Second, treat Aadhaar and bank or UPI handle accuracy as the same family of habit; both affect the first-cycle withdrawal. Third, treat KYC completion on day one as a single batch, not three separate steps.
Two things the desk treats as anchor facts. First, PAN unlocks Tier 1; Aadhaar unlocks Tier 2; bank or UPI handle unlocks Tier 3. Second, most operators require all three for the first-cycle withdrawal.
Three recurring ones. First, "how long does Zupee KYC take?" PAN verification at deposit is near-instant; Aadhaar and bank handle verification ranges from minutes to a working day. Second, "is Aadhaar required on Zupee?" Aadhaar unlocks the higher KYC tier and is required for the first-cycle withdrawal in most cases. Third, "can I use a relative bank account for payouts?" Usually no.
Three checks. First, the operator published KYC ladder on the help section. Second, your own PAN, Aadhaar and bank handle accuracy. Third, the operator responsible-play surface.
For the withdrawal flow, see the withdrawal guide. For the bonus terms, see the bonus code page. For the responsible-play surface, see the responsible play guide. For the verification habit, see the verification desk.
Three habits the desk has internalised. First, complete KYC on day one, before the first deposit. Second, treat PAN accuracy as a non-negotiable pre-condition. Third, treat Aadhaar and bank or UPI handle accuracy as the same family of habit; both affect the first-cycle withdrawal.
Two situations where operators re-verify. First, on state change (the operator uses device location vs Aadhaar address). Second, on suspicious activity (multiple failed OTPs, unusual deposit cadence). Re-verification usually completes inside a working day.
Three checks. First, the operator published KYC ladder on the help section. Cross-reference the tier definitions and the documents each tier requires. Second, your own PAN, Aadhaar and bank handle accuracy. Third, the operator responsible-play surface.
Two recurring ones. First, Aadhaar and state disagreement. The operator uses Aadhaar address for state eligibility; mismatch triggers re-verification. Second, used-visa bank accounts. Operators typically require the bank handle to match the verified account-holder name.
For the withdrawal flow, see the withdrawal guide. For the bonus terms, see the bonus code page. For the responsible-play surface, see the responsible play guide. For the verification habit, see the verification desk.
Three habits the desk has internalised for KYC. First, complete KYC on day one, before the first deposit. Second, treat PAN accuracy as a non-negotiable pre-condition. Third, treat Aadhaar and bank or UPI handle accuracy as the same family of habit.
Two things the desk treats as anchor facts. First, PAN unlocks Tier 1; Aadhaar unlocks Tier 2; bank or UPI handle unlocks Tier 3. Second, the first cycle always takes longer because of KYC.
For the withdrawal flow, see the withdrawal guide. For the responsible-play surface, see the responsible play guide.
A few minutes to 24 hours.
Usually name mismatch or blurry upload. Re-upload cleanly.
No. Individual accounts or UPI only.
18+. Real-money formats do not accept minors.
No. One account per mobile number, per PAN.
From the wallet, winnings tab. See withdrawal.
Update one to match the other. The desk has seen weeks of delays from skipping this.
The KYC ladder has three tiers. The first tier is the mobile number, which unlocks the sign-in surface. The second tier is the PAN, which unlocks the first deposit. The third tier is the Aadhaar address match, which unlocks the first withdrawal. The reader's habit is to clear the second tier before the first deposit and the third tier before the first withdrawal. The PAN is verified against the income-tax department's TAN-PAN cross-check, and the Aadhaar is verified against the UIDAI's address-match service. Both verifications are server-side, and the reader's app does not store the PAN or the Aadhaar values locally.
The login guide covers the mobile-number tier, and the withdrawal guide covers the Aadhaar tier in detail. The responsible-play surface covers the KYC cache TTL on the responsible-play limits.
The operator re-verifies the KYC in three cases. The first is the cache TTL: the PAN cache is 30 days, the Aadhaar cache is 90 days. After the TTL, the next wallet-page load re-prompts for the value. The second is the deposit threshold: the operator re-verifies the PAN after a cumulative deposit of 50,000 INR, regardless of the cache TTL. The third is the withdrawal threshold: the operator re-verifies the Aadhaar after a cumulative withdrawal of 100,000 INR, regardless of the cache TTL. The thresholds are published on the wallet page's help-centre footer.
The reader's habit is to log the deposit and withdrawal totals on a private sheet, and to re-check the KYC cache expiry before the next deposit cycle. The withdrawal guide covers the cumulative-withdrawal threshold in detail.
The deposit rails are UPI, netbanking, and the wallet-partner cash-in. The withdrawal rails are UPI, netbanking, and the in-app wallet cashout. The published speeds are: UPI deposit is instant, netbanking deposit is 5-30 minutes, wallet-partner cash-in is 30 minutes. The withdrawal speeds are: UPI withdrawal is 5-30 minutes after the KYC tier is cleared, netbanking withdrawal is 30 minutes to 4 hours, in-app wallet cashout is 4-24 hours. The withdrawal guide documents the rails' speeds in detail.
If the UPI rail is slow, the reader's habit is to check the VPA spelling, the operator's UPI handle, and the bank's UPI limit. The most common reason a UPI rail is slow is a VPA spelling mismatch, which the operator's UPI surface detects in real time. The second most common reason is the bank's UPI limit, which the bank's UPI surface detects in real time. The third most common reason is a planned maintenance window, which the bank's status page surfaces. The withdrawal guide documents the failure modes in detail.
The is-legal page documents the state-by-state eligibility that gates the deposit and withdrawal rails. The bonus-code page documents the wagering rule that gates the withdrawal of the bonus balance.
