SMS based phone verification mechanisms are riddled with fraud due to SS7 hacking, text forwarding, malware, and social engineering.
Fraudsters/bots creating fake accounts using invalid phone numbers lead to a bad experience for your real customers.
Slow deliveries and bad consumer experience lead to high drop-offs during registration or onboarding.
After downloading your app, the user chooses to sign up with their personal profile information.
The app prompts for the phone number to set it up as the primary identifier for the user. However, this number needs to be verified to ensure it's in possession of the user.
Invoke Phone Number Verification API with the user's phone number to check if the phone number provided by the user is indeed in their possession.
If phone verification API responds with request to fallback to SMS, change the interface to collect SMS pin code and invoke the verify Code API to verify the code.
That's it! Verification is now complete, proceed to the next step of your user on-boarding process. In the scenario the API responds with failure code, send the user back to enter their correct phone number.
No drop-offs and increased conversions as a result of improved UX
Not susceptible to forwarding, malware, SMS Hacking etc.
Shaves on average 30 seconds compared to SMS based methods
Seamlessly conduct two factor authentication for your users prior to high value transactionsSEE USE CASE ⟶
Protect your users from account takeovers by bad actorsSEE USE CASE ⟶
Offer seamless experience to your users without sacrificing on securitySEE USE CASE ⟶