Product
A verifier at the counter. A control plane behind it.
LaurelID is two surfaces held together by one contract: the verifier decides locally, and the platform only ever learns that a decision happened.
01 · The pieces
Six things to understand.
- 01
LaurelID Verifier
The Android verifier that runs the check at the counter.
- 02
LaurelID Console
Create, activate, and govern verifiers across locations.
- 03
Fleet management
Every location and verifier, and what needs attention.
- 04
Offline reliability
Checks continue through network interruptions.
- 05
Reporting
Outcome counts by location and day, never individual records.
- 06
Deployment
Activation, configuration, and rollout model.
02 · The contract underneath
Everything else is downstream of this request.
Product decisions get easier once the request is fixed. There is no configuration screen that widens it, no enterprise tier that adds fields, and no debugging mode that captures more.
- document type
- org.iso.18013.5.1.mDL
- namespace
- org.iso.18013.5.1
- element
- age_over_21
- intentToRetain
- false
Walk the product with an engineer.
Pilots start with a scoping conversation about your point of check, not a demo script.