SD-JWT VC

Issue, store and verify SD-JWT VCs

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.

  • 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 SD-JWT VC lifecycle

Issue, store and verify SD-JWT VCs using open standards.

  1. Issue

    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 & 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 SD-JWT VCs.

    Wallet SDKs & APIs
  3. Verify

    Request only the claims you need via OpenID4VP and DCQL, and check signature, key binding and status with customizable policies.

    Verifier SDKs & APIs

New to SD-JWT? Read SD-JWT VC explained in the docs.

Built for production

Everything you need to launch SD-JWT VCs in production

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

Privacy by Design

Selective Disclosure

Holders share only the claims a verifier asks for, such as "over 18" without a birth date.

Developer-First

APIs and SDKs for Every Layer

Eliminate fragmentation with agnostic APIs/SDKs that support SD-JWT VCs across platforms and ecosystems.

Issuer API
Wallet API
Verifier API

REST APIs

Kotlin Multiplatform
Android
iOS (Swift)
SD-JWT 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 (incl. eIDAS 2).

Interoperable by Design

Global Standards

IETF SD-JWT VC with selective disclosure, exchanged via OpenID4VCI, OpenID4VP with DCQL, HAIP 1.0 and the Digital Credentials API.

SD-JWT VC
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 SD-JWT VC status with the IETF Token Status List.

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 SD-JWT VCs with walt.id.

Does walt.id support SD-JWT VC?

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.

Which protocols can I use to issue and verify SD-JWT VCs?

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.

Is SD-JWT VC required under eIDAS 2?

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.

How do I revoke or suspend an SD-JWT VC?

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.

SD-JWT VC, ISO mdoc or W3C 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, 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.

Which identifiers and key stores are supported?

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.

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.