Raidiam Delivers an Operational Trust Registry for the EUDI Wallet in the WE BUILD Pilot

Raidiam has delivered what it believes to be the first operational Trust Registry for the European Digital Identity (EUDI) Wallet, within WE BUILD, one of the EU's large-scale pilots.

Built with consortium partners, the Registry is live and ready to support payment and business-identity journeys as the implementation phase begins for the pilot's use cases. It was operational well before that. It is not a specification or product demonstration: it is a real, running Trust Registry deployed in the pilot.

What the EUDI Wallet is

The EUDI Wallet is Europe's framework for a personal (and, increasingly, business) digital identity wallet, established under the revised eIDAS regulation, commonly known as eIDAS 2.

It is not one app for an entire continent. Each EU country is expected to provide at least one Wallet and national infrastructure, with those infrastructures designed to work together across borders under a shared legal framework, governance framework and set of harmonised technical standards.

The Wallet is also about more than proving identity. It is designed to support a broader digital-credential ecosystem, including driving licences, diplomas, company mandates, payment attestations and other verified credentials. Sectors can connect their own services and credentials to the same framework.

Cross-border interoperability is not an edge case. It is central to the EUDI model: a credential issued in one country must be recognised and trusted in another.

Built for interoperability from the start

Europe has seen what happens when a major digital ecosystem develops without a sufficiently consistent technical approach. Open banking created significant opportunities, but varying implementations across markets made interoperability more complex than it needed to be.

EUDI is designed differently. This time the rules come with a shared set of mandatory technical standards and conformance testing, coordinated through a common Architecture and Reference Framework, so interoperability is built in from the outset rather than left for countries, providers and intermediaries to solve later.

Why trust is essential

For the EUDI Wallet to work, participants need to be able to trust one another.

A Wallet needs to know whether an organisation requesting information is legitimate. A business needs to know whether a credential was issued by a genuine provider. And organisations across the ecosystem need to establish what they are authorised to do.

That is the role of trust infrastructure.

The challenge is operational as well as technical. As EUDI scales, national ecosystems will need to onboard, verify and govern relying parties numbering from the thousands into the tens of thousands per country, from banks and payment providers down to individual merchants. That population is not static but changes daily as organisations join, change status or leave.

A Registry is not a Trusted List

Member states already publish Trusted Lists of recognised providers under eIDAS. EUDI goes further.

National ecosystems will also need to manage registers of relying parties: the organisations authorised to request information from a Wallet. That means onboarding, verifying and governing a potentially large and constantly changing participant base.

Maintaining a Registry is therefore not the same as publishing a list. It requires an operational trust layer that keeps a large, constantly changing participant population current, enables them to establish their identity and makes their authorisation discoverable to the rest of the ecosystem.

This is one of the most significant implementation challenges facing national EUDI programmes.

There is no shortage of specifications describing how a Registry should work. The harder task is standing one up, connecting real participants and operating it within a live cross-border pilot. That is often where digital-identity programmes stall. It is exactly the part Raidiam has already done, in the pilot rather than on paper, and where practical experience matters most.

The Trust Registry Raidiam delivered

Raidiam provides the Wallet Relying Party Registry (referred to in this article as the Trust Registry).

Working within WE BUILD's Trust Infrastructure work package (WP4), Raidiam has provided the authoritative record within the pilot of relying parties: organisations approved to request data from Wallets. It holds their verified identity and the access credentials that allow Wallets to validate them at the point of interaction. It is where pilot participants register, are recognised and become able to take part.

The Trust Registry connects to the other components of the WE BUILD trust layer:

• Trusted Lists for organisations issuing credentials, certificates or Wallets
• A List of Trusted Lists that brings those lists together as an ecosystem trust anchor
• A Credential Catalogue that enables Wallets and verifiers to discover and assess credential types in circulation

Together, these components create a working trust layer for the WE BUILD pilot.

In the pilot, Raidiam operates the Wallet Relying Party Registry. The underlying platform, Raidiam Connect, provides the full set of components a Member State needs to run a national trust infrastructure: the relying-party Registry, Trusted Lists, and the Access and Registration Certificate Authorities that issue relying parties' access and registration certificates. The pilot exercises one part of a productised platform that can stand up the complete national trust layer, not a one-off build.

An EUDI Trust Registry that is genuinely operational (deployed, running and ready to support payment and business-identity journeys) provides practical proof of what a national-scale trust layer can look like.

“

We have been building and operating Trust Registries for years, and adopting these open standards early. This is the moment they become real. The distance between offering a Registry and standing up a live one that has onboarded real participants is exactly where these programmes stall.

Being first to have that running in a live pilot, ready for payment and business use cases, is a milestone for us, but more importantly it is a working template for what every country in Europe now has to build. And we are just getting started.

Łukasz Jaromin, Head of Standards and Product Strategy, Raidiam

