EU Wallet interoperability self-test

Point your OpenID4VP-capable EU Wallet at the CodeB verifier and get a live report of what worked, what didn’t, and which spec section applied. Free, no sign-up, no cookies, no data retained.

What this tests. The wallet's OpenID4VP + HAIP behaviour against a running verifier — can your wallet parse an ES256-signed JAR with an x509_hash client_id, does it honour DCQL, does it JWE-encrypt the response with ECDH-ES + A128GCM, does it emit a valid KB-JWT with the nonce we sent?

What this does NOT test. Anything server-side (issuer chain, LOTL trust, WUA verification) is out of scope for a wallet-side self-test. See HAIP implementation notes for our verifier's own scope.

Reporting note. Checks marked inferred pass are derived from a single verified/declined signal returned by the verifier, not from per-check evidence. A verified response implies most of the chain (JAR ok, x509 matched, DCQL parsed, nonce echoed, JWE decrypted, KB-JWT verified, disclosures matched, aud matched); per-check server-side evidence lands in a next iteration. Use this page for interop smoke-testing, not for conformance certification.

Scan with your EU Wallet. On the same device, tap the button below to open the wallet directly.

Open EU Wallet on this device

Idle. Click Start test above.

Report

0 pass 0 inferred 0 fail 0 pending Elapsed: —

Start the test to populate the checklist.

This is a wallet-side interop test. Verifier scope + our own implementation record are in HAIP implementation notes. See also drop-in widget, verifier API.