EUDI Wallet — Architecture Reference Framework

← Trust frameworks

The European Digital Identity Wallet Architecture and Reference Framework (ARF) is the technical reference the European Commission and Member States maintain for building EUDI Wallets. Its legal anchor is Regulation (EU) 2024/1183 (eIDAS 2.0) and the implementing regulations adopted under it. The distinction matters: the ARF is a living document, revised several times a year and not legally binding in itself, while the implementing acts are law. Where the two differ, the implementing acts prevail. This page reflects ARF v3.0.0 (July 2026) and the acts as amended by Implementing Regulation (EU) 2026/1731, in force since 11 August 2026.

What the ARF specifies

  • Roles: Users, Wallet Providers (notified by a Member State), PID Providers, providers of QEAA, PuB-EAA and EAA, Relying Parties, and the registrars, access certificate authorities and Trusted List operators that make the system verifiable.
  • Person identification data (PID): the core identity attestation, with a mandatory attribute set defined in Implementing Regulation (EU) 2024/2977.
  • Three attestation categories: qualified electronic attestations of attributes (QEAA), issued by qualified trust service providers; attestations issued by or on behalf of a public body responsible for an authentic source (PuB-EAA); and non-qualified EAA. The ARF treats them as technically identical; they differ in legal effect.
  • Trust anchors and wallet attestations: Trusted Lists and Lists of Trusted Entities publish the keys of providers; the Wallet Provider attests the integrity of each wallet unit and the keys it holds.
  • Protocols: OpenID4VCI for issuance, profiled by HAIP; OpenID4VP or ISO/IEC 18013-7 for remote presentation, including through the W3C Digital Credentials API; ISO/IEC 18013-5 for proximity presentation.
  • Certification and conformance: wallet solutions are certified under Implementing Regulation (EU) 2024/2981; ARF v3.0 adds a Functional Conformance Assessment Framework with shared test cases.

Credential formats in the wallet

Three things decide which formats a wallet handles: the binding annexes of the implementing acts, the recitals that explain where those acts are heading, and the ARF, which profiles the detail.

The binding annexes today. Implementing Regulation (EU) 2026/1731 of 15 July 2026, published in the Official Journal on 22 July 2026 and in force since 11 August 2026, rewrote the format rules. PID must now be issued in SD-JWT VC and ISO/IEC mdoc formats, following clauses 5 and 6 of the standards in Annex II of Implementing Regulation (EU) 2024/2979. Attestations must follow the same Annex II, which applies clauses 2 to 6 of ETSI TS 119 472-1 V1.2.1 (2026-02): general requirements plus the SD-JWT VC and mdoc profiles. The original 2024 text named ISO/IEC 18013-5 and W3C VCDM 1.1 for PID; that reference is gone from the annexes.

The stated intention. W3C VCDM is not ruled out. One of the recitals of 2026/1731 observes that W3C VCDM is the reference format for attestations, in particular in the educational sector, and states that the wallets “should also support this format when the new profiles on the W3C VCDM format are available”. A recital explains intent rather than imposing an obligation, and it sets no date. Binding support would most likely come through a further amendment of the annexes once ETSI has published those profiles. The current ETSI specification appears to contain a JSON-LD W3C-VC realisation already, but if so it sits outside the clauses the act applies.

The ARF. ARF v3.0 (section 5.4.1) lists three formats. Wallet units support mdoc and SD-JWT VC; support for W3C VCDM 2.0 is optional and meant for non-qualified EAA only. Expect that line to move if the W3C VCDM profiles arrive.

FormatImplementing acts (as amended by 2026/1731)ARF v3.0Presentation
ISO/IEC mdoc (18013-5, 23220-2), CBORRequired for PID; permitted for attestationsWallet units support itProximity and remote (ISO/IEC 18013-7 or OpenID4VP)
SD-JWT VC, JSONRequired for PID; permitted for attestationsWallet units support itRemote only (OpenID4VP)
W3C VCDM 2.0Not in the binding annexes today; a recital says wallets should also support it, as the reference format in education, once new W3C VCDM profiles are availableOptional; for non-qualified EAA onlyRemote; transport left to a rulebook

Two cautions. First, mdoc belongs to the ISO mobile-document lineage and is not a verifiable credential in the W3C or IETF sense. Second, SD-JWT VC and W3C-VC are not interchangeable encodings: they are two stacks, not two flavours, and the choice between them is a decision about the credential, covered in Choosing a stack.

Wallet trust hierarchy

  1. Trusted Lists and Lists of Trusted Entities: the trust anchors. QEAA providers appear in national Trusted Lists; the Commission maintains lists for Wallet Providers, PID Providers and others.
  2. Access and registration certificates: registered Relying Parties and providers receive access certificates to authenticate to wallet units; registration certificates, where a Member State uses them, state what a party is registered to request or issue.
  3. Wallet unit attestation: the term used in the implementing acts. ARF v3.0 splits it into a Wallet Instance Attestation, short-lived and attesting the app’s integrity and status, and a Key Attestation, describing the secure cryptographic device and the keys it holds.
  4. PID and attestations: signed by providers whose anchors sit in step 1, and normally bound to keys attested in step 3.

