EUDI Wallet integration handbook
What a relying party — a bank, platform, or service provider that needs to accept the wallet — actually has to do, with links to the primary sources.
Last reviewed 2026-06-17
Who must accept the wallet, and when
Under eIDAS 2.0 (Regulation (EU) 2024/1183), member states must make a European Digital Identity Wallet available by 24 December 2026. From late 2027 (expected — the precise date is subject to the implementing acts), relying parties in regulated sectors — and very large online platforms — will have to accept the wallet wherever they require strong user authentication. If you operate in banking, payments, telecoms, or run a large platform, acceptance is not expected to be optional.
The ARF in brief
The Architecture and Reference Framework (ARF) is the technical blueprint the wallet ecosystem is built on. The pieces a relying party needs to understand:
- PID — the Person Identification Data issued by a member state; the core identity attestation.
- (Q)EAA — (Qualified) Electronic Attestations of Attributes: verifiable claims such as age, diplomas, bank-account ownership or professional licences.
- Credential formats — ISO/IEC 18013-5 mdoc and W3C Verifiable Credentials (SD-JWT VC) for selective disclosure.
- Presentation protocols — OpenID for Verifiable Presentations (OpenID4VP) to request attestations, and OpenID4VCI for issuance.
- Relying-party registration — verifiers register with a national registrar and receive access certificates; the wallet shows the user who is asking and for what.
- Selective disclosure & data minimisation — request only the attributes you need; the user consents per presentation.
Relying-party readiness checklist
- Confirm whether and when the acceptance obligation applies to your sector.
- Identify the exact attributes you need (and only those) for each user journey.
- Register as a relying party / verifier with the relevant national registrar and obtain access certificates.
- Implement OpenID4VP presentation requests; support both mdoc and SD-JWT VC formats.
- Validate issuer trust against the EU/national trust lists; check revocation status.
- Handle selective disclosure responses and verify cryptographic proofs of the presented attestations.
- Design the consent and fallback UX: what happens when a user has no wallet, or declines.
- Map data handling to GDPR — purpose limitation, minimisation, retention.
- Test against a reference wallet / member-state pilot before go-live.
- Plan for cross-border recognition: a wallet issued in one member state must work in yours.
Primary sources
Always verify against the original texts — this page is a summary, not legal advice.