How OTP delivery works for your end users
| swype |
|
WALLETS & SECURITY • OTP
How OTP delivery works for your end usersOne-Time Passwords are delivered by email, not SMS. Here's what that means for your onboarding flow and support scripting. |
|
|
AUDIENCE B2B Clients |
DELIVERY CHANNEL Email only |
SMS OTP Not supported |
Summary: One-Time Passwords are delivered to end users via email. There's no SMS or push-notification channel for OTP delivery today — email is the only path.
| ① |
What this means for your onboarding flow |
Since email is the only OTP channel, the accuracy of the email address you collect during onboarding directly determines whether your end user can complete authentication at all:
| ● | A typo'd or unreachable email address blocks login, not just notifications |
| ● | Don't design a UX flow that assumes SMS as a fallback channel — it doesn't exist today |
| ● | Most "can't log in" or "didn't get my code" tickets trace back to spam filtering or a wrong email on file, not a system issue |
|
Important Equip your first-line support to check spam folders and verify the email on file before escalating "missing OTP" tickets to Swype — it resolves the majority of these cases without needing our involvement. |
Seeing repeated OTP delivery issues?
Let us know if it's affecting a specific email domain or region.
Contact Support →