EU-27 EUDI Wallet & WRPAC Status, Late May 2026: Who's Testable, Who's Only Announced

Every EU-27 table you will find in the wild answers one question: is the wallet testable yet? That question matters, but it is the wrong stopping point for a relying party thinking about cross-border verification. The question that follows is sharper and, as of late May 2026, has a more uncomfortable answer: is there a public, verifiable path for a wallet-relying party access certificate — a WRPAC — in that country?

This post adds that second column.

The short version: the first column varies by country. The second column is uniform across all 27. No Member State has a publicly verifiable, production WRPAC path. Not Germany, not France, not Italy. The EU-wide WRPAC trusted-entity list infrastructure exists at the eIDAS Dashboard, but as of 28 May 2026 the endpoint checkIfListIsPublished/WRPAC returns false and the provider list URL returns HTTP 403. That is not an oversight — the list is simply not published yet. The December 2026 obligations have not yet arrived.

Understanding why that is legally coherent, rather than alarming, is the difference between designing a correct EUDI Wallet integration and designing one that will have to be rebuilt.

Two questions per country

The April scorecard on this site assigned every Member State to one of four readiness tiers based on whether a citizen-grade wallet exists, whether a developer sandbox is open, and whether a credible launch date has been announced. That analysis remains valid.

This post asks two questions per country:

Question 1 — Is the wallet testable? Can a relying party or developer exercise an OpenID4VP or ISO/IEC 18013-5 flow today, even in sandbox conditions? This ranges from "yes, Germany has had an official public sandbox since December 2025" to "no, Bulgaria has a public code repository but no interactive test environment."

Question 2 — Is there a public WRPAC path? Has the Member State named a Wallet-Relying Party Access Certificate issuer, opened a national WRPAC registration portal, or published a CA chain that a cross-border relying party could anchor its certificate to? Article 7(1) of Implementing Regulation (EU) 2025/848 — in force since approximately 27 May 2025, with application from 24 December 2026 — assigns this authorisation obligation to Member States. The obligation applies from that application date, not merely because a wallet sandbox or national app exists earlier.

The answer to Question 2 is the same for every country in the table below: none public; EU WRPAC list unpublished.

That uniformity is not fabricated for rhetorical effect. It reflects the hard technical finding: the EU-wide WRPAC list infrastructure is built and the URL is known, but the list is not publicly served. Country-level WRPAC registration portals are not yet open anywhere that can be publicly verified. No Member State is early, no Member State is behind — the WRPAC authorisation clock starts when Regulation (EU) 2025/848 applies on 24 December 2026. The Article 5f acceptance obligations for regulated private relying parties and very large online platforms run on a separate, late-2027 timeline under Regulation (EU) 2024/1183.

The EU-27 table

The readiness column below is sourced from vendor and ecosystem trackers — specifically the eID Easy May 2026 snapshot and the iGrant EUDI Wallet Status Tracker, last updated 13 May 2026 — cross-checked where possible against official national pages. These are not official EU Commission status determinations. A tracker labelling something "production" frequently means an existing national identity app has been confirmed for EUDI upgrade, not that a certified Article 5a EUDI Wallet is live. The distinction matters and is discussed further in the section below.

The WRPAC column reflects the official eIDAS Dashboard API finding as of 28 May 2026 and public search. It is intentionally identical for every row.

The testable cluster

Across 27 rows, most entries fall into one of two practical categories: existing national app being upgraded, or announced project with nothing yet interactive. A smaller cluster is actually testable today.

Germany is the most structured entry point for a developer integrating against the EUDI Wallet. The Federal Government's official EUDI Wallet FAQ at eudi-wallet.gov.de confirms that an official public sandbox — managed under the SPRIND programme framework — has been available to relying parties since December 2025. The sandbox supports OpenID4VP flows and is the correct technical target for any developer planning a German integration. The important qualifier: what Germany has today is a testable sandbox, not the first production state wallet. The first state wallet version is planned for early 2027, according to the same official source. A relying party building against this sandbox today is building against the right protocol and the right credential structure, but they should not plan for production German wallet users before early 2027 at the earliest.

France has the France Identité developer playground and sandbox, with documented support for PID presentation in both proximity and online flows. The France Identité playground is the public entry point for verifier integration testing. What France has is a well-specified sandbox and an existing national identity app, not a full Article 5a EUDI Wallet in citizen hands. The distinction matters operationally: the playground is realistic enough for verifier integration work, but the broader citizen rollout to a fully certified EUDI Wallet remains ahead.

Denmark has AltID, with a public sandbox or staged rollout available according to ecosystem trackers. Developer access has been publicly discussed in the context of staged integrations.

Ireland has a Government Digital Wallet with announced early public or test access, placing it ahead of purely announced-only countries but behind France and Germany in terms of structured sandbox documentation.

This cluster — Germany with the most mature sandbox, France with the best-documented playground, and Denmark and Ireland with early access — is where a relying party doing integration work in mid-2026 should concentrate their test effort. The remaining 23 entries either have existing national apps that will eventually upgrade (Austria, Belgium, Greece, Italy, Poland, Slovakia, Spain) or announced projects with no public interactive environment yet (Bulgaria, Croatia, Czechia, Estonia, Finland, Latvia, Lithuania, Malta, Romania, Slovenia, Sweden). Building against announced-only countries in mid-2026 is premature at the protocol level because there is nothing to build against. Building against Germany and France is not premature — it is the only credible preparation path for the December 2026 deadline.

