Service Catalog
Services provide the functional capabilities for decentralized identity and ID wallets. They live inside tenants or sub-tenants, and each instance gets its own configuration so you can run multiple variants of the same service (for example, one issuer for W3C VCs and another for SD-JWT VCs). Use this catalog once you know which capability you want to deploy and need the corresponding guide.
Need a different starting point?
- Want the conceptual model (resource tree, service types, dependency patterns)? Go to Enterprise Foundations → Services.
- Ready to manage lifecycle, configuration, or metadata across existing services? See Administration → Service Operations.
How the catalog is organized
The list below is split into operational services (they handle the runtime operations–issuance, verification, wallet actions) and storage & registry services (they persist state and expose it). Pick whichever category matches the capability you’re looking for, then dive into the linked guide.
Operational services
- KMS Service - Manage cryptographic keys for signing and encryption workloads.
- Issuer Service - Sign & issue digital credentials (W3C VC, SD-JWT VC, mDL).
- Verifier2 Service - Request & verify digital credentials using the OpenID4VP 1.0 specification.
- Verifier Service - Request & verify digital credentials using the draft OpenID4VP 1.0 specifications.
- Wallet Service - Run identity wallets for individuals or organizations.
- DID Service - Create decentralized identifiers across supported DID methods.
- Credential Status Service - Manage credential status lists (revocation, suspension, etc.).
Storage & registry services
- DID Store Service - Store and manage DIDs and DID documents.
- Credential Store Service - Store and query issued credentials.
- Holder Policy Store Service - Store and manage holder policies for silent issuance or wallet-driven verification.
- DID Registry - Host did:web documents and expose them over HTTPS.
Last updated on December 3, 2025