Timeline

  • 20 May 2024: Regulation (EU) 2024/1183 enters into force.
  • 24 December 2024: first five implementing acts in force (2024/2977 PID and attestations; 2024/2979 integrity and core functionalities; 2024/2980 notifications; 2024/2981 certification; 2024/2982 protocols and interfaces).
  • May 2025: second batch published, including 2025/848 on registration of wallet-relying parties; ARF v2.0.0 released.
  • July 2025: trust services batch, including 2025/1569 on QEAA and PuB-EAA; the DC4EU pilot holds its final conference.
  • July 2026: 2026/1731 (standards and specifications) adopted on 15 July, published on 22 July and in force from 11 August; further amending acts adopted the same month concern relying-party registration (2026/1730) and QEAA and PuB-EAA (2026/1735); ARF v3.0.0 released.
  • 24 December 2026: each Member State must provide at least one wallet, 24 months after the implementing acts entered into force; the relying-party registration rules apply.
  • December 2027: private relying parties required to use strong user authentication must accept the wallet at the user’s request (36 months).

What this means for universities

You inherit your national wallet

Students will hold what their Member State’s wallet supports. Every wallet unit must handle mdoc and SD-JWT VC; W3C VCDM support is optional for now. The VC guide v1.1 (EUNIS SIG, July 2026), Verifiable Credentials in Higher Education: W3C-VC and SD-JWT VC, advises asking your ministry or national agency, formally and in writing, which formats and proof suites the national wallet supports and has committed to on its roadmap. Treat the answer as a versioned planning input, not conference knowledge.

Which attestation category your credentials fall into

A university can issue a diploma to the wallet as a non-qualified EAA, as a QEAA through a qualified trust service provider, or as a PuB-EAA where national law makes it responsible for the authentic source. The category has format consequences: under ARF v3.0, W3C VCDM is reserved for non-qualified EAA, so a qualified or public-body degree in the wallet would today travel as SD-JWT VC or mdoc. That complicates the two-lane pattern many institutions will adopt (SD-JWT VC for short-lived credentials such as student ID or enrolment, W3C-VC for long-lived, semantically dense ones): for now, a degree on the W3C-VC lane can reach the EUDI Wallet only as a non-qualified EAA, and only where the national wallet supports the optional format. Decide the attestation category and the lane per credential, together.

Watch for the W3C VCDM profiles

The recital in 2026/1731 names the educational sector as the reason wallets should also support W3C VCDM. The formal lane, W3C-VC for degrees, formal microcredentials and professional qualifications, is therefore not dead in the EUDI Wallet; its timing depends on profiles that do not yet exist. Three signals to track: ETSI publishing the new W3C VCDM profiles, an amendment that brings them into the binding annexes, and an ARF release that revisits the optional, non-qualified-only status in section 5.4.1. None has a date. Until they land, keep an SD-JWT VC route for anything that must work in national wallets from December 2026, and plan the W3C-VC lane on its own merits, as set out in Choosing a stack.

Long-lived credentials, short-lived flows

EUDI issuance is built around short-lived attestations refreshed through OAuth-style tokens; the amended rules even exempt attestations valid for 24 hours or less from revocation. A degree must stay verifiable for thirty years or more, and will outlive every token that issued it. Holder binding adds a second problem: keys are usually bound to one device, and graduates change phones many times. Neither issue is settled; see Open problems.

If you verify, you register

A university that requests PID or attestations from wallets, for admissions or mobility, is a wallet-relying party. From 24 December 2026 it must register in its Member State, declaring for each intended use the attributes it will request and why. Article 5a(16) of Regulation (EU) 2024/1183 adds a privacy limit: it prohibits tracking and correlation of users after issuance and requires the framework to enable unlinkability where an attestation does not require identifying the user.

DC4EU

DC4EU, the large-scale pilot for education and social security, concluded in 2025. It is not a production service; its blueprints and its final report, which argues for a pluralistic trust model combining EBSI, eIDAS trust services and federated academic infrastructure, are the legacy. See EBSI and DC4EU.

Key points

  • The ARF guides; the implementing acts bind. Check claims against the acts.
  • Since 2026/1731 (in force 11 August 2026), PID is issued as SD-JWT VC and mdoc, and attestations follow the ETSI SD-JWT VC and mdoc profiles; W3C VCDM 1.1 is no longer named.
  • A recital of the same act says wallets should also support W3C VCDM, the reference format in education, once new profiles for it are available. No date is set.
  • Under ARF v3.0, wallet units support mdoc and SD-JWT VC; W3C VCDM is optional and for non-qualified EAA only.
  • Member States must provide a wallet by 24 December 2026; relying-party registration applies from the same date.
  • Universities should get their national format roadmap in writing, watch for the W3C VCDM profiles, and plan for credentials that outlive devices and tokens.

Sources

← eIDAS 1.0 vs eIDAS 2.0  ·  Trust frameworks  ·  EBSI and DC4EU →