How long does withdrawal take?
UPI: typically instant to 1 working day. Net-banking: 1-3 working days. Cards: 3-7 working days.
The FanCode withdrawal flow runs through UPI, net-banking or cards. Withdrawal is a one-step in-app request after PAN verification.
Withdrawal from the FanCode wallet follows a one-step in-app request after PAN verification. Processing times are 1-3 working days for UPI / net-banking; cards may incur an operator-side processing fee and may take longer.
| Method | Processing | Min | Fee |
|---|---|---|---|
| UPI (any bank) | 1 working day (often instant) | ₹100 | None |
| Net-banking | 1-3 working days | ₹200 | None |
| Cards (debit / credit) | 3-7 working days | ₹500 | Operator fee may apply |
PAN verification is mandatory before any withdrawal. The first deposit triggers KYC; once cleared, the wallet is unlocked for withdrawal. Bank account or UPI binding is required at the withdrawal step; the operator verifies the binding by a micro-deposit or by UPI handle.
Winnings are taxed at source under Indian income-tax rules. The operator deducts TDS at the rate published by the income-tax department and issues Form 16A at year-end. The desk does not provide tax advice; consult a qualified CA for the version-of-record.
If a withdrawal is delayed past the SLA, open an in-app ticket under Help & Support. If the in-app ticket is not acknowledged within 48 hours, escalate via the operator's customer-care email (recorded on the customer-care lane). For unresolved financial disputes, consult a consumer forum under the Consumer Protection Act, 2019.
UPI: typically instant to 1 working day. Net-banking: 1-3 working days. Cards: 3-7 working days.
UPI / net-banking: no fee. Cards: operator fee may apply.
UPI: ₹100. Net-banking: ₹200. Cards: ₹500.
Yes — PAN verification is mandatory before any withdrawal. This is the standard compliance posture under Indian tax rules.
Deposits typically clear in minutes, but withdrawals clear in 1-3 working days because the operator runs a verification check before settling. The KYC check is mandatory; the bank / UPI binding check is mandatory; a large withdrawal (typically above ₹50,000) triggers a manual review for compliance. The desk flags this asymmetry as standard practice in real-money gaming wallets.
The manual review on large withdrawals is a compliance check required by MeitY Online Gaming rules. It's not a friction tactic; it's the operator's standard verification path. The SLA is 24-72 hours; the desk publishes the typical window and the escalation pattern on the lane.
Every credit and debit sits on the wallet statement, downloadable as a PDF. The statement carries the contest ID, the entry fee, the payout credit, the TDS deduction, and the net withdrawal. Tax-filing purposes: the operator issues Form 16A for TDS deducted on winnings. The desk does not provide tax advice; consult a qualified CA for the version-of-record.
Where a statement entry is wrong, raise an in-app ticket with the contest ID and the timestamp. The operator responds within 24-72 hours; disputed entries are paused until the reconciliation completes.
The operator publishes the settlement rules inside the in-app Wallet section. The desk's role is to summarise the published rules in plain English on the withdrawal lane. Where the operator changes a rule, the desk updates the lane within 24 hours of the operator's announcement.
Common settlement rules the desk has summarised: (1) UPI withdrawals typically settle in 1 working day (often instant); (2) net-banking withdrawals settle in 1-3 working days; (3) card withdrawals may incur a processing fee and may take 3-7 working days; (4) large withdrawals (typically above ₹50,000) trigger a manual review for compliance; (5) the operator issues Form 16A on TDS deductions for prize withdrawals.
Where a settlement rule is unclear from the operator's published policy, the desk writes the desk's reading on the lane with a clear caveat: "the desk's reading". For binding calls (e.g. tax interpretation), consult a qualified CA. The desk does not provide tax advice.
Where a published claim on this lane is later found incorrect (e.g. the operator publishes a new rule that changes the summary), the desk publishes the correction on the corrections log. The corrections log is permanent.
The desk's posture: editorial coverage on the withdrawal lane is verified against the operator's published policy at the time of writing. Where the policy changes, the desk updates the lane. Where the policy is unclear, the desk says so. Where the desk is wrong, the desk fixes it.