Solutions/EUDI Wallet
The trust registry for the EUDI Wallet.
By 24 December 2026, every Member State must publish a register of the organisations allowed to ask an EUDI Wallet for data. Raidiam already runs one in the EU's WE BUILD pilot, on the infrastructure behind eight national trust frameworks.
Trusted lists hold dozens. Your register must hold thousands.
A trusted list names a few dozen providers. The EUDI register has to check, certify and publish every bank, merchant and public body that asks a wallet for data, and keep that list current every day.
One registry. Three ways in.
No certificate, no answer from the wallet. No registration, no certificate. Whichever side you are on, it starts with the register.
Already running national registries.
Brazil, Australia, the UAE, New Zealand and the UK. Now the EU's EUDI Wallet pilot.
8
National trust frameworks on Raidiam infrastructure
ARF 3.0
Tracks ARF 3.0 and CIR 2026/1730
What the law asks.
What running it takes.
Raidiam Connect tracks ARF 3.0 and CIR 2026/1730, on the platform behind eight national trust frameworks.
Registration for people and machines
Portal, form or API. The Annex I data set, identity verification and every role the regulation names.
Access and registration certificates
Access certificates from your CA or QTSP. Registration certificates per service and intended use, with status lists and expiry alerts.
Intermediaries at scale
Where the registrar allows it, intermediaries onboard the parties they serve through the API, each mandate on file.
A public, machine-readable register
The common public API: no login, signed responses, rich filters. A human-readable site and open-data exports alongside.
Multi-trust-scheme by design
Reads the ETSI lists to verify entitlements. Publishes trusted lists, X.509 chains and OpenID Federation from the same record.
Operated, not just installed
Audit trail, change history, suspension and cancellation, and health checks, on the platform behind eight national trust frameworks.
Buy the platform. Keep the policy.
Raidiam runs the registry. Your registrar decides who is on it, and your CA issues what they carry.
Relying parties · Issuers
Register once
Directly, or through an intermediary acting for them, each mandate on file.
Raidiam Connect
Runs the registry
Registration, lifecycle, audit trail, the public API and every published format, under your brand and domain.
Wallets · Verifiers
Read the register
Check certificates and the public register before they answer.
Feeding Raidiam Connect
Member State · Registrar
Owns the rules
Registration policy, identity vetting, entitlements and approvals. Every decision stays yours.
Policy and approvalsConnect
CA · QTSP
Issues the certificates
Access certificates from your authorised CA. Registration certificates from it, or from Raidiam Connect as your provider.
CertificatesConnect
Sandbox in your name. Register in production.
- 1
Sandbox register
Your brand and domain on the platform behind the WE BUILD registry.
- 2
Your policy
Flows, data sources, roles and entitlements configured.
- 3
Your CA or QTSP
Authorised certificate providers connected.
- 4
Review and go-live
Security review, your notification to the Commission, first parties live.
- 5
Operate and evolve
Scale intermediaries and sectors. Keep pace with the specification.
One record. Every format.
Raidiam Connect holds each organisation once, with its services, intended uses and certificates, and publishes the register and every list from that record. Each wallet, verifier and regulator reads the format it understands.
Open a field to see where it is published
Participant record
Bank of Utopia PLC
Illustrative participant. Fields follow CIR 2025/848 Annex I.
Register once. Every wallet, verifier and regulator reads its own format.
Each party is held once. Raidiam Connect fills the Wallet Relying Party Registry from that record, and produces every list and certificate the ecosystem reads from it.
Raidiam Connect
One registry record
- Verified identity
- Roles and entitlements
- Services and intended uses
- Intermediary mandates
- Certificate status
Annex I data set · held once
EUDI-specific
MandatoryAccess certificate
What a wallet checks before it answers. Issued by your CA to registered parties only.
Registration certificate
One per service and intended use: which attributes the party may request.
Public register API
The common API every Member State publishes. Signed, searchable, no login.
Trusted lists and federation
For sectors and verifiersLists of trusted entities
Compiled for your notification to the Commission, or as a sector's trusted list.
OpenID Federation
Entity statements and trust marks. EUDI permits it for non-qualified attestations.
X.509 chains and issuer lists
PKI chains for any verifier, and issuer lists the ISO mDL world reads.
A deadline that leaves no time for a build. We have delivered a national registry in three months before.
Brazil's open finance participant directory went live within three months of the contract being awarded, and launched with 159 banks. It now serves 740 institutions.
Read how Raidiam did it“Live within three months of the contract being awarded” (Raidiam, 2021). Track record, not a forecast of EUDI demand.
3
Months from contract award to go-live
159
Banks at launch
740
Institutions on the directory today
One foundation. Multiple ecosystems.
The same control plane governs organisations, applications, APIs, credentials and AI agents. Start with one use case and expand into others without rebuilding trust infrastructure.
Where will your ecosystem take you?
Whether you're a regulator building a national digital economy, an enterprise platformising across brands and clouds, or a bank that wants to stop rebuilding trust for every new use case, there's a next step.
See It in Action
See how one investment in Raidiam Connect covers your first use case, and the next hundred.
See the Proof
Explore how governments, regulators and enterprises are using Raidiam to deliver trusted digital ecosystems.
Have questions first?
Tell us about your ecosystem and we'll show you where Raidiam fits.