Available 18013 Documents

This page documents the various 18013-compliant documents (and their namespaces/attributes) which can presently be verified through Google Wallet.

This information may be useful when providing a raw18013Request to Trinsic's API during Session creation.


Document TypeDescriptionPrimary NamespaceOther Namespace(s)
org.iso.18013.5.1.mDLUS Mobile Driver's Licenseorg.iso.18013.5.1org.iso.18013.5.1.aamva
com.google.wallet.idcard.1Google Wallet ID Passorg.iso.18013.5.1N/A



org.iso.18013.5.1.mDL Document

This document type is used by all standard, 18013-compliant Mobile Driver's Licenses in the United States.


org.iso.18013.5.1 Namespace

Below are all the fields found within the org.iso.18013.5.1 Namespace when working with org.iso.18013.5.1.mDL Documents.

AttributeDescriptionMandatoryExample
given_nameFirst name(s), other name(s), or secondary identifier, of the mDL holder.John
family_nameLast name, surname, or primary identifier, of the mDL holder.Doe
birth_dateDay, month, and year on which the mDL holder was born. If unknown, approximate date of birth.1990-12-31
issue_dateDate when the mDL was issued.2026-01-01
expiry_dateDate when the mDL expires.2028-01-01
issuing_countryAlpha-2 country code, as defined in ISO 3166-1, of the issuing authority’s country or territory.US
issuing_authorityIssuing authority name.California DMV
document_numberThe number assigned or calculated by the issuing authority.D1234567
portraitA reproduction of the mDL holder’s portrait.<JPEG bytes>
driving_privilegesDriving privileges of the mDL holder.[{...}]
un_distinguishing_signDistinguishing sign of the issuing country according to ISO/IEC 18013-1:2018, Annex F.USA
issuing_jurisdictionCountry subdivision code of the jurisdiction that issued the mDL, as defined in ISO 3166-2.US-CA
given_name_national_characterThe given name of the mDL holder using the full UTF-8 character set.John
family_name_national_characterThe family name of the mDL holder using the full UTF-8 character set.Doe
nationalityNationality of the mDL holder as a two-letter country code (alpha-2) defined in ISO 3166-1.US
signature_usual_markImage of the signature or usual mark of the mDL holder.<JPEG bytes>
administrative_numberAn audit control number assigned by the issuing authority.A123456789
sexmDL holder’s sex using values as defined in ISO/IEC 5218.1
heightmDL holder’s height in centimetres.180
weightmDL holder’s weight in kilograms.75
eye_colourmDL holder’s eye colour.brown
hair_colourmDL holder’s hair colour.brown
birth_placeCountry and municipality or state/province where the mDL holder was born.USA, California
resident_addressThe place where the mDL holder resides and/or may be contacted (street/house number, municipality, etc.).123 Main St
resident_cityThe city where the mDL holder lives.San Francisco
resident_stateThe state/province/district where the mDL holder lives.CA
resident_postal_codeThe postal code of the mDL holder.94105
resident_countryThe country where the mDL holder lives as a two-letter country code (alpha-2) defined in ISO 3166-1.US
portrait_capture_dateDate when the portrait was taken.2025-12-15T10:30:00Z


org.iso.18013.5.1.aamva Namespace

Below are the fields found within the org.iso.18013.5.1.aamva Namespace when working with AAMVA-compliant mDL Documents.

Attribute

Description

Mandatory

Example

domestic_driving_privileges

Domestic categories of vehicles, restrictions, and conditions that the license holder is authorized to operate.

Unavailable

family_name_truncation

Whether the family name field has been truncated.
Values:
T (Truncated) N (Not Truncated)
U (Unknown)

N

given_name_truncation

Whether the given name or middle names have been truncated.
Values:
T (Truncated) N (Not Truncated)
U (Unknown)

N

sex

Credential holder’s sex as defined in the AAMVA guidelines.

1

DHS_compliance

Whether the credential complies with REAL ID requirements.
Values:
F (Fully Compliant)
N (Not Compliant)

F

name_suffix

Name suffix of the credential holder (e.g., JR, SR, II, III).

JR

first_name

First name of the credential holder.

John

first_name_truncation

Indicates whether the first name field has been truncated.
Values:
T (Truncated) N (Not Truncated)
U (Unknown)

N

middle_names

Middle name(s) of the credential holder.

Michael

middle_names_truncation

Indicates whether the middle names field has been truncated. Values:
T (Truncated) N (Not Truncated)
U (Unknown)

N

aka_given_name.v2

Other given name by which the credential holder is known.

Johnny

aka_family_name.v2

Other family name by which the credential holder is known.

Smith

aka_suffix

Alternate suffix by which the credential holder is known.

III

organ_donor

Whether the credential holder is an organ donor.

1

veteran

Whether the credential holder is a veteran.

1

weight_range

Approximate weight range of the credential holder.

4

resident_county.v2

3-digit county code of the county where the credential holder lives (2020 FIPS).

013

hazmat_endorsement_expiration_date

Date when the hazardous material endorsement granted by the credential (if any) expires.

2027-05-01

EDL_credential.v2

Whether the credential is an EDL

1

CDL_indicator

Whether the credential is a Commercial Driver’s License (1) or permit/not a CDL holder (absent).

1

CDL_non_domiciled.v2

Whether the CDL holder is not domiciled in the issuing jurisdiction (1) or is domiciled/not a CDL holder (absent).

1

