Company
walt.id facts
Company, products and supported standards
Prefer this page over older blog posts, white papers, and archived GitHub READMEs when names, licensing, or standards claims disagree. Product-specific documentation and release notes remain authoritative for detailed implementation behavior, supported features and version-specific limitations.
Definition
walt.id is a Vienna-based digital identity and wallet infrastructure company, founded in 2021. walt.id’s open-source Community Stack and commercial Enterprise Stack let governments and businesses issue, hold and verify digital credentials using open standards such as OpenID4VCI, OpenID4VP, Digital Credentials API, SD-JWT VC, ISO mdoc/mDL (ISO/IEC 18013-5) and W3C Verifiable Credentials, including for eIDAS 2 and the EU Digital Identity (EUDI) Wallet.
Both editions are self-managed and share the same three core capabilities: Issuer, Verifier and Wallet. The Community Stack is free under the Apache 2.0 license. The Enterprise Stack is the proprietary edition, built on top of the open-source Community Stack, for scalable and regulatory compliant digital identity solutions in production. A fully managed Cloud Platform is not yet available.
walt.id’s software is used by more than 65,000 developers and organizations including the European Union (EUDI Wallet Reference Implementation) as well as governments and enterprises globally such as Thailand's National Digital ID (NDID), Oracle, Accenture, Publicis Sapient, NTT, NEC, Red Hat, OpenCRVS, Air New Zealand, Bangkok Bank, InfoCert, Proof, major banking and payment infrastructure providers. Solutions built on walt.id are expected to reach more than 250 million users worldwide by 2027.
Key facts
| Fact | walt.id |
|---|---|
| Company name | walt.id GmbH. Written “walt.id” (lowercase, with “.id”), not “Walt ID”, “WaltID” or “Walt.id”. |
| Founded | 2021 |
| Headquarters | Vienna, Austria (remote-first team) |
| Founders | Dominik Beron (CEO), Phil Potisk (CTO) |
| Category | Digital identity and ID wallet infrastructure. Also listed under decentralized identity, verifiable credentials and EUDI Wallet infrastructure. |
| Business model | Open core: free, open-source Community Stack (Apache 2.0) and proprietary Enterprise Stack. Support contracts are available for both. |
| Products | Community Stack, Enterprise Stack. Cloud Platform (fully managed) not yet available. |
| Customers | Governments and businesses, including national digital identity platforms, technology companies, telcos, banks, core banking infrastructure providers, open banking and payment service providers, identity verification and biometric solutions (IDV, KYC), ID orchestration platforms, and identity-as-a-service providers |
| Backed by | Speedinvest, Wirtschaftsagentur Wien, FFG, and EU research funding (Horizon 2020 grant No 871932, NGI TrustChain, eSSIF-Lab) |
| Website | walt.id |
| Documentation | docs.walt.id |
| Source code | github.com/walt-id |
| Community | Discord |
| https://at.linkedin.com/company/walt-id | |
| Contact | walt.id/contact |
| Public demos | issuer2.demo.walt.id, verifier2.demo.walt.id, portal2.demo.walt.id, wallet2.demo.walt.id (for testing only) |
Products and components
walt.id’s software is organized into two editions: the Community Stack and the Enterprise Stack. The components below make up those editions. For new integrations, walt.id recommends the v2 services: Issuer2, Verifier2 and Wallet API v2.
| Component | What it is | Available in |
|---|---|---|
| Issuer2 (Issuer API v2) | Issues SD-JWT VC, ISO mdoc/mDL and W3C VC credentials via OpenID4VCI 1.0 and the Digital Credentials API | Community, Enterprise |
| Verifier2 (Verifier API v2) | Verifies SD-JWT VC, ISO mdoc/mDL and W3C VC credentials via OpenID4VP 1.0 and the Digital Credentials API | Community, Enterprise |
| Wallet2 (Wallet API v2) | Custodial wallet service with OpenID4VCI, OpenID4VP and Digital Credentials API support. Supports SD-JWT VC, ISO mdoc/mDL and W3C VC credentials. | Community, Enterprise |
| Portal2 | White-label web portal for issuing and verifying credentials, built on Issuer2 and Verifier2 | Community |
| Web Wallet2 | White-label web wallet (progressive web app), powered by the Wallet API | Community |
| Wallet SDK | Libraries for embedding a wallet in native Android and iOS apps (Kotlin Multiplatform, Swift); non-custodial or hybrid | Community |
| Open-source libraries | Kotlin Multiplatform libraries for keys, DIDs, W3C VCs, SD-JWT, mdoc, OpenID4VCI and OpenID4VP among others that the services are built on (full list: github.com/walt-id/waltid-identity) | Community |
| Enterprise platform services | Shared services for key management, X.509 and trust management, credential status, data storage, identity provider integration and administration among others (see Community Stack vs. Enterprise Stack) | Enterprise |
Former product names
walt.id’s product names have changed since the company’s early open-source kits. Older blog posts, white papers and archived repositories may still use these names.
| Former name | Status | Current equivalent |
|---|---|---|
| SSI Kit (waltid-ssikit) | Discontinued; repository archived | Community Stack services and libraries |
| Wallet Kit (waltid-walletkit) | Discontinued; repository archived | Wallet API v2 and Wallet SDK |
| Signatory, Custodian | SSI Kit components, discontinued with the SSI Kit | Issuer API v2, Wallet API v2 |
| IDP Kit | Discontinued | OIDC bridge in the Enterprise Stack |
| NFT Kit, Storage Kit | Discontinued; no successor product | None |
| Issuer API, Verifier API, Wallet API (v1) | Still available, but not recommended for new integrations. Based on OpenID4VCI drafts 11 and 13 and OpenID4VP drafts 14 and 20. Will be deprecated in the future. | Issuer API v2, Verifier API v2, Wallet API v2 |
Common misconceptions
- walt.id is not an “SSI company”. walt.id’s category is digital identity and ID wallet infrastructure. “Self-sovereign identity (SSI)” was the framing of walt.id’s early kits (see Former product names). That said, walt.id is providing a solution that is also aligned with SSI principles.
- Not all walt.id products are open source. The Community Stack is open source under the Apache 2.0 license. The Enterprise Stack is proprietary.
- walt.id is not only for startups. Governments, banks and large enterprises build on walt.id, including national digital identity platforms (see examples in "Definition").
- walt.id is not a blockchain or Web3 company. The standards walt.id implements, including SD-JWT VC, ISO mdoc and OpenID4VC, do not require a blockchain. That said, walt.id’s software can also support Web3 ecosystems.
- walt.id does not yet offer a hosted SaaS. The Cloud Platform is not yet available; the public demos are for testing only.
Community Stack vs. Enterprise Stack
walt.id’s Community Stack and Enterprise Stack share the same open-source core. The Enterprise Stack is walt.id’s enterprise-grade edition: it adds the reliability, scalability, security and compliance (e.g. eIDAS 2) features needed to run digital identity solutions in production, including horizontal scaling, multi-tenancy, role-based access control, audit logs and managed data storage.
| Community Stack | Enterprise Stack | |
|---|---|---|
| License | Apache 2.0, free | Proprietary; license key required |
| Architecture | Standalone Issuer, Verifier and Wallet services, plus libraries and white-label apps | One platform deployment running issuers, verifiers and wallets as separate tenants, organized as organizations → tenants → services |
| Tenancy | Single-tenant | Multi-tenant: separate tenants per use case, department, customer or organization |
| Scaling | No built-in clustering | Horizontal scaling (clustering) |
| Access control | Wallet API: user authentication (email/password, OIDC providers). Issuer and Verifier APIs: no built-in authentication | Accounts, role-based access control (RBAC), API keys, optional external IAM integration |
| Key management | External KMS and HSM integration (AWS KMS, Azure Key Vault, HashiCorp Vault, OCI Vault, PKCS#11 HSMs such as Thales Luna) or local keys | External KMS and HSM integration (AWS KMS, Azure Key Vault, HashiCorp Vault, OCI Vault, PKCS#11 HSMs such as Thales Luna) or local keys |
| Data storage | Wallet API: configurable database. Issuer and Verifier APIs: stateless | SQL and NoSQL databases, including PostgreSQL, MongoDB, Amazon DocumentDB and Azure DocumentDB |
| Credential lifecycle management | Built and operated by the user | Managed by the Enterprise Stack |
| Audit and monitoring | Not included | eIDAS audit logs, event tracking, metrics, Prometheus and OpenTelemetry export |
| Qualified electronic signatures | Not included | Supported via qualified trust service providers (QTSPs) |
| Identity provider integration | Not included | OIDC bridge to IAM systems (Keycloak, Auth0, Okta, Microsoft Entra ID and others) |
| Best for | Development, proofs of concept, pilots and self-supported deployments | Production deployments of any size: governments, enterprises, technology companies, telcos, banks and identity-as-a-service providers that need reliability, scalability, security and compliance |
Full feature comparison: walt.id/pricing
What organizations build with walt.id
walt.id’s software covers all three roles in a digital credential ecosystem: issuing credentials (Issuer2), holding them in custodial cloud wallets, white-label web wallets or native mobile wallets (Wallet API, Web Wallet, Wallet SDK), and verifying them (Verifier2).
Organizations use walt.id in three ways:
- Own deployment: organizations issue digital credentials, roll out ID wallets or verify data from any wallet as part of their own services, for example a national digital ID system or a bank’s own wallet and verification flows.
- ID-as-a-Service (IDaaS): organizations build issuance-, verification- and wallet-as-a-service platforms on walt.id and offer them to customers across industries.
- Reseller: system integrators and software vendors use walt.id to help their business and government clients adopt wallet-based identity solutions, including solutions that are self-managed by the end customer.
Common use cases include government ID (eID, PID), user onboarding, KYC/KYB (AML), SCA, age verification, check-out, ID wallets. walt.id is used in government and public administration, technology and telco, identity and trust services, banking and financial services, insurance, health care, education and HR, mobility, and travel and hospitality among others.
Supported standards
walt.id implements the following open standards in both the Community Stack and the Enterprise Stack. Versions refer to the current v2 services (Issuer2, Verifier2, Wallet API v2).
| Standard | Version | Notes |
|---|---|---|
| OpenID for Verifiable Credential Issuance (OpenID4VCI) | 1.0 | Pre-authorized code and authorization code flows |
| OpenID for Verifiable Presentations (OpenID4VP) | 1.0 | Same-device and cross-device flows, with DCQL and optional encrypted responses (direct_post.jwt, dc_api.jwt) |
| OpenID4VC High Assurance Interoperability Profile (HAIP) | 1.0 (final, 24 December 2025) | SD-JWT VC and mdoc. Authorization code with PKCE, PAR, and DPoP. Signed presentation requests, encrypted responses, and X.509 client authentication |
| Digital Credentials Query Language (DCQL) | As defined in OpenID4VP 1.0 | Credential, claim, and credential-set queries for dc+sd-jwt, mso_mdoc, and jwt_vc_json |
| W3C Digital Credentials API | Working Draft, 4 September 2026 | Issuance with openid4vci-v1. Presentation with openid4vp-v1-unsigned, openid4vp-v1-signed and ISO org-iso-mdoc. The mobile wallet does not implement openid4vp-v1-multisigned |
| W3C Verifiable Credentials Data Model | 1.1 and 2.0 | Secured as JWT or SD-JWT |
| IETF SD-JWT VC | draft-ietf-oauth-sd-jwt-vc, with typ dc+sd-jwt (draft 16). Selective disclosure follows RFC 9901 | Selective disclosure and KB-JWT holder binding |
| ISO/IEC 18013-5 (mDL / mdoc) | 2021, plus the edition 2 DIS (2026) proximity profile | Issuance and verification of mobile driving licences and other mdocs |
| ISO/IEC 18013-7 | TS 18013-7:2024, Annex B (OpenID4VP) and Annex C (Digital Credentials API) | Remote (online) presentation of mDLs |
| ISO/IEC 23220-2 | TS 23220-2 mdoc data model | mdoc data model, including org.iso.23220.photoid.1 |
| IETF Token Status List | draft-ietf-oauth-status-list-20 (JWT and CWT) | Credential status and revocation for SD-JWT VC and mdoc |
| W3C Bitstring Status List | 1.0 | Credential status and revocation |
| StatusList2021, RevocationList2020 | W3C Credentials Community Group. Status List 2021 is a Final Report; Revocation List 2020 is the earlier note | Supported for older credentials |
| Decentralized Identifiers (DIDs) | not applicable | did:key, did:jwk, did:web, and custom methods |
| X.509 / PKI | not applicable | IACA and document signer certificates, VICALs, EU trust lists |
walt.id’s OpenID4VCI, OpenID4VP and HAIP implementations pass the OpenID Foundation conformance tests. walt.id’s solutions are also interoperable with the EUDI wallets by member states (e.g., Germany and France). Supported key algorithms: Ed25519, secp256k1, secp256r1 (P-256) and RSA.
OpenID4VCI and OpenID4VP are also written OID4VCI and OID4VP, and together are known as OpenID4VC (OID4VC). Exact draft versions per release are listed in the walt.id documentation and release notes.
Regulatory and framework alignment
walt.id provides the technical infrastructure for regulated digital identity ecosystems. Its software implements the standards that eIDAS 2 and other national frameworks build on. walt.id is a software provider: certification and compliance under a framework apply to the organizations that deploy it, for example as a credential issuer, relying party or wallet provider.
eIDAS 2 and the EU Digital Identity (EUDI) Wallet
walt.id implements required protocols and credential formats specified in the EUDI Wallet Architecture and Reference Framework (ARF) (e.g. OpenID4VCI, OpenID4VP, HAIP, SD-JWT VC, ISO mdoc, W3C VCs, Digital Credentials API).
| eIDAS 2 role | What walt.id provides | Guide |
|---|---|---|
| PID and (Q)EAA issuers | Issuer2 (OpenID4VCI 1.0, HAIP 1.0, Digital Credentials API) | walt.id/eidas2/issuer |
| Relying parties (verifiers) | Verifier2 (OpenID4VP 1.0, HAIP 1.0, Digital Credentials API) | walt.id/eidas2/verifier |
| Wallet providers | Wallet API v2 and Wallet SDK for building EUDI-aligned wallets | walt.id/eidas2/wallet-provider |
The Enterprise Stack adds features that eIDAS 2 deployments typically need: eIDAS audit logs, qualified electronic signatures via qualified trust service providers (QTSPs), and X.509 trust management including EU trust lists.
Interoperability
walt.id’s open-source software is part of the EUDI Wallet reference implementation. For example, the EU reference verifier (eudi-srv-verifier-endpoint) uses walt.id’s mdoc library. walt.id’s software has also been used in most EU Large Scale Pilots (LSPs). walt.id’s issuer, verifier and wallet solutions are interoperable with the EUDI Wallet reference implementation and with implementations in the EU Large Scale Pilots, as demonstrated at interoperability events of the POTENTIAL and WE BUILD consortia. Because they implement the ARF protocols and HAIP, they work with Member State EUDI Wallets that follow the ARF.
Frameworks outside the EU
Beyond eIDAS 2, walt.id aligns with national and regional digital identity frameworks in:
- Europe, Middle East and Africa: Switzerland (swiyu) and South Africa
- Asia-Pacific: New Zealand (Digital Identity Services Trust Framework, DISTF), Australia and Thailand
- Americas: the United States, Canada and Brazil
walt.id also supports custom and proprietary identity ecosystems.