Product Update [December 2024]

[Feature] Phone Data Enrichment!

We heard your feedback loud and clear! You wanted to know more about the person behind a phone number, and we got you over 120 data points that will help your company:

1. Get reliable, high-quality alternative data from your user’s phone numbers to train underwriting and risk models.
2. Improve your KYC and KYB processes by cross-checking user-reported information and their phone number’s historical data.
3. Detect fraudsters, bots, impersonators, and hackers and determine each number's risk level

The information you can now obtain falls under four categories:

1. Phone number metadata includes information such as the carrier that provides the service (including information on its offerings), the city where the phone number was registered, the type of phone number (e.g., landline, mobile, virtual, or satellite), and dozens of other fields.
2. Verification metadata includes information such as the device used for the verification, languages, networks, response times, and IP addresses. We also transform IP addresses into geolocation, Internet service provider, connection type, and VPN and proxy usage for your convenience.
3. Blacklists of phone numbers used by fraudsters or for illegal activities. We obtain this information by continuously crawling and scrapping the websites these people use. This category is currently in Alpha and is expected to be fully baked before the end of Q1-2025.
4. Anonymized carrier data coming directly from the companies providing telephony services will help you dig deeper into a phone number's activity and transactional profile. This data doesn’t contain any personal information or sensitive raw data that can be used to identify the customer directly. However, it contains valuable answers to questions like: how old is this number’s contract? Is it pre-paid or post-paid? What’s the contract’s spending profile? How risky is it to interact with this number?

Today, every plan can access data categories 1 to 3 by migrating from version 1.0.0 to version 1.1.0 of our Verification Result endpoint. Please refer to that endpoint’s documentation to check the availability of each field based on your plan; paid plans get access to the whole dataset at no extra cost!

If you are interested in data category four, schedule a call with us to discuss your needs and use cases. It operates under a different pricing model and requires carrier approval.

Need help migrating to the new version? Or do you want to discuss the minutia of the data with our team? Let us know, and we’ll hop on a call with your team.

[Feature] Custom Fonts!

Our prebuilt verification UIs are getting even better, and now you can set up custom fonts on our mobile SDKs. Configure different fonts for titles, buttons, texts, labels, and interactive elements. This works out-of-the-box for native implementations, Flutter, and React Native.

New SDK versions containing this feature

Versions 1.1.0 and above of our native SDKs. On iOS is available via Github/Cocoa Pods; and available for Android via Maven Central.

This feature is 100% backward compatible, so if you upgrade, nothing will break, nor will you be forced to use custom fonts.

[Feature] Standalone Traditional OTP Endpoint

Some clients have also requested a standalone web service to send OTPs without direct user interaction (e.g., when triggered by a server or third party). Our sending infrastructure is now available to you. You can find more information about this endpoint in our API documentation here.

This service is available on all paid plans and allows your server to send OTPs via SMS, phone calls, and WhatsApp (this last channel requires us to set up your account first). Contact us if you need assistance.

[DevX] New API documentation

Navigating our API documentation was a bit complicated in the past, and we decided to change that. The new website (available at developer.veriph.one/api) will let you interact with each endpoint under the OpenAI standard and explore the different response objects and inputs needed. We also increased the comprehensiveness of our descriptions for each field so you can better understand what each data point means.

But don’t worry; our Swagger website and its corresponding YAML and JSON specifications are still available if needed.

Finally, with the holidays upon us, the Veriph.One team wishes you and all close to you a warm end of the year and a very prosperous new year! Thank you very much for your continued support and preference!

🎄🎄🎄🎄🎄🎄🎄🎄🎄