What is eIDAS 2.0?
“eIDAS 2.0” is a common name for the European Digital Identity framework established by Regulation (EU) 2024/1183. It amends the earlier eIDAS Regulation (EU) No 910/2014 and adds a harmonised framework for European Digital Identity Wallets, wallet-related attestations, and their use across public and private services.
The framework sits alongside existing rules for electronic identification and trust services, such as electronic signatures, seals, certificates, and registered delivery. The Wallet is a prominent new part of that framework, but eIDAS 2.0 is broader than wallet presentation alone.
Main building blocks
- European Digital Identity Wallets: wallet units let users hold and present person identification data and electronic attestations of attributes, and support other functions defined by the framework.
- Person identification data (PID): identity data associated with a person and issued under the applicable scheme and profile.
- Electronic attestations of attributes (EAAs): attestations from an issuer about attributes such as qualifications or other facts. Availability and accepted formats depend on the issuer and wallet ecosystem.
- Trust services: eIDAS also covers services such as electronic signatures, seals, time stamps, certificates, and electronic registered delivery.
- Relying parties: services that request data from a wallet are expected to identify themselves, state their intended use, request only the declared data, and validate the PID or attestation they receive under the applicable rules.
How wallet verification fits
A relying party creates a request for specific claims or attestations. The user reviews the request in a compatible wallet and chooses whether to present the requested data. The relying party then validates the presentation and issuer under its configured profile and applies its own service policy.
Protocols such as OpenID for Verifiable Presentations define technical request and response flows. Credential formats such as SD-JWT VC and ISO mdoc define different ways to represent credentials and holder or device proofs. The regulation does not mean that every wallet supports every credential, protocol profile, or attribute.
What the framework does not decide for your application
Technical validation is only one input to a relying party's process. An API that verifies a presentation does not register the relying party, establish the service's legal basis, decide which attributes are necessary, or determine whether a particular onboarding or access decision meets sector-specific requirements.
Before launch, identify the rules that apply to the service and jurisdiction, confirm the required relying-party registration and wallet profiles, and define issuer trust, request purpose, data retention, and fallback paths. Requirements can depend on the type of service and applicable Union and national rules.
Technical implementation resources
- EUDI Wallet overview for relying parties
- EUDI Wallet integration checklist
- OID4VP overview
- EUDI Wallet verification API