How to Read a DigiLocker Driving Licence Check
Interpret DigiLocker driving licence results by checking the source, download integrity, issuer signature status, and validity before your application acts.
Read a driving licence check as several pieces of evidence. Look at the document source, download integrity, signature status, and validity dates. Then apply the rules for the activity you are reviewing.
DigiLocker distinguishes issued documents from files a person uploads. The requester specification also describes an integrity check for downloaded content. Record which checks your integration performed. DigiLocker FAQ Requester v2.4 specification
Read a synthetic result
The following example illustrates selected fields in the NamoID preview. The dates and reference are synthetic. The table omits other fields.
| Field | Example | How to use it |
|---|---|---|
| Document type | Driving licence | Compare with the type your workflow requires |
| Masked reference | Ending in 0427 | Use for case matching within the appropriate account |
| Source | Passed | Record the approved document source used for retrieval |
| Integrity | Passed | Record the successful download integrity check |
| Issuer signature | Not verified | Route to a separate check if policy requires an independent signature |
| Expiry | Valid | Compare the recorded dates with the intended activity |
| Checked at | 7 November 2026 | Use as the evidence observation time |
A successful download and processing result can contain an expired or unknown validity result. Read the individual fields before displaying an approval or granting access.
Decide which dates matter
Identify when the person plans to perform the activity. A document can be valid on the day of booking and expire before handover. A later end date can matter for an extended activity.
If the approved source returns class-specific validity periods, examine the period for the intended activity. A reviewer may need to check a required class or date that the result cannot establish.
For a synthetic booking, the document expires on 12 November and the trip begins on 13 November. The lookup can succeed on 7 November. Your policy should still route the booking to its approved review path.
Record the decision separately
Keep the verification reference, check time, and the policy version used for the decision. Record the reviewer if a person resolves an exception. Limit result access to the booking or account that needs it.
A validity date describes the supplied record. A live suspension check or a driving eligibility decision requires its own approved source and policy. Vehicle handover workflow.
Discuss the NamoID preview
The NamoID repository contains a controlled preview for post-login driving licence verification. It checks the approved source and download integrity. It reports the independent issuer signature status as not_verified. Access depends on workspace and application approval.
Share your required checks and a synthetic result example. The team can help you assess fit and plan a provider test. Message the NamoID team in Slack