EUDI Wallet integration for relying parties

If your service needs to accept the EUDI Wallet, you are a relying party (a verifier). This is the high-level integration path; the handbook has the full readiness checklist and primary-source links.

1. Register as a verifier

You register with the relevant national registrar and receive access certificates that identify your organisation and the attributes you are entitled to request. The wallet uses this to show the user who is asking — a core anti-abuse control.

2. Request attestations with OpenID4VP

Presentation requests use OpenID for Verifiable Presentations (OpenID4VP). You specify exactly which attributes you need; the user reviews and consents in the wallet. Issuance (when you also issue credentials) uses OpenID4VCI.

3. Support both credential formats

• mdoc (ISO/IEC 18013-5) — used for mobile documents like driving licences.
• SD-JWT VC — selective-disclosure JWT verifiable credentials used widely for attribute attestations.

A production integration should handle both, because issuers differ in what they use.

4. Verify trust and proofs

• Validate the cryptographic proof on each presented attestation.
• Check the issuer against EU/national trust lists.
• Check revocation status.
• Honour selective disclosure — store only the attributes you actually requested.

5. Design the fallback and consent UX

Not every user will have a wallet on day one. Decide what happens when a user has no wallet or declines, keep your data handling within GDPR purpose limitation, and test against a member-state reference wallet before launch.

Where to go next

Work through the relying-party readiness checklist, and confirm the acceptance obligation timing for your sector.