Credential Formats
SD-JWT VC (dc+sd-jwt), W3C VC as JWT (jwt_vc_json), ISO/IEC 18013-5 mdoc (mso_mdoc), and ISO/IEC 23220.
Overview
Unlike the Community Stack, the Enterprise Stack isn't split into three separate products (Issuer, Verifier, Wallet). It's a single, unified stack that can power different digital identity use cases. One of those is running one or many credential verifiers via its multi-tenant model.
Below is the full list of Enterprise Stack capabilities that are relevant for building credential verification solutions.
Credential Verification Capabilites
Protocols
OID4VP 1.0 and ISO-18013-7 for mDL / mdoc remote presentation. Deprecated Verifier v1 still covers drafts 14/20.
Status Credential Formats
TokenStatusList (incl. draft 8), Bitstring Status List v1.0, StatusList2021, RevocationList2020
Digital Credentials API
Unified browser API for credential issuance/verification; abstracts OID4VCI/VP & ISO-18013-7 for 1-click web integrations.
Same-device remote flow
User stays on one device for issuance or presentation, typically via redirect or in-app handover.
Cross-device remote flow
QR code or companion-device handover for issuance and remote presentation.
Proximity presentation
On roadmapIn-person credential share over BLE or NFC, including ISO/IEC 18013-5 proximity flows.
Selective disclosure
Only requested claims leave the wallet, using SD-JWT disclosures or mdoc namespaces.
Signed request object (JAR)
Wallet authenticates the verifier from a signed request object before showing consent.
Request by reference
Wallet fetches the presentation request from request_uri over HTTPS, including GET and POST retrieval.
X.509 verifier identity
Verifier identity from certificate-bound client identifiers, including x509_hash and x509_san_dns.
Posted / encrypted presentation responses
Authorization responses posted to response_uri as direct_post or encrypted direct_post.jwt.
Last updated on July 30, 2026