OpenID for Verifiable Presentations
OID4VP Verification API
Integrate an OID4VP relying-party flow without building every wallet protocol step into your application. Use a verification API for supported SD-JWT and mdoc presentations, with a TypeScript SDK for session creation.
01 / OpenID for Verifiable Presentations
From presentation request to verified result
Your service creates a verification session with the requested credential formats and claims. For signed JAR sessions, choose POST delivery so compatible wallets can provide metadata for Request Object encryption negotiation. The wallet responds to the presentation request, and the gateway validates the response before returning the requested attributes or predicate outcome.
- Define the formats and claims supported by your relying-party flow
- Use POST with wallet metadata to negotiate supported Request Object encryption; GET remains available for compatibility
- Bind the response to its session and nonce, then handle the result in your application and webhook workflow
02 / OpenID for Verifiable Presentations
Support for wallet credential formats
The gateway includes OID4VP flows for supported SD-JWT and ISO mdoc presentations. The exact request profile and claims depend on the wallet, credential, and relying-party configuration.
- SD-JWT presentation processing
- mdoc presentation processing for configured profiles
- Issuer and credential trust checks with fail-closed verification
03 / OpenID for Verifiable Presentations
Build with the SDK and guides
Use the quickstart to create a session, then consult the advanced OID4VP guide for profiles and testing. Exercise successful and rejected presentations in the sandbox before connecting production workflows.
- TypeScript SDK and API reference
- Advanced OID4VP implementation and test guidance
- Webhook security guidance for receiving outcomes
Continue exploring
Implementation guides and related pages
Request Object encryption depends on wallet support and compatible advertised keys and algorithms. Invalid or unsupported encryption metadata fails closed; GET delivery and POST without an encryption JWKS return a signed, unencrypted Request Object. OID4VP does not by itself define the relying party’s authorization policy, establish credential assurance, or guarantee that every wallet supports every request profile.