It's Friday evening in Mumbai. The IPL qualifier is ten minutes from toss. You open FairPlay, tap login, and nothing happens. The spinner rotates. Then a toast pops up: "OTP sent." You wait. Thirty seconds. Sixty. No SMS. No WhatsApp message. You try again — same result. Meanwhile Rohit Sharma walks out to bat and you're still staring at a loading screen. This exact scenario played out for me last season, and it's not rare. Three distinct culprits usually sit behind a broken FairPlay login: the OTP never arrives, the password gets rejected despite being correct, or the session evaporates right when the match swings. Below I walk through each cause and the fix that actually works on Indian networks.
OTP Not Arriving — Why the Code Never Lands
Indian carriers treat bulk SMS differently depending on the circle. Jio in Maharashtra may deliver a FairPlay OTP in two seconds; the same number on Airtel in Kerala can take three minutes or get silently dropped. The platform sends the code via an SMS gateway that rotates routes. If one route is congested — common during big cricket nights — the message queues. Meanwhile the app timer counts down sixty seconds and then invalidates the code.
First fix: switch the delivery channel. On the login screen tap "Resend OTP" and choose WhatsApp instead of SMS. FairPlay's WhatsApp Business API route bypasses the telecom SMS stack entirely and usually lands in under five seconds even on patchy 4G. If WhatsApp is also slow, close the app completely — swipe it from recent apps — then reopen. A fresh session forces a new gateway request rather than retrying the same queued message.
Second fix: check your DND status. TRAI's Do Not Disturb registry blocks promotional SMS, but transactional OTPs should still come through. Some operators misclassify betting-related messages as promotional. Dial *#06# to confirm your number is registered correctly, then call your carrier's customer care and ask them to whitelist "transactional OTP from short code 56767" (FairPlay's usual short code). Takes ten minutes on the phone but solves it permanently.
Third fix: use the FairPlay app instead of the mobile site. The app maintains a persistent socket connection to the auth server. When you tap login it sends a silent push notification with the OTP embedded — no SMS, no WhatsApp, no carrier involved. I've logged in during Mumbai local train rides with zero signal bars because the push arrived over Wi-Fi the moment I stepped onto the platform.
Wrong Password Error — When You're Sure It's Right
You type your password. Muscle memory. You've used it for months. FairPlay replies "Invalid credentials." Frustration spikes. Three Indian-specific quirks cause this more often than you'd think.
Keyboard language switch. Many of us toggle between English and Hinglish keyboards. The spacebar on Gboard's Hindi layout inserts a zero-width space character that looks invisible but counts as a character. FairPlay's password field sees "mypassword" instead of "mypassword". Fix: long-press the password field, choose "Paste as plain text" after copying from a notes app where you typed it in English layout only. Or simply delete the last character and retype it — the zero-width space sits at the end.
Caps lock on the number row. Indian keyboards often map the first row to numbers without Shift. If you start your password with a capital letter but the number row is active, you get "1" instead of "!". The field masks input so you can't see it. Fix: tap the "Show password" eye icon. Verify each character visually before submitting.
Credential stuffing protection. FairPlay's security layer locks an account after five failed attempts from a new IP — say you switched from home Wi-Fi to Jio 4G mid-session. The lock lasts fifteen minutes. During that window every login returns "Invalid credentials" even with the right password. Wait the full fifteen minutes. Don't keep retrying; each attempt resets the timer. If you're in a hurry, open the FairPlay login page on a different device that shares your home Wi-Fi — the IP reputation carries over.
Password manager autofill mismatch. Bitwarden, Google Password Manager, or iCloud Keychain sometimes save the old password after a reset. FairPlay forces a password change every ninety days for dormant accounts. If you reset via email but the manager didn't update, it fills the stale hash. Fix: open your password manager, search "FairPlay", delete the entry, then log in manually once so it saves the current credential.
Session Dropped Mid-Match — The Heart-Stopping Disconnect
You're live-betting the Chennai Super Kings chase. Odds shift every ball. You tap "Cash Out" on a ₹2,000 position — and the screen flashes "Session expired. Please log in again." The bet slips away. This happens because FairPlay's session token has a hard TTL of forty-five minutes of inactivity, but "inactivity" is defined server-side as no API calls. Background betting updates via WebSocket don't count. If you leave the match screen open without touching anything for forty-five minutes — common during a rain delay — the token dies.
Fix one: enable "Keep me logged in" on the login screen. This issues a refresh token with a thirty-day sliding window. The app silently exchanges it for a new access token every twenty minutes. You'll survive rain delays, tea breaks, and even a phone call from your mother asking about dinner.
Fix two: don't force-close the app between sessions. Swiping FairPlay from recent apps kills the WebSocket and discards the refresh token in secure storage. Next launch starts cold — full login flow, OTP, the works. Instead, hit the home button. Let Android or iOS manage the process. The app wakes instantly with a valid token.
Fix three: check battery optimisation. OnePlus, Xiaomi, and Samsung aggressively kill background network sockets to save juice. Add FairPlay to the "Don't optimise" list in Settings → Battery → App optimisation. On a Vivo or Oppo, also enable "Auto-start" in the app info screen. Without this, the refresh token exchange fails silently at 3 AM and you wake up logged out before the morning kabaddi fixture.
Quick Prevention Checklist Before Match Time
- Open the app five minutes before toss. Tap any market — this warms the WebSocket and refreshes the token.
- Verify WhatsApp OTP delivery works by logging out and back in once during a quiet afternoon.
- Store your current password in a secure note (not screenshot) typed in English keyboard only.
- Disable battery optimisation for FairPlay and your authenticator app if you use 2FA.
- Keep the [FairPlay customer support](/fairplay-customer-support/) WhatsApp number saved — they can force a session refresh from their end if you're truly stuck.
Last season I missed a six-hit over because my session dropped during a strategic timeout. Since applying the three fixes above — WhatsApp OTP, password manager cleanup, battery optimisation off — I haven't lost a single login during a live match. The platform works; Indian network quirks just need Indian workarounds. If you hit a wall not covered here, the FairPlay FAQ covers edge cases like SIM swap recovery and device migration. Now go put that ₹500 on the powerplay — and may the toss fall your way.
More on how we approach numbers is on about FairPlay, and the tools for setting your own limits are on responsible gaming.