mDocs beyond the driver's license

The mobile driver's license (mDL) is often the first credential people encounter when learning about mobile documents. That makes sense. mDLs are widely recognized, regulated, and already in production in many jurisdictions.

But it is important not to mistake the starting point for the end state. The standards, infrastructure, and user experience patterns developed for mDLs are designed to apply to a much wider class of credentials: mobile documents, or mDocs. This page explains how mDocs extend beyond the driver's license, the role ISO/IEC 23220 plays in that extension, and why this matters for organizations planning digital identity programs.

The mDL as a starting point, not the end state

There are good reasons that so many digital identity programs have begun with the mDL:

• Familiarity. A driver's license is a credential most people already understand and carry today. Holders, verifiers, and operations teams can intuitively grasp what an mDL is for and what it should look like.
• Regulatory clarity. Driver's licenses are issued under well-defined authorities, with established processes for identity verification, issuance, and renewal. The governance model translates relatively cleanly into a digital form.
• Standards maturity. ISO/IEC 18013-5 was published in 2021 and gave the ecosystem a stable, internationally agreed standard to build against. Wallets, verifier SDKs, and certification programs have been built around it.
• General-purpose identity utility. In many jurisdictions, the driver's license is already used informally as a general-purpose identity document. Putting it on a phone is a natural extension.

Starting with the mDL lets issuers, wallets, and verifiers prove out their trust infrastructure, wallet experience, and integration patterns on a credential everyone already understands. It also produces a working ecosystem that the rest of a digital identity program can plug into.

The mDL is, in other words, an excellent first mobile document. It is not meant to be the only one.

What does "beyond the driver's license" actually mean?

Once an issuer, wallet, and verifier are comfortable with mDLs, the same underlying capabilities open the door to many other credential types. These include, for example:

• National identification cards: the closest natural extension of the mDL pattern, often issued by the same or adjacent authorities.
• Residence permits and travel documents: credentials that today often involve physical cards and in-person checks.
• Vehicle registration and ownership documents: credentials that benefit from being presented alongside or independently of a driver's license.
• Professional licenses and permits: for example, regulated occupations such as healthcare, law, transport, or trades.
• Sector-specific government records: hunting and fishing permits, firearms licenses, social benefit entitlements, and so on.
• Other high-assurance credentials where strong issuer authentication, device binding, selective disclosure, and offline verifiability are valuable.

All of these can be carried as mDocs because mDocs are not a driver's-license-specific format. They are a general-purpose, high-assurance digital credential format that happens to have been standardized first for driver's licenses.

Why mDocs work well for credentials beyond mDLs

The same properties that make mDocs a good fit for driver's licenses make them a good fit for the broader class of mobile documents:

• Strong issuer authentication. Verifiers can cryptographically check who issued the credential and that the data has not been tampered with. This matters as much for a national ID or a professional license as it does for a driver's license.
• Device binding. The credential is bound to the holder's device, which makes cloning much harder. For regulated credentials, this is often a hard requirement.
• Selective disclosure. A holder can share only the specific facts a verifier needs, not the whole credential. A health professional might prove their registration status without revealing every detail of their record.
• Offline-capable verification. Verification does not require a live call to the issuer. This matters for field deployments such as border control, roadside checks, or remote service delivery.
• In-person and online presentation. ISO/IEC 18013-5 handles proximity, ISO/IEC 18013-7 extends to online, and the same credential can flow through both. This is just as useful for a residence permit as it is for a driver's license.

These properties are properties of the format and trust model, not of any one credential type.

How ISO/IEC 23220 enables the move beyond mDLs

The standards community recognized early on that the model created for mDLs would need to generalize. That is the role of ISO/IEC 23220, a series of international standards that generalizes the mDoc model.

ISO/IEC 23220:

• Reuses the same building blocks as ISO/IEC 18013-5 (CBOR encoding, COSE signing, IACA-anchored trust, salted hashed claims for selective disclosure).
• Decouples the model from the driver's license. Instead of describing mDL-specific data, 23220 talks about mobile documents in general.
• Adds capabilities such as holder authentication, which strengthens the link between the credential and the person presenting it.
• Stays compatible with 18013-5 and 18013-7, so wallets and verifiers that already support mDLs can extend to other mDocs without reinventing their infrastructure.

