How data validation works

Validation types

Transmit allows you to perform the following types of data validation:

• Email validation
• Phone validation
• Address validation
• Name validation
• SSN validation
• DoB (Date of birth) validation
• Identity validation

Validation source

Transmit validates different identity data sets using built-in integrations to third-party providers, which we consider the validation source. Here are the providers that are supported, along with the types of data they can validate:

• Telesign (Phone validation)
• EmailHippo (Email validation)
• Melissa (SSN, name, email, phone, DoB and address validations)
• Google (Address validation)
• Idology (Identity validation)

Learn more about the validations performed by each provider, and the data they return:

• EmailHippo MORE Edition 1
• EmailHippo MORE Edition 2
• Telesign Score API
• Melissa APIs doc
• Melissa Email
• Melissa Phone
• Melissa Address
• Melissa Name
• Melissa SSN
• Google Address
• Idology

Validation result

Once the user provides identity data (such as email, phone number, address, etc.), Transmit validates the data using external providers, and returns an aggregated result. The result can be further processed and analyzed by your app to determine if the data is reliable, to assess the overall risk, and to decide how to proceed.

For example, the result may indicate if an email is real, its age, if the phone number exists, if it's roaming, who is the mobile service provider, if the SSN is valid, if it relates to the person's name, if the address is real and corresponds to the person, etc.

Managing validations

Validations can be managed from the Identity data validation page of the Admin Portal. For each type of validation, you can control which providers to enable. When data validation is requested, Transmit will perform the data validation only using the providers that you've enabled.

Testing validations

From the Identity data validation page of the Admin Portal, you can run a simulation of a data validation process based on the enabled providers. Once you provide data for testing and click Test, the validation results will be displayed.

Requesting validations

Data validations are performed when needed using our dedicated API, by sending a POST request with the identity data you want to validate. Transmit will send the data to the enabled providers to validate concurrently and then process the results they return. The API response will include a single JSON that encapsulates all the provider results.