- Only SMS and Voice charges apply
- Save more with customized pricing and committed-spend contracts
By submitting this form, you agree we may contact you in the manner described in our Privacy Policy.
Boost OTP Conversions with Verify API
Get effortless SMS verification with robust fraud control delivered via our all-in-one API.
Fraud Shield is your armor against SMS pumping attacks
Automatically identify, intercept, and prevent fraudulent messages.
-
Auto-pilot mode:Fraud Shield monitors your messaging patterns, establishes thresholds for each country, and automatically alerts you when a pattern looks unusual.
-
Manual override:Fine-tune and override messaging throughput thresholds for each country.
-
Savings calculator:In-built reporting to evaluate your cost savings from preventing fraud attacks using the Verify Fraud Shield savings calculator.
No Additional Costs
 |
$0 Authentication fee
|
 |
No number purchases or rentals
|
 |
No compliance fees
|
 |
No extra cost for Fraud Shield
|
More reasons to choose Plivo's Verify API
Pre-approved templates optimized for conversions
Ready-made message templates are pre-approved and designed to boost conversions.
Reduce implementation time by up to 90%
Faster integration with less development hassle.
Plivo is enterprise grade
Secure cloud communications
Say goodbye to fraud with Plivo's Verify API – where security meets success
Verify API FAQs
Verification and authentication are typically used interchangeably, but they aren’t the same thing. Verification occurs at signup. It ensures that a user is who they say they are. Authentication occurs every time a user logs in. Plivo Verify can be used for both verification and authentication.
Both are great options, but they have different benefits.
- SMS verification is fast and easy for users to complete.
- SMS verification has great reach: almost all mobile devices support SMS functionality.
- Voice verification provides an accessible alternative for individuals who may have visual disabilities.
- Voice verification works best for customers who only have access to a landline, as landlines don’t support SMS.
- Voice verification can be a reliable alternative or fallback in cases of delays or failures in SMS delivery. Voice is prioritized on carrier networks, resulting in higher delivery rates compared to SMS.
- Voice offers significantly richer data points for analytics, enabling users to gain deeper customer insights and optimize conversions.
Two-factor authentication, or 2FA, refers to the use of two different types of authentication factors to verify a user's identity. These factors can come from any of the following three categories.
- Something you know: This could be a password, PIN, or the answer to a security question.
- Something you have: This could be a smartphone (to receive an SMS or use an authenticator app), a smart card, or a hardware token.
- Something you are: This refers to biometric data, like a fingerprint, facial recognition, or retina scans.
SMS verification adds an extra layer of security by using two-factor authentication (2FA) to verify users’ identities. SMS verification helps ensure that the person trying to access the account or register for the service has a mobile device tied to that account. This can help prevent unauthorized access, even if someone gains access to the user's username and password.
Here are the steps in the SMS verification process:
- A user provides their mobile number to log in to an account or register for a service.
- The system then sends a request to Plivo to initiate the SMS verification process for that mobile number.
- Plivo generates a one-time password OTP) — a unique code that can be used for this one instance for verification.
- The OTP is sent via SMS to the user's mobile number. Plivo also keeps a copy of the OTP to check it against the user's input.
- The user receives the OTP in an SMS message on their phone and enters the OTP into the website or application to which they’re trying to log in or sign up.
- The user’s entry is is sent to Plivo. Plivo verifies whether it matches the OTP that was originally generated and sent to the user.
- If the OTPs match, Plivo verifies the user. If not, Plivo may resend the OTP,or the user may have to initiate the process again.
- Once the user is verified, they can proceed to log in to their account or complete their registration.