What is an mDL?

A mobile Driver’s License (mDL) is a driver’s license stored on a mobile device, usually in a digital wallet app.

A true mDL is not just a photo or digital copy of a plastic card. It is a standards-based digital credential designed to let a person share license information securely and let another party verify that information with confidence.

mDLs are designed for both in-person and online verification. Standards such as ISO/IEC 18013-5 and ISO/IEC 18013-7 help make that possible by defining how mDL data is requested, presented, protected, and verified.

In simple terms: what does an mDL do?

An mDL lets a person use their phone to prove information that would traditionally be shown using a physical driver’s license.

That can include proving:

• identity
• age
• driving entitlement
• address or other license-related attributes, depending on the use case and jurisdiction

The main idea is simple: instead of handing over a plastic card, the holder shares verified information from a digital credential.

How is an mDL different from a physical driver’s license?

A physical driver’s license is usually checked by visually inspecting it. A verifier looks at the photo, reads the details, and decides whether the card appears genuine.

An mDL works differently.

Because it is a digital credential built on technical standards, an mDL can support cryptographic verification. That means the verifier may be able to confirm:

• that the credential was issued by a trusted issuer
• that the data has not been changed
• that the credential is being presented in a secure session
• in some cases, that the credential is bound to the device presenting it

This gives an mDL capabilities that a physical card does not easily provide:

• stronger digital verification
• more privacy-aware data sharing
• online and remote presentation
• support for automated or semi-automated verification workflows

Another important difference is data minimisation. With a physical license, the whole card is usually shown even when only one fact is needed. With an mDL, a verifier can request specific data, and the holder can consent to sharing only what is required for the interaction.

What interactions can an mDL enable?

An mDL can support both in-person and remote identity checks.

In-person use cases

A mobile driver’s license can be used in situations such as:

• roadside checks
• age verification for restricted goods or venues
• proving identity at a service desk
• access to regulated services
• identity checks in hospitality, travel, or events

Some mDL workflows are designed to work offline in real time, which is useful where internet access is unavailable or unreliable.

Online and remote use cases

An mDL can also support remote workflows, including:

• online account opening
• remote onboarding
• access to digital government services
• online age checks
• identity verification in financial transactions

These online interactions matter because many digital services still rely on scans, uploads, and repeated manual checks. A standards-based mDL provides a more structured and trustworthy way to exchange verified identity information online.

Same-device and cross-device workflows

Online mDL verification may happen:

• on the same device, where the user completes a transaction and presents the credential on one device
• across multiple devices, where one device is used for the service and another for the credential presentation

This flexibility supports a wider range of service designs and user experiences.

What standards are used for mDLs?

The two most important standards commonly discussed in relation to mDLs are ISO/IEC 18013-5 and ISO/IEC 18013-7.

ISO/IEC 18013-5

ISO/IEC 18013-5 defines how a mobile driver’s license can be presented and verified, especially in proximity or in-person scenarios.

It provides the technical foundation for:

• the structure of the credential
• the way data is exchanged
• the cryptographic mechanisms used to establish trust
• the ability for a verifier to validate the issuer and the credential data

In practice, this is what helps distinguish a real mDL from a simple digital copy of a license card.

ISO/IEC 18013-7

ISO/IEC 18013-7 extends mDL capabilities to remote or online verification.

It supports the use of mDLs over internet-based interactions, helping organisations build workflows where license data can be requested and presented securely online. This expands mDL use beyond face-to-face presentation.

Why these standards matter

These standards matter because they improve:

• trust, by defining how credentials are verified
• interoperability, by giving ecosystem participants a shared framework
• scalability, by reducing the need for bespoke approaches
• consistency, by aligning issuers, wallets, and verifiers around common models

How do mDLs support privacy and security?

mDLs are often discussed in terms of both security and privacy, because they are designed to improve how identity information is shared.

Security features

An mDL or mDoc-based credential can support:

