Prompt
How do I replace SMS OTP with passwordless sign-in?
Latest observation
Oct 28, 2026
OpenAI APIWeb search: off
Replacing SMS OTP with passwordless sign-in usually means moving from a phone-number-based one-time code to a stronger authentication method that doesn’t rely on SMS. The best approach depends on your user base and app platform, but the common options are:
Good passwordless options
-
Passkeys (best overall)
- Uses device biometrics or PIN via WebAuthn/FIDO2
- Resistant to phishing and SIM-swap attacks
- Great for web and mobile apps
-
Email magic links / email OTP
- User enters email, receives a link or code
- Easier to adopt, but less secure than passkeys
-
Authenticator apps (TOTP)
- Time-based codes from apps like Google Authenticator
- More secure than SMS, but still requires users to type codes
-
Push-based login
- User approves a login on a trusted device
- Good UX, usually combined with a mobile app
Recommended migration path
A practical rollout is:
- Keep SMS temporarily as fallback
- Introduce passwordless as the default
- Let users enroll a passkey or email login
- Gradually deprecate SMS for new sign-ins
- Use SMS only for account recovery if needed
- Eventually remove SMS entirely if your risk model allows
If you want true passwordless
The strongest setup is:
- Primary login: passkeys
- Recovery: backup codes, email recovery, or support flow
- Optional fallback: SMS only during transition, not as the main method
High-level implementation steps
-
Choose an auth standard
- Web/mobile: WebAuthn/passkeys
- If starting simpler: magic link via email
-
Add enrollment flow
- Ask users to register a passkey after login
- Store public keys and credential metadata on your backend
-
Add authentication challenge
- Server generates a one-time challenge
- Client signs it using passkey/private key
- Server verifies using stored public key
-
Handle recovery
- Backup codes
- Secondary email
- Support-assisted recovery for high-risk accounts
-
Update product UX
- “Sign in with passkey”
- “Use email link instead”
- “Turn on biometric sign-in”
Important security notes
- Don’t use SMS as the primary factor if you can avoid it
- Never store OTPs in plaintext; hash them and expire them quickly
- Rate-limit login attempts and enrollment
- Protect account recovery flows carefully
- Add device binding and risk checks if you support multiple methods
Example migration strategy
- Phase 1: Offer passkeys alongside SMS
- Phase 2: Default to passkeys, SMS only as fallback
- Phase 3: Encourage users to enroll recovery options
- Phase 4: Remove SMS login for most users
If you want, I can also give you:
- a technical architecture
- a step-by-step WebAuthn/passkey implementation
- or a migration plan for a specific stack like React, iOS, Android, Firebase, Auth0, or Cognito