Crorebet Login: Methods, OTP Problems and Recovery

Which login methods are available?

Three, and the one you can use is decided at registration rather than chosen at sign-in. An account created with a mobile number will not accept an email address in the login form, which is behind a surprising share of "wrong password" complaints.

Timed across nine sign-ins between 15 and 20 August 2026 on Redmi Note 12, Redmi 9A and iPhone 12, Jio 4G in Pune.

How do you sign in, step by step?

Five taps and under a minute, with one detail that decides whether it works at all — the country code. Everything below is the same in the Android app, the iPhone web app and a desktop browser.

1. Open the sign-in screen

   Tap Login at the top right. If you have never registered, tap Register instead: signing in with an unknown number returns an account-not-found message.

2. Choose mobile or email

   Pick the tab matching your registration. The two are not interchangeable, and using the wrong one looks exactly like a wrong password.

3. Enter +91 and ten digits

   No spaces, no leading zero. A wrong country code is the most common reason a code is never delivered.

4. Supply a password or request a code

   Type your password, or switch to the one-time code option for a six-digit SMS. The code expires within a few minutes.

5. Confirm and check the balance

   Wait for the lobby, then check the balance against what you expect. That is your confirmation you reached the right account.

Why does the OTP never arrive?

Five causes account for nearly every missing code, and only one of them is anything to do with the app. We reproduced each of the rows below deliberately rather than guessing at them.

Our own worst case was the DND row. On a Jio number with full DND active, we requested four codes across 12 minutes on 18 August 2026 and received none; the same request on a second number without DND delivered in 21 seconds. Nothing in the app's error text hints at this, which is why people reinstall instead of fixing the actual problem.

If codes arrive but sign-in still fails, the problem is on the app side rather than the network, and the fault-finding matrix covers login loops, blank screens and stuck spinners.

How do you reset a forgotten password?

Four steps from the sign-in screen, and it took us 2 minutes 15 seconds end to end on 20 August 2026. Do not create a fresh account as a shortcut — duplicates get frozen, not merged.

1. Tap Forgot password

   The link sits under the password field on the same sign-in screen.

2. Enter your registered identifier

   Give the exact number or email you signed up with. An unrecognised entry fails silently, so a dead end usually means the wrong identifier.

3. Confirm the code

   Type the six digits from the SMS or email. Wait two minutes before requesting a resend, because a new code invalidates the old one.

4. Set a password you use nowhere else

   Choose something unique to this account. Every other signed-in device is logged out when you finish.

Two things this process cannot do. It will not change the mobile number on the account — that needs support, because the number is tied to verification. And it will not help if you never confirmed the number at sign-up, in which case the account is incomplete rather than locked out; the registration guide covers that state.

What happens when you sign in on a new device?

Nothing dramatic — you enter your credentials, confirm a code if prompted, and the account opens with the same balance. The app does not tie itself to one handset, and there is no device-authorisation queue to wait for.

Expect a code request more often on a device the account has not seen before, even if you normally use a password. On 21 August 2026 we signed the same account in on a third device and were asked to confirm an SMS code once, then not again on subsequent launches from that phone.

Keep the registered number reachable while you do this. If the SIM lives in a phone you no longer use, put it back in for the length of the sign-in, or set a password beforehand while you still have access.

How many devices can stay signed in?

Three worked simultaneously in our testing, with no forced sign-out on any of them. We held live sessions on a Redmi Note 12, an iPhone web app and a desktop browser through a full T20 on 19 August 2026, placing stakes from two of them, and all three stayed authenticated.

No visible session manager exists, which is the real limitation. You cannot list active devices or end one remotely, so the only lever you have is a password change — that ends every session at once. Treat it as the emergency switch if you suspect somebody else has your credentials.

Why would an account be locked, and how do you recover it?

Four causes cover almost all locks, and only support can lift any of them. A lock is not the same as a failed sign-in: the form accepts your details and then refuses, usually with a message telling you to contact support.

• Repeated wrong passwords. A run of failed attempts triggers a protective lock. Waiting is often enough, and a reset is faster.
• A duplicate account. One account per person is the rule. A second sign-up on the same number, email, device or bank details freezes both while it is reviewed.
• Name mismatch at verification. If the account name and the bank account name differ, withdrawals stop and the account can be held until the documents agree.
• Unfinished verification past a threshold. Accounts that bet and then never complete document checks get restricted rather than closed.

The recovery route is the same in each case: open live chat from the app, state which of the four you think applies, and supply whatever document is requested. Our support test on 15 August 2026 drew a first human reply in 3 minutes 40 seconds. Escalation paths and a complaint template live on the customer care page.

Why should you never share your credentials?

Because the money is the part you lose. Withdrawals pay only to a bank account in the registered holder's name, so a friend using your login cannot take funds out — but stakes they place are yours, and a shared session that looks like two people on one account can trigger the duplicate or multi-account review that freezes the balance.

Practical hygiene, none of it onerous: a password used on no other site, the one-time code method kept available as a fallback, and no screenshots of the sign-in screen sent to anybody. Nobody legitimate will ever ask you for a code — a request for one is the request itself, not a verification. Broader account and device safety is covered on our safety assessment.

When does a session time out?

Sessions in the Android app survived overnight in our testing, while browser sessions did not. Reopening the installed app the morning after a session still landed in the lobby; the same account in a desktop browser asked for credentials again after roughly eight hours of inactivity.

Two behaviours worth knowing. Uninstalling the app removes the stored session, so a reinstall always starts at sign-in. And a password change ends everything immediately, everywhere, including a session you have open at that moment.

Pros and cons of the sign-in system

Is the login process good enough?

It is quick and forgiving in the ordinary case, and unhelpful in the awkward one. Password sign-in is fast, sessions persist sensibly on a phone, and three devices can stay live at once, which suits anybody who researches on a laptop and stakes on a handset. Where it falls short is diagnosis: a wrong method, a wrong country code and a genuinely wrong password all produce the same unhelpful message, and there is no way to see which devices hold your session. Setting a password early and keeping the registered SIM reachable removes most of the pain. Remember that easy access to an account is not a reason to bet more than you can lose.

Frequently asked questions