• issuer authentication, so the verifier can check who issued the credential
• device authentication, which can help reduce risks such as cloning
• holder authentication, such as comparing the portrait to the presenter in person
• session encryption, which helps protect the exchange from eavesdropping in both in-person and online workflows

Privacy features

An mDL can also support:

• selective disclosure, where only needed information is requested
• holder consent, where the person can see what is being asked for
• reduced over-sharing, compared with handing over a full physical card

This makes mDLs relevant not only for convenience, but also for better data handling practices.

How does an mDL relate to mDocs?

A mobile driver’s license is commonly treated as a specific type of mobile document, or mDoc.

The broader mDoc concept refers to standards-based digital documents that can be stored on a mobile device and shared in trusted interactions. An mDL is one important example, but similar approaches may also be applied to other documents such as national IDs, health cards, certificates, and employee IDs.

In short:

• mDL = a mobile driver’s license
• mDoc = a broader category of mobile documents, which can include mDLs

Why are mDLs important?

mDLs are important because people and organisations increasingly need to exchange identity information in ways that are secure, digital, and usable across channels.

They bring trusted identity into digital channels

Many important interactions now happen online, but identity checking processes are often fragmented or weak. mDLs provide a path toward more reliable digital verification.

They can improve user experience

Instead of repeatedly uploading scans or manually entering data, users may be able to share verified information more directly and consistently.

They can reduce fraud and compliance risk

Because mDLs support stronger verification and secure exchange, they can help organisations improve assurance and reduce some forms of misuse or tampering.

They create a bridge between physical and online identity use

An mDL is familiar enough to be understandable to everyday users, but technically capable enough to support modern digital trust workflows. That makes it a practical entry point into broader digital credential ecosystems.

Frequently asked questions

What does mDL stand for?

mDL stands for mobile driver’s license. It refers to a digital version of a driver’s license stored on a mobile device and designed for secure, standards-based sharing and verification.

Is an mDL just a digital copy of a driver’s license?

No. A true mDL is not just a photo, screenshot, or PDF of a physical card. It is a digital credential designed to be verified using technical standards and cryptographic protections.

Can a mobile driver’s license be used online?

Yes. Modern mDL implementations are increasingly designed to support remote and online verification, especially through standards such as ISO/IEC 18013-7.

Can a mobile driver’s license be used in person?

Yes. In-person or proximity presentation is a core use case for mDLs, especially under ISO/IEC 18013-5.

What is the difference between ISO/IEC 18013-5 and ISO/IEC 18013-7?

ISO/IEC 18013-5 focuses on how mDLs are presented and verified, especially in in-person interactions.

ISO/IEC 18013-7 extends that model to support remote and online verification over the internet.

Are mDLs more secure than physical driver’s licenses?

They can be more secure in important ways because they can support cryptographic verification, secure sessions, and more controlled data sharing. However, the exact security outcomes depend on the implementation, the issuer, the wallet, and the verifier setup.

Do mDLs support selective disclosure?

Yes. One of the key benefits of an mDL is that a verifier can request only the data needed for a transaction, rather than requiring the holder to reveal the full contents of a physical card.

Can mDLs work without internet access?

Some in-person mDL workflows can support real-time offline verification, depending on the interaction model and implementation.

Are mDLs the same as mDocs?

Not exactly. An mDL is a specific kind of mDoc.

An mDoc is a broader category of mobile document that can include mobile driver’s licenses as well as other digital credentials.

Why are people interested in mDLs now?

Interest in mDLs is growing because organisations need better ways to support secure digital interactions across both physical and online channels, while also improving privacy, reducing fraud risk, and meeting rising expectations for digital services.

Summary

A mobile driver’s license (mDL) is a standards-based digital version of a driver’s license stored on a phone. Unlike a photo or digital copy of a physical card, an mDL is designed for secure, verifiable data sharing. It can support in-person and online identity checks, selective disclosure of information, and stronger privacy and security through standards such as ISO/IEC 18013-5 and ISO/IEC 18013-7.