Topic starter
10/07/2026 9:07 pm
TL;DR: Mobile driver’s licenses are moving from pilots into everyday identity verification, with 21 U.S. states plus Puerto Rico issuing standards-based mDLs and California reporting 3.5 million applications, according to Incode. The security issue is no longer whether mDLs work, but how IAM, onboarding, and compliance flows adapt to fragmented wallet coverage and selective disclosure.
Editorial analysis by NHI Mgmt Group, based on content published by Incode: “Mobile Driver’s Licenses (mDLs) Are On The Rise. Here’s What to Expect”.
Key questions
Q: How should teams design verification flows for mobile driver's licenses?
A: Design the flow around issuer verification, wallet support, and the minimum attributes needed for the decision.
Q: What happens when an mDL wallet is not supported by a verifier?
A: The credential may still be valid, but the business cannot complete the verification path for that wallet.
Q: How can organisations use selective disclosure without weakening compliance?
A: Ask for only the attributes the business decision requires, then store the verification result rather than the full document where policy allows.
Practitioner guidance
- Map your mDL acceptance boundaries List which issuers, wallets, and verification channels you will support, then define the fallback path for wallets not yet covered.
- Minimise downstream data capture Use selective disclosure to stop collecting full document images when the decision only requires age, identity match, or licence validity.
- Separate credential trust from wallet coverage Document which controls validate the issuer signature, which validate device presentation, and which simply route the user into the right flow.
Bottom line: Mobile driver's licenses move identity verification toward standards-based credential checks, which changes how onboarding and age assurance flows are designed.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
10/07/2026 9:31 pm
Mobile driver's license adoption is turning identity verification into a standards and coverage problem, not a document-format problem. The article shows that the core question is no longer whether a digital license can be verified, but whether the organisation can support the issuer, wallet, and remote-presentation combinations that customers actually bring. That means identity programmes must be designed for interoperability and partial coverage from the start.
A question worth separating out:
Q: Should identity teams replace physical ID capture with mDL verification?
A: Not everywhere, but mDLs should replace card scans wherever the legal, wallet, and issuer conditions are in place. The right decision is to segment journeys by risk and jurisdiction, then use mDLs to remove unnecessary friction and reduce data exposure in the supported paths.
👉 Read our full editorial: Mobile driver’s licenses are changing identity verification flows