My FairPlay Login — ID or OTP Route, Then a Live Account Menu

People type "my FairPlay login" for two quite different reasons. Some have a user ID written in a notes app and just want the sign-in box. Others registered months ago with a phone number, never looked at the ID again, and now only know the mobile. FairPlay accepts both, which is convenient, but the two routes behave differently once something goes wrong.

Our own habit? User ID first. It skips the SMS wait entirely, and on a crowded match evening those seconds count because the market you wanted may have moved. The OTP route is the backup, the one you reach for when the password is gone.

Mobile-with-password is the in-between option that trips people up most. The box that says "User ID" on FairPlay usually takes a 10-digit mobile too, but only if that mobile is the one saved on the account. Type it without the country code, without spaces. If the ID was issued through WhatsApp rather than the signup form, the registered number is the one you messaged from — check that before assuming the account is broken.

Most regular players do not type anything at all. They keep FairPlay signed in on one phone and open it straight into the account. That works well. It also has a few catches that show up at the worst time, usually right when an over is about to start.

There are three places a saved sign-in can live:

• The browser. Chrome or Safari offers to remember the password after your first FairPlay login. Accepting it fills the ID and password next time, on that address only.
• The Android app. The FairPlay APK keeps you signed in between sessions until you log out or the session times out. Install steps live on the FairPlay app page.
• The iPhone home-screen shortcut. It behaves like the browser underneath, so the saved password comes from Safari's keychain.

The catch with the browser is the address. A password saved on one FairPlay mirror is filed under that domain. Open a different mirror (support hands out a new one when an old address gets blocked) and the browser has nothing to fill, even though the account is identical. Nothing is wrong with the ID. The browser just does not know the two addresses belong to the same place.

Second catch: after you change your password inside FairPlay, the browser keeps offering the old one for a while. Accept its "update password" prompt when it appears, or delete the stale entry by hand. Otherwise the autofill keeps failing and it looks like a lockout.

Moving my FairPlay login to a new phone

Old phone first, while its still working. Open FairPlay there, note the user ID shown in the account menu, and confirm which mobile number is registered. Then:

1. Move the SIM (or keep the same number) so the OTP route still reaches you.
2. On the new phone, open the current FairPlay address from support and sign in with Route A.
3. Reinstall the Android app or re-add the iPhone shortcut; the same details work there.
4. Log out on the old handset before you sell it or pass it on, and clear its saved passwords.

Changing the number at the same time as the phone is where it gets awkward. Do the two jobs on different days if you can: phone first, number later, through support.

One more small thing. Some people save the sign-in and then forget the actual password completely, which is fine until the phone is replaced. Keep the user ID somewhere you will find it later (a note, an email to yourself). The password can be reset through the registered mobile; the ID is harder to dig up if nobody wrote it down.

The "my" in my FairPlay login is really about what comes after the password. Once in, the account menu holds four screens you will use again and again. Labels shift slightly between mirrors and between the app and the browser, but the contents stay the same because it is one FairPlay account underneath.

• Balancemoney available to stake right now
• Open betspositions not yet settled
• Statementevery credit and debit, dated
• Passwordchange it from inside the account

Balance, minus what sits in open positions

The balance on FairPlay is what you can place right now. On the cricket exchange, money tied up in a lay bet or an open back bet is held aside, so the figure drops when you place and climbs back when the market settles. People sometimes read that dip as missing money. It is not; check open bets before raising it with support. Deposits by UPI, IMPS or bank transfer show here once credited, and the low minimum is shown in the cashier itself.

Open bets still waiting on a result

This list shows every position still waiting on a result: match odds, bookmaker, fancy lines, casino rounds that have not closed. It is the first screen to open after a dropped connection mid-match, because it tells you whether the bet actually went through before the network died.

Statement, the dated ledger

