The European Digital Identity Wallet will let every EU citizen prove who they are with their phone — and banks will be required to accept it. We help you get ready: from regulatory readiness to a working integration in your onboarding and KYC.
From the team that created BankID.cz, the Czech bank identity.
The European Digital Identity Wallet (EUDI Wallet) is a mobile app that every EU member state must offer its citizens under the revised eIDAS Regulation (EU) 2024/1183, known as eIDAS 2.0.
It holds verified person identification data (PID) and other attestations — such as a driving licence, diploma or proof of address. Users decide what to share, can disclose only selected attributes, and can create qualified electronic signatures.
For banks it is a new, government-backed way to identify customers remotely, authenticate them and let them sign — usable across all EU countries.
Deadlines follow from the regulation and its implementing acts. Exact dates may differ per country — we track them for you.
Regulation (EU) 2024/1183 sets the legal basis for the EUDI Wallet.
Every member state must offer at least one EUDI Wallet to its citizens.
New EU anti-money-laundering rules recognise electronic identification, including the wallet, for customer due diligence.
Regulated institutions that must use strong customer authentication have to accept the wallet when a customer chooses to use it.
Accepting the wallet is not just another login button. It touches six areas of your bank.
Register with the national authority, declare which data you will request and why, and obtain the certificates the wallet uses to recognise you.
Add the wallet as an onboarding channel next to bank identity, video identification or branch visits — without breaking conversion.
Check which wallet attributes satisfy your customer due diligence rules under national law and AMLR — and what you still need to collect.
Implement wallet protocols and credential formats defined in the EU Architecture and Reference Framework, such as OpenID4VP, SD-JWT VC and ISO mdoc.
Decide where the wallet is used for login, transaction confirmation and qualified electronic signatures — and how it fits with your SCA.
Cover new ICT risks, vendor dependencies and monitoring, and prepare support processes for customers using the wallet.
Bank identity is trusted and used every day. The EUDI Wallet adds a cross-border, government-issued identity that customers carry everywhere. The two will coexist — and banks that are identity providers today need a clear strategy for both.
We created BankID.cz, so we know the bank identity model from the inside. That lets us help you answer the questions that matter: where the wallet replaces existing channels, where bank identity stays stronger, and how to position your bank as both a relying party and an identity provider.
Start with a clear picture, then deliver — as a part of your project or end to end.
Gap analysis across onboarding, KYC, architecture and compliance. You get a prioritised roadmap and a business case for management.
Target processes, relying-party architecture, vendor choice and the legal framework — agreed with your business, IT and compliance teams.
Agile implementation, testing with wallet test environments and a controlled pilot before the obligation applies.
25 questions to check where your bank stands — onboarding, KYC, architecture, security and compliance.
Yes. Under eIDAS 2.0, private relying parties that are required by law to use strong user authentication — which includes banks and other financial institutions — must accept the EUDI Wallet when the customer chooses to use it. The obligation is expected to apply from the end of 2027.
Yes. The wallet provides verified person identification data at a high level of assurance. The EU anti-money-laundering regulation (AMLR) recognises electronic identification means under eIDAS for customer due diligence. Banks still need to map wallet data to their own KYC requirements.
A relying party is any organisation that requests data from the wallet — for example a bank verifying a new customer. Relying parties must register in their member state and state which data they request and for what purpose.
Not by itself. Bank identity schemes are widely used and trusted. The two are likely to coexist, and banks will need a strategy for both — as relying parties and, in some cases, as identity providers.
The EU Architecture and Reference Framework (ARF) defines the technical basis, including OpenID for Verifiable Presentations (OpenID4VP), SD-JWT verifiable credentials and the ISO/IEC 18013-5 mdoc format.
Yes. The wallet supports qualified electronic signatures, which have the same legal effect as a handwritten signature across the EU.
Now. Registration, process changes, KYC mapping, integration and testing typically span several budget cycles. Banks that start early can also use the wallet as a competitive onboarding channel, not just a compliance task.
Talk to the team that built BankID.cz. One call is enough to see where you stand.