Prepare a future pilot
Scope locations, hardware, staff training, fallback policy, and the exact production-support boundary.
Start a pilotstate · AR · Registry 2026.09.13.1
Arkansas is currently listed by both Apple Wallet and Google Wallet. Laurel has not completed every production gate for either wallet, so both remain outside production support.
Live operational status has not yet been confirmed. No production support is asserted by this static page.
No jurisdiction-wallet pair is production enabled by the checked-in public delivery model.
Current status
The issuing authority for this record is Arkansas Department of Finance and Administration Office of Driver Services. Every status below is generated from the same canonical registry used by Laurel’s public support API and device-policy artifacts.
| Wallet | Wallet status | Issuer trust | Automated | Physical | Laurel production |
|---|---|---|---|---|---|
| Apple Wallet | Wallet available | Not yet established | Not yet run | Physical pass Elo M51 | Not production supported |
| Google Wallet | Wallet available | Not yet established | Not yet run | Physical pass Elo M51 | Not production supported |
State mobile-ID overview
Arkansas passed Laurel's physical Apple Wallet and Google Wallet checks on Elo M51. Official Arkansas certificate bytes have not yet been obtained and independently pinned, so the state remains physical_pass_trust_binding_pending and Laurel does not claim production support.
The issuing authority publishes an official mobile-ID program page. That page can establish a public program claim; it cannot independently make issuer material trusted by Laurel.
Complete the remaining qualification gates, repeat-session target, defect review, and explicit audited promotion before enabling production.
Next source review due .
Jurisdiction review record
This record identifies the authority, exact first-party source, program finding, provider-list result, predicate evidence, and trust gate used for this page.
Privacy-preserving age verification
LaurelID uses the ISO mdoc request for
org.iso.18013.5.1.mDL, namespace
org.iso.18013.5.1, element age_over_21, with
intentToRetain=false. If the required predicate is unavailable,
the result is Unable to verify. The verifier does not request date of birth as
a fallback.
The platform receives an allowlisted outcome and operational metadata. It does not retain a patron’s name, date of birth, address, portrait, document number, wallet identifier, mobile-ID payload, session transcript, or repeat-visitor identifier.
Merchant and venue preparation
Confirm with Arkansas Department of Finance and Administration Office of Driver Services which credential channels are currently available; do not treat a wallet-provider listing as Laurel qualification.
Bookmark the reviewed Arkansas mobile-ID program page and record any issuer or enrollment change before scheduling a qualification session.
Keep a documented physical-ID fallback and train staff that “Unable to verify” is not an age decision.
Prepare a managed Android verifier profile with NFC, Bluetooth Low Energy, secure device management, and a tested offline operating procedure.
Review the age-check workflow with privacy and security stakeholders: Laurel requests only age_over_21, sets intentToRetain=false, and does not retain patron identity.
Keep the fallback visible: Acceptance requirements depend on applicable law, merchant policy, and the issuing authority. Laurel’s technical compatibility status is not a legal determination.
Qualification participation
Eligible credential holders, merchants, hardware partners, and resellers can volunteer for a controlled test. Qualification mode is marked “NOT FOR COMMERCE,” requires an operator-selected jurisdiction and wallet, and creates a separate privacy-safe qualification event. A successful test never promotes a wallet automatically.
Contact details submitted here are stored separately from verification telemetry and cannot be linked to a presentation event.
Pilot and review
Scope locations, hardware, staff training, fallback policy, and the exact production-support boundary.
Start a pilotWalk through issuer trust, device configuration, offline behavior, event allowlists, and the no-patron-PII architecture.
Request a security reviewAlign qualification evidence, managed hardware, operator training, and truthful status language before selling.
Explore reseller readinessKnown limitations
Official sources
Page last reviewed . Registry version 2026.09.13.1.
Frequently asked questions
Yes. Apple’s current official availability page lists Arkansas. That confirms wallet availability, not Laurel production support.
Yes. Google’s current official availability page lists Arkansas. That confirms wallet availability, not Laurel production support.
No. Arkansas has not passed every Laurel production gate. A page in this directory, wallet availability, or an issuer announcement does not independently create production support.
The verifier requests only the ISO mdoc age_over_21 predicate and sets intentToRetain=false. It does not fall back to requesting a date of birth, name, address, portrait, or document number.
Browse the nationwide directory or the compatibility overview. Permanent URL: /mobile-id-age-verification/arkansas .