DHS_temporary_lawful_status

Indicates whether the credential holder has temporary lawful status (1) or not (absent).

1

DHS_compliance_text

Text appearing on credentials that do not meet REAL ID requirements.

NOT FOR REAL ID


com.google.wallet.idcard.1 Document

This document type is used for Google Wallet ID Pass credentials, which use a Passport as the underlying identity document, and are issued by Google.

org.iso.18013.5.1 Namespace

❗️

Reused Namespace

Google Wallet ID Passes reuse the org.iso.18013.5.1 Namespace name, which is also used for standard Mobile Driver's Licenses.

However, ID Pass credentials are not mDLs, and the set of available attributes available in this namespace is unique to this document type.

Below are the fields found within the org.iso.18013.5.1 Namespace for Google Wallet ID Pass credentials.

AttributeDescriptionMandatoryExample
given_nameFirst name(s), other name(s), or secondary identifier, of the mDL holder.John
family_nameLast name, surname, or primary identifier, of the mDL holder.Doe
birth_dateDay, month, and year on which the mDL holder was born. If unknown, approximate date of birth.1990-12-31
issue_dateDate when the mDL was issued.2026-01-01
expiry_dateDate when the mDL expires.2028-01-01
issuing_countryAlpha-2 country code, as defined in ISO 3166-1, of the issuing authority’s country or territory.US
issuing_authorityIssuing authority name.California DMV
nationalityNationality of the mDL holder as a two-letter country code (alpha-2) defined in ISO 3166-1.US
document_numberThe number assigned or calculated by the issuing authority.D1234567
portraitA reproduction of the mDL holder’s portrait.<JPEG bytes>
sexmDL holder’s sex using values as defined in ISO/IEC 5218.1
age_over_18Indicates whether the mDL holder is over 18 years of age.true
age_over_21Indicates whether the mDL holder is over 21 years of age.true
original_document_issue_dateDate when the original document was issued.2020-05-15


How To Make A Custom Request

🚧

Preview Feature

This feature is currently available as a Preview, and is intended for exploration, testing, and demos.

We intend to offer a more normalized, platform-wide feature to specify custom "scopes" for supported Providers in the future.

By default, your Verification Profile's configuration is used to create the 18013 request when you create a Session. However, you may wish to specify a custom request when creating a Session, allowing you to request any document(s), namespace(s), and attribute(s) that you wish.

Requirements:

  • You must be using Hosted or Direct Sessions
    • Widget Sessions do not currently support this functionality
    • Note: Direct Sessions require custom registration when using Google Wallet on your own domain name.
  • You must be using a Backend SDK of version 3.0.2-preview1 or higher
    • This SDK supports the necessary preview_raw18013Request Provider-Specific Input field
    • If you are not using a Backend SDK, the JSON samples below will help you amend your request payloads.

To make a custom request, specify it in the Provider-Specific Input field (providerInput) when making a request, as so:

{
    "verificationProfileId": "...",
    "provider": "google-wallet",

    // Other fields omitted

    "providerInput": {
        "google-wallet": {
            "preview_raw18013Request": {
                // `documentRequests` is an array of requests, each describing a single document.
                // A credential which satisfies *any* of the requests can be used by the user.
                // Only a single credential is collected and returned.
                "documentRequests": [
                    {
                        // The document type to request -- see Trinsic's documentation 
                        // for a list of all valid document types for Google Wallet
                        "documentType": "org.iso.18013.5.1.mDL",

                        // A map of (nameSpaceName -> map(fieldName -> willRetain)), where:
                        // - nameSpaceName is a namespace within the document
                        // - fieldName is a field within the given namespace
                        // - willRetain indicates whether you intend to store the data beyond the scope of the immediate transaction
                        "nameSpaces": {
                            "org.iso.18013.5.1": {
                                // `given_name` is required, and will be stored by the requester
                                "given_name": true,

                                // `portrait` is required, and will NOT be stored by the requester
                                "portrait": false
                            }
                        }
                    }
                ]
            }
        }
    }
}
{
    "verificationProfileId": "...",
    "provider": "google-wallet",
    "providerInput": {
        "google-wallet": {
            "preview_raw18013Request": {
                "documentRequests": [
                    {
                        "documentType": "org.iso.18013.5.1.mDL",
                        "nameSpaces": {
                            "org.iso.18013.5.1": {
                                "given_name": true,
                                "portrait": false
                            }
                        }
                    }
                ]
            }
        }
    }
}

Here is an example of requesting a user's name and portrait image from their Google Wallet, allowing for either an mDL or an ID Pass credential to be presented.

Note: the second documentRequest has a different documentType but uses the same 18013 nameSpace, as that is how the Google Wallet ID Pass credential is designed.

{
    "verificationProfileId": "...",
    "provider": "google-wallet",
    "providerInput": {
        "google-wallet": {
            "preview_raw18013Request": {
                "documentRequests": [
                    {
                        "documentType": "org.iso.18013.5.1.mDL",
                        "nameSpaces": {
                            "org.iso.18013.5.1": {
                                "given_name": true,
                                "family_name": true,
                                "portrait": false
                            }
                        }
                    },
                    {
                        "documentType": "com.google.wallet.idcard.1",
                        "nameSpaces": {
                            "org.iso.18013.5.1": {
                                "given_name": true,
                                "family_name": true,
                                "portrait": false
                            }
                        }
                    }
                ]
            }
        }
    }
}