Digital Credentials API integration
OpenID4VP defines response modes for integration with the W3C Digital Credentials API (DC API). This enables browser-mediated wallet invocation where the browser, verifier web app, and wallet coordinate presentation exchange.
For a detailed understanding see Digital Credentials API. This page focuses on the OpenID4VP-specific “DC API profile”: response modes, protocol identifiers, and request object shapes.
In OpenID4VP, the DC API integration uses these response modes:
dc_apidc_api.jwt
Protocol identifiers
Section titled “Protocol identifiers”The DC API profile defines protocol identifiers that indicate how the request is packaged:
openid4vp-v1-unsignedopenid4vp-v1-signedopenid4vp-v1-multisigned
These identifiers are used by the browser and wallet to select the correct processing rules.
Request object shapes
Section titled “Request object shapes”In Vidos’ shared types, DC API authorization request objects can take multiple forms:
- Unsigned: An OpenID4VP request object without a
client_id. - Signed: A JWT wrapper containing the request in a
requestclaim. - Multisigned: A structure that carries a payload plus one or more signatures.
Which form you use depends on your wallet ecosystem and trust requirements.
Relationship to direct_post
Section titled “Relationship to direct_post”DC API response modes are still conceptually “post back to the verifier,” but the invocation mechanism and trust model differ from a plain direct_post.