Wallet and KYC — the reader-first walkthrough.

Most KYC delays are photography problems, not identity problems. Cropped corners, glare on PAN laminate, and mismatched names across Aadhaar and bank account create manual review queues that feel like “the app is broken.”

Shoot documents on a matte dark surface, fill the frame, and avoid filters. Names must match character-for-character with the bank account you will withdraw to. If your bank account uses a shortened middle name, fix the bank profile or pick a document set that matches reality.

Video KYC, when offered, fails for the same human reasons: talking over the agent, poor lighting, or switching apps mid-call. Stay in a quiet room with the original ID in hand, not a gallery photo of the ID.

If KYC is pending beyond the published window, re-check upload quality before arguing policy. Re-upload only when the UI asks; duplicate uploads can reset the queue.

If cash is pending withdrawal past SLA, send one ticket with UTR expectations, KYC status screenshot, and instrument details. Parallel tickets slow the same desk.

Never “test” the wallet with money you need within 24 hours. First-week accounts are where unknown holds appear. Keep early sessions tiny until a full deposit-withdraw loop succeeds.

Treat KYC as infrastructure, not as a popup you will “do later when lucky.” The cheapest time to fix a name mismatch, an expired ID crop, or a UPI handle tied to a different legal name is before any deposit feels emotionally large. Build a first-week path: verify identity, bind one payout rail, run a tiny deposit and a tiny withdrawal, then raise limits only after both legs clear.

Document quality matters more than document quantity. A sharp, full-frame photo of a valid ID beats three glare-heavy crops and a rushed selfie. Match the name string to your bank account character for character, including spacing and initials. Support teams reverse engineer fuzzy matches slowly; you can prevent that delay in two minutes of careful typing.

Understand holds as product behaviour, not personal punishment. Bonus wagering, fraud checks, and first-withdrawal reviews can park rupees even when the balance screen looks green. Read the wallet breakdown: withdrawable cash, locked bonus, pending review. If the UI does not separate those buckets, ask support for a written split before you plan rent around a number you cannot move.

When a submission is rejected, fix the stated reason only. Resubmitting the same blurry image five times with angry tickets does not accelerate review. If the rejection text is generic, reply once with the reference id, the exact field you changed, and a new capture. Parallel tickets from friends’ phones can look like account sharing and slow you further.

Keep payout rails boring. Avoid rotating through every UPI app in the house to chase a faster hit. Each new beneficiary can retrigger checks. One stable rail, one legal name, and a calm micro-withdrawal history will move more money over a month than clever routing through three handles after a lucky session.

Finally, never send ID images through random Telegram “KYC help” contacts. Official support paths exist inside the authenticated product surface. Third parties who offer to “push verification” in exchange for screenshots are collecting a dossier, not clearing your queue.