- Glossary
- OID4VP (OpenID for Verifiable Presentations)
OID4VP (OpenID for Verifiable Presentations)
An OpenID Foundation protocol for requesting credentials from a digital wallet and presenting them to a service.
OpenID for Verifiable Presentations defines how a service (the verifier) asks a digital wallet for credentials and how the wallet sends back a presentation. It builds on OAuth 2.0, works with several credential formats, including SD-JWT VC and mdoc, and is the presentation protocol of the EU Digital Identity Wallet.
A typical flow
- The verifier creates a request that says which credentials or attributes it needs, often shown as a QR code or link.
- The wallet shows the holder what is being asked for and by whom.
- With the holder's consent, the wallet sends a presentation that shows the credential is valid and bound to that wallet.
- The verifier checks the issuer's signature, the holder binding and whether the credential has been revoked.
OID4VP in the EUDI Wallet and the Swiss E-ID
The EUDI Wallet Architecture and Reference Framework uses OID4VP for remote presentation, so services that want to accept EU wallets under eIDAS 2.0 will need to support it. Presentation in person, for example at a counter, uses ISO/IEC 18013-5 instead.
Switzerland's swiyu trust infrastructure also uses OID4VP for presenting credentials, together with OID4VCI for issuing them and SD-JWT VC as the credential format. Because the same protocol is used on both sides of the border, a verifier built for one can be adapted to the other more easily, although trust lists and registration rules differ.
OID4VP also supports the data minimisation that the GDPR and the nFADP require: the request names exactly which claims are needed, and with SD-JWT VC the wallet discloses only those.
How secuveri handles it
secuveri accepts swiyu Beta-IDs and saved secuveri Verified IDs from the swiyu wallet in swiyu's public beta, for identity and for age (over 18 only). Accepting identity data from EU member-state wallets is planned. The swiyu playground shows the flow: get a secuveri credential, present it from the swiyu app and see what was checked and shared.
Frequently asked questions
- What is the difference between OID4VP and OID4VCI?
- Both are OpenID Foundation protocols for digital credentials. OID4VCI covers issuance: how a wallet obtains a credential from an issuer. OID4VP covers presentation: how a verifier asks a wallet for a credential and receives it. A wallet usually supports both, while a business that only checks credentials needs OID4VP.
- Is OID4VP the same as OpenID Connect?
- No, though they are related. OpenID Connect lets a user sign in through an identity provider, which vouches for them at that moment. With OID4VP, the user presents a credential they already hold, and the verifier checks the issuer's signature itself. The issuer is not contacted during the presentation and doesn't learn where the credential was used.
Related terms
Articles on this topic
Talk to us
Tell us what you’re trying to verify. We’ll show you how secuveri can fit your workflow.
