Verifiable Credentials · Use Case Mapping
Map it. Document it. Share it.
A structured tool to map verifiable credential use cases — from the current journey to the future with VCs. Designed for everyone in the VC ecosystem.
🏛️
Government teams
Ministries, registries, agencies building VC infrastructure
🔍
Verifying entities
Banks, employers, hospitals that verify credentials
🛠️
Practitioners
Consultants, NGOs, academics supporting VC adoption
🌍
DPI facilitators
Teams running bootcamps and co-implementation missions
Select the option that best describes you (optional)
Takes 30–90 min depending on depth. Save at any point and continue later.
Step 1 · Setup
Use case setup
Name your use case and select what you want to map. You can always adjust later.
The credential Required
What are you mapping? *
🏛️
Issuance
How the credential is issued to the citizen by the issuing entity
e.g. A farmer requests their land title certificate from the Ministry of Agriculture
🔍
Verification
How the credential is verified to access a service
e.g. A bank verifies the farmer's land title to approve a loan
↔️
Both
Map the full cycle — issuance and verification
e.g. From issuing the credential to using it to access a service
Step 2 · Context
Context & problem
Describe who is affected and what the core problem is today. This anchors the rest of the mapping.
The citizen affected
Issuance · Step 3
Issuance — today and with verifiable credentials
Map how issuance works today. For each step, mark whether it changes with VCs — most steps often stay the same, only a few actually change.
Issuance process Required
Add steps below to see the journey map
Summary — before / after
Today
hrs
With VCs
hrs
Issuance · Step 4
Legal framework & technical documentation
Document the legal context and what is known about the technical setup. Fill what you know — leaving fields blank is also useful information.
Legal & regulatory framework
Data source (issuing entity)
Integration & access
Verification · Step 5
Verification — today and with verifiable credentials
Map how verification works today. For each step, mark whether it changes, is eliminated, or is new with VCs.
Verification context
Verification process Required
Add steps below to see the journey map
Summary — before / after
Today
hrs
With VCs
hrs
Verifying entity — technical notes
Step 7 · Indicators
Indicators & scale
Quantify the current process and expected impact. Best estimates are valuable — numbers make the case.
Volume & reach
Time comparison
Today (As-Is)
hrs
hrs
→
With VCs (To-Be)
hrs
hrs
Cost & quality
Problems in the current process
Step 8 · Impact
Expected impact
What changes when this use case is implemented with verifiable credentials?
👤 For the citizen
🏛️ For the entity
🌍 For the country
Summary
Use case summary card
Auto-filled from your answers. Edit anything before exporting — this is what you share and present.
Some key fields are empty
The summary card may be incomplete. Fill these fields for a stronger case:
Use case
Verifiable Credentials Use Case
Use case name
Credential
Problem today
With VCs — what changes
Citizen time · As-Is → To-Be
Entity time · As-Is → To-Be
Channel change
Citizens affected / year
Who benefits most
Data source
Priority 1–10:
Use "Finish & export" below to download this case (PDF, Excel or .json).
1 / 9
Case saved — choose how to export it
Your copy stays with you. This also registers the case with CDPI.