Verifiable Credentials
Reusable, user-held credentials, shared only with consent.
What it does
After a person is verified once, this module issues a W3C Verifiable Credential in SD-JWT-VC format into their own wallet, linked to a decentralised identifier. When a platform needs identity data it sends a request; the user reviews and signs it, and only the requested fields are disclosed, with a receipt recording the consent. It is the credential layer beneath SBX ID, working alongside ZK Identity for checks that need no personal data at all.
Powers
How it works
Verifiable Credentials sit between one-time verification and every platform that relies on it. ZK Identity proves conditions without data, the Encrypted Data Vault holds the documents, and the Attestation Registry records status and revocation.
Select a step to replay it. Hover to pause.
Step 1 of 3: Issue. A credential is issued into the user's own wallet after one-time verification.
Key capabilities
W3C VC 2.0 and DIDs
Credentials in open standards, portable beyond any single platform.
Selective disclosure
SD-JWT-VC lets a platform see only the fields it asked for.
Consent receipts
Every share is signed by the user and recorded for both sides.
Standard exchange
OpenID for Verifiable Credentials to issue and request credentials.