Digital IDs Are Quietly Replacing the Wallet, Starting With the Least Controversial Document

Mobile driver's licenses have spread across a growing number of US states and several national ID systems abroad on the strength of the least controversial use case available: proving age or identity at a checkpoint that already trusts a physical card, with the phone as a strict superset of what the card could do. Airport security and age-restricted purchases were the wedge, not because they were the most valuable use case but because they required no new legal category — a phone showing a verified credential to a TSA agent or a cashier is functionally the same transaction as a card, just harder to forge and possible to present selectively. That selective presentation is the actual technical advance, and it is the part most coverage undersells. A physical driver's license exposes every field on it — full name, address, exact birth date, photo — to whoever glances at it, regardless of what the transaction actually required. A well-implemented mobile credential can prove a single attribute, "over 21," or "name matches boarding pass," without transmitting the rest of the document. Whether a given deployment actually does this, versus simply displaying a digital photo of the same license, varies enormously by implementation, and it is the single most consequential design decision buried inside "we now support digital ID." The interoperability problem is the same one every identity standard eventually hits: a credential a state issues has to be verified by relying parties — retailers, airlines, other states' police — who did not build the issuing system and have no reason to trust it by default. The standards work here has converged on ISO/IEC 18013-5 (mDL) for the credential format, which gives issuers and verifiers a common technical contract, but a shared format does not by itself produce a shared trust relationship; a verifier still has to decide which issuers it accepts, and that decision-making infrastructure is younger than the credential format itself. The unresolved question is what gets built on top once the verification infrastructure exists for one document. A phone that can prove a driver's license also has the technical capacity to prove other credentials — professional licenses, insurance cards, vaccination records, age verification for online services — and the strongest argument for building the mobile-ID rails carefully now is that the digital driver's license is not really the destination. It is the low-controversy pilot for infrastructure that later credentials, with considerably higher stakes if the privacy design is wrong, will be built on top of.