Question
What are the pricing models for the Vonage Verify API V1 (Legacy)?
Applies To
- Verify API V1 (Legacy)
- Pricing
Answer
The Vonage Verify API V1 (Legacy) has three unique pricing models.
-
Verify Success
- You are only charged for successful conversions based on the country you are sending the traffic (meaning the PIN code you gave us matches the one returned by the end-user) regardless of which channels are being used, but there is no charge for unsuccessful attempts.
- Verify Success is only available to enterprise customers sending high volumes of 2FA traffic.
- Traffic to high-risk countries is unavailable.
-
Verify Conversion
- This is the default pricing model.
- A fixed platform fee is charged for successful conversions + messaging, and voice rates for every SMS or TTS sent as part of the request.
- This is ideal for customers who need to automate the entire verification process including PIN code management and auto-failover.
- Traffic to high-risk countries is unavailable. Managed customers sending high volumes should contact their account manager.
-
Verify Request
- A fixed platform fee is charged for each verification request + messaging, and voice rates for every SMS and TTS sent as part of that request.
- This is ideal for customers who want more control of the verification process, including the ability to manage their own PIN code and workflow failover sequence.
- Traffic to high-risk countries is unavailable. Managed customers sending high volumes should contact their account manager.
Here are a few simple guidelines that you can use to minimize costs:
- Ensure your application clearly explains to the end-users that a verification will take place, for example, require their consent for it to start by placing a button.
- Once the end-user has acknowledged they want to start the verification, immediately display a screen where they can enter the PIN code.
- We recommend adding a rate limit to the amount of verification attempts that can be initiated for a particular phone number.
Additional Information
The pricing model is slightly different in Verify API V2, more details can be found here.
Articles in this section
- What is the Verify Anti-Fraud System?
- Error 15 on Verify API Request
- Can I use Verify with any number in the world?
- Understanding the error code 409 "A template fragment for this channel and locale already exists" when creating a Fragment for Custom Template in Verify API V2.
- What are the charges for using Verify API V2?
- Where do I find the Verify API Voice Call Logs?
- How fast can I send Verify API requests?
- Can I provide my own PIN/Code numbers in Verify API v2?
- How do I find the Vonage Verify API Request IDs?
- Error 20 on Verify API v1 Request