W3C Verifiable Credentials

Issue, store and verify W3C Verifiable Credentials

walt.id's Issuer, Wallet and Verifier support W3C Verifiable Credentials alongside SD-JWT VC and ISO mdoc. Start with the open-source Community Stack and scale with the Enterprise Stack, on premises or in your own cloud.

  • Open-Source
  • Standard & Regulatory Compliant
  • Gov & Enterprise Proven

Used by +70.000 developers and organisations

Trusted by leading organizations

Accenture logoAir New Zealand logoNEC logoT-Systems logoBangkok Bank logoBoston Consulting Group logoEuropean Union logoEY logoMastercard logoIBM logoid-now logoNDID logoInfoCert logoNetherlands logoNTT Ltd logoOrange logoOracle logoPS logoRaiffeisen Bank logonetcompany logoAccenture logoAir New Zealand logoNEC logoT-Systems logoBangkok Bank logoBoston Consulting Group logoEuropean Union logoEY logoMastercard logoIBM logoid-now logoNDID logoInfoCert logoNetherlands logoNTT Ltd logoOrange logoOracle logoPS logoRaiffeisen Bank logonetcompany logo

End-to-end

One stack for the whole W3C VC lifecycle

Issue, store and verify W3C Verifiable Credentials using open standards.

  1. Issue

    Turn data from your existing systems into signed W3C VCs and deliver them to any compliant wallet via OpenID4VCI.

    Issuer SDKs & APIs
  2. Store

    Launch your own wallet or add wallet features to your app, custodial, non-custodial or hybrid, so users can receive, hold and present W3C VCs.

    Wallet SDKs & APIs
  3. Verify

    Request exactly the claims you need via OpenID4VP and check signature, issuer and status with customizable policies.

    Verifier SDKs & APIs

New to VCs? Read What are W3C Verifiable Credentials? in the docs.

Built for production

Everything you need to launch W3C VCs in production

Open standards, your own keys and full credential lifecycle control.

Developer-First

APIs and SDKs for Every Layer

Eliminate fragmentation with agnostic APIs/SDKs that support W3C Verifiable Credentials across platforms and ecosystems.

Issuer API
Wallet API
Verifier API

REST APIs

Kotlin Multiplatform
Android
iOS (Swift)
W3C VC

SDKs & Libraries

Future-Proof ID Infrastructure

Regulatory Alignment

Aligned with emerging global frameworks, ensuring your credentials are accepted by governments and compliant wallets worldwide.

Interoperable by Design

Global Standards

W3C VC Data Model 1.1 and 2.0, exchanged via OpenID4VCI, OpenID4VP with DCQL and the Digital Credentials API.

VCDM 2.0
OpenID4VCI
OpenID4VP
DC API
Total Data Sovereignty

Your Keys, Your Vault

Keep signing keys in your preferred KMS or HSM, such as AWS KMS, Azure Key Vault, HashiCorp Vault or a PKCS#11 HSM. Available in both product editions, so you keep full control of your keys.

Full Lifecycle Management

Revoke, Suspend, or Restore

Manage W3C VC status with the W3C Bitstring Status List, plus StatusList2021 and RevocationList2020 for older credentials.

Automated Trust

Verification Policies

Signature, validity, status and allowed-issuer checks out of the box. Add custom rules or pass checks to your external systems via webhooks.

  • Signature
  • Credential status
  • Schema
  • Custom
Trust Anchors

Issuer & Verifier Identification

Identify issuers and verifiers with Decentralized Identifiers (did:web, did:key, did:jwk) or X.509 certificates.

Partners And Integrations

Works With Your Infrastructure.

Seamlessly connect your existing stack and deploy anywhere with full flexibility and total data control.

Product Editions

Build or Buy.

Build on top of the industry's leading open source stack or scale quickly with our secure, regulatory compliant enterprise solution.

Self-Managed

Enterprise

Enterprise Stack

Everything you need to roll-out and scale. The fast and worry-free way to build ID platforms, ship complex use cases and ensure compliance.

FAQs

Frequently asked questions.

Answers to common questions about W3C Verifiable Credentials with walt.id.

Does walt.id support the W3C Verifiable Credentials Data Model 2.0?

Yes. walt.id issues, stores and verifies credentials following the W3C Verifiable Credentials Data Model 1.1 and 2.0, secured as JWT or SD-JWT, in both the open-source Community Stack and the Enterprise Stack.

Which protocols can I use to issue and verify W3C Verifiable Credentials?

OpenID4VCI 1.0 for issuance and OpenID4VP 1.0 with DCQL for presentation, plus the W3C Digital Credentials API. walt.id's OpenID4VCI, OpenID4VP and HAIP implementations pass the OpenID Foundation conformance tests.

Which DID methods and key stores are supported?

Issuers can be identified with Decentralized Identifiers, for example did:key, did:jwk or did:web, or with X.509 certificates. Signing keys can stay in your preferred KMS or HSM, for example AWS KMS, Azure Key Vault, HashiCorp Vault or HSMs via the PKCS#11 interface, or be managed locally. This applies to both editions. For all supported DID methods and key stores, see the feature list in the docs.

How do I revoke or suspend a W3C Verifiable Credential?

With a status list. walt.id supports the W3C Bitstring Status List 1.0, plus StatusList2021 and RevocationList2020 for older credentials. In the Community Stack you create and sign status lists and host and update them yourself; the Enterprise Stack manages the credential lifecycle, including status updates and publishing.

W3C VC or SD-JWT VC: which format should I use?

It depends on the ecosystem you need to work with. SD-JWT VC and ISO mdoc are the formats used for PID in the EU Digital Identity Wallet, while many other ecosystems build on the W3C data model. walt.id's Issuer, Wallet and Verifier support all three, so you don't have to choose up front. Compare the formats in the docs.

Is walt.id a hosted service?

No. Both editions, the open-source Community Stack and the Enterprise Stack, are self-managed: you run them on premises or in your own cloud. A fully managed Cloud Platform is not yet available. The public demos are for testing only.