Verified people, organizations and credentials
Verifiable Credentials
Issue trust that others can check.
Digital credentials that express signed facts about people, organizations, applications and agents.
In practice
What this service does.
Turn verified facts into portable, cryptographically verifiable credentials. Enable trusted organizations and applications to exchange the evidence they need without repeatedly rebuilding the same verification process.
Best for
Education, accreditation, enterprise, identity ecosystems
Integration detail — endpoints, token shapes, SDKs and the standards each flow follows — lives in the developer portal.
Capabilities
- W3C Verifiable Credentials issuance and verification
- Credential types, schemas and issuer identities
- Presentation verification and status checks
- Selective disclosure profiles where supported
- Credential expiration and status management
- Holder wallets and interoperability adapters
Capabilities describe what the service is built to do. Which of them a given tenant uses — and in which environments — is part of the configuration you choose.
Same family
More in Verified people, organizations and credentials.
Evidence that an account belongs to a real person or a real company, and credentials others can check.
Identity Verification and Proofing
Connect digital accounts to trusted evidence.
Orchestrate proofing workflows to establish higher confidence in the person behind an account.
Service detailsBusiness and Organization Verification
Trust the organization behind the account.
Establish organization identity and verified associations with representatives and agents.
Service detailsDigital Identity Wallet Interoperability
Credentials people and systems can carry.
Interoperate with digital identity wallets and credential exchange protocols.
Service detailsDelegated Identity and Representation
Prove who acts on whose behalf.
Identity evidence for representatives, delegated users, applications and autonomous agents.
Service detailsPut Verifiable Credentials to work.
Start with a development tenant and one application, or talk through the architecture first — tenancy, credential lifecycle and which parts stay in your own stack.
Packages and metered usage are set out on the pricing page; the figures themselves are agreed with our team against the services you need.