Why this matters now

This is not a whitepaper exercise. EUDI is a binding European framework with implementation deadlines.

Every EU member state is expected to make a Wallet available to citizens by the end of 2026. From late 2027, regulated sectors (including banks, payment providers and organisations that require strong user authentication) must accept the Wallet when an individual chooses to use it.

The economic case is also substantial. The European Commission estimates that the proposed EU Business Wallet could save businesses at least €150 billion each year by reducing repeated identity checks, paperwork and compliance overhead.

Some countries will build national trust infrastructure themselves. Others will buy it through a system integrator. Many are still working through the approach. The external deadlines are fixed, but the harder clock is internal: an operational Registry has to be specified, built, connected to real participants and tested well before late 2027, which means the build decision is a 2026 decision, not a 2027 one.

WE BUILD demonstrates that a practical model now exists: a Trust Registry, Trusted Lists, a List of Trusted Lists and a Credential Catalogue operating together in a live pilot environment rather than only in theory.

Experience at scale

Operating trust infrastructure at scale is not new to Raidiam.

Raidiam provides trust infrastructure for open banking and open finance ecosystems in the United Kingdom, Brazil, the United Arab Emirates and Australia. That is the same operational track record that WE BUILD's Trust Infrastructure work package (WP4, led by DIGG) selected it to bring into the EUDI pilot. These ecosystems require participants to be onboarded, accredited and tested against shared rules at scale.

In Brazil's open finance ecosystem alone, Raidiam's infrastructure supports 740 financial institutions and around 60 million consumers. Raidiam went from being selected as the ecosystem's trust-infrastructure provider (2020) to a live first phase (2021): a national-scale trust layer in production in around a year. That ecosystem now processes more than 250 billion API calls a year. See the Open Finance Brasil case study.

Raidiam is active in the standards community, contributing within the OpenID Foundation to the foundational specifications that digital credentials increasingly rely on: OpenID Federation, OpenID for Verifiable Credential Issuance (OpenID4VCI) and OpenID for Verifiable Presentations (OpenID4VP), now adopted across the EUDI ecosystem.

One platform, many trust mechanisms: beyond Europe

EUDI is one ecosystem, but the trust problem is global. Different jurisdictions rely on different trust mechanisms. Raidiam Connect is a multi-trust-mechanism platform. The same trust registry can express and consume trust through whichever mechanism a jurisdiction requires: ETSI Trusted Lists (the EUDI baseline), OpenID Federation, and issuer trust lists such as VICAL for ISO mobile documents (mDL).

That is what makes cross-jurisdiction and global interoperability practical. Rather than locking a country into a single scheme, one platform can bridge ecosystems built on different trust frameworks, so a Member State's infrastructure stays interoperable not just across the EU, but with digital-identity ecosystems beyond Europe as the wider landscape converges. For a government planning past a single border, a multi-trust-mechanism trust registry is what protects that investment.

Why it was ready, and why you can move just as fast

The Registry did not have to be invented for the pilot. It runs on Raidiam Connect, a trust platform already operating in production across several national ecosystems, so the work in WE BUILD was to configure and adapt proven technology to the EUDI context, not to build a trust layer from first principles. That is why it was operational well before the implementation phase reached it: what we contributed to the pilot was working, tested software, not a design on paper.

The same logic is what makes this repeatable. Because the platform is productised and already battle-tested elsewhere, the route to a live national trust layer is adopt-and-adapt, measured in months, not a multi-year build. The pilot is the proof; the technology is already here for any Member State or integrator that needs it.

What this means for governments and integrators

Governments, national digital-identity programmes and systems integrators face a difficult, time-bound challenge: creating trust infrastructure that can onboard and manage a large number of participants while supporting secure, interoperable services across borders. The window to choose build-vs-adopt is narrowing faster than the headline dates suggest, because delivery lead time, not the deadline, sets the real start date.

Raidiam's WE BUILD work is a productised, proven starting point: rather than build an operational Trust Registry from scratch, carrying the specification, integration and operational risk that stalls programmes, they can adopt a model already running in the EUDI pilot and adapt it to national or sector-specific requirements. That is the difference between adapting in months and building over years.

Raidiam will continue its work in WE BUILD, focused on payment and business-identity use cases, and on aligning the Wallet ecosystem with the proposed EU Business Wallet.

What's next

Raidiam discussed the move from Trust Registry definition to practical, national-scale implementation at the Global Digital Collaboration 2026 conference in Geneva.

Łukasz Jaromin spoke on the panel, "Trust Infrastructure for the EUDI Wallet: From Definition to Piloting to Reality," alongside leaders working across the WE BUILD and APTITUDE large-scale pilots. The session explored how Trust Registries, Trusted Lists, access certificates and Credential Catalogues fit together, along with the practical lessons emerging as the EUDI ecosystem moves into implementation.