Email OTP
Verify registration, login and recovery email addresses with a bounded code lifecycle and independent Email OTP billing.
INDEPENDENT OTP PRODUCTS
Email, SMS and WhatsApp OTP verification without full KYC.
OTP products can be integrated independently of document verification. Each request has its own status, expiry, verification and idempotency behavior, so a login or recovery flow does not need to become a KYC application.
Capabilities built around the actual customer journey.
Implementation and testing status is stated separately from commercial activation, so your team can evaluate what is genuinely available.
Phone and SMS OTP
Use the standalone phone-verification contract where a configured provider and destination are supported. Provider acceptance is required before a live delivery claim.
Official WhatsApp Cloud API
WhatsApp OTP uses Meta’s official Cloud API and approved authentication templates, with delivery status processing rather than a third-party messaging relay.
Integration-friendly controls
Scoped live credentials, idempotency keys, explicit error codes and product-specific credits help prevent duplicate sends and confusing charges.
Where this can be used.
- Account registration
- Passwordless login
- Password reset confirmation
- Transaction or action verification
- Independent OTP integration services
A controlled implementation path.
- 1Choose Email, SMS or WhatsApp OTP
- 2Create an idempotent request with the destination
- 3Handle provider acceptance and delivery status
- 4Verify the code before it expires
- 5Record the actual charge only under the approved product rule
Current availability and acceptance limits
Application-level OTP validation is implemented, but real delivery acceptance must be demonstrated separately for SMTP, SMS and WhatsApp. A test payload or queued request is not proof that a customer received a message.
Frequently asked questions
Is full KYC required for Email OTP?
No. Email OTP can be used independently without document upload or a KYC case.
Does a successful API response prove delivery?
No. Delivery must be established from the actual provider response and, where supported, subsequent delivery status.
Does every OTP request cost the same?
No. Email, phone/SMS and WhatsApp OTP have product-specific rules and credits. Always check the current published price and activation status before charging.
Evaluate the exact workflow before you go live.
Review the documentation, test the actual document and provider path, or ask our integration team for a scoped technical assessment.