Georgia House Bill 296 is the most significant mDL mandate in the United States. Signed into law alongside Georgia’s mDL rollout, it establishes a clear timeline for law enforcement agencies to adopt mobile driver’s license readers — with a hard deadline of July 1, 2027.
If you’re a chief, sheriff, or procurement officer at a Georgia law enforcement agency, here’s exactly what the law requires and how to prepare.
The Two Phases of HB 296
HB 296 rolls out in two phases:
| Phase | Effective Date | Requirement |
|---|---|---|
| Phase 1 | July 1, 2025 | Officers who have mDL readers must accept mobile driver’s licenses. If an officer does not have a reader, the driver must present a physical card as fallback. |
| Phase 2 | July 1, 2027 | All Georgia law enforcement agencies must have mDL readers deployed and must accept mobile driver’s licenses. No fallback exception. |
The bottom line: After July 1, 2027, every Georgia law enforcement agency must be capable of verifying mobile driver’s licenses in the field.
Key Provisions
Mandatory Acceptance
Once an agency has mDL readers (Phase 1) — or after the Phase 2 deadline — officers must accept a mobile driver’s license as a valid form of identification. A driver cannot be cited for failing to produce a physical card if they present a valid mDL.
Privacy Protections
HB 296 includes strong privacy provisions:
- No phone seizure — presenting an mDL does not constitute consent to search the driver’s device. Officers cannot take possession of the phone.
- Selective disclosure — the mDL reader only receives the specific data fields requested (e.g., name, date of birth, license status). The officer does not see the driver’s full digital wallet.
- No data retention — the mDL transaction is ephemeral. Compliant readers do not store the driver’s personal information after verification.
Physical Card Requirement
During both phases, drivers are still required to carry their physical driver’s license. The mDL is an additional, legally recognized form of identification — not a replacement for the physical card.
How to Comply: Agency Checklist
Use this checklist to prepare your agency for HB 296 compliance:
- Evaluate mDL reader solutions — look for ISO 18013-5 compliant readers that verify the state’s cryptographic signature (not just barcode scanners)
- Choose a deployment model — dedicated hardware readers or software-based readers on existing patrol devices (phones/tablets)
- Test with live mDLs — Georgia mDLs are available in Apple Wallet, Google Wallet, and the Georgia DDS app. Verify your reader works with all three.
- Train officers — the verification process is simple (tap-to-verify), but officers need to understand the privacy provisions (no phone seizure, selective disclosure)
- Update SOPs — document the mDL verification procedure in your standard operating procedures
- Plan for connectivity — mDL verification works fully offline, but ensure your reader solution doesn’t require internet for basic operation
- Budget and procure — allocate funding for readers and any associated licensing. Many software-based solutions run on hardware your agency already owns.
Officer Safety Benefits
Beyond compliance, mDL readers offer a tangible officer safety improvement during traffic stops. The traditional process — approach, collect physical ID, return to patrol vehicle, run the ID, approach again to return the card — creates multiple points of vulnerability at the vehicle window.
With mDL tap-to-verify:
- Single interaction — verify the credential in one approach, reducing time at the window
- Immediate results — cryptographic verification takes seconds, not minutes
- No physical handoff — no card to take, run, and return
- Hands-free data — verified identity data appears on the officer’s device without manual entry
For agencies evaluating mDL readers, this operational improvement alone justifies early adoption — well before the legal deadline.
CJIS and Data Security Considerations
Georgia agencies subject to the FBI CJIS Security Policy should note that compliant mDL readers align well with CJIS requirements:
- No PII retention — ISO 18013-5 compliant readers do not store personal data after verification, reducing the data security burden
- Encrypted transmission — all data exchanged between the holder’s phone and the reader is encrypted, meeting CJIS encryption-in-transit standards
- Audit trails — agencies should ensure their chosen reader supports verification event logging for CJIS accountability
- Access controls — reader apps should require officer authentication (PIN or biometric) before use
When evaluating reader solutions, confirm that the vendor can provide documentation of their security architecture for your agency’s CJIS compliance review.
Why Rural Agencies Should Act Now
Georgia has approximately 500+ law enforcement agencies, and many smaller and rural departments have publicly stated they are years from readiness. The July 2027 deadline does not distinguish between large metro departments and small-town agencies — the mandate applies equally.
Starting the procurement and training process now gives your agency time to:
- Evaluate and pilot solutions without rush
- Train officers in a low-pressure environment
- Identify and resolve any technical issues before the deadline
- Take advantage of potential state or federal grant funding for technology upgrades (including Edward Byrne Memorial Justice Assistance Grants (JAG) and state-level technology modernization funds)
Georgia’s mDL Landscape
Georgia is one of the leading states in mDL adoption:
- ~8% of the 7.2 million U.S. mDLs are Georgia credentials (as of late 2025)
- Digital IDs are available through Apple Wallet, Google Wallet, and the Georgia DDS mobile app
- The state’s mDL program launched alongside HB 296, signaling a coordinated push toward digital-first identity
As adoption grows, the frequency of mDL presentations during traffic stops and other encounters will increase steadily — making reader deployment a practical necessity well before the legal deadline.
Frequently Asked Questions
When do Georgia police need mDL readers?
Georgia HB 296 has two phases. Phase 1 (effective July 1, 2025) requires officers who have mDL readers to accept digital credentials. Phase 2 (effective July 1, 2027) requires ALL Georgia law enforcement agencies to have mDL readers and accept mobile driver’s licenses.
What happens if my agency isn’t ready by July 2027?
After July 1, 2027, all Georgia law enforcement agencies are required to accept mDLs. Agencies without readers will not be in compliance with state law. Drivers who present valid mDLs cannot be penalized for not having a physical card if the agency fails to provide a reader.
Can officers take a driver’s phone during an mDL check?
No. Georgia HB 296 explicitly states that presenting a mobile driver’s license does not constitute consent to search the device. The officer cannot take possession of the driver’s phone.
Does Georgia HB 296 apply to businesses?
HB 296 specifically mandates acceptance by law enforcement agencies. However, businesses that verify IDs — such as bars, retailers, and age-restricted venues — can also benefit from mDL readers to prevent fraud and streamline verification.
What is an mDL reader?
An mDL reader is a device or app that implements the ISO 18013-5 standard to verify mobile driver’s licenses. It communicates with the holder’s phone via NFC or Bluetooth, checks the state’s cryptographic signature, and displays verified identity information. Learn more: How Does mDL Verification Work?
Munio is an ISO 18013-5 compliant mDL reader built for law enforcement and businesses. Contact us to learn how Munio can help your agency comply with HB 296.