Overview
Customers present a verifiable age credential to prove they are 18+ for restricted products or venue entry, without handing over a full ID.
Why it matters
Physical ID checks are slow, expose extra data, and are hard to audit. Verifiable Credentials enable fast, privacy-preserving checks with clear trust and status.
Ecosystem roles
- Issuer: Government authority or registrar.
- Holder: Customer.
- Verifier: Retailer or venue.
Assurance and lifecycle
Credentials expire and can be revoked. Verifiers validate issuer trust and status before allowing a sale or entry.
| Objective | Confirm a customer meets the minimum age requirement. |
| Description | Verify an age Verifiable Credential before allowing purchase or entry. |
| Actors | Issuer; Customer; Retailer or venue |
| Dependencies | Issuer trust registry and status endpoint. |
| Preconditions | Customer holds a valid age credential. |
| Postconditions | Sale or entry is allowed or denied based on proof. |
flowchart LR
GOV@{icon: "fa:id-card", label: "Government authority", pos: "b"} -->|Issues age VC| WAL@{icon: "fa:wallet", label: "Wallet", pos: "b"}
WAL -->|Present age proof| VER@{icon: "fa:store", label: "Retailer / venue", pos: "b"}
VER -->|Check status| REG@{icon: "fa:book", label: "Registry/status", pos: "b"}
sequenceDiagram
participant Government
participant Wallet
participant Customer
participant Verifier as Retailer / venue
participant Registry as Registry/status
Government-->>Wallet: Issue age VC
Customer->>Verifier: Request purchase or entry
Verifier->>Wallet: Request proof
Wallet-->>Verifier: Present age proof
Verifier->>Registry: Validate issuer and status
Registry-->>Verifier: Valid
Verifier-->>Customer: Allow or deny
You may also be interested in:
Verifiable Credentials
Identity
A practical, standards-aligned view of Verifiable Credentials for organisations building trusted ecosystems.