FAQ | Authenticate

Utilize tyntec’s FAQs to help solve any issues you may have. Additionally, learn about cloud communications, CPaaS, SMS for business, authentication, and more. If any questions arise while reading, don’t hesitate to contact us.

How Does the 2FA API Work?

FAQs

Authenticate

Getting Started

Overview

How Can I Create My tyntec 2FA Account?

How Does the 2FA API Work?

Why Should I Use SMS for Authentication?

What Are the Benefits of Using Phone Numbers As a Digital Identifier?

What Usecases Does the 2FA API Support?

What Is the Difference Between 2FA API and tyntec’s OTP SMS API?

Can I Use the 2FA API With Any Number in the World?

How Much Does tyntec’s 2FA API Cost?

Is There a Charge for Additional Verification Attempts?

How Long Does It Take to Verify a Phone Number With tyntec’s Two-factor Authentication Codes?

How Are PIN Codes for 2FA Generated?

What Is the Length of a 2FA PIN Code/ One-time Password?

Can I Provide My Own 2FA Codes?

How Can I Retry a Verification Attempt?

What Is the Validity Period for 2FA API’s PIN Codes?

How Many Times Can a Customer Enter a PIN Code?

Where Can I See the Status of a PIN Code/otp?

How Do I Map the PIN Code/OTP the Customer Enters for the Original Request?

What Should I Do If I Haven’t Received a 2FA PIN Code?

Why Is My 2FA SMS/TTS (Text-to-Speech) Call Not in the Primary Language of the Destination Country?

What Happens If the Line Is Busy or There Is No Answer When Receiving a TTS Call?

How Do I Know Whether TTS or SMS Will Be Used?

How does the 2FA API work?

The 2FA API works like this:

  1. The user registers on your website or app and provides a mobile phone number for verification

  2. tyntec’s API automatically chooses the channel to send the verification code (SMS or voice call/text-to-speech). Alternatively, the enterprise can give the user the option to choose

  3. Both SMS and voice trigger the enterprise’s web back-end and calls the tyntec 2FA API at the phone number provided.

  4. tyntec sends the user a unique one-time password via SMS or voice call

  5. The user enters the one-time password (OTP) on the website or app to verify their identity

  6. The enterprise’s back-end sends an API call to the tyntec 2FA service and tyntec replies, confirming whether the OTP entered by the user is correct or not

  7. If the OTP is correct, the website back-end authorizes the registration

For more information, check out this video on how the 2FA API works and the features it provides.