EUDI Wallet for Irish businesses — getting ready for 2027
Under the eIDAS 2.0 regulation, private-sector providers in Ireland that perform strong customer authentication or KYC will be required to accept EUDI Wallet credentials by the end of 2027. That's a substantial integration project for many businesses — banks, payment service providers, telecoms, qualified trust services, and (depending on legislative implementation) several other regulated sectors. This page is for the people who have to plan it.
Who has to accept the wallet, and when
| Sector | When acceptance is mandatory | What that actually means |
|---|---|---|
| Public-sector services (state departments, agencies, local authorities) | End of 2026 | Must accept wallet credentials for identification where the service requires identity verification. |
| Banks (full-service deposit-taking) | End of 2027 | Must accept wallet credentials for KYC at account opening AND for strong customer authentication under PSD2. |
| Payment service providers (PSPs) | End of 2027 | Same — wallet credentials accepted for SCA-required transactions. |
| Qualified trust service providers (eIDAS) | End of 2027 | Must accept wallet identity attributes when issuing qualified certificates and similar. |
| Telecoms (mobile, fixed-line, broadband) | End of 2027 | Phased — applies to services requiring SCA, including SIM activation in some cases. |
| Other regulated sectors | Member-state dependent | Some sectors (e.g. age-restricted retail, gambling) may add wallet acceptance via national legislation. |
What changes practically
Most Irish businesses are not building identity verification from scratch. They use a vendor (Yoti, Persona, Veriff, OneID, Onfido, Jumio, Trulioo, Mitek and others). The practical question is therefore not "how do I implement EUDI Wallet" but "does my vendor have an EUDI roadmap that covers my use case, and how do I integrate".
The vendor-readiness conversation
Five questions to ask your existing identity-verification vendor today:
Is your EUDI Wallet integration on roadmap, in beta, or in production?
Vendors vary widely. Some have public roadmaps with dates. Others are vague. Specifics matter.
Which credential types from the wallet will you support at launch?
Identity attributes (PID), the mobile driving licence (mDL), educational credentials, qualified electronic signatures — each is a separate integration. Confirm which apply to your use cases.
How does the integration map to our existing flow?
If your current flow asks for a document upload + selfie, the EUDI version asks the user to present a wallet credential. The UX is genuinely different. Plan for both flows running in parallel during transition.
What happens to credential retention?
Wallet credentials are typically asserted at the moment of verification, not retained. Your records will look different. Your DPO needs to know.
What's the fallback for users who don't have the wallet at the moment of verification?
Document-based verification will continue to coexist. Confirm your vendor maintains both.
What you (probably) need to do in-house
- Update your DPIA (Data Protection Impact Assessment) to cover wallet-based verification. The data flows are different and your DPC documentation will need to reflect it.
- Update your privacy notice to mention wallet credentials as a verification method.
- Update your KYC / SCA procedures internally. Front-line staff need to know what a wallet presentation looks like and how it differs from document-based.
- Update your audit logs. Wallet credential presentations create different audit-record shapes than document verifications.
- Update your fraud-detection rules. Wallet-based fraud will look different. Your fraud team should know.
What you probably do NOT need to do
- You probably do not need to integrate directly with the Irish EUDI Wallet API. Almost everyone will integrate via their existing verification vendor.
- You probably do not need to write your own credential issuance. The credentials are issued by member states; you accept them.
- You probably do not need to support every credential type. Only the ones your service needs.
Timing-sensitive considerations
The end-of-2027 deadline sounds far away. Three reasons to start in 2026:
- Vendor capacity is finite. Every regulated Irish business will be asking the same questions. The vendors who have done EU rollouts before will be busy. Earlier conversations get better outcomes.
- DPIA + privacy-notice updates take time. Your DPO and your legal team are involved. Multi-month process at most institutions.
- Internal procedure changes take time. Training, system updates, audit log changes, fraud-rule updates — none of these are quick.
The strategic question
For some businesses, the wallet is just a new credential format. For others, it's an opportunity to simplify a previously complicated onboarding. Three high-value strategic questions worth asking now:
- Can wallet-based verification reduce our drop-off rate at onboarding? The data from early rollouts in other EU member states suggests yes, materially.
- Can wallet-based verification reduce our cost per verified user? Probably, eventually. Less than the wallet evangelists claim; more than the wallet sceptics admit.
- Does wallet-based verification change our cross-border addressable market? A wallet from any EU member state is, in principle, accepted in every other. For Irish businesses with EU-wide ambitions this is a real opportunity.
How MyID can help
We publish updates as the EUDI Wallet timeline evolves — Government announcements, vendor roadmaps, sector-specific implementation notes. We also offer (small-scale) advisory engagements for businesses preparing for 2027 acceptance — contact /contact/.
Primary sources
- eIDAS 2.0 — EUR-Lex.
- Government Digital Wallet consultation — gov.ie.
- European Commission EUDI Architecture Reference Framework — eu-digital-identity-wallet.github.io.
Related
- EUDI Wallet hub
- EUDI Wallet vs MyGovID
- Online Safety Code — adjacent regulation arriving in the same window.