The statement is the running ledger: deposits, withdrawals, settled wins and losses, bonus credits. Filter by date when you are checking a single day. Support asks for the statement line (date and amount) whenever a payment question comes up, so a screenshot saves a round of messages.

Swapping the FairPlay password from inside

If your FairPlay ID came with a temporary password, change it here on the very first login. Pick something you do not use on any other site. After the change, every other device that was signed in may ask for the new password. Normal.

Log out, properly

Closing the tab is not logging out. On a phone you own that barely matters. On anything else, open the account menu and use the log-out option at the bottom, then check that the FairPlay home screen shows the sign-in buttons again rather than your balance. Two seconds, and it closes the one gap a saved session leaves open. A quick way to test it: reopen the address. If it asks for the ID, you are out; if it shows your balance, you are not.

Withdrawals also start from this area, but the timing rules (same-name bank, KYC first, why the first payout can run longer) belong on the FairPlay withdrawal time page, so we will not repeat them here.

General sign-in errors (wrong password, a locked account after too many tries, the page refusing to load) have their own table on the main FairPlay login page. This section covers a narrower set. These are the problems that appear when someone moves between the ID route and the mobile route, or between devices, and the account itself is fine.

The zero-balance one causes the most panic by far. It nearly always happens the same way. Someone lands on a new FairPlay address, sees a sign-up button before the login button, and registers again with a new ID. The fresh account is empty, naturally. The old account, with the old money in it, is untouched. Sign out and use the original user ID. Then tell support about the duplicate so it does not confuse things later.

For the OTP problem, the order matters. You cannot change the registered mobile from a login screen, only from inside the account or through support, so you need Route A working first. If both the password and the old SIM are gone, message support on WhatsApp at +91 81097 11726 from the new number with your user ID, and expect them to ask a few questions before they change anything. That is slower then a normal login, but it is the only safe way to move an account to a new number.

Addresses change; the account does not. When an Indian block knocks out the FairPlay address you had bookmarked, support passes on another one, and the user ID and password you already own open it with the balance intact. Pro, global, club, live, 365, 247: different address bars, one login behind all of them. The FairPlay Pro page explains what each address type is for.

Two rules keep this painless. Open the address support gave you, not whatever a search engine throws up first, because copycat pages exist and they are happy to collect a password. And sign in, never sign up, when you arrive somewhere new; the duplicate-account mix-up above starts exactly there.

The app works the same way. The FairPlay APK on Android and the home-screen shortcut on iPhone are simply other doors into the account you already have, so there is no separate app ID to register. If you need a fresh account for someone else in the house, that is a new signup with their own mobile — the FairPlay register page lists the fields.

A composite, pieced together from the kind of messages support sees on match nights.

1. Around 11 pm, Jio data, second innings under way. The player taps the home-screen shortcut. The saved password fills, but the page will not open, because the address it points to has been blocked since last week.
2. Fix the address, not the account. They message support, get the current FairPlay address, and open it in the same browser. Nothing fills in automatically, because the browser has filed the password under the old domain.
3. Route A. User ID typed by hand, password typed by hand. In. Balance is the same figure as yesterday, which confirms it is the right account.
4. Open bets first. A back bet placed before the address went dark is sitting there, unsettled, exactly as it was. The chase is on, so they leave it.
5. Housekeeping. They save the new password entry, delete the old shortcut and add a fresh one for the new address. Maybe two minutes of fiddling in all.
6. After the match. The bet settles, the statement shows the credit with the date, and they request a withdrawal to the bank account in their own name.

Nothing in that evening needed the OTP route. It would have, though, if the phone had been a new one with no saved entry and the password lived only in the old browser. That is the whole case for writing the user ID and password down somewhere safe: the day you need them is the day autofill cannot help.

Could it go wrong in other ways? Sure. The SMS can lag on a congested tower, and the session can drop if a family member opens the same FairPlay ID on the the other phone. The fixes are in the table above. In practice the address change is by far the most common snag, and it is also the easiest to sort.