district · DC · Registry 2026.09.13.1

Mobile ID age verification in District of Columbia

District of Columbia 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

Availability, qualification, and support are different gates.

The issuing authority for this record is District of Columbia Department of Motor Vehicles. Every status below is generated from the same canonical registry used by Laurel’s public support API and device-policy artifacts.

District of Columbia mobile-ID status by wallet and Laurel qualification gate
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
Official mDL program
Unknown
Laurel qualification
Planned
Laurel production support
No live production-enabled pair
Last reviewed

State mobile-ID overview

What first-party sources establish for District of Columbia.

District of Columbia 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.

Required next action

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

The evidence record reviewed for District of Columbia.

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

  1. District of Columbia Department of Motor Vehicles is the issuing authority recorded for District of Columbia (US-DC, District). The exact first-party authority source retained for this review is https://dmv.dc.gov/; it was reviewed on 2026-09-13.
  2. No dedicated issuer mobile-ID program page was recorded in this review. The program remains Unknown, and monitoring starts with the official issuing authority rather than a third-party summary.
  3. Apple Wallet is planned 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. No jurisdiction-specific Laurel evidence for age_over_21 is recorded; provider protocol capability is not treated as issuer proof. Issuer trust is not established in the public record and remains a separate authoritative-certificate review 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 District of Columbia operator can do now.

  1. Monitor District of Columbia Department of Motor Vehicles and the wallet providers for a current issuance notice; avoid promising a launch date.

  2. Monitor District of Columbia Department of Motor Vehicles'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.

  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 District of Columbia 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: District of Columbia

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 not available
Tested
Not yet tested
Offered by Laurel
Not offered
Legal review
Legal review not started
  • No real credential issued through District of Columbia Department of Motor Vehicles for District of Columbia has been physically qualified by Laurel.
  • 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 District of Columbia.

  1. District of Columbia Department of Motor Vehicles District of Columbia Department of Motor Vehicles. No publication date shown. Retrieved .
  2. Jurisdiction Data Maps AAMVA. No publication date shown. Retrieved .
  3. ID in Wallet Apple. No publication date shown. Retrieved .
  4. 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

District of Columbia mobile-ID questions.

Is a mobile ID from District of Columbia available in Apple Wallet?

The reviewed current Apple source does not establish Apple Wallet availability for District of Columbia. Absence from that list is treated as unknown, not proof that availability is impossible.

Is a mobile ID from District of Columbia available in Google Wallet?

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

Does LaurelID support production age verification for District of Columbia?

No. District of Columbia 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 District of Columbia?

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/district-of-columbia .