Create your 10cricklive account in India
Create your account in a short form, confirm the details you enter, and move into the same login flow we use for Indian sign-ins.
What happens when you submit
When you submit the form, we check the basics first: name, mobile number, and the login details you choose. If something needs another look, the form points it out before you move ahead, so you do not lose time guessing what went wrong. Once the account is set, you can return with the same login
on mobile or desktop and keep the same profile and settings. We keep the flow simple because most people want to finish registration once and get back in without repeat steps.
-
Quick form check We catch mismatched fields before the submission goes through, so you can correct them on the spot instead of waiting for a later problem with access or account recovery.
-
Secure sign-in Your login moves through encrypted pages, and the same protection stays in place when you come back later from a new device or browser. That helps keep access tied to the details you entered.
-
One login on devices Use the same account on phone or desktop without creating a second profile. That keeps your details, preferences, and access history together in one place, which makes future sign-ins quicker.
-
Help during setup If the code does not arrive or a field refuses to pass, our team can check the issue and tell you the next step before you try again.
Your details are protected with encrypted, secure access.
UPI, Paytm and PhonePe for registration
After registration, your wallet setup stays close to the form so you do not need another long step.
UPI
Paytm
PhonePe
Help while you open your account
If anything slows down during registration, our help channels can step in before you restart the form. Use live chat for quick fixes, or send the details through the help form if you need a careful look at a number, code, or mobile mismatch. We keep the same support style on phone and desktop, so you can finish the account setup from whichever device you started on.
Live chat
Open live chat if you need a quick answer while the form is still on screen. We can look at login errors, code delays, or a field that will not submit.
Help form
Send the problem through our help form when you want a careful check after the session ends. Add the mobile number and the exact step where the process stopped.
Email follow-up
Use email for a threaded reply if your sign-in question needs more detail or a screen capture. We keep the thread on the same account so you do not repeat the basics.
Checks that protect your login
Registration is only useful if the account stays under your control after you create it.
Encryption on forms
Registration pages are sent through encrypted connections, so the details you type move in a protected session instead of plain text. That matters when you are entering a mobile number, password, or recovery detail.
Identity match checks
If a withdrawal or profile change comes later, the account record helps us match the request to the same details you used at registration. That reduces confusion when more than one screen is involved.
Password control
You choose the login password, and we encourage a mix of letters and numbers that is hard to guess but easy for you to remember. You can update it from account settings when needed.
Session monitoring
If a sign-in looks unusual, the session can pause and ask for another check. That helps keep the account from being opened by someone who does not know your details.
Data minimisation
We ask for only the details needed to create and access the account. Keeping the form lean lowers the chance of errors and makes future updates easier to manage.
Device alerts
When you use a new phone or browser, the login flow can show a notice before it finishes. That extra step helps you spot access you did not start yourself.
Questions about registration and access
These answers focus on the first steps after you decide to create an account. We cover the form, the verification code, sign-in on a new device, and what to do when a field or code does not behave as expected. If local law does not allow access where you are, you should not use the form.