It is 19:42 IST on a Tuesday. You are sitting in your Mumbai flat, chai cooling beside the laptop, ready to back Mumbai Indians at 1.85 before the toss. You open the FairPlay app, tap login, and nothing happens. The spinner spins. The OTP never arrives. Or worse — you are three overs into the chase, the odds shift, and the session evaporates, dumping you back at the login screen. Three different failures. One ruined evening. Below is the walkthrough I wish I had the first time it happened.
OTP Not Arriving
The most common culprit is the mobile network, not FairPlay. Indian carriers — Jio, Airtel, Vi — occasionally delay transactional SMS by thirty seconds to three minutes during peak hours. If you requested the code twice in thirty seconds, the second request often cancels the first. Wait a full two minutes before tapping resend.
Check the spam folder in your Messages app. Some handsets shove six-digit codes into a separate "Promotions" or "Spam" tab. On Xiaomi and Realme devices, long-press the Messages icon, choose "App info", then "Notifications", and ensure "Transactional" is toggled on.
If you recently ported your number, the new operator may not have updated the DLT registry that FairPlay's SMS gateway uses. In that case, switch to the WhatsApp OTP option on the FairPlay login screen. The WhatsApp channel bypasses the DLT layer entirely and usually lands in under ten seconds.
Still nothing? Open the dialler and type *#*#4636#*#*. Tap "Phone information", scroll to "SMSC", and note the number. Call your carrier's customer care (198 for Jio, 121 for Airtel, 199 for Vi) and ask them to verify the SMSC matches. A mismatched SMSC drops every OTP silently.
- Wait two full minutes before requesting a second code.
- Check spam or promotional tabs in your SMS app.
- Enable "Transactional" notifications for Messages on Chinese handsets.
- Use WhatsApp OTP if your number was ported recently.
- Verify SMSC with carrier support if the problem persists.
Wrong Password Errors
You are certain the password is correct. You typed it slowly. The error still reads "Invalid credentials". First, confirm caps lock is off — the field is case-sensitive. Second, check for a trailing space. Copy-paste from a password manager sometimes appends an invisible space at the end. Paste into a notes app first, delete the last character, then copy again.
If you changed the password on the desktop site but the mobile app still rejects it, clear the app cache. On Android: Settings → Apps → FairPlay → Storage → Clear Cache. On iOS: offload the app (Settings → General → iPhone Storage → FairPlay → Offload App), then reinstall. Offloading preserves your keychain entry so the new build picks up the updated credential.
FairPlay locks the account after five failed attempts for fifteen minutes. The lockout is IP-based, so switching from Wi‑Fi to mobile data (or vice versa) often restores access immediately. If you share a flat in Bangalore or a PG in Delhi, your flatmate's failed tries count against the same public IP. A quick toggle of airplane mode for ten seconds assigns a fresh IP on most 4G networks.
Forgot the password entirely? Use the "Forgot password" link on the login page. The reset link expires in twenty minutes. Open it in the same browser you intend to bet from — clicking the link in Gmail's in-app browser then switching to Chrome breaks the token. Set a new password of at least twelve characters, mixing upper, lower, digit, and symbol. Avoid "Mumbai123" or "RCB2024"; credential-stuffing bots try those first.
- Disable caps lock and strip trailing spaces.
- Clear app cache (Android) or offload and reinstall (iOS).
- Switch network to bypass IP-based lockout after five failures.
- Reset via the email link in the same browser you will bet with.
- Choose a unique twelve-plus character password.
Session Dropped Mid-Match
You placed a ₹2,000 live bet on Chennai Super Kings at 2.10. Two balls later the screen greys out, a toast reads "Session expired", and you are staring at the login screen again. The bet may or may not have been accepted. This is the most painful failure because money is on the line.
FairPlay's session cookie lasts ninety minutes of inactivity. "Inactivity" means no API calls — not just no clicks. If you left the match page open while checking WhatsApp, the heartbeat ping stops after the browser throttles background tabs. Chrome on Android aggressively throttles after five minutes. The fix: keep the match tab in the foreground, or enable "Desktop site" in Chrome's three-dot menu, which disables throttling for that tab.
Network handover is the second killer. Moving from your home Wi‑Fi in Pune to Jio 4G while walking to the balcony changes your public IP. FairPlay's security layer treats the IP shift as a hijack attempt and kills the session. The workaround: before the match starts, disable "Wi‑Fi assist" (Settings → Mobile Data → Wi‑Fi Assist off) so the phone stays on one network until you manually switch.
If the session dies, reopen the FairPlay app immediately. The native app maintains a persistent token that survives IP changes better than the mobile web version. Log in, navigate to "My Bets" → "Open", and verify the wager appears. If it shows "Void" or is missing, screenshot the bet slip timestamp (the app shows IST down to the second) and raise a ticket via FairPlay customer support within the hour. Agents can replay the server log and confirm whether the stake was deducted.
- Keep the match tab foregrounded or enable "Desktop site" to stop throttling.
- Disable Wi‑Fi assist to prevent mid-session IP changes.
- Prefer the native app — its token survives network handover.
- Check "My Bets → Open" immediately after re-login.
- Screenshot timestamps and contact support within sixty minutes if the bet is missing.
When Nothing Works — Escalate Properly
You have tried every step above. The OTP still ghosts, the password still rejects, the session still evaporates. Do not keep hammering the login button — that extends the lockout. Instead, gather evidence: screenshot the error, note the exact IST timestamp, record your device model, OS version, app version (Settings → About in the app), and network type (Jio 4G, Airtel Fiber, etc.).
Open a ticket through the FairPlay contact us page. Choose "Technical Issue → Login" as the category. Paste the evidence into the description box. Support replies typically arrive within four hours during IST business hours (09:00–21:00). If the issue is a known platform bug — they happen after major app releases — the agent will give you a reference number and an ETA for the hotfix.
While you wait, you can still access your account history, deposit and withdrawal logs, and responsible-gaming tools from the desktop site at fairplay.id using a different browser or incognito window. That endpoint uses a separate session store and often stays alive when the main login is broken.
One last tip: keep a small balance in your UPI-linked wallet (PhonePe, GPay, Paytm). If the app is down for maintenance — usually 02:00–04:00 IST on Tuesdays — you can still top up via the web deposit page at FairPlay deposit and be ready the moment the platform returns. No missed toss, no missed odds.
- Stop hammering login — it extends the lockout.
- Collect screenshots, timestamps, device and network details.
- Raise a ticket via Contact Us → Technical Issue → Login.
- Check account history on the desktop ID endpoint while waiting.
- Keep UPI wallet funded for instant top-up after maintenance windows.
Login failures feel personal when the match is live and the odds are moving. They are not. They are almost always a mix of carrier SMS latency, browser throttling, IP handover, or a cached credential mismatch. Run through the checklist above once, methodically, and you will be back in the game before the next strategic timeout. The chai will still be warm.
More on how we approach numbers is on about FairPlay, and the tools for setting your own limits are on responsible gaming.