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.
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.
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.
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.
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.
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
eIDAS 2.0 (Regulation 2024/1183) is published but national implementing acts and trust registry infrastructure remain in active development as of mid-2026; production EUDI Wallet traffic is limited to pilots — do not plan mandatory use before the 2026-2027 deadlines.
The PID credential format differs between Member States that chose mdoc (ISO 18013-5) versus SD-JWT VC; a verifier must support both formats or risk incompatibility with subsets of Member State wallets.
EUDI Wallet relying party registration requirements and fees differ per Member State; operating across the EU requires separate registrations or a pan-EU trust anchor solution from a QTSP.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp