EUDI Wallet glossary

A certificate for electronic seals or signatures with which a relying party authenticates itself to the wallet. Without a valid access certificate the wallet will not release any data. It is issued only to registered relying parties.

Reference: Implementing Regulation (EU) 2025/848, Art. 2(12), Art. 7Read more →See also: Registration certificate, Relying party, Trusted list

The technical framework for the EUDI Wallet agreed by the Commission and the member states: architecture, roles, flows and the standards to use. It is updated continuously on GitHub; only the implementing regulations are legally binding.

Reference: ARF on GitHubRead more →See also: eIDAS 2.0, OpenID for Verifiable Presentations, SD-JWT VC, mdoc (ISO/IEC 18013-5)

A single characteristic, right or permission of a person or an object – for example “over 18”, “holds a category B driving licence” or “student at University X”.

Reference: Regulation (EU) 2024/1183, Art. 3(43)See also: Electronic attestation of attributes, Selective disclosure

A register or system of a public or private body that is considered the primary source of certain information, such as population, driving licence or business registers. Attributes for the wallet can be verified against authentic sources.

Reference: Regulation (EU) 2024/1183, Art. 3(47)See also: Public-sector attestation of attributes, Attribute

Name of Germany’s government EUDI Wallet, presented by the Federal Ministry for Digital Transformation and Government Modernisation on 9 September 2026. Launch announced for 2 January 2027; the official FAQ says “early 2027”. Voluntary and free of charge.

Reference: eudi-wallet.gov.de, FAQSee also: EUDI Wallet, German Digital Identities Act, Wallet provider

An overview in the wallet of all transactions: which relying parties received which data. From there users can ask a relying party to erase their data and report suspicious requests to the data protection authority.

Reference: Regulation (EU) 2024/1183, Art. 5a(4)(d)See also: Relying party, Registration certificate

Common name for Regulation (EU) 2024/1183, which amends the 2014 eIDAS Regulation and introduces the EUDI Wallet. In force since 20 May 2024; details are set out in Commission implementing regulations.

Reference: Regulation (EU) 2024/1183 (EUR-Lex)Read more →See also: EUDI Wallet, Architecture and Reference Framework

An electronic credential for one or more attributes that can be verified, such as a driving licence, diploma or membership card. There are simple, qualified and public-sector attestations.

Reference: Regulation (EU) 2024/1183, Art. 3(44)See also: Attribute, Qualified electronic attestation of attributes, Public-sector attestation of attributes, Person identification data

A rule that the issuer embeds in a credential, specifying which relying parties may request it – for example only employers or certain sectors. The wallet evaluates the rule for each request and shows the result to the user.

Reference: Implementing Regulation (EU) 2024/2979, Art. 2(9), Art. 10, Annex IIISee also: Electronic attestation of attributes, Registration certificate

An app that lets citizens and businesses securely store their identity data and other credentials, share them selectively with online services or in person, and create qualified electronic signatures. Every EU member state must provide at least one such wallet; use is voluntary and free for citizens.

Reference: Regulation (EU) 2024/1183, Art. 3(42), Art. 5aRead more →See also: Person identification data, Electronic attestation of attributes, eIDAS 2.0, d-you

German act implementing the eIDAS wallet rules: responsibilities (including the Federal Office of Administration as registrar and the Federal Network Agency as supervisor), fees and acceptance in purely domestic cases. As of 12 October 2026: government bill (Bundestag printed paper 21/7408), not yet adopted.

Reference: Bundestag printed paper 21/7408See also: Registrar, d-you

OpenID Foundation profile that narrows the many options of OpenID4VCI and OpenID4VP and of the SD-JWT VC and mdoc formats to a fixed, secure selection, so wallets and relying parties from different vendors interoperate. Since Implementing Regulation (EU) 2026/1731, the basis of one of the two mandated presentation profiles.

Reference: OpenID Foundation: HAIPRead more →See also: OpenID for Verifiable Credential Issuance, OpenID for Verifiable Presentations, SD-JWT VC, mdoc (ISO/IEC 18013-5)

A service provider that interacts with the wallet on behalf of relying parties, such as an identity service. It is itself considered a relying party, must register and must not store the content of transactions.

Reference: Regulation (EU) 2024/1183, Art. 5b(10)See also: Relying party

The obligation to accept the EUDI Wallet for identification at the user’s request. It applies to public bodies and – from 24 December 2027 at the latest (calculated) – to private providers that require strong authentication by law or contract, such as banks, energy and telecoms providers, and to very large online platforms. Micro and small enterprises are exempt.

Reference: Regulation (EU) 2024/1183, Art. 5fRead more →See also: Strong user authentication, Relying party

Credential format and protocol from ISO/IEC 18013-5, originally for the mobile driving licence. Data is binary-encoded (CBOR) and individually disclosable; particularly suited to in-person presentation via NFC, Bluetooth or QR code. ISO/IEC 18013-7 adds online presentation. Mandated for PID and attestations; the only format for in-person presentation.

