Mobile driver's licenses are quietly becoming mandatory US infrastructure in 2026
Mobile driver's licenses have quietly crossed from novelty to infrastructure in 2026. More than two dozen US states now issue a digital ID that lives in Apple Wallet or Google Wallet, TSA accepts them at a majority of major airport checkpoints, and several states have started requiring businesses — bars, rental counters, age-restricted retailers — to accept the digital version alongside the physical card. That last shift is the one that turns an optional convenience feature into something closer to mandatory infrastructure.
The pitch is straightforward: tap your phone instead of handing over a physical card, share only your age or photo instead of your full address and license number, and get a tamper-resistant credential that's harder to forge than a laminated card. The reality in 2026 is messier — interoperability between states is inconsistent, the privacy guarantees depend entirely on how a given verifier's app is built, and the rollout has created a new category of digital exclusion for people without a smartphone or stable connectivity.
How we got here faster than expected
TSA's PreCheck and REAL ID digital wallet acceptance, expanded significantly through 2025 and 2026, was the forcing function. Once the federal government's own primary identity-checking agency accepted a digital credential at scale, state DMVs had a concrete reason to invest rather than run a permanently experimental pilot. Utah, Colorado, Arizona, and Maryland were early movers; by 2026 the list includes most of the Sun Belt and a growing number of Northeastern states, built on the mDL (mobile driver's license) ISO/IEC 18013-5 standard that defines how these credentials are issued, stored, and verified across different wallet apps and hardware.
That shared standard is the unglamorous reason this worked at all. Previous state-level digital ID pilots failed to scale because each state built incompatible proprietary systems; a Delaware verifier app couldn't read a California credential. ISO 18013-5 gives every state-issued mDL the same underlying data structure and cryptographic verification method, so a bar's ID scanner or a TSA checkpoint reader built to the standard can verify a credential from any participating state without a custom integration per state.
The selective disclosure promise, and where it actually holds
The headline privacy feature is selective disclosure: a bar can request "is this person over 21" and receive a yes/no answer plus a photo, without seeing the person's address, exact birthdate, or license number. This genuinely works at the protocol level — the cryptographic structure supports it, and TSA's rollout has demonstrated it in production at scale.
Where it breaks down is implementation. A verifier's app has to be built to actually request the limited data set rather than the full record, and early audits of some third-party age-verification apps built on top of state mDL systems found several requesting and logging more data than the protocol required — defeating the entire privacy argument for the digital format over a physical card a bouncer glances at and hands back. The standard enables privacy; it doesn't enforce it, and enforcement so far has been inconsistent across the hundreds of businesses building verifier integrations.
Who gets left behind
States requiring digital ID acceptance alongside physical cards — not instead of them, for now — have been careful to frame this as additive. But the practical direction of travel is clear: every digital-first convenience nudges infrastructure, staff training, and eventually policy toward assuming a smartphone. That's a real burden for older residents, people who can't afford a smartphone with a recent enough OS to support the wallet credential, and anyone in a dead zone or without reliable connectivity at the moment of verification — the digital ID requires the verifier's device to be online to check revocation status in most state implementations, meaning a connectivity outage can turn a legally valid digital ID holder into someone who can't prove their identity.
What to actually do with this if you live somewhere it's rolled out
Set up your state's mDL in Apple Wallet or Google Wallet if your state offers it, but keep your physical card — no state has eliminated the physical license requirement, and several explicitly require you to carry both. Before relying on it for air travel, check your specific airport's TSA checkpoint list, since acceptance is inconsistent even within a single state's major airports. And if you're evaluating this as a business owner building age or identity verification, request only the minimum data field your use case needs — not because an audit will catch you immediately, but because the entire value proposition of mobile IDs depends on verifiers actually honoring selective disclosure, and that discipline is currently voluntary rather than enforced.