Available 18013 Documents
This page documents the various 18013-compliant documents (and their namespaces/attributes) which can presently be verified through Samsung Wallet.
This information may be useful when providing a raw18013Request to Trinsic's API during Session creation.
| Document Type | Description | Primary Namespace | Other Namespace(s) |
|---|---|---|---|
org.iso.18013.5.1.mDL | US Mobile Driver's License | org.iso.18013.5.1 | org.iso.18013.5.1.aamva |
org.iso.18013.5.1.mDL Document
org.iso.18013.5.1.mDL DocumentThis document type is used by all standard, 18013-compliant Mobile Driver's Licenses in the United States.
org.iso.18013.5.1 Namespace
org.iso.18013.5.1 NamespaceBelow are all the fields found within the org.iso.18013.5.1 Namespace when working with org.iso.18013.5.1.mDL Documents.
| Attribute | Description | Mandatory | Example |
|---|---|---|---|
given_name | First name(s), other name(s), or secondary identifier, of the mDL holder. | ✅ | John |
family_name | Last name, surname, or primary identifier, of the mDL holder. | ✅ | Doe |
birth_date | Day, month, and year on which the mDL holder was born. If unknown, approximate date of birth. | ✅ | 1990-12-31 |
issue_date | Date when the mDL was issued. | ✅ | 2026-01-01 |
expiry_date | Date when the mDL expires. | ✅ | 2028-01-01 |
issuing_country | Alpha-2 country code, as defined in ISO 3166-1, of the issuing authority’s country or territory. | ✅ | US |
issuing_authority | Issuing authority name. | ✅ | California DMV |
document_number | The number assigned or calculated by the issuing authority. | ✅ | D1234567 |
portrait | A reproduction of the mDL holder’s portrait. | ✅ | <JPEG bytes> |
driving_privileges | Driving privileges of the mDL holder. | ✅ | [{...}] |
un_distinguishing_sign | Distinguishing sign of the issuing country according to ISO/IEC 18013-1:2018, Annex F. | ✅ | USA |
issuing_jurisdiction | Country subdivision code of the jurisdiction that issued the mDL, as defined in ISO 3166-2. | ❌ | US-CA |
given_name_national_character | The given name of the mDL holder using the full UTF-8 character set. | ❌ | John |
family_name_national_character | The family name of the mDL holder using the full UTF-8 character set. | ❌ | Doe |
nationality | Nationality of the mDL holder as a two-letter country code (alpha-2) defined in ISO 3166-1. | ❌ | US |
signature_usual_mark | Image of the signature or usual mark of the mDL holder. | ❌ | <JPEG bytes> |
administrative_number | An audit control number assigned by the issuing authority. | ❌ | A123456789 |
sex | mDL holder’s sex using values as defined in ISO/IEC 5218. | ❌ | 1 |
height | mDL holder’s height in centimetres. | ❌ | 180 |
weight | mDL holder’s weight in kilograms. | ❌ | 75 |
eye_colour | mDL holder’s eye colour. | ❌ | brown |
hair_colour | mDL holder’s hair colour. | ❌ | brown |
birth_place | Country and municipality or state/province where the mDL holder was born. | ❌ | USA, California |
resident_address | The place where the mDL holder resides and/or may be contacted (street/house number, municipality, etc.). | ❌ | 123 Main St |
resident_city | The city where the mDL holder lives. | ❌ | San Francisco |
resident_state | The state/province/district where the mDL holder lives. | ❌ | CA |
resident_postal_code | The postal code of the mDL holder. | ❌ | 94105 |
resident_country | The country where the mDL holder lives as a two-letter country code (alpha-2) defined in ISO 3166-1. | ❌ | US |
portrait_capture_date | Date when the portrait was taken. | ❌ | 2025-12-15T10:30:00Z |
org.iso.18013.5.1.aamva Namespace
org.iso.18013.5.1.aamva NamespaceBelow 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 categories of vehicles, restrictions, and conditions that the license holder is authorized to operate. | ✅ | Unavailable |
| Whether the family name field has been truncated. | ✅ |
|
| Whether the given name or middle names have been truncated. | ✅ |
|
| Credential holder’s sex as defined in the AAMVA guidelines. | ✅ |
|
| Whether the credential complies with REAL ID requirements. | ✅ |
|
| Name suffix of the credential holder (e.g., JR, SR, II, III). | ❌ |
|
| First name of the credential holder. | ❌ |
|
| Indicates whether the first name field has been truncated. | ❌ |
|
| Middle name(s) of the credential holder. | ❌ |
|
| Indicates whether the middle names field has been truncated. Values: | ❌ |
|
| Other given name by which the credential holder is known. | ❌ |
|
| Other family name by which the credential holder is known. | ❌ |
|
| Alternate suffix by which the credential holder is known. | ❌ |
|
| Whether the credential holder is an organ donor. | ❌ |
|
| Whether the credential holder is a veteran. | ❌ |
|
| Approximate weight range of the credential holder. | ❌ |
|
| 3-digit county code of the county where the credential holder lives (2020 FIPS). | ❌ |
|
| Date when the hazardous material endorsement granted by the credential (if any) expires. | ❌ |
|
| Whether the credential is an EDL | ❌ |
|
| Whether the credential is a Commercial Driver’s License ( | ❌ |
|
| Whether the CDL holder is not domiciled in the issuing jurisdiction ( | ❌ |
|
| Indicates whether the credential holder has temporary lawful status ( | ❌ |
|
| Text appearing on credentials that do not meet REAL ID requirements. | ❌ |
|
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
- You must be using a Backend SDK of version
3.0.2-preview1or higher- This SDK supports the necessary
preview_raw18013RequestProvider-Specific Input field - If you are not using a Backend SDK, the JSON samples below will help you amend your request payloads.
- This SDK supports the necessary
To make a custom request, specify it in the Provider-Specific Input field (providerInput) when making a request, as so:
{
"verificationProfileId": "...",
"provider": "samsung-wallet",
// Other fields omitted
"providerInput": {
"samsung-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 Samsung 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": "samsung-wallet",
"providerInput": {
"samsung-wallet": {
"preview_raw18013Request": {
"documentRequests": [
{
"documentType": "org.iso.18013.5.1.mDL",
"nameSpaces": {
"org.iso.18013.5.1": {
"given_name": true,
"portrait": false
}
}
}
]
}
}
}
}Updated 9 days ago