Reference: Implementing Regulation (EU) 2026/1731 (amending 2024/2977, 2024/2979, 2024/2982)Read more →See also: SD-JWT VC, Offline mode (proximity), Selective disclosure

Using the wallet at a physical location via close-proximity technology such as QR code, NFC or Bluetooth, without the wallet needing to reach remote servers – for example at a traffic stop or a supermarket checkout.

Reference: Regulation (EU) 2024/1183, Art. 3(57)See also: mdoc (ISO/IEC 18013-5)

OpenID Foundation protocol through which issuers deliver PID and credentials to the wallet. Built on OAuth 2.0; version 1.0 has been final since September 2025 and is mandated for the EUDI Wallet by Implementing Regulation (EU) 2026/1731.

Reference: OpenID Foundation: OpenID4VCIRead more →See also: OpenID for Verifiable Presentations, High Assurance Interoperability Profile

OpenID Foundation protocol with which a relying party requests data from the wallet and the wallet presents it – online in a browser or app, including via the browsers’ Digital Credentials API.

Reference: OpenID Foundation: OpenID4VPRead more →See also: OpenID for Verifiable Credential Issuance, High Assurance Interoperability Profile, Relying party

The official identity data set in the wallet, such as name, date of birth and nationality. It is issued under Union or national law and allows a person to be identified unambiguously – the digital counterpart of the ID card.

Reference: Regulation (EU) 2024/1183, Art. 3(3)See also: PID provider, Electronic attestation of attributes, EUDI Wallet

The body that issues and revokes person identification data and ensures that it is cryptographically bound to the user’s wallet, so copied data cannot be used on another device.

Reference: Implementing Regulation (EU) 2024/2977, Art. 2(4)See also: Person identification data, Wallet unit

The user’s facial image as part of the PID. Optional until 10 Aug 2028, mandatory from 11 Aug 2028 unless the member state provides an opt-out. The wallet warns before sharing biometric data; relying parties generally may not retain the image.

Reference: Implementing Regulation (EU) 2024/2977, Art. 3a and annex Table 1, inserted by 2026/1731Read more →See also: Person identification data, Selective disclosure

The wallet can generate a pseudonym for a service and store it encrypted on the device. This lets a service recognise a returning user without learning their identity. Relying parties must not refuse pseudonyms where identification is not legally required.

Reference: Regulation (EU) 2024/1183, Art. 5a(4)(b), Art. 5b(9)See also: Selective disclosure

An attestation of attributes issued by a public body responsible for an authentic source (or a body designated for this), for example a credential from an official register. Legally equivalent to a qualified attestation.

Reference: Regulation (EU) 2024/1183, Art. 3(46), Art. 45fSee also: Electronic attestation of attributes, Authentic source

An attestation of attributes issued by a qualified trust service provider that meets the requirements of Annex V of the eIDAS Regulation. It has the same legal effect as a lawfully issued paper attestation.

Reference: Regulation (EU) 2024/1183, Art. 3(45), Art. 45bSee also: Electronic attestation of attributes, Qualified trust service provider

An electronic signature with the same legal effect as a handwritten one. The EUDI Wallet must offer it by default and free of charge to citizens; member states may limit free use to non-professional purposes.

Reference: Regulation (EU) No 910/2014, Art. 3(12), Art. 25; Regulation (EU) 2024/1183, Art. 5a(5)(g)See also: Qualified trust service provider, EUDI Wallet

A trust service provider granted qualified status by the supervisory body, for example for qualified signatures or qualified attestations of attributes. It is listed in its member state’s trusted list.

Reference: Regulation (EU) No 910/2014, Art. 3(20)See also: Trust service, Trusted list, Qualified electronic attestation of attributes, Qualified electronic signature

A public directory in each member state listing all registered relying parties and the data they intend to request. From 24 December 2026 it is accessible without login via a common REST API and a website.

Reference: Implementing Regulation (EU) 2025/848, Art. 2(10), Art. 3, Annex IIRead more →See also: Registrar, Relying party, Registration certificate

The body designated by a member state to keep the register of relying parties, check registrations and suspend or revoke them in case of violations. In Germany, the draft Digital Identities Act assigns this role to the Federal Office of Administration (BVA) (as of 12 October 2026, not yet adopted).

Reference: Implementing Regulation (EU) 2025/848, Art. 2(14), Art. 6, Art. 9See also: Register of relying parties, German Digital Identities Act

A data object describing what a relying party uses the wallet for and which data it has registered for this purpose. The wallet can use it to check whether a request stays within the registered scope. Mandatory since amending Regulation (EU) 2026/1730.

Reference: Implementing Regulation (EU) 2025/848, Art. 2(15), Art. 8See also: Access certificate, Register of relying parties, Embedded disclosure policy

