A mobile driving licence (mDL) lets a person present driving-licence information from a mobile device. ISO/IEC 18013-5:2021 specifies interfaces for an mDL, an mDL reader, and the issuing authority infrastructure. In the EUDI Wallet context, the Reference Verifier documentation identifies an mDL use case with the document type org.iso.18013.5.1.mDL. Read the ISO standard overview and the EUDI Reference Verifier configuration.
For a relying party, the practical question is how to request the smallest relevant piece of driving-licence information, explain the request to the customer, and handle cases where a compatible wallet or credential is unavailable.
An experimental mDL flow in DLBR EID
DLBR EID includes an experimental driving-licence check for interoperability testing. It creates an OpenID4VP request for an mDOC credential of type org.iso.18013.5.1.mDL and selects the driving_privileges claim. The request does not select a name, date of birth, or portrait.
Selecting a claim in the request does not guarantee that every wallet or credential will present identical data. The credential issuer, wallet implementation, and supported presentation profile affect what can be returned. The relying party should inspect the response and make its own decision for the stated service purpose.
The flow is shown under Experimental flows in the dashboard. It is available only when the active relying-party policy permits the mDL document type and driving_privileges for the selected issuer and intended use. If the policy does not allow them, the dashboard keeps the flow unavailable and explains what registration needs to include.
What teams should test
Before using an mDL check in a customer journey, test the complete flow with the wallets and issuers that matter to your service:
- Confirm the wallet recognises the request and presents the mDL clearly to its holder.
- Check which values are returned within
driving_privilegesand how the verifier reports them. - Test cancellation, unavailable credentials, expired licences, and interrupted sessions.
- Confirm the relying-party registration and intended use cover the request in each target market.
- Define what the service does when a wallet response is missing, invalid, or insufficient for the business decision.
An mDL presentation is evidence for a relying party to evaluate. It does not determine whether a person may rent a vehicle, use a mobility service, or meet another business rule. The organisation remains responsible for its decision and for applicable market requirements.
Keep the data request and customer explanation aligned
Tell customers why the service is asking for a mobile driving licence and what information the verifier is requesting. Keep the request aligned with the declared purpose, and avoid adding identity claims simply because the credential can provide them.
The exact wallet journey can differ between remote and in-person use. DLBR EID's experimental template covers an OpenID4VP verification request; proximity presentation and other mDL workflows have different interoperability requirements and are outside this template.
Frequently asked questions
What is an mDL?
An mDL is a mobile driving licence: driving-licence information held and presented from a mobile device. ISO/IEC 18013-5:2021 specifies interfaces for the mDL application and reader.
Is the DLBR EID mDL flow production-ready?
No. The flow is experimental and intended for controlled interoperability testing with compatible wallets and issuers. Production use requires separate validation of wallet support, registration, service requirements, and customer operations.
Does the flow request a person's name or date of birth?
The experimental template selects driving_privileges; it does not select a name, date of birth, or portrait. Wallet and issuer behavior can affect the presentation, so verify the returned data in the target environment.
Can an mDL response make the business decision automatically?
No. The relying party must decide how the verified information applies to its service, which fallback to offer, and which legal or operational requirements govern that decision.
If your team is testing EUDI Wallet verification for a defined service, request DLBR EID pilot access and include your target markets and wallet test plan.