Back to guides

Mobile Driver's License and NFC: How Digital ID Reads

A mobile driver's license presents over NFC using ISO 18013-5. Here's exactly what happens when you tap your phone, and what a reader actually learns.

Published

What It Is

A mobile driver's license — an mDL — is a phone-based ID that presents itself to a compatible reader over NFC. It's built on ISO/IEC 18013-5, the international standard approved in August 2021 that defines the data format and the NFC/BLE transport a phone and reader use to talk.

If you already read NFC tags with NFCore, the mechanism feels familiar: a short-range contactless handshake. What's different is what happens during it — a phone holding a driver's license doesn't hand over a data dump, it negotiates field by field what the reader gets to see. That's the interesting part, and it's what the rest of this article covers.

How It Actually Works

Getting it onto the phone. Before you can present anything, you have to provision it. Apple Wallet and Google Wallet both require photos of the front and back of the physical card plus a liveness check — a selfie, a Live Photo, or head-movement prompts — so the issuer can confirm the person adding the ID is the person on the card, not someone using a photo or a mask.

The tap. Presenting it uses the same gesture NFCore users already know from how Apple Pay and Google Pay use NFC: hold the top of the phone near the reader. The screen shows exactly what's being requested before anything moves, you confirm with Face ID, Touch ID, or your screen lock, and a checkmark closes the exchange. Android's flow is nearly identical — unlock, hold it near the terminal, review, authorize, wait for confirmation.

Why it's not just scanning a card. ISO 18013-5 supports selective disclosure. A bar checking your age gets back "over 21: yes," not your date of birth. Nothing leaves the device until you've authenticated locally, and the radio link itself is encrypted, so there's no passive read the way there can be with an unlocked NFC tag (our NFC security basics covers sniffing and replay in more depth). Neither Apple, Google, nor the issuing DMV can see when or where you used it — there's no phone-home built into the standard.

How this compares to a passport chip. If you've read a passport's NFC chip with your phone, you've already touched the ancestor of this idea. A passport's chip (ICAO 9303, since 2003) gets read in full and checked against a certificate the issuing country publishes globally. An mDL borrows that contactless-plus-signed-trust model but flips the disclosure around: your phone decides which fields go out, instead of a reader pulling everything at once.

Where You'll See It

Right now, the dominant real-world use is airport security. mDLs and digital passports are accepted at more than 250 TSA checkpoints across 21 states and Puerto Rico. Outside TSA, acceptance is thinner — retail age checks, some DMV kiosks — because every relying party has to deploy and certify its own ISO 18013-5 reader, state by state.

iOS and Android don't handle this identically, either. Supported states differ between Apple Wallet and Google Wallet. Either way, both companies are explicit that a digital ID doesn't replace the physical card yet, so keep carrying it.

Tips, Gotchas, and NFCore's Place in This

NFCore reads and inspects NFC tags — UID, tag type, raw NDEF payload — the same structural curiosity that makes an mDL's tap-and-negotiate flow interesting. To be clear: NFCore doesn't read, write, or interact with mDL or passport credentials. Those run a different secure protocol than consumer NFC tags, and that's a boundary by design.

If what you actually want is the tag side of NFC — UIDs, NDEF structure, locking — open NFCore and inspect a tag you own.

Frequently Asked Questions

Is a mobile driver's license the same as an NFC passport chip?

Related, not the same. A passport's NFC chip (ICAO 9303) is read in full and checked against a signed certificate — a fixed pull. A mobile driver's license under ISO 18013-5 also uses NFC, but the phone negotiates which fields to release, so an age check gets a yes/no, not your birthdate.

Can someone read my digital ID just by standing near me with an NFC reader?

No. ISO 18013-5 requires on-device authentication — Face ID, Touch ID, or an Android screen-lock check — before anything leaves the phone, and the screen shows what's being requested first. There's no passive broadcast; you have to tap and approve.

Does adding a digital ID mean I can leave my physical license at home?

Not yet. Apple and Google both say a digital ID doesn't replace the physical card. Acceptance is still mostly limited to TSA checkpoints and a handful of state services, so carry the physical card as backup.

Which US states support digital driver's licenses right now?

It varies by wallet and keeps expanding. Google Wallet currently covers Arizona, Colorado, Georgia, Maryland, and New Mexico, with Iowa and Ohio in progress. Apple's list overlaps but isn't identical — check your state DMV before assuming yours is covered.

Conclusion

The interesting part was never that it's "just NFC" — plenty of things use NFC. It's that the standard hands your phone the decision about what to share, field by field, instead of a reader taking everything at once. As more states and countries adopt ISO 18013-5, expect that tap-to-verify gesture to show up in more places than airport security.