The EU Digital Identity Wallet is becoming
an interoperable source of trust.
By the end of 2026, every EU Member State must offer at least one wallet. Receiving a verified attribute is only the start: organisations need registration, trust validation, purpose policy and controlled downstream use.
Status reviewed 22 August 2026. This page explains implementation readiness and is not legal advice.
Current status
The legal framework exists. Operational rollout is the next threshold.
The wallet is no longer only a policy proposal, but production availability and relying-party readiness still require implementation across Member States and sectors.
May 2024
European framework in force
Regulation (EU) 2024/1183 amended eIDAS and created the legal framework for EU Digital Identity Wallets.
December 2024 onward
Implementation rules established
Core functions, protocols, interfaces, attestations, certification and ecosystem notifications are covered by Commission implementing regulations, with further rules including relying-party registration.
2023–2026
Pilots and reference implementations
Large-scale pilots, open-source reference components and the Architecture and Reference Framework test cross-border use cases and conformance.
By end of 2026
Wallet availability required
Each Member State must offer at least one wallet. Use by citizens remains voluntary; acceptance obligations apply to public and specified private services.
What a relying party needs
Connecting a wallet is a trust and data-governance project.
The request shown to the holder, the registered purpose and the data actually used downstream must remain aligned.
Do not collapse distinct roles
Identity, signatures and payments can meet in one operation without becoming the same thing.
Datastreams coordinates the verified results and conditions. Regulated issuers, trust services and payment providers keep their own responsibilities.
Verified attributes
The wallet can present identity data or attestations such as age, qualification or authority. The recipient still validates trust and applies its business policy.
Signatures and seals
Wallets support electronic signing. A qualified electronic signature or seal depends on the qualified trust-service chain and must not be treated as an ordinary app signature.
Payments
The wallet can support strong authentication and bind transaction data. Payment authorisation, processing and settlement still involve the applicable payment service provider and rules.
Where the runtime fits
Turn a verified presentation into a permitted business outcome.
The wallet supplies a presentation. Datastreams connects it to the rest of the operation: contract validation, trust checks, consent and purpose, entitlement, destination, evidence and recovery. Wallet, issuer and trust-service adapters can be replaced behind the same contract when their formats, trust level and legal status are compatible.
- 01Receive the wallet presentation
- 02Validate proof, issuer, status and requested attributes
- 03Evaluate purpose, consent and business policy
- 04Transform or minimise the accepted data
- 05Deliver only to permitted destinations
- 06Record the decision and downstream result
Primary sources
Track the framework, not the headlines.
Technical profiles and national processes continue to evolve. Verify against the applicable regulation, implementing acts and current framework before production.
Prepare the business operation before the wallet request arrives.
Choose one service, the minimum attribute it needs, its legal purpose, permitted destination and required evidence. That becomes the first wallet-enabled stream configuration.
Map a wallet-enabled service