Interactive demonstration
Try reusable verification
See what changes when a service asks for one useful fact instead of another document upload.
Local simulation · fictional issuer and services
One membership credential. Two services. A separate decision for every request.
This demonstration performs no real identity checks or cryptographic verification. It sends no demo selections or claims to a server and saves no demo state after a reload.
01 · In your example wallet
The credential stays with you
- Issuer
- Example Membership Association
- Credential
- Active membership
- Name
- Example member · kept private
- Member number
- DEMO-0042 · kept private
Scenario: available membership credential.
02 · The request
Review before sharing
- Service
- Example shared workspace
- Purpose
- Check eligibility for a member desk booking
- Requested fact
- Is this membership active?
- Request
- Create a request to begin
The example receipt contains the service, purpose, request reference and membership result. The pilot must agree a retention period before accepting real participants.
Share only the membership answer with this service? This choice applies to this request. You can decline.
03 · The service receives
No claim shared yet
Create a request and review what the service is asking.
Production checks still needed: issuer signature and trust, holder authentication, fresh request binding, expiry and status. This demo models outcomes; it does not run those checks.
Your example sharing history
Only successful presentations appear here. Changing services requires a fresh consent request; pausing sharing keeps existing receipts.
- No successful presentations yet.
What this helps you evaluate
The same credential can serve different purposes, but each service needs its own accepted issuer, fresh request and user decision. A successful presentation must establish trust as well as cryptographic validity.
All organisations and credentials in this demo are fictional. It does not connect to VEID, issue credentials, prove identity, or establish age or financial KYC compliance.
Read the pilot proposal · Inspect the proposed integration · Review issuer trust