Overview

The Database Verification (sometimes referred to as Authoritative Database Verification) takes in collected text values that contain identifying information such as name, date of birth, and/or address, and runs the inputs through trusted authoritative data sources to verify the provided information. Authoritative data sources vary widely in each country (and even region, province, or state) and the Database Verification allows you to centralize the process of verifying individuals for existence in at least one trusted source.

A Database Verification answers the question "Do authoritative databases corroborate and confirm the provided user data?"

Understanding data sources

Authoritative data sources include credit agencies, voting registries, telephone database, government records (e.g. court filings), consumer databases, utility registration, postal authorities, and register of deaths. This is in contrast to non-authoritative data sources (i.e. social media), which is available through a Non-Authoritative Database Verification, and issuing data sources (i.e. Department of Motor Vehicles (DMV)), Social Security Administration (SSA)), which are available through other Verification products like AAMVA Verification, eCBSV Verification, Brazil Serpro Verification, and more. This variety of sources, combined with customizable configurations, allows you to build and optimize solutions that meet your specific risk tolerance, compliance requirements, and business goals.

Verification Features

Verification Inputs

Each country has specific suggested minimum inputs and at absolute minimum, the Database Verification requires at least two of the following attributes:

• Full Name (Required)
• National ID (suggested if country can utilize a country-specific National ID per Coverage Map i.e. Social Security Number for the United States)
• Birthdate
• Address
• Phone Number
• Email Address

For suggested minimum inputs per country, review the appropriate country-specific Database Verification resource.

Collection of inputs

• Via Inquiries
  • The Database Verification (and any associated screens) can be added to an existing Inquiry Template through a pre-built Module in the Flow Editor or as a new Inquiry Template via the Inquiry Template or Solution Library
• Via API
  • You can also run a Database Verification via a Transaction with an accompanying Workflow that contains the Run Database Verification action step

Verification Outputs

Verification status

A Verification’s status is an indicator of where the Verification is in its lifecycle. After a Verification has run the simplest output and indicator is the status as failed or passed. This is an easy way to ascertain, at a high level, if the attempt to verify the identity met the requirements set forth in the configurations of the Verification Template.

Verification Check statuses

Each Database Verification check will be shown as passed, failed, or not applicable. This will give a more detailed look at which of the Verification Checks the attempt failed. In the Dashboard, the results view of the Verification also show which checks were required on the Verification Template when the Verification ran. Those that were required determine what checks are necessary to receive a passed at the Verification Status level.

Verification Check details

Given that the Verification checks can determine whether the attempt passes or fails the Verification, some Verification checks offer more detail about the failure reason and the specifics around why the attempt failed or passed that particular check. This allows a reviewer to understand more granularly what constitutes pass and fail, and gives insights into what Verification Template configurations may need to be optimized or adjusted.

Identity Comparison Check details

In the Dashboard view of a Database Verification run, the Identity Comparison Check detail is expanded by default. This is to call out the importance of this check as a key configuration of the overall Verification as it determines the level of match per attribute and what combination of attributes are necessary to be considered a match within the authoritative data sources. The detailed view gives insight into the quality of the match.

The example dashboard view, at the top of this resource details what the Identity Comparison Check would look like when configured using Match Groups (allows you to set multiple combinations of what constitutes a match). Note that some businesses have configured a legacy version of the Identity Comparison Check without Match Groups.

Read more on Database Verification Outputs here.

Configuration options

The Database Verification offers a variety of configurations such as required or un-required verification checks, acceptable countries, Identity Comparison Check with Match Groups which define acceptable match levels per attribute (i.e. partial, exact, 2 characters off), and verification check sub-configurations.

Given that Verification configurations are nuanced, explore detailed explanations around these configurations in the Help Center Articles > Verifications > Features > Configurations.

Database Verification access by plan

Learn about pricing and plans

Disclaimer

Persona is not a consumer reporting agency and the services (and the data provided as part of its services) do not constitute a ‘consumer report’ for the purposes of the Federal Fair Credit Reporting Act (FCRA). The data and reports we provide to you may not be used, in whole or in part, to: make any consumer debt collection decision, establish a consumer’s eligibility for credit, insurance, employment, government benefits, or housing, or for any other purpose authorized under the FCRA. If you use any of any of our services, you agree not to use them, or the data, for any purpose authorized under the FCRA or in relation to taking an adverse action relating to a consumer application.