PhoneID - Phone Number & Fraud Intelligence API | TeleSign

PhoneID

Detailed and actionable global phone number and subscriber data intelligence to strengthen authentications, evaluate fraud risks, and enhance the user experience
GET STARTED NOW

PROVIDE FASTER, SAFER & SMARTER ONLINE EXPERIENCES

Answer critical questions about users by using their phone numbers to get actionable data intelligence about their device, contact information, location, and more. Phone number data intelligence can help strengthen and validate the user verification process, reduce fake accounts, inform risk models, improve conversions and accuracy of collected information and even determine the optimal channel for message delivery.

The PhoneID API cleans and reformats a submitted phone number and instantly returns phone device-type, telecom carrier name and phone registration information. Additional data attributes are available for configuration via add-ons to best fit your specific use case.

CONTACT

Provide end-user phone number intelligence and receive contact information (first & last name, street address, city, state), based on carrier subscriber contact data. Use to strengthen existing fraud risk models and improve registration UX with pre-filled form fields.

*US only

NUMBER DEACTIVATION

Provide end-user phone number and receive data intelligence on when a phone number has been truly deactivated, based on carriers’ phone number data and our proprietary analysis. Delivers a date and time stamp, in the event a trust anchor has been broken.

CONTACT MATCH

Provide end-user phone number data, first/last name and address and receive a score of 0-100 as matched against carrier subscriber contact data. Use to validate an end-user’s physical address at onboarding, during a high-value transaction, verify a shipping address and to strengthen existing fraud risk models.

CONTACT PLUS

Provide end-user cell phone number and zip code data and receive their contact information (first & last name, street address, city, state), based on carrier subscriber contact data. Use to strengthen existing fraud risk models and improve registration UX with pre-filled form fields.

DEVICE INFO

Provide end-user phone number insight and receive its IMEI number, phone make & model to detect fraud or understand the strength, value or risk of the device holder and adjust content and marketing strategies per device.

SUBSCRIBER STATUS

Provide end-user phone number intelligence and receive current carrier subscriber status (prepaid or postpaid; active, suspended, de-active; account type; primary account holder; length of account tenure; and date of last status change) to understand the strength, value or risk of a user.

CURRENT LOCATION (coming soon)

Provide end-user phone number and receive current country information of device to strengthen identity, prevent fake accounts and gain deeper customer insights.

CURRENT LOCATION PLUS

Provide end-user phone number intelligence and receive current proximity location information (cell tower latitude/longitude or triangulated location) to prevent fraudulent transactions, KYC (know your customer), and strengthen identities.

*Data coverage varies by add-on. Contact sales for specific country coverage. Some data attributes may require implicit or explicit end-user consent to return personal information.

Key Benefits

TRUE GLOBAL DATA COVERAGE

Answer critical questions about your users with valuable data available in over 230 countries and territories. Data coverage by country varies by API.

STRENGTHEN AUTHENTICATIONS & REDUCE FRAUD

Instant API access to ongoing and accurate key phone number and user identity data attributes to help make better decisions about new registrations, user activity and fraud risks.

EASY INTEGRATION

Do business with confidence, improve conversions, and maintain compliance with real-time data on phone numbers and users in the optimal format for faster decision-making.

How It Works

A common use case and method for leveraging TeleSign’s PhoneID API plus our Contact Match add-on is to verify users and create valid customer profiles during the onboarding process, helping to prevent the creation of fake accounts.

1
When a new user registers for a Web or mobile account, they are asked
to provide their name, address and phone number. (Explicit consent may
be required from the user--depending on data attributes requested--and
should be collected using a separate, checked box.)
2
In this scenario, the business seeks to evaluate phone-data attributes and
compare the end-user-provided information (name & address) against
verified carrier subscriber data (identity data through the Contact Match
add-on) to confirm and validate the information provided by the end-user.
3
If the returned phone type data is not preferred (ex: phone type is VoIP
or prepaid) and the carrier contact name & address data does not match
against the user-provided data (returns a low score), the new account
registration can be blocked, flagged or required to verify using two-factor
authentication (2FA).
4
If successful (phone type acceptable and high Contact Match score
returned), the new end-user account can be created, as the user has
been authenticated into the service.

GET STARTED WITH TELESIGN

Integrate our products seamlessly into your user experience.
TALK TO AN EXPERT