Traditional two factor authentication methods disrupt the flow to complete authentication before letting the user finish their task.
SMS messages are susceptible to phishing, malware attacks, and social engineering. Thus making them less reliable as a second factor.
Traditional SMS, App or USB based methods require heavy user involvement to setup the 2FA process.
This could be an action like transferring money, paying a bill, buying a product or even changing their password.
Use the phone number of the user in your database and invoke the phone verification API to check if the phone number provided by the user is in her/his 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 the high value transaction. In the scenario, the API responds with failure code, step up the authentication for the user in the manner appropriate for your business.
The user's mobile network serves as the 2nd factor in the two factor verification process. This network is not susceptible to bad actors.
No user interaction is needed and the 2FA verification can be completed in the background, while the user is executing their high-value transaction.
Zero initial setup is needed to get the 2FA operational. Simply make the API call from the app or mobile-web when you want to conduct 2FA.
Check if the phone number provided by the user is in their possession.SEE 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 ⟶