Skip to content

EUDI Wallet Request Lab

SysSeder · Identity engineering

EUDI wallet learning lab

Explore a synthetic OpenID4VP request, inspect a small DCQL subset and check browser API presence—without opening a wallet.

Educational, not a verifier or certification service. Do not paste real credentials, identity documents, tokens, private keys or personal data. This code does not transmit or save input; the surrounding blog and its scripts have their own privacy behavior. SysSeder is not acting as a registered EUDI relying party.

1. Build & inspect a synthetic request

The example requests a fictional age claim using dc+sd-jwt. The reserved .invalid endpoints are deliberately non-operational. No QR code, launch link or identity request is produced.

Ready. All actions are local to this page; no wallet prompts.

2. What this lab can—and cannot—test

  • Available: JSON parsing, selected request-field checks, a limited SD-JWT DCQL structure, secure-random nonce/state generation and passive browser API presence.
  • Not implemented: complete OpenID4VP/DCQL schema validation, mdoc/CBOR, credential decoding, signatures, holder binding, expiry, revocation, replay protection, issuance, installed-wallet discovery or interoperability tests.
  • Requires additional infrastructure: a controlled verifier, authenticated requests where required, secure sessions and response handling, credential trust validation, and the applicable relying-party registration and certificates. A public blog snippet cannot supply that authority.

3. Continue with official implementations

Use synthetic test identities only and review each external environment’s own instructions and privacy terms before using it. External links leave this local lab.

References checked 24 October 2026. This lab pins a narrow educational subset; it does not establish compliance with any EUDI profile or legal requirement.

Post a Comment