What Is OTP SMS? Mobile Verification Explained
Resumo
Pixel’s announcement explains how OTP SMS verifies control of a phone number and traces a code from your server to a handset. It covers code length and retry limits, common delivery blockers such as sender registration and template issues, and when to choose SMS, passkeys, or authenticator apps.
DEV Community
What Is OTP SMS? How Mobile Verification Works
An OTP SMS is a text message carrying a one-time password: a short random code that works once and expires within minutes. Mobile verification uses that code to show that someone controls a phone number right now. It proves access to the number, not who the person is. This guide follows one code from your server to a handset, works out how many digits and tries you can safely allow, and explains why OTPs fail before they reach the handset. It ends with a decision map for choosing a channel and a checklist for choosing an OTP SMS service. Note: Key takeaways An OTP SMS shows control of a number at one moment. It does not establish identity, so don't treat it as KYC. Your server makes the security decisions when you run verification yourself. It generates the code, limits the tries, and judges the answer, while the network only carries the text. An OTP can fail well before the handset. Missing sender registration, template drift, the wrong category, or an unlisted URL can each stop a message. SMS is the reach option, not the strongest one. Keep it for coverage, and offer a passkey or authenticator app where the risk justifies the enrolment. What does OTP mean in an SMS? OTP stands for one-time password, also written as one-time passcode. TRAI's regulations define it as an automatically generated random number that authenticates a user's action for one transaction or session. In practice, the SMS reads something like this: Your Acme login code is 123456. It expires in 10 minutes. Do not share it with anyone. The word "password" misleads. You never choose this code or memorise it, and it has no value once used. Not every OTP is made the same way The name covers three different mechanisms, and many explainers blur them. HOTP and TOTP are the two standard algorithms, and a texted code usually works differently from both. NIST treats a texted code as an out-of-band secret rather than an OTP authenticator, and the distinction changes your threat model. Type Where the code comes from Shared in advance Travels over the network SMS OTP Your server draws a random value for this one request Only the phone number Yes, in the SMS HOTP (RFC 4226) Secret key plus a moving counter A secret key No TOTP (RFC 6238) Secret key plus the current time, with a default 30-second step A secret key No So the 30-second countdown belongs to authenticator apps. An SMS code lives as long as your server allows. What does mobile verification actually prove? Mobile verification proves that whoever typed the code could read a message sent to that number within your time limit. That is useful, and it is narrower than people assume. It says nothing about the person's legal name, and a number can move to a new SIM or a new owner. Match the check to the question you are really asking: Your question Is SMS OTP enough? What to add Is this a working number the user can reach? Usually yes Format it in E.164 first Is this the same person who owns the account? Only for lower-risk accounts A password, passkey, or device check Did the customer approve this payment? One factor at most A second factor, as RBI's rules require Is this person who they claim to be? No A KYC process with identity evidence If you're in India, there is also a government route for the first question. The 2025 telecom cyber security amendment created a Mobile Number Validation platform that checks an identifier against operator subscriber records. Entities may be directed to use it or may seek permission. MediaNama reports that the final rules left fees to DoT's portal. We could not confirm a public launch date, so treat it as something to watch. How does one OTP travel from request to approval? Eight steps cross three parties. The two highlighted steps are where you win or lose on security. At step 2, generate and store carefully. Draw the code from a cryptographically secure random generator. Don't keep codes in plaintext. Store a keyed hash with the expiry and try count. Use a server-side secret...

Powered by Readybot.io