Prepare a future pilot
Scope locations, hardware, staff training, fallback policy, and the exact production-support boundary.
Start a pilotstate · WA · Registry 2026.09.13.1
Washington is included in Laurel’s nationwide qualification directory, but the reviewed current Apple and Google sources do not establish wallet availability. No Laurel production support is claimed.
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 Washington State Department of Licensing. 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 | Planned | Not yet established | Not yet run | Not yet tested | Not production supported |
| Google Wallet | Planned | Not yet established | Not yet run | Not yet tested | Not production supported |
State mobile-ID overview
Washington is represented for nationwide qualification planning. The reviewed Apple and Google current lists do not establish wallet availability, and Laurel does not claim production support.
The reviewed registry does not contain a current official program URL. Laurel treats the program status as unknown, without inferring availability from an old announcement or third-party report.
Monitor first-party issuer and wallet sources. Merchants can prepare policy, hardware, training, and a physical-ID fallback without representing the jurisdiction as supported.
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
Monitor Washington State Department of Licensing and the wallet providers for a current issuance notice; avoid promising a launch date.
Monitor Washington State Department of Licensing's driver-license and mobile-ID notices. Laurel did not find a dedicated current program page in this review, so do not infer issuance from a general licensing page.
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
The reviewed current Apple source does not establish Apple Wallet availability for Washington. Absence from that list is treated as unknown, not proof that availability is impossible.
The reviewed current Google source does not establish Google Wallet availability for Washington. Absence from that list is treated as unknown, not explicit unavailability.
No. Washington 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/washington .