It was a Tuesday evening in Bangalore, the sort where the traffic on Outer Ring Road finally clears and you settle onto the balcony with a cup of filter coffee, ready to check the toss for the Mumbai Indians match. You tap the FairPlay app, thumb hovering over the login screen, and realise you haven't signed in since the IPL qualifiers. The password you're sure you used — something with a capital letter, a number, maybe an exclamation mark — just spins back an error. Three attempts later the button greys out. That's the moment most people start guessing, but guessing is exactly what locks you out longer.
Start from the login screen, not the homepage
Open the FairPlay login screen on the app or the mobile site. Do not try to reset from a generic homepage banner or an old email link — those routes often drop you into a stale session that rejects the very code you're about to request. On the login screen you'll see a "Forgot Password?" link right under the password field. Tap it once. The screen shifts to a single field asking for your registered mobile number or email. Enter whichever one you used when you first created the account. If you signed up with a Delhi number but now use a Mumbai SIM, use the Delhi number. The system matches the identifier, not your current location.
After you submit, a six-digit OTP lands on that mobile or email within thirty seconds. If you're on Jio or Airtel in a metro like Chennai or Hyderabad it usually arrives instantly; on BSNL in a tier-two town it can take a minute. Do not close the app. Do not switch to WhatsApp to tell a friend you're locked out. The moment you leave the screen the timer starts ticking, and the code you just received becomes the only one that works.
Why only the newest code works
FairPlay's reset flow issues a single-use, time-bound token tied to the exact request you just made. When you tap "Resend OTP" or trigger a second request — say because you fat-fingered the first number — the backend invalidates the previous token and generates a fresh one. The old code is now mathematically useless. This isn't a bug; it's a security design that prevents someone who intercepted an earlier SMS from slipping in later. I learned this the hard way during a test match at Eden Gardens: I requested a code, got distracted by a wicket, requested another, and the first one stopped working. Only the second code let me set a new password.
The token expires after ten minutes. If you wait longer — maybe you went to grab a samosa from the corner stall — you must request a new one. Each request kills the prior token. So the rule is simple: request once, stay on the screen, enter the code the moment it arrives.
Setting the new password
Once the OTP is accepted you land on the "Create New Password" screen. The requirements are straightforward: minimum eight characters, at least one uppercase letter, one lowercase letter, one number, and one special character such as @, #, or $. A pattern like "Kohli@18" meets the rules but is too obvious if your socials are full of cricket posts. Pick something only you would connect — maybe the auto-rickshaw fare from your Pune hostel to the stadium back in 2019, mixed with a symbol. Type it twice. The app checks for match on the fly; if the green ticks appear you're good.
Hit "Confirm". The screen flashes "Password updated" and kicks you back to the login page. Now enter your mobile or email and the brand-new password. You should land straight on the dashboard, balance intact, any pending bets still visible. If you see a "Session expired" toast, just log in once more — it's a harmless cache clear.
Common pitfalls that waste time
- Requesting the OTP on the website but trying to enter it in the app (or vice versa). The token is bound to the platform that generated it.
- Using a different phone number than the one registered. The system does not cross-reference KYC documents at this stage.
- Copy-pasting the OTP with a trailing space. The field trims whitespace on some keyboards but not all; type it manually if paste fails.
- Closing the app before the ten-minute window. The token dies with the session.
If you genuinely lost access to the registered mobile — say you ported the number and the old SIM is dead — you cannot complete the automated reset. In that case open the FairPlay contact us page, choose "Account Access" from the dropdown, and raise a ticket with your registered email, full name, and the last four digits of the UPI ID you use for deposits. The support team verifies manually and resets the linkage, but that takes a few hours during IST business time.
After you're back in
Now that you're logged in, take thirty seconds to harden the account. Go to Settings → Security and enable two-factor authentication if you haven't already. It sends a fresh OTP every login, not just on reset, and it's the single best shield against someone else burning through your balance on a late-night kabaddi accumulator. While you're there, confirm your registered email is current — password resets can also be sent there, giving you a backup channel if the SIM acts up.
If you share the device with a flatmate in Mumbai or a cousin in Kolkata, log out after each session. The "Remember me" toggle is convenient but it stores a session token that survives a password change on some older app builds. A clean logout forces a fresh handshake next time.
One last habit: store the new password in a password manager or a physical notebook you trust. The next time you sit down for a Royal Challengers Bangalore chase, you'll tap the FairPlay login screen, the credentials autofill, and you're straight into the match odds — no coffee gone cold, no frantic OTP chase.
More on how we approach numbers is on about FairPlay, and the tools for setting your own limits are on responsible gaming.