Steps

Evaluate QTSP-provided EUDI Wallet Connector or Verifier APIs (e.g., Digidentity, Vidos, iGrant.io); confirm the connector is compliant with the EU Architecture Reference Framework (ARF) and supports both SD-JWT VC and mdoc/ISO 18013-5 credential formats.
Register as a relying party with the connector provider; provide your service purpose, the attribute scope requested, and your redirect URI for the OID4VP response.
Configure the presentation request: specify the credential type (eu.europa.ec.eudi.pid.1 for the Person Identification Data credential) and the minimum set of attributes required using the SD-JWT selective disclosure or mdoc namespace field selectors.
Integrate the verifier connector's authorization initiation endpoint into your authentication or onboarding flow; the connector returns a QR code or deep link for the user's EUDI Wallet app to scan.
Receive and parse the OID4VP response at your registered redirect URI; the connector handles cryptographic signature validation, trust registry lookups, and revocation checks, returning a normalized verified claims payload.
Log the verification transaction ID, the issuing Member State, credential type, disclosed attributes, and verification timestamp for GDPR data processing records.

Known gotchas

EUDI Wallet pilots are ongoing through 2026; the ARF and implementing acts are still being finalized, meaning connector APIs from QTSPs may change interfaces before the mandatory rollout deadlines — build versioned abstraction layers.
Selective disclosure means users can choose not to disclose optional attributes; design your service to function with only the minimum required attributes and avoid hard dependencies on optional fields that users may decline to share.
GDPR purpose limitation applies: attributes obtained via EUDI Wallet verification may only be used for the purpose stated in your relying party registration; secondary use or retention beyond the stated purpose requires a separate legal basis.

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

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

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

Stand up an eIDAS 2.0 EUDI Wallet verifier using a QTSP-provided connector API

Steps

Known gotchas

Related routes

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

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