Verifiable credentials
Verifiable credentials your application can check
Use signed verification records with explicit issuer, expiry and acceptance rules.
01Trusted issuer
Example flow
Holder chooses a claim to share
Verifier checks the proof
The holder controls presentation
The job
- Every partner integration becomes another API and another data-sharing agreement.
- A credential that only your systems can read is a lock-in, not a credential.
- Revocation and expiry get bolted on afterwards, badly.
How it works.
- 01
Choose the verification
Identify the claim your service needs and the issuer you will accept.
- 02
Read the credential
Use the documented API or attestation interface for that verification.
- 03
Check status and expiry
Apply your acceptance rules to the result, including how expired or missing evidence is handled.