Solutions/EUDI Wallet
The trust registry for the EUDI Wallet.
By 24 December 2026, every Member State must run a register of every relying party and issuer that talks to an EUDI Wallet. Raidiam already runs one in the EU's WE BUILD pilot, on the infrastructure behind eight national trust frameworks.
Not another trusted list
A trusted list holds a few dozen providers. How do you register thousands of relying parties and issuers, issue each of them certificates recognised across the EU, and do it in time?
The national register, live sooner than you think
Wallets know whom they may talk to. The national register, one of the EU's federated registers, at the centre of the country's trust infrastructure.
National registries already running on our technology
Open finance in the UK, Brazil and the UAE. Now the EUDI Wallet, where a Wallet-Relying Party Registry runs in WE BUILD.
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 by portal or API
Remote registration by user interface or API, as the regulation asks. The required data set, identity checks, standard identifiers, every role. Agents use the same API.
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.
Every trust scheme, one record
Lists of trusted entities prepared for notification to the Commission. Sector lists and federations, X.509 chains, and OpenID Federation with trust marks, permitted only for non-qualified attestations.
Operated, not just installed
Audit trail, change history, suspension and cancellation, and health checks, on the platform behind eight national trust frameworks.
Not a form and a database
What does it take to keep a register running? A PKI, certificate lifecycle, signed publication, notification data and standards that keep moving. You keep the policy. The platform carries the rest.
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, in your name, on your domain.
Wallets · Verifiers
Read the register
Check certificates and the public register before they answer.
Feeding Raidiam Connect
Member State · Registrar
Owns the rules
Policy, vetting, entitlements, who may provide. Every decision stays yours, and so does your data if you leave.
Policy and decisionsConnect
CA · QTSP
Issues the certificates
Access certificates to talk to wallets, registration certificates to say what for. Both profiles still change. The built-in PKI keeps up; your CAs and QTSPs plug in.
CertificatesConnect
Path to production: compliance first, scale next
The sequence, not a schedule. Your procurement, policy and notification set the pace.
- 1
Your register, configured
Your national register, on your domain: flows, data sources, roles and entitlements.
- 2
Plugged into what you have
Your wallet test environment, eID infrastructure and the CA you choose.
- 3
Compliance go-live
Security review, your notification to the Commission, public API live, first parties registered.
- 4
Scale
Intermediaries in bulk, sector lists, every specification release.
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.
Lists of trusted entities
Your notifications to the Commission, compiled and ready to send.
Trusted lists and federation
For sectors and verifiersTrusted lists
Recognised providers, for a country or a sector scheme.
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.
Where will your ecosystem take you?
We have built a national registry in three months before.
See It in Action
See how one investment in Raidiam Connect covers your first use case, and the next hundred.
See the Proof
Brazil's participant directory: “live within three months of the contract being awarded” (Raidiam, 2021). Track record, not a forecast.
Have questions first?
Tell us about your ecosystem and we'll show you where Raidiam fits.