A PID provider is the body a member state makes responsible for issuing and revoking Person Identification Data and for binding a user’s PID to their wallet unit. It verifies the user’s identity at assurance level high before issuing.
Legal termReviewed 7 October 2026
On the issuer side, where data is put into the wallet.
Issuer
Signs credentials: a member state, university, bank or employer
Issuance
EUDI Wallet
Belongs to the user, who decides what to share
Presentation
Relying party
The service that requests and checks the data
Trust layer: who is allowed to sign, and is it still valid?
Rules: the law and technical framework behind it all
The PID provider does the identity proofing that everyone else relies on. It checks who the user is, issues the PID into their wallet unit bound to a key held there, and keeps the ability to revoke it, for example when the data changes or the wallet unit is compromised.
It is not always the authority that holds the population register. A member state can designate an agency or another body, and it notifies the Commission which bodies act as PID providers so verifiers in other countries can trust them.
A relying party never contacts the PID provider during a presentation. It checks the provider’s signature against the trusted lists and checks the revocation status the provider publishes.
Defined in
Regulation (EU) 2024/1183 Art. 5a(5)(f) and 5a(18); Commission Implementing Regulations (EU) 2024/2977 and 2024/2980; ARF Annex 1
When you verify a PID you are relying on the PID provider’s identity proofing. Checking its signature against the trusted lists is what turns a set of attributes into a verified identity.
Authbound handles the protocols, formats, trust lists and revocation checks behind these terms. See what people build with them.
