LaurelID
Start a pilot
LaurelID

Supported IDs · Registry 2026.09.13.1

Which mobile IDs LaurelID accepts today.

Wallet availability from a state is not the same as Laurel support. This page keeps the two apart: what is available now, what is being qualified, and what is planned, for every state, DC and Puerto Rico.

What you get today, and what is coming.

Every capability on this site carries one of three labels. Nothing planned is described as if it already works.

Available now

  • Mobile driver's licenses from 13 states and Puerto Rico in Apple Wallet and Google Wallet, on Elo M51.
  • A local 21+ decision on the verifier: Verified 21+, Under 21, or Unable to verify.
  • Verification continues when the network does not; outcomes catch up later.
  • The console: add a verifier in three steps, see every location and verifier, aggregate reports, team roles.

In qualification

  • Arkansas: physically tested in both wallets, waiting on the issuing authority's certificate binding.
  • Further states as their issuing authorities publish trust material and each pair passes physical testing.

Planned

  • A per-decision evidence record your business can keep and export, still without patron identity.
  • A decision API and a local result surface so a register or gate can ask Laurel and get an answer.
  • Longer offline operation under a signed licence, instead of daily renewal.

Per-jurisdiction detail, with the evidence behind each label, is on the supported IDs page.

Live operational status has not yet been confirmed. Static matrix rows do not assert production support.

Status vocabulary

Only “Supported” means Laurel production support.

Supported

Supported

Every gate passed and the matching live operational API response confirms production_enabled=true.

In qualification

In qualification

Some Laurel evidence exists, but the pair is not production enabled.

Wallet available

Wallet available

The provider lists the issuer. Laurel qualification is a separate claim.

Planned

Announced or planned

No current provider availability or completed Laurel gate is implied.

Canonical support matrix

All 52 required U.S. jurisdictions.

Select a jurisdiction for its issuer, evidence, qualification gates, limitations, last-reviewed date, and practical next action.

Registry-derived mobile-ID status for all required U.S. jurisdictions
Jurisdiction Apple Wallet Google Wallet Laurel status Production wallet Last reviewed
Alabama Planned Planned Planned No live production-enabled pair
Alaska Planned Planned Planned No live production-enabled pair
Arizona Wallet available Wallet available In qualification Live operational status required
Arkansas Wallet available Wallet available In qualification No live production-enabled pair
California Wallet available Wallet available In qualification Live operational status required
Colorado Wallet available Wallet available In qualification Live operational status required
Connecticut Planned Planned Planned No live production-enabled pair
Delaware Planned Planned Planned No live production-enabled pair
District of Columbia Planned Planned Planned No live production-enabled pair
Florida Planned Planned Planned No live production-enabled pair
Georgia Wallet available Wallet available In qualification Live operational status required
Hawaii Wallet available Wallet available In qualification Live operational status required
Idaho Planned Planned Planned No live production-enabled pair
Illinois Wallet available Wallet available In qualification Live operational status required
Indiana Planned Planned Planned No live production-enabled pair
Iowa Wallet available Wallet available In qualification Live operational status required
Kansas Planned Planned Planned No live production-enabled pair
Kentucky Announced Announced Announced No live production-enabled pair
Louisiana Planned Planned Planned No live production-enabled pair
Maine Planned Planned Planned No live production-enabled pair
Maryland Wallet available Wallet available In qualification Live operational status required
Massachusetts Planned Planned Planned No live production-enabled pair
Michigan Planned Planned Planned No live production-enabled pair
Minnesota Planned Planned Planned No live production-enabled pair
Mississippi Planned Planned Planned No live production-enabled pair
Missouri Planned Planned Planned No live production-enabled pair
Montana Wallet available Wallet available In qualification Live operational status required
Nebraska Planned Planned Planned No live production-enabled pair
Nevada Planned Planned Planned No live production-enabled pair
New Hampshire Planned Planned Planned No live production-enabled pair
New Jersey Planned Planned Planned No live production-enabled pair
New Mexico Wallet available Wallet available In qualification Live operational status required
New York Planned Planned Planned No live production-enabled pair
North Carolina Planned Planned Planned No live production-enabled pair
North Dakota Wallet available Wallet available In qualification Live operational status required
Ohio Wallet available Wallet available In qualification Live operational status required
Oklahoma Wallet available Planned In qualification No live production-enabled pair
Oregon Planned Planned Planned No live production-enabled pair
Pennsylvania Planned Planned Planned No live production-enabled pair
Puerto Rico Wallet available Wallet available In qualification Live operational status required
Rhode Island Planned Planned Planned No live production-enabled pair
South Carolina Planned Planned Planned No live production-enabled pair
South Dakota Planned Planned Planned No live production-enabled pair
Tennessee Planned Planned Planned No live production-enabled pair
Texas Planned Planned Planned No live production-enabled pair
Utah Announced Planned In qualification No live production-enabled pair
Vermont Planned Planned Planned No live production-enabled pair
Virginia Wallet available Planned In qualification No live production-enabled pair
Washington Planned Planned Planned No live production-enabled pair
West Virginia Wallet available Wallet available In qualification Live operational status required
Wisconsin Planned Planned Planned No live production-enabled pair
Wyoming Planned Planned Planned No live production-enabled pair

