A mobile driver’s license (mDL) is a digital version of your physical driver’s license, stored on your smartphone and issued by your state’s Department of Motor Vehicles. Unlike a photo of your card, an mDL is a cryptographically signed credential that can be verified as authentic — making it far more secure than a physical card.
mDLs are built on the ISO/IEC 18013-5:2021 international standard, which defines how digital credentials are stored, presented, and verified. This standard ensures interoperability across states, wallets, and reader devices.
How Does an mDL Work?
When you present your mDL, your phone communicates with the verifier’s device using NFC (tap) or Bluetooth Low Energy (BLE). Here’s what happens:
- The verifier’s device sends a request — specifying which data fields it needs (e.g., name, date of birth, or just “over 21?”)
- Your phone asks for your approval — you see exactly what’s being requested and authorize sharing with Face ID, Touch ID, or your passcode
- Only the approved data is transmitted — encrypted over a secure channel
- The verifier’s device checks the state’s cryptographic signature — confirming the credential is authentic and hasn’t been tampered with
The entire process takes seconds and works offline — no internet connection is required for either party.
Why Are Governments Adopting mDLs?
State governments are rolling out mDLs for several compelling reasons:
- Fraud prevention — mDLs are nearly impossible to forge. Each credential is signed by the issuing state’s certificate authority, and that signature is verified cryptographically during every transaction.
- Privacy protection — unlike handing over a physical card, mDLs enable selective disclosure. A bar only needs to know you’re over 21, not your home address. An mDL can share just that one data point.
- Convenience — residents increasingly expect digital-first government services. An mDL lets citizens carry their ID on the device they already have with them.
- Reduced identity theft — physical cards can be photographed, photocopied, or stolen. mDL data is encrypted and never stored on the verifier’s device.
- Federal alignment — the Department of Homeland Security (DHS) and the American Association of Motor Vehicle Administrators (AAMVA) have actively supported mDL development. AAMVA publishes the mDL Implementation Guidelines that help states align their programs with the ISO 18013-5 standard and federal REAL ID Act requirements.
The Role of AAMVA, DHS, and Federal Standards
The mDL ecosystem is shaped by several federal and industry bodies:
- AAMVA (American Association of Motor Vehicle Administrators) — the organization that coordinates DMV operations across all U.S. states and territories. AAMVA maintains the mDL Implementation Guidelines, operates the mDL Connection service for cross-state certificate trust, and works with ISO on the 18013-5 standard.
- DHS / TSA — the Transportation Security Administration accepts mDLs at participating airport checkpoints nationwide. As of 2026, mDLs are accepted at 25+ airports across participating states. DHS has signaled that digital credentials will play a growing role in REAL ID compliance.
- REAL ID Act — the federal law requiring states to issue IDs that meet minimum security standards for federal purposes (boarding flights, entering federal buildings). While current REAL ID requirements focus on physical cards, future amendments are expected to recognize compliant mDLs as valid REAL ID credentials.
- ISO/IEC JTC 1/SC 17 — the international standards body that developed and maintains the 18013-5 standard. The upcoming ISO 18013-7 standard will extend mDL verification to online and remote use cases.
Which States Have mDL Programs?
mDL adoption is accelerating across the United States. Here’s the current landscape:
| State | Status | Notes |
|---|---|---|
| Georgia | Active + Mandate | HB 296 requires all LE agencies to accept mDLs by July 2027 |
| Arizona | Active | Available in Apple Wallet and state app |
| California | Active | DMV Wallet app, Apple Wallet, Google Wallet |
| Colorado | Active | Available in Apple and Google Wallets |
| Iowa | Active | Pioneer state — first U.S. mDL pilot (2016) |
| Maryland | Active | Available in Apple Wallet |
| Utah | Active | Available via state mobile ID app |
| Louisiana | Active | LA Wallet app, widely accepted |
| Ohio | Active | Launched 2025 |
| Arkansas | Active | Available in state app, Apple Wallet, Google Wallet, Samsung Wallet |
| Hawaii | Active | Available in Apple Wallet |
| Montana | Active | mDL program live |
| New Mexico | Active | mDL program live |
| North Dakota | Active | mDL program live |
| New York | Active | MiD app and Apple Wallet, 200K+ enrollments |
| Virginia | Active | Available in Apple Wallet, expanding use cases |
| Delaware | Active | mDL program live |
| Illinois | Active | mDL program live |
| Kentucky | Active | mDL program live |
| Alaska | Active | mDL program live |
| Puerto Rico | Active | mDL program live |
| West Virginia | Active | mDL program live |
For a detailed breakdown of state mandates and compliance deadlines, see our State-by-State mDL Reader Requirements Tracker.
How Is an mDL Different from a Physical License?
| Feature | Physical DL | Mobile DL (mDL) |
|---|---|---|
| Forgery resistance | Moderate (holograms, UV ink) | Very high (cryptographic signature) |
| Selective disclosure | No — full card is visible | Yes — share only needed fields |
| Offline verification | Visual check only | Full cryptographic verification offline |
| Data retention | Verifier sees all info | Verifier device retains nothing |
| Lost/stolen risk | High — card can be used by anyone | Low — biometric lock on device |
| Update speed | Requires new card | Instant OTA update from DMV |
How Do Agencies and Businesses Verify mDLs?
Verification requires an mDL reader — a device or app that implements the ISO 18013-5 standard. The reader:
- Establishes a secure connection with the holder’s phone (NFC or BLE)
- Requests specific data elements
- Receives the signed response
- Validates the issuing state’s certificate chain
- Displays the verified information to the operator
For a deeper dive into the verification process, see How Does mDL Verification Work?
For law enforcement agencies, this means officers can verify a digital ID in the field with a single tap — no manual data entry, no visual-only checks, and full cryptographic proof of authenticity.
For businesses, mDL readers enable age verification, identity checks, and fraud prevention without handling physical documents or storing personal information.
What Does This Mean for Law Enforcement?
Mandates Are Coming
Several states are moving beyond voluntary adoption to mandate mDL acceptance. Georgia’s House Bill 296 is the most prominent example:
- Phase 1 (July 2025): Officers equipped with readers must accept mDLs
- Phase 2 (July 2027): All Georgia law enforcement agencies must have mDL readers and accept digital credentials
Read the full breakdown: What Does Georgia HB 296 Require for Law Enforcement?
For agencies evaluating compliance, the key question is not whether to adopt mDL readers, but when — and the deadlines are approaching fast.
Officer Safety
mDL verification has a direct impact on officer safety during traffic stops. Traditional ID checks require the officer to approach the vehicle, take the physical card, return to the patrol vehicle to run it, and then make a second approach to return the card. Each approach to the vehicle window is a point of vulnerability.
With mDL tap-to-verify, the officer can verify the credential in a single interaction — reducing time at the window and minimizing exposure. The verification result is immediate, and there is no physical card to handle or return.
Use Cases Beyond Traffic Stops
mDL readers are not limited to roadside encounters. Law enforcement agencies are deploying them across operations:
- Booking and intake — verify identity during arrest processing without relying on potentially fraudulent physical documents
- Warrant service — confirm the identity of the subject before executing a warrant
- Probation and parole check-ins — streamline identity verification during routine reporting
- Court appearances — verify defendant identity at arraignment or sentencing
- Investigations — verify witness or suspect identity in the field without transporting to a station
- Special events and access control — verify credentials at secure perimeters, government buildings, or restricted areas
CJIS Compliance Considerations
Any technology that handles personally identifiable information (PII) in a law enforcement context must align with the FBI’s Criminal Justice Information Services (CJIS) Security Policy. Key considerations for mDL reader deployments:
- Data at rest — compliant mDL readers should not retain personal data after verification, which simplifies CJIS requirements since no PII is stored
- Data in transit — the ISO 18013-5 standard requires encrypted communication between the holder’s device and the reader, aligning with CJIS encryption requirements
- Access control — reader applications should enforce authentication (PIN, biometric) before an officer can initiate a verification
- Audit logging — agencies should ensure their reader solution supports audit trails for verification events, consistent with CJIS accountability requirements
Frequently Asked Questions
Is a mobile driver’s license the same as a photo of your license?
No. A mobile driver’s license (mDL) is a cryptographically signed digital credential issued by your state’s DMV, stored in a secure element on your phone. A photo of your license has no security features and can be easily faked. An mDL can be verified as authentic using the state’s digital signature.
What states accept mobile driver’s licenses?
As of 2026, over 20 states plus Puerto Rico have active mDL programs, including Georgia, Arizona, California, Colorado, Iowa, Maryland, New York, Virginia, and others. Georgia’s HB 296 mandates that all law enforcement agencies accept mDLs by July 2027. TSA accepts mDLs at 25+ airports. Adoption is growing rapidly across the U.S.
What is the ISO 18013-5 standard?
ISO/IEC 18013-5:2021 is the international standard that defines how mobile driver’s licenses are stored, presented, and verified. It specifies the cryptographic protocols, data structures, and communication methods (NFC and BLE) used for mDL verification. The standard is maintained by ISO/IEC JTC 1/SC 17 and is the foundation for all compliant mDL programs in the United States, guided by AAMVA implementation guidelines.
How is a mobile driver’s license verified?
An mDL is verified using a reader device or app that communicates with the holder’s phone via NFC or Bluetooth. The reader checks the state’s cryptographic signature to confirm the credential is authentic and unaltered. Only the data fields approved by the holder are shared.
Do I still need to carry my physical driver’s license?
In most states, yes. Even in states with active mDL programs, drivers are generally still required to carry their physical card. The mDL is an additional form of identification, not a replacement.
Can someone steal my identity through an mDL?
No. mDLs are designed with privacy as a core feature. Your phone only shares specific data fields you approve (e.g., just your age for an age check), the data is encrypted during transmission, and the verifier’s device does not retain your information.