OpenID4VP verifier guide – with DCQL examples for SD-JWT VC
This page is for developers who build their own verifier (relying party) and want CodeB Wallet to answer its requests. It lists what the wallet checks before it shows a request, and gives DCQL queries of the kind our own demo verifier sends – copy them and change the type. If you would rather keep plain OpenID Connect in your application, the CodeB EUDI Gateway does all of this for you.
The request: by reference, signed, with your access certificate
openid4vp://?client_id=x509_hash:<hash of your certificate>
&request_uri=https://verifier.example/request/abc
&request_uri_method=post- The link or QR code carries
client_idandrequest_uri. Withrequest_uri_method=postthe wallet fetches the request by POST and sends awallet_nonce; your request object must carry the same value. - The request object is a signed JWT (
typoauth-authz-req+jwt, for example ES256) with your certificate chain inx5c. client_iduses the prefixx509_hash:(the hash of your certificate) orx509_san_dns:(a DNS name in it).- The certificate must lead to an access certificate authority on a trusted list. If it does not, CodeB Wallet refuses the request and shares nothing.
- Put your registration certificate into
verifier_info. The wallet compares what you ask with what you are registered for and warns the person if you ask for more.
DCQL examples (Digital Credentials Query Language)
OpenID4VP 1.0 describes what you ask for in DCQL; the older Presentation Exchange format is not part of it. Each query names a format, the accepted types (vct_values) and the claims as paths. Ask for as little as you need – the person sees every item before sharing.
{
"credentials": [{
"id": "age",
"format": "dc+sd-jwt",
"meta": { "vct_values": ["urn:eudi:pid:de:1"] },
"claims": [ { "path": ["age_equal_or_over", "18"] } ]
}]
}{
"credentials": [{
"id": "city",
"format": "dc+sd-jwt",
"meta": { "vct_values": ["urn:eudi:pid:1", "urn:eudi:pid:de:1"] },
"claims": [ { "path": ["address", "locality"] } ]
}]
}{
"credentials": [{
"id": "name",
"format": "dc+sd-jwt",
"meta": { "vct_values": ["urn:eudi:pid:1", "urn:eudi:pid:de:1"] },
"claims": [ { "path": ["given_name"] }, { "path": ["family_name"] } ],
"trusted_authorities": [ { "type": "aki", "values": ["<key identifier of an issuer CA you accept>"] } ]
}]
}{
"credentials": [{
"id": "member",
"format": "dc+sd-jwt",
"meta": { "vct_values": ["https://issuer.example/vc/member-card/1.0"] },
"claims": [ { "path": ["member_number"] }, { "path": ["member_name"] } ]
}]
}Nested values are paths: ["address", "locality"] is the city inside the address. With trusted_authorities you name the issuers you accept; cards from other issuers are not offered to the person.
The answer
- With
response_modedirect_postthe wallet posts the answer to yourresponse_uri. Withdirect_post.jwtthe answer is encrypted to the key in yourclient_metadata. - For each query you receive one presentation: the SD-JWT VC with only the disclosures you asked for, and a key-binding JWT over your
nonceand yourclient_id. - Check the issuer’s signature and its place on the trusted lists, validity and status, the key binding and the nonce. Then keep only what you need.
Formats and flows
- Formats: SD-JWT VC (
dc+sd-jwt) and ISO mdoc (mso_mdoc). - Cross-device flow: a QR code on a computer, scanned with the phone. Same-device flow: a link or button on the phone that opens the wallet.
- Digital Credentials API in the browser: a signed request must name your website in
expected_origins.
Test your verifier with CodeB Wallet
Install CodeB Wallet (closed beta), open a free CodeB account for a test PID and point your verifier at the wallet. The use-case demos show how such requests look to the person.
A verifier with a test certificate that is on no trusted list is refused. For such tests the app has a switch for testers; how to get it is on the page about the public EUDI test playground.