The takeaway is that ISO/IEC 23220 lets ecosystem participants reuse what they have built for mDLs and apply it to a wider range of credentials. For a deeper look at how 18013-5, 18013-7 and 23220 fit together, see the ISO/IEC 18013-5, 18013-7 and 23220 explained page.

What this means in practice

For organizations planning a digital identity or credential program, the practical consequence is straightforward: an mDL program can be designed as the first step in a broader credential strategy, not as a standalone product.

That implies a few useful planning principles:

• Choose infrastructure that is not mDL-specific. Wallets, verifier SDKs, and trust registries that only support mDLs will block future expansion. Look for solutions that support mDocs in general, including 23220-aligned credentials.
• Design issuance processes that can carry other credentials. Many of the same identity proofing, claims sourcing, and key management workflows that issue an mDL can also issue other mDocs. Build them with that in mind.
• Plan verifier acceptance broadly. Verifiers that accept mDLs today can usually be extended to accept other mDocs with relatively modest changes, provided the underlying format support is in place.
• Think about holder experience across credentials. Holders will eventually carry multiple mDocs in a single wallet. Wallet selection and credential presentation flows should anticipate this.

How MATTR supports mDocs beyond the driver's license

MATTR's mDoc format is generic. It is not restricted to driver's license claims. The same MATTR VII issuance and verification capabilities used to support an mDL program can also be used to issue and verify other mobile documents, including identity cards, permits, and sector-specific credentials.

MATTR works with governments, ecosystem partners, and large organizations on credential programs that go beyond mDLs. If you are planning a program that starts with the mDL but anticipates other mobile documents over time, or that begins directly with another mDoc type, contact us to talk through the design.

Frequently asked questions

Are mDocs only for driver's licenses?

No. The mobile driver's license (mDL) is the most established example of an mDoc, but the underlying credential format, security mechanisms, and presentation protocols are designed to carry a much wider range of mobile documents. ISO/IEC 23220 generalizes these foundations so they apply to any high-assurance mobile document.

What kinds of credentials can be issued as mDocs beyond mDLs?

mDocs are well-suited to any high-assurance identity or entitlement credential that benefits from cryptographic verification, device binding, selective disclosure, and offline presentation. Examples include national identification cards, residence permits, vehicle registrations, professional licenses, sector-specific permits, and other government-issued records.

Why is the mDL such a common starting point?

Driver's licenses are widely recognized, regulated, and already used as a general-purpose identity document in many jurisdictions. ISO/IEC 18013-5 standardized them first, and many governments have launched mDL programs as an entry point into broader digital identity ecosystems. The mDL gives issuers, wallets, and verifiers a concrete first credential to test patterns, infrastructure, and user experience before extending to other mobile documents.

What is ISO/IEC 23220 and how does it help?

ISO/IEC 23220 is a series of international standards that generalizes the model established by ISO/IEC 18013-5 so it can apply to any mobile document, not only mDLs. It is compatible with 18013-5 and 18013-7 while introducing additional capabilities such as holder authentication. This lets issuers reuse the same trust model, wallets, and verification infrastructure across many credential types.

Can MATTR help me extend an mDL program to broader mDocs?

Yes. MATTR's mDoc format is generic and can carry the claims required for many credential types beyond driver's licenses. MATTR works with governments and ecosystem partners on programs that go beyond mDLs, including national IDs and other regulated credentials. Contact us to discuss your specific use case.

Summary

The mobile driver's license is an excellent first credential, not the only credential. The same standards, infrastructure, and user experience patterns built for mDLs apply to a much broader class of mobile documents, from national IDs to residence permits to professional licenses. ISO/IEC 23220 generalizes the foundations of 18013-5 so the same trust model and tooling can carry these other credentials. For organizations planning a digital credential program, the practical implication is to design with mobile documents in general in mind, with the mDL as an early step rather than the destination.