Claim Sets

Request specific identity data from mDL holders using predefined or custom claim sets.

When creating a verification session, you specify which claims (data fields) you want to request from the mDL holder. Following the principle of data minimization, you should only request the claims necessary for your use case.

Predefined Claim Sets

The SDK provides predefined claim sets for common verification scenarios. These make it easy to request the right data without remembering individual claim names.

Age Verification

Identity Verification

Driving Privileges

Custom Claims

For specific requirements, you can request individual claims by name:

Available Claims (ISO 18013-5)

The following claims are defined by the ISO 18013-5 standard and may be available in mDL credentials:

Identity Claims

Claim	Type	Description
`family_name`	String	Family name / last name
`given_name`	String	Given name / first name
`birth_date`	String	Date of birth (YYYY-MM-DD)
`portrait`	ByteArray	Facial photo (JPEG data)

Age Verification Claims

Claim	Type	Description
`age_over_18`	Boolean	Is holder 18 years or older
`age_over_21`	Boolean	Is holder 21 years or older

Document Claims

Claim	Type	Description
`document_number`	String	License/document number
`issue_date`	String	Document issue date
`expiry_date`	String	Document expiration date
`issuing_authority`	String	Issuing authority name

Address Claims

Claim	Type	Description
`resident_address`	String	Street address
`resident_city`	String	City
`resident_state`	String	State/province code
`resident_postal_code`	String	ZIP/postal code
`resident_country`	String	Country code

Driving Claims

Claim	Type	Description
`driving_privileges`	List	License classes and restrictions

Accessing Claim Values

After successful verification, access the claim values through the MDLClaims object:

Generic Access

Best Practices

Data Minimization: Only request the claims you actually need. Requesting unnecessary data may reduce holder trust and could have privacy implications.

✅ Do

Request only claims necessary for your use case
Use age verification claims instead of full birth date when possible
Explain to users why you need each piece of data
Handle missing claims gracefully (holders may decline)

❌ Don't

Request full identity when you only need age verification
Store sensitive claims longer than necessary
Request address data unless legally required

Handling Declined Claims

Holders may decline to share certain claims. Always check if a claim value is present before using it: