Drivers License Data Verification report

Start here

This guide presents a technical overview of Entrust's Driver's License Data Verification (DLDV) report, available for integration through Workflow Studio.

Introduction

The DLDV report verifies the authenticity of an end user's driver's license by comparing it against US state driver's license databases to confirm whether the data submitted corresponds to a genuine driver's license.

Entrust uses a third-party subprocessor to verify driving license data against the American Association of Motor Vehicle Administrators (AAMVA) database, facilitated by the Department of Motor Vehicles (DMV). This allows quick and accurate verification that a given driver's license is real, providing a strong signal against synthetic fraud.

Supported documents and issuing states

Entrust's DLDV report is only available for the United States, supporting the following documents for verification:

• US driver's license
• US learner's permit or provisonal license
• State-issued ID card

Supported issuing states include:

• AR - Arkansas
• AZ - Arizona
• CO - Colorado
• CT - Connecticut
• DC - District of Columbia
• DE - Delaware
• HI - Hawaii
• FL - Florida
• IA - Iowa
• ID - Idaho
• IN - Indiana
• IL - Illinois
• KS - Kansas
• KY - Kentucky
• MA - Massachusetts
• MD - Maryland
• ME - Maine
• MI - Michigan
• MO - Missouri
• MS - Mississippi
• MT - Montana
• NC - North Carolina
• ND - North Dakota
• NE - Nebraska
• NJ - New Jersey
• NM - New Mexico
• OH - Ohio
• PA - Pennsylvania
• RI - Rhode Island
• SD - South Dakota
• TN - Tennessee
• TX - Texas
• VA - Virginia
• VT - Vermont
• WI - Wisconsin
• WA - Washington
• WY - Wyoming
• GA - Georgia
• OR - Oregon

Result logic

The DLDV report can return a result of clear, consider and unidentified:

Entrust's third-party subprocessor uses fuzzy matching on the name fields during DLDV verifications. This is because information can be provided in many different ways and errors in data submission or collection can be quite high. Fuzzy matching allows capturing data variations.

Report breakdowns and properties

The DLDV report breakdowns can have a result of clear or consider. Breakdowns will only have a clear result when all included sub-breakdowns are clear.

Below is an example Driver's License Data Verification report breakdown:

1{
2    "breakdown": {
3        "document": {
4            "result": "clear",
5            "breakdown": {
6                "category": {
7                    "result": "clear",
8                    "properties": {}
9                },
10                "expiration_date": {
11                    "result": "clear",
12                    "properties": {}
13                },
14                "issue_date": {
15                    "result": "clear",
16                    "properties": {}
17                },
18                "document_number": {
19                    "result": "clear",
20                    "properties": {}
21                }
22            }
23        },
24        "address": {
25            "result": "clear",
26            "breakdown": {
27                "city": {
28                    "result": "clear",
29                    "properties": {}
30                },
31                "line_1": {
32                    "result": "clear",
33                    "properties": {}
34                },
35                "line_2": {
36                    "result": "clear",
37                    "properties": {}
38                },
39                "state_code": {
40                    "result": "clear",
41                    "properties": {}
42                },
43                "zip4": {
44                    "result": "clear",
45                    "properties": {}
46                },
47                "zip5": {
48                    "result": "clear",
49                    "properties": {}
50                }
51            }
52        },
53        "personal": {
54            "result": "clear",
55            "breakdown": {
56                "first_name": {
57                    "result": "clear",
58                    "properties": {}
59                },
60                "name_suffix": {
61                    "result": "clear",
62                    "properties": {}
63                },
64                "height": {
65                    "result": "clear",
66                    "properties": {}
67                },
68                "weight": {
69                    "result": "clear",
70                    "properties": {}
71                },
72                "sex_code": {
73                    "result": "clear",
74                    "properties": {}
75                },
76                "eye_color": {
77                    "result": "clear",
78                    "properties": {}
79                },
80                "date_of_birth": {
81                    "result": "clear",
82                    "properties": {}
83                },
84                "last_name": {
85                    "result": "clear",
86                    "properties": {}
87                },
88                "middle_name": {
89                    "result": "clear",
90                    "properties": {}
91                },
92                "first_name_fuzzy": {
93                    "result": "clear",
94                    "properties": {}
95                },
96                "middle_name_fuzzy": {
97                    "result": "clear",
98                    "properties": {}
99                },
100                "last_name_fuzzy": {
101                    "result": "clear",
102                    "properties": {}
103                },
104                "middle_initial": {
105                    "result": "clear",
106                    "properties": {}
107                }
108            }
109}

Driver's License Data Verification Report task

Similar to other Entrust reports, to run a DLDV report, the dedicated DLDV Report task should be added to a Studio workflow from the Workflow Builder.

Input data for this task can be received from the workflow input data, and the task should always follow the path of a Document Capture task in order to extract the appropriate task input data to process the verification.

Note that the applicant's first name, last name, driving license number and the issuing state are mandatory for running this report. Optional task input can also include the document's category, expiration date, issue date, as well as the applicant's middle name, date of birth, gender, eye colour, height and weight.

Below you will find an illustrated example of a Studio workflow running a DLDV report:

More information about report tasks can be found in our Studio Product Guide.

Driver's License Data Verification Report task results

If you want to obtain the specific outputs from the DLDV Report Task via the Entrust Identity Verification API (for example, the overall report result or breakdown results), you can manage this by configuring the Workflow Output in the Studio Workflow Builder.

You can refer to our Studio product guide for more information on Workflow Output configuration. Once set up, the output can be consumed by making a Retrieve Workflow Run call to the API. Report results are found in the output property.

Workflow Run results can also be accessed on the results tab of your Studio Dashboard.