This year has been quite intense in terms of development at Veriph.One, with a complete focus on our mission to make phone verification more reliable and secure. In the past two months, we have added:
We made a vital upgrade to our Inverse OTP infrastructure in Mexico and have substantially reduced the users' waiting time to an average of 23 seconds after the user sends the verification message via SMS. Delivery times can go as low as 10 seconds in many cases!
This new infrastructure makes a massive difference in User Experience and vastly reduces the probability of users abandoning the process or trying a different method. We strive to keep these improvements coming for all countries so that your security and phone verification needs are never in the way of User Experience.
From now on, our API Key management UI in the Veriph.One dashboard will let you manage the verification methods you use on each key in real-time. This feature is available for free and paid plans, with Inverse OTP (via SMS and WhatsApp) setup capabilities for all and the Traditional OTP Add-On limited to paid ones.
Note: This feature has one exception. If you want to set up the Traditional OTP Add-On via WhatsApp, you’ll need to contact us for assistance, as manual configuration is required to connect it to your Facebook Business account. The other Traditional OTP channels (SMS and phone call) are entirely self-service.
Beyond selecting which methods to use and in which order, paid plans using the Traditional OTP Add-On can also configure a prefix (“OTP Template Label” in the UI) shown to the user on the SMS message they receive and its sending limits. This last element is crucial to safeguard your account from SMS pumping fraud and to avoid over-costs by limiting how many OTPs we send to users within the configured time frame (“Cooldown period”).
We have expanded our payment processing capabilities and can now receive top-ups from most countries worldwide with full invoicing and local tax support. Remember that you can manage your balance and change your plan directly on our dashboard.
The developer experience is our top priority at Veriph.One, and we strive to make integrations a breeze for any team, no matter their tech stack and level of expertise. Which is why we have expanded our technical resources to include:
For companies working with non-native mobile platforms, our Github account now includes integration examples for Flutter and React Native platforms using our native libraries; this is just the beginning of the examples and resources we’ll put out for non-native platforms. We also aim to add plug-and-play support to these frameworks via plugins and similar mechanisms soon to make integrations easier.
Flutter: https://github.com/Veriph-One/veriph-one-examples-flutter
React Native: https://github.com/Veriph-One/veriph-one-examples-react-native
There’s also a treat for back-end developers: we have published an interactive website based on Swagger for your team to explore our API and automate parts of the integration. You can find it at https://service.veriph.one/swagger.
You can also find the Swagger specification in JSON and YAML format for automation and import purposes.
