What that looks like in practice
Thandi has a wallet on her phone. Her university, her bank, and her city have each issued credentials into it: a student card, a proof-of-account, a digital driver’s licence. A property platform she is registering with asks her to prove she is over 18 and has a verified bank account. Thandi opens her wallet, sees what is being asked, approves the parts she is willing to share. The platform receives cryptographic proofs it can verify in milliseconds, without storing her date of birth or her bank statements. Three issuers, one wallet, one verifier, one transaction. Each issuer signed once. Thandi decided what to share, this time. The verifier confirmed the proofs cryptographically, with no callback to any issuer.The three roles
Issuer
Sign and offer credentials. Universities, employers, government departments, banks. Most issuer integrations live in
the me-creds API.
Holder
Hold credentials and decide what to share. Most holders use the didx:me wallet app — try it. The me-wallet API
serves holder-side integration if you are building a wallet of your own.
Verifier
Request credentials and validate them. Banks, employers, marketplaces, platforms. Most verifier integrations live in
the me-creds API.
What next?
Issue your first credential in 10 minutes
Feel up to the challenge? The Quickstart explains how to get sandbox keys via Slack, then walks you through issuing
your first credential.