Plan a live-status-gated pilot
Scope locations, hardware, staff training, fallback policy, and the exact production-support boundary.
Start a pilotstate · NM · Registry 2026.09.13.1
New Mexico has checked-in qualification and administrative evidence for Apple Wallet and Google Wallet, but this static page does not assert live production support. A matching live operational API response is required to display Supported. Google Wallet and Apple Wallet remain independent qualification dimensions.
Live operational status has not yet been confirmed. No production support is asserted by this static page.
The checked-in registry preserves completed evidence for Apple Wallet and Google Wallet, but a matching live operational response is required before displaying Supported.
Current status
The issuing authority for this record is New Mexico Motor Vehicle Division. 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 | Issuer trust recognized | Automated pass | Physical pass Elo M51 | Live operational status required |
| Google Wallet | Wallet available | Issuer trust recognized | Automated pass | Physical pass Elo M51 | Live operational status required |
State mobile-ID overview
The checked-in registry records completed qualification evidence for Apple Wallet and Google Wallet in New Mexico. Live operational API status is required before this website can label that jurisdiction-wallet pair Supported; each other wallet remains an independent qualification target.
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.
Maintain New Mexico continuity testing after every trust-list, registry, verifier, or transport release.
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 New Mexico Motor Vehicle Division which credential channels are currently available; do not treat a wallet-provider listing as Laurel qualification.
Bookmark the reviewed New Mexico 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 New Mexico. That confirms wallet availability, not Laurel production support.
Yes. Google’s current official availability page lists New Mexico. That confirms wallet availability, not Laurel production support.
The checked-in registry records completed qualification evidence for Apple Wallet and Google Wallet, but live operational API status is required before this page can answer yes. If that status is unavailable or suspended, Laurel makes no production-support claim and staff must use the documented physical-ID fallback.
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/new-mexico .