The honest caveat on tracker data

The readiness column in this table is the best public-source picture available in late May 2026. It is not official EU status, and the gap between tracker labels and actual EUDI Wallet certification status is significant enough to note explicitly.

The iGrant tracker reports 19 jurisdictions in "production or public pilot" as of its 13 May 2026 update, out of 32 jurisdictions tracked (including non-EU candidates). That figure is interpretively generous: a country like Italy, where the mIT-Wallet / IT-Wallet app is in citizen hands and is the single most important real-world verifier target today, is legitimately "production" from a practical integration standpoint. A country where an existing national eID app has been confirmed for EUDI upgrade but where the upgrade has not yet shipped, and where the app does not yet implement the EUDI technical specifications, is not "production" in any sense meaningful to a cross-border verifier.

The eID Easy May 2026 snapshot is more conservative and more useful for planning: it distinguishes between countries where a public sandbox exists (and therefore developer integration is possible today) and countries where the only evidence is an official confirmation that an upgrade is coming. That distinction — testable now versus confirmed for later — is the one that actually determines your Q3/Q4 2026 development roadmap.

Neither tracker says anything about WRPAC. That is not a gap in their coverage — it reflects that there is no publicly verifiable production WRPAC status to report. No country has published a WRPAC provider, opened a national WRPAC registration portal, or named a CA chain for relying-party access certificates in any publicly verifiable way. eID Easy's announcement of French and German EUDIW sandbox access through its own platform in May 2026 is a vendor/platform integration offering, not an official WRPAC licence or certificate pathway.

The one shared truth across all 27 countries

For a cross-border relying party, the uniform WRPAC answer resolves one architectural question clearly: you cannot build a WRPAC-anchored certificate chain today for any Member State, because no Member State has published one.

What you can build — and what the entire testable cluster is already running — is protocol-layer integration. OpenID4VP is the presentation layer across all EUDI Wallet implementations. SD-JWT VC and ISO/IEC 18013-5 mdoc are the two credential formats in active use, with France emphasising SD-JWT and Germany and Italy leading with mdoc. A single OpenID4VP verifier endpoint, a per-country trust list resolver configured to watch the eIDAS Dashboard for list publication events, and a credential parser handling both formats: that is the architecture that absorbs per-country variation as configuration rather than re-implementation.

The WRPAC layer slots in on top of that protocol core once Member States publish their CA chains and WRPAC registration portals go live. Building the protocol layer now and deferring WRPAC anchor setup until the list is published is the correct sequencing. It is not a shortcut — it is the only technically available path.

For more on how production WRPAC certification differs from sandbox access, see Real production WRPAC vs. sandbox certificate. For the legal background on why the published provider list is the specific threshold that matters, see No published WRPAC provider list yet.

The implementing regulation governing WRPAC obligations is Regulation (EU) 2025/848, which entered into force approximately 27 May 2025 and applies from 24 December 2026. The wallet deployment obligation itself runs under Regulation (EU) 2024/1183, with the same 24 December 2026 deadline for Member State availability. Both deadlines are still seven months away from this writing. The current state — no published WRPAC list, most wallets pre-launch — is precisely what the regulatory calendar predicts.

What to watch

The table in this post will change. The specific events that should trigger a re-read of your integration plan are as follows.

The most consequential single event will be the eIDAS Dashboard WRPAC flag flipping from false to true. That is the moment the EU-wide trusted provider list becomes publicly served. Once it does, any relying party planning to present wallet-verified credentials in production needs to anchor their access certificate to a WRPAC-listed provider in the Member State where they are established. Checking the official API endpoint — https://eidas.ec.europa.eu/efda/api/v2/wallet/lists-of-trusted-entities/checkIfListIsPublished/WRPAC — costs a single HTTP call and should be on any integration team's monitoring checklist.

The second event class is a Member State naming a WRPAC-issuing CA. No such announcement has been publicly made anywhere in the EU as of this writing. The first country to do this — whether it is a qualified trust service provider being mandated, a new national body being stood up, or an existing national CA expanding its scope — will be the first concrete data point for what a WRPAC certificate path actually looks like in practice. Germany's SPRIND programme and France's France Identité governance structure are high-signal ecosystems to monitor, but that is observation rather than a prediction.

Third: watch for any Member State opening a national relying-party registration portal. Even before the EU-wide list is published, a Member State could publish a national register or registration process for wallet relying parties. Luxembourg, which has an active national EUDI Wallet programme through MinDigital/CTIE and existing qualified trust service actors including LuxTrust, has the institutional infrastructure to do this — but no such portal has been found as of this writing.

Until one of those three events occurs, the integration roadmap is the same for all 27 countries: build to the protocol layer, test against the testable cluster, and monitor the dashboard flag.

Related Articles

No EU Country Has a Published WRPAC Provider List Yet — What It Means for Your December 2026 Deadline

As of late May 2026 the official EU trusted-entity lists are not published: the eIDAS Dashboard reports WRPAC as unpublished and the providers list is not publicly served. Here is why that is by design, and what it changes for your December 2026 planning.

8 min read

EUDI Wallet Rollout Status by Member State — April 2026

EU Digital Identity Wallet readiness across all 27 member states. Who has a live wallet, who has a public sandbox, who is still behind, and when you can verify customers from each country.

11 min read