Quick Read ยท mDL

What Data Is in a Mobile Driver's License (mDL)?

An mDL contains structured identity data issued by a state DMV and formatted using ISO/IEC 18013-5 so it can be securely verified by systems anywhere.

mDLQuick ReadStandards
Overview

Standardized data fields

The data is organized into fields defined by ISO/IEC 18013-5, allowing verifiers to interpret the information consistently across jurisdictions.

Every verifier โ€” whether at an airport, retail checkout, or online service โ€” uses the same field definitions to request and read credential data. This standardization is what makes an mDL issued in one state readable by a verifier in another.

Core fields

Core identity fields

Every mDL includes a baseline set of identity attributes used for identification.

Field
Family name
Description
Last name as recorded by the issuing authority
Field
Given name
Description
First name as recorded by the issuing authority
Field
Birth date
Description
Date of birth in ISO format
Field
Issue date
Description
Date the credential was issued
Field
Expiration date
Description
Date the credential expires
Field
Document number
Description
License number assigned by the issuing authority
Field
Issuing authority
Description
The DMV or government body that issued the credential
Field
Portrait photo
Description
Facial image of the credential holder
Field
Driving privileges
Description
Vehicle classes, restrictions, and endorsements
FieldDescription
Family nameLast name as recorded by the issuing authority
Given nameFirst name as recorded by the issuing authority
Birth dateDate of birth in ISO format
Issue dateDate the credential was issued
Expiration dateDate the credential expires
Document numberLicense number assigned by the issuing authority
Issuing authorityThe DMV or government body that issued the credential
Portrait photoFacial image of the credential holder
Driving privilegesVehicle classes, restrictions, and endorsements

These standardized fields ensure that any compliant verifier can understand and process the credential without custom integration per issuer.

U.S. implementations

Additional identity attributes

In the United States, the AAMVA mDL specification expands the data set to include additional attributes used in identity verification.

Height

Physical height of the holder as recorded by the DMV.

Eye color

Eye color as recorded on the physical license.

Sex

Sex as recorded by the issuing authority.

Residential address

Home address of the credential holder.

Age in years

Computed age derived from the birth date.

These fields help verifiers confirm identity quickly and consistently across states.

Privacy-preserving

Derived verification attributes

mDLs may include derived attributes designed for privacy-preserving verification โ€” sharing only a yes/no answer instead of raw data.

Age check

age_over_18

A boolean confirming the holder is 18 or older, without revealing the exact birth date.

Age check

age_over_21

A boolean confirming the holder is 21 or older โ€” commonly used for alcohol purchases or venue entry.

Instead of revealing a full birth date, the credential provides a simple confirmation for age-restricted scenarios. The verifier gets only what it asked for.

Optional

Optional data fields

Some jurisdictions include additional attributes depending on their requirements and use cases.

Nationality

Country of nationality as recorded by the issuing authority.

Place of birth

City or country of birth.

Signature image

Image of the holder's signature.

Biometric templates

Fingerprint or other biometric data for advanced verification use cases.

Summary

Structured, standardized, privacy-aware

An mDL is more than a digital copy of a plastic card โ€” it's a structured credential designed for selective, verifiable sharing.

โ„น๏ธ
In summary
An mDL contains core identity attributes, driving privilege information, and derived verification fields such as age_over_21. Because the data follows ISO/IEC 18013-5, verifiers can request only the fields needed for a transaction while maintaining interoperability and privacy across jurisdictions.