EUDI Wallet Readiness Checklist
Last updated: July 2026
The EUDI Wallet Readiness Checklist is a free 20-question self-assessment for banks and other regulated businesses preparing for mandatory EUDI Wallet acceptance.
It covers 6 readiness areas - Strategic Readiness, Customer Experience, Technology & Integration, Orchestration & Fallback, Compliance & Risk, and Future Scalability - with a scoring guide that tells you whether your organisation is Operationally Ready, In Progress, or Not Ready.
The context: all 27 EU member states must provide a certified EUDI Wallet by December 24, 2026. The acceptance mandate for banks, payment providers, telecoms and other regulated sectors follows by December 2027.
The checklist exists to surface the gaps before those deadlines do.
What does the checklist cover?
The checklist has 20 questions across 6 readiness areas. Regulatory status current as of July 2026. Each question carries a risk score: HIGH (15 questions) means regulatory exposure or significant operational failure if ignored, MEDIUM (5 questions) means a meaningful gap that creates friction or delay.
The questions are deliberately architectural rather than box-ticking. Reading a PID credential from one wallet is the easy part. The checklist probes what happens when wallet authentication fails, when a customer presents a credential issued in another member state, and when the wallet you integrated does not support the same protocol as the next one.
Strategic Readiness
# | Risk | Question |
|---|---|---|
1 | MEDIUM | Has the organisation defined a position on EUDI Wallet adoption - not just as a compliance requirement, but as a customer experience and competitive opportunity? |
2 | HIGH | Is eIDAS 2.0 alignment formally part of the organisation's roadmap for 2026/2027, with ownership assigned, resources and a timeline in place? |
3 | MEDIUM | Has the organisation identified which customer journeys - onboarding, re-verification, cross-border authentication, payments authorization - are most likely to be affected first? |
4 | HIGH | Has the organisation made a strategic decision regarding the implementation of credential issuing components for EUDI Wallets for certain credentials, such as SCA? |
Customer Experience
# | Risk | Question |
|---|---|---|
5 | HIGH | Has the organisation accounted for different user journeys in its implementation, depending on whether a given wallet supports the Digital Credentials API or only OpenID for Verifiable Presentations (OID4VP)? |
6 | HIGH | Is there a defined fallback path for customers who do not yet have an EUDI Wallet, including non-EU customers and those in markets where rollout is delayed? |
7 | HIGH | Has the organisation assessed the impact of regulatory updates on the user journey within processes involving Strong Customer Authentication (SCA) for payment transaction authorization? |
Technology & Integration
# | Risk | Question |
|---|---|---|
8 | HIGH | Is the customer-facing interface ready to handle wallet-based credential presentation, both online and in person (proximity verification)? |
9 | HIGH | Can the current identity infrastructure ingest and validate wallet-based credentials, or would this require significant re-architecture? |
10 | MEDIUM | Is the system designed to support the simultaneous presentation of multiple credentials (so-called combined presentation)? |
11 | HIGH | Has the organisation conducted a comprehensive assessment of its systems architecture to embed wallet-based credential services, encompassing not only customer KYC, but also payment authorization processes (SCA)? |
12 | HIGH | Has the organisation analyzed which elements of their data architecture and core systems will require the most extensive redefinition to support the data minimization requirement (i.e., selective disclosure) and the absence of traditional identity documents following the eIDAS 2.0 implementation? |
13 | HIGH | Has the organisation started adapting its systems to support reading credentials from the new eIDAS 2.0-compliant wallets? |
Technology and integration carries the most questions because it is where readiness usually breaks.
Orchestration & Fallback
# | Risk | Question |
|---|---|---|
14 | MEDIUM | Is the organisation prepared to handle wallet credentials alongside existing methods - national eIDs, bank-based identity, biometrics, and document verification - within a single onboarding flow? |
15 | MEDIUM | Does the architecture support intelligent routing: selecting the most appropriate identity method based on customer context, jurisdiction, assurance level, and wallet credentials availability? |
16 | HIGH | Does the architecture support the case where wallet authentication fails - due to reasons such as credential expiration? Has a fallback sequence been defined for this scenario? |
Compliance & Risk
# | Risk | Question |
|---|---|---|
17 | HIGH | Has the compliance team assessed how wallet-based PID (Person Identification Data) maps to existing KYC and AML requirements, including standards under AMLR and EBA guidelines? |
18 | HIGH | Is there a defined process for handling selective disclosure - where a customer shares only a subset of wallet attributes - and verifying that the disclosed data meets the compliance obligation? |
19 | HIGH | Has the organisation assessed cross-border risk: what happens when a customer presents a credential issued by a member state different from the organisation's domicile - will the organisation have the technical capability to process it correctly? |
Future Scalability
# | Risk | Question |
|---|---|---|
20 | HIGH | Has the organisation's solution factored in potential implementation discrepancies in wallet processing (e.g., protocol differences) to guarantee interoperability and broad credential acceptance across state-issued, private, and BigTech wallets (a multi-wallet ecosystem) without a full rebuild? |
What does EUDI Wallet readiness involve for regulated organisations?
EUDI Wallet readiness for a regulated business means being able to accept a wallet credential when a customer presents one, and to serve every customer who cannot. It spans 6 areas: strategic ownership, customer experience, technology and integration, orchestration and fallback, compliance and risk, and future scalability.
The common failure is treating it as a single integration project. All 27 member states must provide a certified wallet by 24 December 2026, and the private sector acceptance mandate follows in late 2027. Between those dates most customers will still arrive without a wallet, which is why fallback appears in the checklist as a readiness requirement rather than an optimisation.
The two areas organisations most often underestimate are protocol fragmentation - not every wallet supports the same presentation method - and cross-border processing, where a credential issued in one member state has to be validated by an organisation domiciled in another.
How is it scored?
Count your completed answers per risk level and compare against three thresholds: Operationally Ready (13-15 HIGH and 4-5 MEDIUM completed), In Progress - act now (9-12 HIGH), or Not Ready - immediate action (8 or fewer HIGH).
The scoring is intentionally strict: most HIGH questions map directly to the acceptance mandate, so an incomplete answer usually means a compliance gap, not a nice-to-have.
Who is the checklist for?
Any organisation covered by the eIDAS 2.0 acceptance mandate: banks, payment providers, telecoms, and other regulated businesses that must be able to process an EUDI Wallet credential when a customer presents one.
It is written for the people who own that problem - compliance leads, identity and onboarding product owners, and the engineering teams who will build or buy the integration.
It pairs with our analysis of the simplest way to implement the EUDI Wallet, which argues that the right question is not how to connect one wallet, but how to be ready for all 27. Denmark's AltID launch shows why the fallback questions matter in practice: a live EUDI Wallet operating alongside the existing MitID system, with both arriving in the same onboarding flow.
Authologic connects the EUDI Wallet alongside national eIDs, government wallets and BankIDs through one API, so the orchestration and fallback questions in the checklist have a concrete implementation path.
How can organisations assess their readiness for the EUDI Wallet?
Run the 20 questions as a single cross-functional session with compliance, product and engineering in the room, then count completed answers against the thresholds above. Circulating the checklist by email tends to produce optimistic answers, because no single function can see all 6 areas. Compliance rarely knows whether the architecture supports fallback; engineering rarely knows what AMLR requires of the evidence trail.
FAQ: EUDI Wallet Readiness Checklist
Is the checklist free?
Yes. The PDF is a direct download with no signup, form, or email gate.
How long does the self-assessment take?
Around 30-60 minutes if the right people are in the room. Most questions require input from compliance, product, and engineering, so the fastest path is running it as a single cross-functional session rather than circulating it by email.
Does the checklist cover AMLR compliance?
Partially. One section maps wallet-based PID to KYC and AML requirements, including standards under AMLR and EBA guidelines. AMLR applies from July 2027 and is a separate regulation from eIDAS 2.0; the checklist flags the overlap but is not a full AMLR readiness assessment. For that, use the SCA & AMLR Readiness Checklist - a free 32-question self-assessment covering both regimes.
Is the checklist legal advice?
No. It is a self-assessment tool reflecting the regulatory status as of the date shown in the document. For binding interpretation of eIDAS 2.0 or AMLR obligations, consult your legal team.
Will the checklist be updated?
Yes. The document states the regulatory status date on its first page, and the page changelog records each revision. The download link always points to the current version.
Changelog
- July 30, 2026 - Full 20-question checklist published on page.
- July 28, 2026 - FAQ updated with a link to the SCA & AMLR Readiness Checklist.
- July 23, 2026 - Initial publication of the generalised version for regulated businesses (20 questions, 6 readiness areas, scoring guide).
Share article
Press Contacts
Dominika Cepek
dominika.cepek@authologic.comAuthologic
contact@authologic.com
