Selective Disclosure
Holders share only the claims a verifier asks for, such as "over 18" without a birth date.
SD-JWT VC
walt.id's Issuer, Wallet and Verifier support SD-JWT VC alongside ISO mdoc and W3C Verifiable Credentials. Start with the open-source Community Stack and scale with the Enterprise Stack, on premises or in your own cloud.
Used by +70.000 developers and organisations
End-to-end
Turn data from your existing systems into signed SD-JWT VCs, with every claim selectively disclosable, and deliver them to any compliant wallet via OpenID4VCI.
Issuer SDKs & APIsLaunch your own wallet or add wallet features to your app, custodial, non-custodial or hybrid, so users can receive, hold and present SD-JWT VCs.
Wallet SDKs & APIsRequest only the claims you need via OpenID4VP and DCQL, and check signature, key binding and status with customizable policies.
Verifier SDKs & APIsNew to SD-JWT? Read SD-JWT VC explained in the docs.
Built for production
Holders share only the claims a verifier asks for, such as "over 18" without a birth date.
Eliminate fragmentation with agnostic APIs/SDKs that support SD-JWT VCs across platforms and ecosystems.
REST APIs
SDKs & Libraries
Aligned with emerging global frameworks, ensuring your credentials are accepted by governments and compliant wallets worldwide (incl. eIDAS 2).
IETF SD-JWT VC with selective disclosure, exchanged via OpenID4VCI, OpenID4VP with DCQL, HAIP 1.0 and the Digital Credentials API.
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.
Manage SD-JWT VC status with the IETF Token Status List.
Signature, validity, status and allowed-issuer checks out of the box. Add custom rules or pass checks to your external systems via webhooks.
Identify issuers and verifiers with Decentralized Identifiers (did:web, did:key, did:jwk) or X.509 certificates.
Partners And Integrations
Works with any KMS/HSM, database, cloud provider or application.
Product Editions
Open Source
The easiest way to get started and build. Own infrastructure and develop your platform based on the leading open source stack.
Enterprise
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
Yes. walt.id issues, stores and verifies SD-JWT VCs following the IETF SD-JWT VC specification (dc+sd-jwt), with selective disclosure based on the IETF SD-JWT standard (RFC 9901) and KB-JWT holder binding, in both the open-source Community Stack and the Enterprise Stack.
OpenID4VCI 1.0 for issuance and OpenID4VP 1.0 with DCQL for presentation, the OpenID4VC High Assurance Interoperability Profile (HAIP) 1.0 and the W3C Digital Credentials API. walt.id's OpenID4VCI, OpenID4VP and HAIP implementations pass the OpenID Foundation conformance tests.
Yes. Together with ISO mdoc, SD-JWT VC is mandatory for the EU Digital Identity Wallet. walt.id implements the formats and protocols specified in the EUDI Wallet Architecture and Reference Framework (ARF), and its open-source software is part of the EUDI Wallet reference implementation.
With the IETF Token Status List. 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.
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, ISO mdoc is the format for mobile driving licences, and 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. See W3C Verifiable Credentials and mobile driving licences, or compare the formats in the docs.
Issuers and Verifiers can be identified with X.509 certificates or with Decentralized Identifiers, for example did:web, did:key or did:jwk. 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.
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.
We use cookies to measure traffic and improve your experience. By clicking Accept, you consent to analytics cookies. Read our privacy policy for details.