LaurelID
Start a pilot
LaurelID

state · OK · Registry 2026.09.13.1

Mobile ID age verification in Oklahoma

Oklahoma is currently listed by Apple Wallet. Google Wallet availability is not established by the reviewed sources, and Laurel has not completed production qualification.

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

Availability, qualification, and support are different gates.

The issuing authority for this record is Service Oklahoma. Every status below is generated from the same canonical registry used by Laurel’s public support API and device-policy artifacts.

Oklahoma mobile-ID status by wallet and Laurel qualification gate
Wallet Wallet status Issuer trust Automated Physical Laurel production
Apple Wallet Wallet available Issuer trust recognized Automated pass Not yet tested Not production supported
Google Wallet Planned Issuer trust recognized Automated pass Not yet tested Not production supported
Official mDL program
Legacy Decommissioned
Laurel qualification
In qualification
Laurel production support
No live production-enabled pair
Last reviewed

State mobile-ID overview

What first-party sources establish for Oklahoma.

Oklahoma's issuing-authority certificate is authenticated through the authenticated AAMVA Digital Trust Service VICAL and Laurel's verification path is fixture-verified for it; Apple Wallet lists Oklahoma as currently wallet-available. No real Oklahoma credential has been physically tested, so 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.

Required next action

Complete the remaining qualification gates, repeat-session target, defect review, and explicit audited promotion before enabling production.

Next source review due .

Jurisdiction review record

The evidence record reviewed for Oklahoma.

This record identifies the authority, exact first-party source, program finding, provider-list result, predicate evidence, and trust gate used for this page.

  1. Service Oklahoma is the issuing authority recorded for Oklahoma (US-OK, State). The exact first-party authority source retained for this review is https://oklahoma.gov/service/all-services/driving-and-automobiles.html; it was reviewed on 2026-09-13.
  2. The issuer-specific source reviewed for this record is “Oklahoma Mobile ID App to be Decommissioned,” published by Service Oklahoma. The registry classifies the program as Legacy Decommissioned.
  3. Apple Wallet is wallet available for this record. The controlling source is “ID in Wallet,” reviewed 2026-09-13.
  4. Google Wallet is planned for this record. The controlling source is “Add your US Driver's License or State ID,” reviewed 2026-09-13.
  5. The reviewed record contains separate Laurel evidence for the age_over_21 predicate. At least one wallet qualification record maps to reviewed authoritative trust material: exact certificate bytes from either a signed VICAL or an issuing authority's official endpoint. Live verifier status remains a separate gate.

Privacy-preserving age verification

Ask the credential for an answer, not an identity.

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.

Requested Retained
age_over_21 false
name / birth date never requested
portrait / document number never requested
identity linkage never created

Merchant and venue preparation

What a Oklahoma operator can do now.

  1. Confirm with Service Oklahoma which credential channels are currently available; do not treat a wallet-provider listing as Laurel qualification.

  2. Bookmark the reviewed Oklahoma mobile-ID program page and record any issuer or enrollment change before scheduling a qualification session.

  3. Keep a documented physical-ID fallback and train staff that “Unable to verify” is not an age decision.

  4. Prepare a managed Android verifier profile with NFC, Bluetooth Low Energy, secure device management, and a tested offline operating procedure.

  5. 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

Help qualify Oklahoma without claiming support early.

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.

Jurisdiction: Oklahoma

Can you participate in an in-person controlled test?

This contact record is handled separately from verification telemetry. Do not submit a driver-license number, date of birth, document image, wallet screenshot, credential payload, or verification-event detail.

Pilot and review

Choose the next conversation based on your role.

Prepare a future pilot

Scope locations, hardware, staff training, fallback policy, and the exact production-support boundary.

Start a pilot

Review the security boundary

Walk through issuer trust, device configuration, offline behavior, event allowlists, and the no-patron-PII architecture.

Request a security review

Prepare a reseller deployment

Align qualification evidence, managed hardware, operator training, and truthful status language before selling.

Explore reseller readiness

Known limitations

What this page does not claim.

Implemented
Implemented
Issuer trust
Issuer trust reviewed
Tested
Verified with test credentials
Offered by Laurel
Not offered
Legal review
Legal review not started
  • Oklahoma's issuing-authority certificate bytes are reviewed and pinned (the authenticated AAMVA Digital Trust Service VICAL, reviewed 2026-09-13) and the Android fixture matrix passes for Oklahoma; no real Oklahoma credential has been physically tested on Laurel hardware.
  • Laurel requests only age_over_21 with intentToRetain=false.
  • Acceptance requirements depend on applicable law, merchant policy, and the issuing authority. Laurel's technical compatibility status is not a legal determination.
  • Wallet availability, a registry record, or an operator selection does not independently establish cryptographic issuer trust.

Official sources

Evidence reviewed for Oklahoma.

  1. Service Oklahoma Service Oklahoma. No publication date shown. Retrieved .
  2. Jurisdiction Data Maps AAMVA. No publication date shown. Retrieved .
  3. Oklahoma Mobile ID App to be Decommissioned Service Oklahoma. Published or updated February 8, 2024. Retrieved .
  4. ID in Wallet Apple. No publication date shown. Retrieved .
  5. Mobile Driver License Digital Trust Service AAMVA. No publication date shown. Retrieved .
  6. Android per-jurisdiction credential fixture matrix: reviewed authority resolves, authenticated issuer admitted, foreign issuer refused Laurel Secure. Published or updated September 13, 2026. Retrieved .
  7. Add your US Driver's License or State ID Google. No publication date shown. Retrieved .

Page last reviewed . Registry version 2026.09.13.1.

Frequently asked questions

Oklahoma mobile-ID questions.

Is a mobile ID from Oklahoma available in Apple Wallet?

Yes. Apple’s current official availability page lists Oklahoma. That confirms wallet availability, not Laurel production support.

Is a mobile ID from Oklahoma available in Google Wallet?

The reviewed current Google source does not establish Google Wallet availability for Oklahoma. Absence from that list is treated as unknown, not explicit unavailability.

Does LaurelID support production age verification for Oklahoma?

No. Oklahoma has not passed every Laurel production gate. A page in this directory, wallet availability, or an issuer announcement does not independently create production support.

What information does LaurelID request from a mobile ID issued by Oklahoma?

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/oklahoma .