A company, authority or other organisation that requests data from the wallet to identify users or check credentials – for example a bank opening an account. Anyone who wants to rely on the wallet must first register in their member state.

Reference: Regulation (EU) 2024/1183, Art. 3(6), Art. 5bRead more →See also: Register of relying parties, Access certificate, Registration certificate, Intermediary

IETF standard (RFC 9901) for signed JSON Web Tokens from which the holder can omit individual claims without invalidating the signature. The basis for selective disclosure in the SD-JWT VC format.

Reference: IETF RFC 9901See also: SD-JWT VC, Selective disclosure

Credential format based on SD-JWT that defines how the issuer, type and validity of a credential are expressed. Since Implementing Regulation (EU) 2026/1731, one of the two mandated formats for PID and attestations alongside mdoc (profile: ETSI TS 119 472-1), mainly for online flows. Still an IETF draft (as of 12 October 2026).

Reference: IETF: SD-JWT-based Verifiable CredentialsRead more →See also: SD-JWT, mdoc (ISO/IEC 18013-5), Architecture and Reference Framework

Users share only the information a service actually needs – for example just “over 18” instead of the full ID with name, address and date of birth. The wallet must support this; technically it is provided by formats such as SD-JWT VC and mdoc.

Reference: Regulation (EU) 2024/1183, Art. 5a(4)(a)Read more →See also: SD-JWT, mdoc (ISO/IEC 18013-5), Attribute, Pseudonym

Authentication with at least two independent factors from different categories: knowledge (e.g. PIN), possession (e.g. smartphone) or inherence (e.g. fingerprint). Services that require it fall under mandatory acceptance.

Reference: Regulation (EU) 2024/1183, Art. 3(51)See also: Mandatory acceptance

IETF mechanism for revocation: the issuer publishes the status of many credentials as a compressed bit list (valid, revoked, suspended). Verifiers fetch the whole list, so the issuer does not learn which credential is being checked. Mandated for wallet attestations by Implementing Regulation (EU) 2026/1731; still an IETF draft (as of 12 October 2026).

Reference: IETF: Token Status ListRead more →See also: SD-JWT VC, Wallet unit attestation

A simple, recognisable sign showing that a wallet has been provided and certified under the eIDAS Regulation. It helps users tell genuine EUDI Wallets from imitations.

Reference: Regulation (EU) 2024/1183, Art. 3(50)See also: EUDI Wallet

An electronic service under the eIDAS Regulation, such as issuing certificates for signatures and seals, time stamps, electronic registered delivery, electronic archiving or issuing attestations of attributes.

Reference: Regulation (EU) 2024/1183, Art. 3(16)See also: Qualified trust service provider, Trusted list

An official machine-readable list per member state of qualified trust service providers and their services. For the wallet, the Commission additionally publishes lists of, among others, wallet providers, PID providers and access certificate providers. Verifiers use them to trace signatures and certificates back to a trusted body.

Reference: Regulation (EU) No 910/2014, Art. 22; Implementing Regulation (EU) 2024/2980See also: Qualified trust service provider, Access certificate, PID provider

Umbrella term for digital credentials whose origin and integrity can be verified cryptographically. The original 2024 implementing regulations named the W3C Verifiable Credentials Data Model; since the amendment by Implementing Regulation (EU) 2026/1731, the EUDI Wallet relies on SD-JWT VC and mdoc.

Reference: W3C: Verifiable Credentials Data Model 2.0See also: Electronic attestation of attributes, SD-JWT VC, mdoc (ISO/IEC 18013-5)

The wallet app installed on the user’s smartphone or other device, through which the user operates their wallet unit.

Reference: Implementing Regulation (EU) 2024/2979, Art. 2(10)See also: Wallet unit

The body that provides a wallet solution – the member state itself, on its behalf, or recognised by it. In Germany, the federal government provides d-you.

Reference: Implementing Regulation (EU) 2024/2979, Art. 2(7)See also: Wallet unit, d-you

Tamper-resistant hardware such as a security chip in the smartphone, an external secure element or a hardware security module at the provider. It holds the keys that bind credentials to the wallet.

Reference: Implementing Regulation (EU) 2024/2979, Art. 2(12)See also: Wallet unit, PID provider

A user’s personal wallet: the app on the device (wallet instance) together with the associated cryptographic application and secure cryptographic device. PID and credentials are bound to it.

Reference: Implementing Regulation (EU) 2024/2979, Art. 2(2)See also: Wallet instance, Wallet secure cryptographic device, Wallet unit attestation

A data object with which the wallet provider confirms the components of a wallet unit and that it is genuine. Issuers of PID and credentials check it before issuing anything into the wallet.

Reference: Implementing Regulation (EU) 2024/2979, Art. 2(8)See also: Wallet unit, Wallet provider