OTP Not Received: What to Check, In Order
A one-time code that never arrives is the most common access failure, and it is almost never the operator's fault. Codes are blocked by carrier filters, phone settings, message filters and by the very act of requesting them too many times. This guide walks through the causes in the order that resolves most cases fastest.
First: is the number the right one?
Check the last two digits of the number registered on the account. A second SIM, a number from another country, or a number changed after a phone upgrade are the three usual mismatches. If the account was opened with a number you no longer hold, no amount of retrying will help — recovery goes through support, with proof of identity.

SMS code not arriving: is it being filtered?
- Spam filters — on Android, check the spam and blocked folders in the messages app. Codes from unknown senders are exactly what filters hide.
- Unknown senders — some apps move short-code messages to a separate "unknown" thread.
- Do not disturb — does not block SMS, but blocks the notification, which makes the code look absent.
- Second SIM — if two SIMs are active, confirm which one receives messages and whether the app reads the right one.
OTP troubleshooting: rate limits and cooldowns
Requesting a code five times in a minute triggers a cooldown. The timer is usually counted from the last request, so retrying restarts it. The practical rule: request once, wait two minutes, request again — and if the second attempt fails, stop and use another route instead of escalating.
Fourth: the alternatives that exist for a reason
| Route | When it works | What it needs |
|---|---|---|
| SMS code | Default route | Registered number, signal, no filter |
| Email code | When SMS is blocked or the number changed | Access to the registered mailbox |
| Authenticator app | After it was set up in advance | Setup before the problem, not after |
| Support recovery | Number lost, mailbox lost | Identity documents and a written request |
What never helps
Asking someone else to receive "your" code. Installing a "code forwarder" app. Sharing the OTP with anyone who asks — including a person claiming to be support. Support never needs the code itself: they need to know a code was sent and did not arrive. A request for the code is the single clearest sign of a scam call, and it is covered in fake support schemes.
When to stop and write instead
If two attempts on two routes fail, the account is in a state that self-service cannot fix: a number change, a blocked session or a pending verification. At that point a written request with the right facts resolves it faster than a third attempt — the request builder assembles those facts into a message.
Prevention that costs nothing
- Keep the registered number and mailbox current, before a problem appears.
- Set up an authenticator app while access still works.
- Save the recovery codes if the account offers them, offline.
- Do not use a number you may lose — a prepaid SIM recycled after inactivity is a common cause of permanent lockout.
Why codes fail at the carrier level
Short-code messages travel a different route than ordinary SMS. Some carriers filter or delay them, some prepaid plans block international senders, and a number that was recently ported can sit in a routing gap for days. None of this is visible to the operator, which is why support often answers "the code was sent" and is telling the truth: it was sent and it did not arrive.
Three carrier-level causes cover most cases: a DND (do not disturb) service active on the number, a sender ID blocked as spam at the network level, and a plan that does not accept application-to-person messages.
Testing the route without the app
- Send a message from another phone to your own number and confirm it arrives.
- Ask the operator to resend the code once, then wait two minutes before a second attempt.
- Try the email route if the account has one — it uses a completely different path.
- Put the SIM in a second phone: if the code arrives there, the problem is the device, not the network.
That fourth test is the one that separates device problems from carrier problems, and it takes two minutes. Most people skip it and jump to a support ticket that cannot be resolved because the cause was never identified.
Device settings that hide the message
- Message categorisation — newer Android versions move unknown senders into a separate tab.
- Blocked numbers — a number blocked in the past for spam can be the short code.
- Third-party message apps — some do not show short-code threads by default.
- Dual-SIM defaults — messages can arrive on the SIM the app is not reading.
When the number itself is the problem
A prepaid number that is not used for a period can be recycled and reissued to someone else. If the account was registered with such a number, the code will go to a stranger — and no troubleshooting will fix it. The only route is recovery through support with identity documents, which is slower than a code but is the only route that ends. Details are on the KYC documents page.
Reducing the chance of a repeat
Move the second factor to an authenticator app while access still works. Add a recovery mailbox you control and check once a month. Keep a written note of the registered number and the date it was last changed — the two facts support asks for first.
Joya9 sends codes to the number registered on the account; a recycled prepaid SIM is the one cause no retry can fix.
Continue reading
The other sections cover account, app, VIP, betting, bonus and payment questions.