verified outcome
Verified 21+
The mobile credential proves the guest is 21 or older.
Staff action: Proceed according to venue policy.
Mobile ID age verification for doors and registers
Tap a mobile ID. See 21+. Never see identity.
LaurelID turns the driver's license in a customer's phone into a fast, private answer at the door or the register: Verified 21+, Under 21, or Unable to verify. Your staff never see, and your business never holds, the person's name, birth date, photo, address, or ID number.
Available now for mobile driver's licenses from 13 states and Puerto Rico, in Apple Wallet and Google Wallet, on Elo M51.
01 · Outcomes
One question. Three answers. Nothing ambiguous.
Under 21 is a successful check, not an error. Uncertainty is never rounded into a pass: when the phone cannot prove the answer, staff use the procedure they already have.
verified outcome
Under 21
The credential successfully proves the guest is not 21 or older.
Staff action: Refuse according to venue policy.
inconclusive outcome
Unable to verify
The verifier could not complete a trustworthy mobile-ID check.
Staff action: Use the approved manual procedure.
02 · Why a business pays for this
Checking one phone is easy. Running every door, every night, is the job.
A state's own verifier app can read that state's ID on a staff member's phone. A business needs more than a reader.
A dedicated verifier at every point of check
A purpose-built device, not a staff phone. Add one from the console in three steps; it is ready in about two minutes.
Every location in one place
Whether each location can verify, which verifier needs attention, and what to do about it.
Keeps working when the network does not
The decision is made on the verifier. Checks continue through an outage and counts catch up afterwards.
Counts you can report, no records you have to protect
Outcome counts by location and day. No scan log and no patron file to protect.
Nothing for you to build
Wallet behaviour, the mobile-ID standard and issuer trust updates are Laurel's problem, not yours.
Fits the systems you already run
Managed through enterprise Android device management today. A decision API for registers and gates is planned, not shipped.
03 · What the phone is asked
The product asks for the answer, not the person.
The verifier asks the phone one question, "is this person over 21", and tells the wallet it will not keep the answer. That is the whole request.
The exact request
The entire verification request Narrow by design
- document type
- org.iso.18013.5.1.mDL
- namespace
- org.iso.18013.5.1
- element
- age_over_21
- intentToRetain
- false
Not requested or retained
- Name
- Date of birth
- Address
- Portrait or photo
- Document number
- Wallet identifier
- Mobile-ID payload
- Session transcript
- Patron identifier
- Repeat-visitor identifier
These fields are refused by the verifier and by the platform; they are never collected and later deleted. Review the privacy architecture.
04 · The console
Is everything working? One screen answers.
Every location, every verifier, three plain states. When something needs a person, the console says who and what.
- Add a verifier in three stepsLocation, name, activation code.
- Four states, one actionReady, Setting up, Needs attention, Off. Attention always names the fix.
- Verification, reporting, connectionReported separately. A network problem never reads as a verifier that cannot check IDs.
- Roles and locationsTeam members scoped to the locations they run.
05 · Now, in qualification, planned
Stated precisely, on purpose.
Available now
- Mobile driver's licenses from 13 states and Puerto Rico in Apple Wallet and Google Wallet, on Elo M51.
- A local 21+ decision on the verifier: Verified 21+, Under 21, or Unable to verify.
- Verification continues when the network does not; outcomes catch up later.
- The console: add a verifier in three steps, see every location and verifier, aggregate reports, team roles.
In qualification
- Arkansas: physically tested in both wallets, waiting on the issuing authority's certificate binding.
- Further states as their issuing authorities publish trust material and each pair passes physical testing.
Planned
- A per-decision evidence record your business can keep and export, still without patron identity.
- A decision API and a local result surface so a register or gate can ask Laurel and get an answer.
- Longer offline operation under a signed licence, instead of daily renewal.
Per-jurisdiction detail, with the evidence behind each label, is on the supported IDs page.
Live production status is checked when this page loads. Until it answers, no row above is upgraded to Supported.
06 · Start
Prove it at one location.
Thirty days, one location, two to five verifiers, with your existing manual check left in place the whole time.
30days
1location
2–5verifiers
Unable to verify always returns staff to the procedure you already use, so a pilot cannot leave a door uncovered.
- Deployment support and operator training
- Security and privacy review package
- Metrics agreed in advance
- Written rollback plan and readout
Running several venues, a casino floor or a stadium? Say so; multi-site rollouts start with a different conversation. Review privacy and security.