EUDI Wallet readiness for Irish businesses
Ireland’s Government Digital Wallet is still moving through testing, legislation and EU implementation. Businesses can map their use cases and architecture now without pretending the final Irish onboarding process already exists.
The State must provide an EUDI Wallet under the EU framework. The Irish Government says public-body acceptance is due to commence by the end of 2026 and acceptance by certain private providers using strong customer authentication is due by the end of 2027. Registration, certificates and sector-specific obligations require current professional review.
A staged readiness model
| Stage | Work that can be done now | Evidence required before advancing |
|---|---|---|
| 1. Governance | Name the accountable entity, service decision, legal/status owner and cross-functional team. | Approved use-case statement and responsibility map. |
| 2. Attributes | Define the minimum PID or attestation fields and why each is necessary. | Purpose and data-minimisation record. |
| 3. Registration | Prepare entity, contact, intended-use and requested-data information. | Current official Irish registration procedure when published. |
| 4. Architecture | Map issuer, wallet, verifier, trust, status, logs and fallback. | Selected profiles, integration design and threat model. |
| 5. User journey | Design same/cross-device requests, clear purpose, errors and alternatives. | Accessibility, privacy and representative-user review. |
| 6. Assurance | Set protocol, trust, conformance, security and operational tests. | Production-scoped evidence and resolved material gaps. |
| 7. Pilot and operations | Predefine metrics, incidents, support, change and stop conditions. | Controlled pilot results and accountable go/no-go decision. |
Readiness checklist
-
Name the transaction
Document exactly why identity or an attribute is requested, the assurance level needed and the lawful basis for processing.
-
Minimise the request
Ask whether an “over 18”, licence-status or professional-qualification proof can replace a full identity-document copy.
-
Map the relying-party role
Identify each legal entity, application and domain that may request credentials. The EU architecture includes registration and relying-party access certificates.
-
Separate current IDV from future wallet support
Require suppliers to state which functions work today and which depend on unfinished national or EU infrastructure.
-
Design fallback and support
Document what happens when a person has no compatible wallet, device or credential and how contested results are reviewed.
-
Prepare evidence
Maintain data-flow diagrams, retention rules, processor terms, security controls, accessibility tests and change logs.
What remains implementation-dependent
The EU framework establishes relying-party registration and declared data use. Irish organisations should not invent the responsible Irish register, operational portal, certificate process or sector evidence requirements. Track official publication and treat supplier roadmaps as claims until the relevant production capability can be tested.
Map the roles
Issuer, wallet, PID, attestation, relying-party and assurance responsibilities.
Track registration
What Article 5b establishes and which Irish details remain open.
Design the journey
Consent, selective disclosure, error states, fallback and accessibility.
Questions for suppliers
- Which OpenID4VP, OpenID4VCI and ISO mobile-document profiles are supported today?
- Who is the processor or controller for each step?
- What is retained after a successful or failed presentation?
- How are wallet, certificate and trust-list changes handled?
- Can the integration request only the minimum attribute?
- What independent certification or audit evidence is available?
Primary references
In this topic: EUDI Wallet readiness
What should an Irish relying party prepare now?