in the US, TokenWorks and ONEPROOF have switched on what they call ‘the nation’s largest mobile driver’s license (mDL) verification network‘ by software-upgrading 15,000+ devices across 7,500+ business locations to accept ISO/IEC 18013-5 (in-person) and 18013-7 (remote) mDLs.

Critically, venues didn’t need new hardware; the upgrade rides on existing Android scanners already sitting at doors and counters. That makes this a production rollout, not a demo. 

These mDLs are cryptographically signed, privacy-preserving IDs on a phone. With 18013-5, a venue can verify your credential over NFC/BLE without reading more than it needs (e.g., “21+”). With 18013-7, the same credential works remotely for online age or identity checks—no photo uploads of plastic cards, no manual review queues. ONEPROOF says its verification stack supports both profiles today, which means the same acceptance footprint can extend from the door to the app. 

What this means for the U.S.

1) Acceptance before issuance—finally.

For years, mDL adoption has been a chicken-and-egg problem: few places accepted it, so consumers didn’t bother. Rolling out acceptance at national chains—bars, retailers, casinos, venues—at scale flips that equation. Once a critical mass of venues say “yes,” state DMVs see real demand signals to accelerate issuance; consumers try it because it “just works.” This is the network-effects moment the ecosystem has been waiting for. 

2) Lower friction, higher assurance at the edge.

Door staff get a green check instead of eyeballing plastic under bad lighting. The verifier checks the issuer’s signature, confirms the data is fresh, and can perform selective disclosure (e.g., birth-year only). That reduces underage access risk and identity fraud—particularly in high-risk retail (alcohol, vape, cannabis), entertainment, and gaming. The fact that this came as a software upgrade to existing devices is key: it keeps the total cost of adoption down and makes broad rollouts viable. 

3) Remote verification moves from theory to practice.

Support for ISO/IEC 18013-7 turns mDLs into a practical tool for remote age gates, SIM/eSIM onboarding, and KYC-lite sign-ups. Instead of asking customers to scan plastic or upload selfies, apps can trigger a standards-based remote presentation backed by the issuing DMV. That’s better UX, fewer false rejects, and stronger privacy by design. As more states light up their mDL programs, this becomes a default building block for regulated online journeys. 

4) Privacy upside—without bespoke plumbing.

mDL flows can prove attributes (e.g., “21+”) without exposing address or license number. Because the rollout leans on ISO profiles, verifiers don’t need one-off SDKs for every state or brand; they implement the standard once and ride the ecosystem’s growth. That standards adherence is the difference between a boutique pilot and a national platform. 

5) A clearer path for wallets and verifiable credentials.

mDLs are not the whole identity story in the U.S., but they’re a credible first credential consumers will use in the wild. As wallets mature (and as verifiable-credential rails expand in parallel), this acceptance footprint creates a habit: present a digital credential, get a fast, privacy-preserving yes. That habit is how we jump from pilots to real usage across sectors.

Who should care (and what to do next)

Retailers, venues, and gaming operators

• Turn it on where you can. If you run TokenWorks devices, check with your vendor about the mDL update and train staff on selective disclosure.
• Set your acceptance policy. Decide what data you’ll request (e.g., “21+,” photo match) and document fallback procedures (dead phone, out-of-state credential).
• Measure the lift. Track reduced manual checks, shorter queues, and decline rates for fake/borrowed IDs.

Telcos, delivery apps, and online marketplaces

• Pilot 18013-7 flows for remote age gates and number portability/SIM activation.
• Cut the image uploads. Replace “scan your card and selfie” flows with a standards-based remote presentation to reduce abandonment and fraud.  

State DMVs and policymakers

• Accelerate issuance and trust-list plumbing. The acceptance network is ready; citizens will expect availability. Make sure public keys and metadata are easily discoverable so verifiers can validate credentials reliably.
• Lean into privacy by design. Encourage selective disclosure and publish implementation guidance to keep verifiers from over-collecting.

Solution vendors and integrators

• Treat mDL like a platform feature, not a one-off. Build ISO-compliant verification into your IDV stack, expose it via clean APIs, and support both in-person and remote profiles.
• Plan for convergence. Expect mDLs to live alongside other credentials (employee IDs, age tokens, travel documents). Design for multi-credential wallets from day one.

The bottom line

The U.S. now has a production-scale mDL acceptance network that spans thousands of real venues, runs on existing devices, and speaks the right standards. That’s a watershed moment. If you build consumer journeys that hinge on proof of age or identity, it’s time to move mDL from the roadmap to the backlog—and to do it in a way that preserves privacy, reduces fraud, and scales nationally. 

Sources:

• PR Newswire announcement;
• Identity Week coverage;
• Biometric Update (standards compliance);
• ISO overview of 18013-7.