Supported mobile IDs
Government-issued credentials. One narrow question.
Laurel Secure is evaluating government-issued mobile IDs built on the ISO/IEC 18013-5 mobile driver’s license standard. Any reader, issuer, wallet, and predicate path must be verified for the specific pilot before it is treated as supported.
01 · Why cryptographic beats visual
A signature check, not a glance at a plastic card.
Visual inspection asks a person to judge a laminate, a hologram, and a birth date under pressure, in seconds, often in bad light. A mobile ID is different in kind: the issuing authority signs the credential cryptographically, and the reader verifies that signature on the spot.
That changes what a forged or borrowed ID can accomplish. A counterfeit fails the signature check. And because the credential can answer a single predicate — is this person over the threshold? — proving age no longer requires showing a name, address, and birth date to a stranger.
When the cryptographic path cannot complete, the answer is
unable_to_verify, and staff use the business’s normal
physical-ID fallback. Laurel is the mobile-ID path — not a replacement for that
fallback.
02 · Credential landscape
What patrons actually carry.
States issue mobile IDs through their own wallet apps and through the device-native wallets. Laurel targets the standard those credentials share.
| Credential type | How it presents | What Laurel requests |
|---|---|---|
| ISO/IEC 18013-5 mDL | Tap or QR handshake from the state’s mobile ID app | Confirm during qualification |
| State ID in a device-native wallet | Presented from the phone’s built-in wallet where the issuing state supports it | Confirm during qualification |
| Physical driver’s license | Outside the Laurel path — staff use the standard manual check | Not read by Laurel |
Jurisdiction coverage differs by state and issuer and changes as programs roll out. We confirm the exact credential coverage for your locations during pilot qualification rather than publishing a blanket claim.
03 · What the credential releases
The attributes stay home.
An 18013-5 credential can disclose attributes selectively. Any Laurel reader integration, if approved for a pilot, will be scoped to the minimum operational predicate agreed during qualification. No credential path is treated as production-supported from this page alone.
04 · Straight answers
Coverage questions, answered plainly.
Which states are supported today?
Mobile ID programs are live in a growing set of states and expanding quickly, which is exactly why we do not publish a static list here. During pilot qualification we confirm coverage for the jurisdictions your locations operate in, against the current issuer landscape.
What about patrons without a mobile ID?
They hand over a physical ID and staff follow the business’s existing manual procedure. Laurel does not read physical documents and does not replace your fallback — it removes identity exposure from the growing share of checks that can happen cryptographically.
Does a different age threshold change anything?
The mechanism is the same: the reader requests the predicate configured for the checkpoint, and the answer that crosses the boundary is still only pass, fail, or unable to verify.
Confirm coverage for your locations.
Pilot qualification includes a jurisdiction-by-jurisdiction credential check.