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.

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

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?

What is the difference between 2FA API and tyntec’s OTP SMS API?

tyntec’s two-factor authentication (2FA) API enables your business to seamlessly capture and confirm your users’ phone numbers as part of the sign-up and 2FA processes. It is a feature-rich, programmable API that detects the phone number type (mobile or landline) and sends the passcode via the appropriate channel (SMS or text-to-speech).

In addition, tyntec’s 2FA API offers:

  • PIN generation, verification and expiration handling

  • The ability to customize language and sender ID to specific locales

  • Customized message and call templates, PIN length and time retry configuration

  • Pay per successful verifications.

At the same time, tyntec’s SMS API enables you to send SMS messages globally. The SMS API can be used to send One Time Passwords (OTPs) globally, however it lacks verification features that assist companies in the 2FA process.

If your business has authentication capabilities in place and just need the OTP transmission, the SMS API can be ideal (though its business model is pay per message). In case your business prefers to get a verification service and/or requires a pay per successful verification, the 2FA API may be the best choice.