eudi.tools · Guide
Test your OpenID4VP verifier with a wallet that shows its working
You are building a verifier for EU Digital Identity credentials, and you need a wallet to test it against — one that tells you what it made of your request, which credential matched and why, and what it sent back. This guide takes you from an empty wallet to a presentation your verifier receives, in a few minutes, with synthetic test data.
What you need
- A verifier that creates OpenID4VP 1.0 requests with a DCQL query, as an
openid4vp://link or a QR code — by value, or by reference withrequest_uri. - A
response_urireachable overhttps, withresponse_modedirect_postordirect_post.jwt(encrypted). eudi.tools posts the response from its server so it can show you your verifier's answer; it stores and logs nothing. - Testing a verifier on
localhost? That works too: the wallet fetches the request and posts the response straight from your browser, so nothing passes through eudi.tools. Your browser may ask whether eudi.tools may reach your local network — allow it. To see your verifier's answer, have it sendAccess-Control-Allow-Origin: https://eudi.tools. - A browser. No account, no install.
1. Put a test credential in the wallet
Open eudi.tools and choose Get a test PID: a Person Identification Data credential about a made-up person, Alex Bloggs, issued over OpenID4VCI in a few seconds and bound to a key only your browser holds. Make your own PID lets you choose the name and birth date. The issuer also offers a mobile driving licence (mdoc), so you can test SD-JWT VC and mdoc requests alike.
2. Hand the wallet your request
- Paste the
openid4vp://link into the bar at the top — or press ⌘V anywhere on the page. - Drop or paste a screenshot of the QR code; the wallet reads it in the browser.
- Or pair your phone from the wallet's header, and scan the QR code on another screen with it.
3. Read the review
The request opens as a sheet that says, before anything is sent:
- Who is asking — the client identifier and its prefix (
redirect_uri,x509_san_dns,x509_hash, …), whether the request had to be signed under that prefix, and the certificate it was signed with. - What it asks for — each credential query in your DCQL, the card that answers it, and the claims that would leave, by name. What is not shared is listed too.
- Beyond its registration — when the request carries
verifier_info, claims asked for beyond what the verifier registered are marked. - Transactions —
transaction_datais shown in words, as what you are approving.
4. When nothing matches
A request the wallet cannot answer is not a dead end. It says, for each credential it holds, why it does not match your query — the wrong vct, a claim path that does not exist, a value that does not meet your constraint — and offers to collect one that would. This is usually where a DCQL bug shows itself.
5. Send, and see what travelled
Approve, and the wallet builds the presentation — selective disclosures and a key binding JWT for SD-JWT VC, a device-signed response for mdoc — and posts it to your response_uri — encrypted to your key first, when you ask for direct_post.jwt. It shows your verifier's status and body verbatim, files a receipt on the card, and See the wire opens every message: the request as fetched, the response as sent, and each token decoded.
6. Test the refusals
A verifier is tested as much by what it rejects. The issuer offers credentials that a conformant verifier must refuse: expired, signed by the wrong key, tampered with after issuance, missing a mandatory attribute, and revoked on its status list two minutes after issuance. Collect one, present it, and check that your verifier says no — and why.
Not supported yet
- The browser's Digital Credentials API (
navigator.credentials.get).
When something fails on the issuing side, the errors pages explain the common refusals.