Summary: walt.id is best cataloged not as one more generic identity vendor, but as an open-source middleware stack for issuing, storing, presenting, and verifying digital credentials across multiple standards. Its docs and repo make the architecture unusually legible: white-label apps on top, wallet/issuer/verifier APIs in the middle, and lower libraries for cryptography, DID handling, W3C credentials, SD-JWT, mdoc, and OpenID4VC underneath. The reusable mechanism insight is that walt.id turns standards-heavy identity plumbing into deployable developer surfaces, which makes it a useful comparison point for where practical power sits in open credential ecosystems: middleware defaults, DID-method support, issuance-time data functions, verification policies, feature flags, and wallet/app packaging.
What it does:
Provides white-label wallet and portal apps for credential issuance, storage, and verification flows
Exposes wallet, issuer, and verifier APIs so developers can build custom applications on top of the same identity stack
Supports multiple credential formats including W3C Verifiable Credentials, SD-JWT VCs, and ISO mdoc / mDL flows
Implements OID4VCI and OID4VP-based exchange flows rather than inventing a proprietary credential-delivery protocol
Includes lower libraries for key management, DID creation/resolution, credential issuance/verification, SD-JWT handling, and OpenID4VC protocols
Extends wallet functionality into optional web3-wallet integration so identity wallets can also surface chain assets and wallet login patterns
Key claims:
The main waltid-identity repo describes the project as an all-in-one open-source identity and wallet toolkit with multi-platform libraries, APIs, and white-label apps
The repo explicitly breaks the stack into web wallets, issuer/verifier portal apps, and dedicated Issuer API, Verifier API, and Wallet API layers, which makes the architecture more modular than a single-product framing suggests
The wallet docs say the Wallet API can manage keys, DIDs, multiple credential types, and OIDC4VC credential exchange while also supporting web3-wallet integration across ecosystems like Ethereum and Polygon
The issuer docs say the Issuer API can issue W3C, SD-JWT VC, and mDL credentials via OID4VC and can dynamically populate credentials through issuance-time data functions
The verifier docs say the Verifier API supports W3C, SD-JWT, and mDL verification via OID4VP and exposes customizable verification policies
The docs consistently emphasize standards support rather than one bespoke format: DID methods, credential-status schemes, signing algorithms, OpenID4VC, and ecosystem-specific integrations are all configurable surfaces
The OID4VCI concept guide shows the stack’s broader worldview: open credential issuance and presentation are treated as foundational global identity infrastructure rather than niche product features
Whitepaper: No canonical walt.id whitepaper surfaced in this pass. The strongest primary materials were the docs corpus and the main open-source identity repository collected in ../whitepapers/walt-id-primary-sources-2026-05-13.md.
Keep the comparison on deployable middleware defaults — issuer policy, verifier policy, DID-method support, and exchange-flow packaging — rather than broad identity-theory sprawl.