Lint OpenID4VP presentation requests against the EU Digital Identity Wallet relying-party rules: registered client_id, a stated purpose, minimised claims, encrypted response, live registration. Runs entirely in your browser — nothing is uploaded.
Same engine as the VS Code extension, byte for byte.
This page is the working piece. The full pack has everything below.
Nine rules that read the JSON your service sends to an EU Digital Identity Wallet
One hour of a European contract identity engineer costs more than $29 once — this reads the same nine rules in a second.
Buy the full version — $29It reads an OpenID4VP presentation request — the JSON your service sends to a user's EU Digital Identity Wallet — and applies nine rules to it: registered client_id prefix, a purpose on every credential query, named claims instead of whole credentials, age flags over date of birth, encrypted response mode, nonce, signed request, live registration window, and known credential types.
Identity, payments and onboarding engineers at EU banks, marketplaces and public services that have to accept the wallet. If you are writing the verifier side of OpenID4VP against the EUDI Architecture and Reference Framework, and your relying-party registration is being prepared for the national register, this is your file.
A JSON schema validator says your request is valid JSON. A general linter has never read Implementing Regulation (EU) 2025/848. Chat assistants trained before the 2025 implementing acts still suggest presentation_definition with a bare URL client_id, which is exactly the pattern rule one rejects. The rules here carry the article they come from.
Free finishes a real job: lint one request file, in the editor or on the web page, and read all nine rules with the article behind each finding. The full version changes the scope — it scans every request file in the workspace in one pass and exports a dated relying-party evidence report you keep and hand on.
One hour of a European contract identity engineer costs more than the full version does once. Reading Implementing Regulation (EU) 2025/848 and the Architecture and Reference Framework against one request set takes longer than an hour the first time, and the reading has to happen again each time the request changes.
One question, answered by the person who built it. Your email only if you want the answer sent.