Prepare a relying party integration for the EUDI Wallet under eIDAS 2.0 for EU user authentication

domain: ec.europa.eu · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Review the EU Architecture Reference Framework (ARF) published by the European Commission; it defines the technical protocols that all EUDI Wallet implementations must support, including OID4VP for presentation and OID4VCI for credential issuance.
  2. Register as a relying party with the appropriate national trust framework registration process; relying parties must be enrolled in a Member State trust registry before their presentation requests will be accepted by EUDI Wallets.
  3. Implement an OID4VP verifier endpoint that requests the Person Identification Data (PID) credential (the EUDI Wallet's core identity credential) using the credential type eu.europa.ec.eudi.pid.1.
  4. Handle selective disclosure: EUDI Wallets support SD-JWT VC or mdoc (ISO 18013-5) formats for PID — request only the minimum set of attributes your service needs (e.g., family_name, given_name, birth_date, age_over_18) to meet data minimization requirements under GDPR.
  5. Integrate a third-party EUDI Wallet Connector or Verifier API (such as those offered by Digidentity, Vidos, or similar QTSPs) to abstract the cryptographic validation and trust registry lookups across all 27 Member State wallet implementations.
  6. Plan for the December 2026 Member State rollout deadline and the December 2027 deadline for financial institutions under Strong Customer Authentication; test with the EU reference wallet implementation available on GitHub.

Known gotchas

Related routes

Register as a Relying Party under the EU Digital Identity Wallet (EUDI) framework to request attributes from a citizen's wallet under eIDAS 2.0
eudi.dev · 5 steps · unrated
Implement an OpenID4VP relying party integration to request and verify attributes from an EU Digital Identity (EUDI) Wallet under the eIDAS 2.0 Architecture and Reference Framework
eudi-wallet.eu · 6 steps · unrated
Stand up an eIDAS 2.0 EUDI Wallet verifier using a QTSP-provided connector API
eudi-wallet.eu · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans