Easit

Ecosystem

How the EUDI Wallet ecosystem fits together.

The Architecture and Reference Framework (ARF) defines several distinct roles around the wallet. This map shows how they connect — who issues what, how a presentation is requested and returned over OpenID4VP, and who certifies everyone involved.

issues PID provisions wallet issues attestations presentation request returns VP registration & access cert trust list trust list PID Provider issues Person ID Data Wallet Provider provides the wallet app (Q)EAA Provider issues attestations EUDI Wallet on the user's device Relying Party directly, or via an Intermediary National Registrar & Trust Framework registers & certifies ecosystem participants
Issuers provision the wallet, a Relying Party (or its Intermediary) exchanges an OpenID4VP request and response with it, and a national registrar issues the certificates and trust listings every party relies on.
Issuance / provisioning OpenID4VP exchange Registration & trust

The roles, briefly

PID Provider

Issues Person Identification Data into the wallet — the base identity credential everything else builds on.

(Q)EAA Provider

Issues (Qualified) Electronic Attestations of Attributes — credentials beyond core identity, such as diplomas or professional qualifications.

Wallet Provider

Builds and operates the wallet application the user installs and holds their credentials in.

EUDI Wallet

The user-controlled app that stores credentials and responds to presentation requests on the user's behalf.

Relying Party / Intermediary

Requests a presentation over OpenID4VP to verify something about the user — either directly, or through a registered intermediary.

National Registrar & Trust Framework

Registers Relying Parties, issues Registration and Access Certificates, and maintains the trust lists every party checks against.

Not sure where you fit in this picture?

Talk it through with us