Every EU member state must make an EU Digital Identity Wallet available to its citizens by the end of 2026, and about twelve months later banks and other financial services firms must start accepting it. The obligations come from Regulation (EU) 2024/1183, the revision of the eIDAS Regulation commonly called eIDAS 2, which requires private firms that use strong user authentication for online identification to accept the EU Digital Identity Wallet when a customer asks to use it.
For banks, payment institutions and fintechs operating in the EU, the wallet is less a consumer app than a new identity rail. It changes how customers prove who they are at onboarding, how firms collect verified attributes, and what each firm must register before it can ask for data at all.
The countdown runs from implementing acts that took effect on 24 December 2024
eIDAS 2 does not set calendar dates for the two headline deadlines. Instead, Article 5a(1) gives each member state 24 months to provide at least one wallet, and Article 5f(2) gives private relying parties 36 months to accept it. Both periods run from the date of entry into force of the implementing acts referred to in Article 5a(23) and Article 5c(6).
The first set of those implementing acts was adopted by the European Commission on 28 November 2024. Implementing Regulation (EU) 2024/2977, which governs the person identification data and attestations issued to wallets, was published in the Official Journal on 4 December 2024 and entered into force on 24 December 2024, alongside companion acts on wallet integrity and core functions (2024/2979) and on protocols and interfaces (2024/2982). The European Commission states that the framework mandates member states to provide wallets to citizens by the end of 2026.
| Milestone | Legal basis | Timing |
|---|---|---|
| Implementing acts on wallet rules adopted | Article 5a(23), Article 5c(6) | Adopted 28 November 2024; Regulation 2024/2977 in force 24 December 2024 |
| Each member state provides at least one wallet | Article 5a(1) | Within 24 months of those acts: end of 2026 |
| Banks and other regulated private firms must accept the wallet on request | Article 5f(2) | Within 36 months of those acts: late December 2027 |
Which banks and fintechs must accept the EU Digital Identity Wallet
Article 5f(2) applies to private relying parties that are required by Union or national law, or by contract, to use strong user authentication for online identification. The article lists banking and financial services by name, alongside transport, energy, health, telecommunications and other sectors. Microenterprises and small enterprises, as defined in Commission Recommendation 2003/361/EC, are exempt.
The regulation defines strong user authentication in Article 3(51) as authentication based on at least two independent factors from the categories of knowledge, possession and inherence. That definition closely tracks the strong customer authentication test that payment service providers already apply, which is why most EU banks, e-money institutions and payment institutions of any size should assume they are in scope.
Two limits matter. First, acceptance is required only upon the voluntary request of the user: a bank must offer the wallet as an option, not force customers onto it. Second, recital 15 says member states should not limit access to services for people who do not use a wallet and should make alternatives available, so existing onboarding journeys will need to run in parallel.
Registration comes before the first data request
Under Article 5b, any relying party that intends to rely on wallets must register in the member state where it is established. The registration must include the firm’s name and registration number, its contact details and the intended use of the wallet, including an indication of the data it will request from users.
That last point is binding. Article 5b(3) states that relying parties shall not request any data other than what they registered. Member states must publish the registration information online in a machine-readable, signed or sealed form, and firms must notify changes without delay. Article 5b(10) adds that intermediaries acting on behalf of relying parties, such as identity verification vendors, are treated as relying parties and must not store data about the content of the transaction.
For compliance teams, this turns data minimisation from a policy statement into a registered, publicly visible scope. A bank that later wants to collect an extra attribute through the wallet will need to update its registration first.
What the wallet actually hands over at onboarding
Implementing Regulation 2024/2977 sets out the person identification data (PID) that member states issue into wallets. For natural persons, the mandatory attributes include family name, given name, date of birth and nationality, together with technical fields such as the expiry date and the issuing country. Residential address, portrait, email address and mobile number are optional, so banks cannot assume every wallet will carry an address.
PID must be issued in two formats: the format specified in ISO/IEC 18013-5:2021 and the W3C Verifiable Credentials Data Model 1.1. Recital 62 of eIDAS 2 says wallets and attestations of attributes should help the financial sector meet customer due diligence requirements and support strong customer authentication for account login and the initiation of payment transactions.
Under Article 5b(9), the relying party remains responsible for authenticating and validating the PID and attestations it requests. Revocation is built in: Article 5 of the implementing regulation requires PID providers to publish validity status, to tell users within 24 hours when their PID has been revoked, and to ensure revocations cannot be reversed. A bank’s onboarding flow therefore needs a live status check, not just a one-time signature check.
Where the EU Digital Identity Wallet fits in KYC and fraud controls
The wallet is designed around selective disclosure: users can share only the attributes a service needs, and a built-in dashboard logs every relying party they have shared data with. For banks, that means requesting a defined attribute set rather than an image of a passport and a selfie, and accepting that customers will be able to see and query exactly what was taken.
The practical gains sit in remote onboarding, where document fraud and synthetic identities remain a cost, as covered in Fintechly’s analysis of digital identity verification as banks’ fraud battleground. Government-issued PID bound to a certified wallet gives a stronger starting point than a photographed document. It does not replace ongoing due diligence, sanctions screening or the event-driven reviews described in our explainer on perpetual KYC.
Firms should also plan for pseudonyms. Article 5b(9) bars relying parties from refusing pseudonyms where Union or national law does not require identification. Regulated account opening does require identification, but marketing, product browsing and some non-regulated services may not, and those journeys will need separate logic.
EU Digital Identity Wallet FAQs
Does a bank have to use the EUDI wallet for payment authentication as well as onboarding?
Article 5f(2) requires acceptance of the wallet where strong user authentication is used for online identification. Recital 62 says the wallet should support strong customer authentication for account login and payment initiation, but the binding obligation in the article is framed around identification. Banks should treat login and onboarding as the core scope and monitor further guidance on payment authorisation.
Can a bank stop offering its existing onboarding methods once it accepts the wallet?
Acceptance under Article 5f(2) applies only upon the voluntary request of the user. Recital 15 says member states should not restrict access to services for people who choose not to use a wallet and should make alternatives available. A bank should therefore keep at least one non-wallet route open.
Are small fintechs exempt from the acceptance duty?
Yes, Article 5f(2) exempts microenterprises and small enterprises as defined in Commission Recommendation 2003/361/EC. A small firm that chooses to accept the wallet voluntarily must still register as a relying party under Article 5b.
Can a bank ask for more data than it registered?
No. Article 5b(3) states that relying parties shall not request users to provide any data other than the data indicated in their registration. If a product needs additional attributes, the bank must update its registration, and Article 5b(6) requires changes to be notified without delay.
Does using an identity verification vendor shift responsibility away from the bank?
Article 5b(10) treats intermediaries acting on behalf of relying parties as relying parties themselves and prohibits them from storing data about the content of the transaction. Article 5b(9) keeps responsibility for authenticating and validating the data with the relying party. Vendor contracts should reflect both duties.
The EU Digital Identity Wallet gives banks and fintechs roughly a year between national wallet launches and their own acceptance deadline, and the work is mostly in registration, attribute mapping, status checking and parallel journeys rather than in the wallet itself. Firms that also serve UK customers should watch the separate approach there, set out in Fintechly’s coverage of the UK banking-app identity pilot, since a single onboarding stack will need to handle both.