Question
What are the pricing models for the Vonage Verify API V2?
Applies To
- Verify API V2
- Pricing
Answer
The Vonage Verify API V2 offers two distinct pricing models tailored to different customer needs:
1. Verify Success
• Charges apply only for successful conversions, determined by a match between the PIN code provided by the application and the one entered by the end
• Pricing is based on the destination country, regardless of the channels used in the workflow.
• Unsuccessful attempts are not charged, with one exception: If the Silent Authentication channel is used, events with a "Rejected" status are charged as well since they are considered legitimate authentication attempts.
• This model is available exclusively to enterprise customers handling high volumes of two-factor authentication (2FA) traffic.
• Traffic to high-risk countries is not supported.
2. Verify Conversion (Default Model)
• A fixed platform fee is charged for successful conversions.
• Channel fees (SMS, TTS, WhatsApp, Email, Silent Authentication) are applied based on usage, regardless of conversion outcome.
Ideal for customers who:
• Require full automation of the verification process, including PIN code management and failover handling.
• Prefer granular control over the verification flow, such as managing their own PIN codes and custom failover sequences.
• Traffic to high-risk countries is not supported. Managed customers with high volumes should contact their account manager for tailored support.
Additional Information
The pricing model is slightly different in Verify API V1 (Legacy), more details can be found here.
Articles in this section
- What is the Verify Anti-Fraud System?
- Verify API service to restricted countries
- Can I use Verify API with any number in the world?
- Rejection for Invalid Number in Verify V2
- Why does Verify Dashboard Analytics report less traffic than the invoice?
- Does Silent Authentication work for users with Apple’s Private Relay enabled?
- How to Change the Validity Period for Verify PIN Codes?
- Understanding the error code 409 when creating a Fragment for Custom Template in Verify API V2.
- What are the charges for using Verify API V2?
- Does Silent Authentication work with eSIM?