Need a faster starting point? Browse the filterable U.S. mobile-ID directory.

What LaurelID can read

Three kinds of digital ID, six separate facts each.

Implemented, issuer trust, tested, wallet presentation, offered, and legal review are recorded independently. None of them implies another, and only a real-credential test on Laurel hardware turns “implemented” into “verified.”

State driver's license or ID

Implemented
Implemented
Issuer trust
Issuer trust reviewed
Tested
Verified with a real credential
Wallet presentation
Presentable in person
Offered by Laurel
Pilot
Legal review
Legal review required

Only age_over_21 is requested, with intentToRetain=false.

Technical details

ISO/IEC 18013-5:2021. Document type org.iso.18013.5.1.mDL, namespace org.iso.18013.5.1, requested element age_over_21, never retained.

Digital ID (U.S. passport) in Apple Wallet

Implemented
Implemented
Issuer trust
Issuer trust reviewed
Tested
Verified with test credentials
Wallet presentation
Documented by the wallet provider for standard readers
Offered by Laurel
Not offered
Legal review
Legal review not started

Apple's consumer availability statement names only select TSA checkpoints; Apple's developer documentation states ISO 18013-5 capable terminals may accept the credential. Whether Apple Wallet presents a Digital ID to this terminal in person is unverified until a physical session.

Technical details

ISO/IEC TS 23220-4 Photo ID profile presented over ISO/IEC 18013-5 device retrieval. Document type org.iso.23220.photoid.1, namespace org.iso.23220.1, requested element age_over_21, never retained.

ID pass in Google Wallet

Implemented
Implemented
Issuer trust
Issuer trust reviewed
Tested
Verified with test credentials
Wallet presentation
Wallet presentation not verified
Offered by Laurel
Not offered
Legal review
Legal review not started

Out of scope for the Apple credential expansion; carried unchanged.

Technical details

Google Wallet ID pass (ISO/IEC 18013-5 namespace, Google docType). Document type com.google.wallet.idcard.1, namespace org.iso.18013.5.1, requested element age_over_21, never retained.

Apple Wallet

Apple availability is its own evidence dimension.

Apple’s current provider page and official issuer material determine public availability claims. A historical announcement absent from the current list remains “Announced,” not wallet available.

Checked-in evidence and live boundary

The registry preserves completed physical evidence for 15 jurisdictions in both Apple Wallet and Google Wallet; 14 have also passed the canonical production gates. Arkansas is physically qualified in Apple Wallet and Google Wallet, but official issuing-authority certificate binding remains pending; it is not production enabled. This static page does not label any of them Supported. A matching live operational response must confirm production_enabled=true. Every other jurisdiction remains separately gated.

Google Wallet

Google follows the same standards-first verifier path.

Google documents ISO 18013-5 mDL presentation and the age_over_21 attribute. That provider capability is not per-jurisdiction predicate proof and does not replace signed trust material or physical qualification.

14 Google Wallet qualification candidates are recorded

The checked-in registry records Google Wallet physical evidence for the same 14 trust-bound jurisdictions as Apple Wallet. Wallet family remains an evidence dimension only: production presentation is wallet-agnostic, and live operational status is still required before this static page says Supported.

Frequently asked questions

Compatibility, without shortcuts.

Does wallet availability mean LaurelID supports the credential?

No. Wallet availability is evidence about an issuer and wallet provider. Laurel production support additionally requires validated issuer trust, the protected ISO mdoc scope, automated tests, real-credential testing, repeated sessions or an approved exception, an audited promotion, and no unresolved high or critical defect.

Which jurisdiction-wallet combination is production supported?

This static page does not assert live production support. The checked-in registry preserves completed physical evidence for 15 jurisdictions in both Apple Wallet and Google Wallet; 14 have also passed the canonical production gates. Arkansas is physically qualified in Apple Wallet and Google Wallet, but official issuing-authority certificate binding remains pending; it is not production enabled. Only a matching live operational API response may upgrade a row to Supported. An unavailable or suspended response fails closed.

What happens when a mobile ID is not production supported?

Production mode fails closed and staff use the business’s documented physical-ID fallback. Controlled testing must use the visibly marked qualification mode and does not create a production verification event.

Does LaurelID request a date of birth when age_over_21 is missing?

No. LaurelID requests only age_over_21 with intentToRetain=false. If the predicate is unavailable, the result is Unable to verify.

Next step

Have a real credential for a controlled qualification?

Open your jurisdiction page to register testing interest without submitting credential data, screenshots, or verification-event details.

Start a pilot Request a security review