What it feels like to use

The technology is invisible by design. Here's what each person actually does — and what they no longer have to.

The story, end to end

1. The DMV issues a mobile license

   A resident requests their mobile driver's license from the DMV portal or app. They authenticate once, pick the wallet they already use, and the license lands in it — alongside their existing physical card.

   No state-mandated app. Their wallet, their choice.

2. The resident holds and controls it

   The license lives on their phone, under their control. Nothing is shared automatically — every presentation needs an explicit, one-time approval the resident sees and consents to.

   The state can't watch where it's used.

3. They prove just one thing, when needed

   At a bar, the resident taps to prove "over 21" — and reveals nothing else. No name, no address, no birthdate. At an airport or a website, they share exactly the fields asked for, and no more.

   Selective disclosure: minimum data, every time.

What the resident experiences

• Their choice of wallet. Not a single government-approved app.
• Prove a fact, not your identity. "Over 21" without your birthdate.
• One-tap consent. Nothing leaves the phone without approval.
• No tracking. The state doesn't see each place it's used.

What the agency experiences

• Privacy by design. Data minimization is built into every request.
• Instant, tamper-evident checks. No call-backs to the DMV.
• No vendor or wallet lock-in. Works with every conformant wallet.
• Standards-based. Built on open W3C Verifiable Credentials.

See the technical flow Build it