APIs and SDKs for Every Layer
Eliminate fragmentation with agnostic APIs/SDKs that support W3C Verifiable Credentials across platforms and ecosystems.
REST APIs
SDKs & Libraries
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.
Used by +70.000 developers and organisations
End-to-end
Turn data from your existing systems into signed W3C VCs 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 W3C VCs.
Wallet SDKs & APIsRequest exactly the claims you need via OpenID4VP and check signature, issuer and status with customizable policies.
Verifier SDKs & APIsNew to VCs? Read What are W3C Verifiable Credentials? in the docs.
Built for production
Eliminate fragmentation with agnostic APIs/SDKs that support W3C Verifiable Credentials across platforms and ecosystems.
REST APIs
SDKs & Libraries
Aligned with emerging global frameworks, ensuring your credentials are accepted by governments and compliant wallets worldwide.
W3C VC Data Model 1.1 and 2.0, exchanged via OpenID4VCI, OpenID4VP with DCQL 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 W3C VC status with the W3C Bitstring Status List, plus StatusList2021 and RevocationList2020 for older credentials.
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 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.
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.
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.
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.
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.
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.