Europass is the EU Commission’s flagship platform for managing skills and credentials. Within Europass, the European Digital Credentials Infrastructure (EDCI) component handles digital credential issuance and verification. EDCI was the first EU-wide production digital credential infrastructure (2020 onwards). It predates the EUDI Wallet and eIDAS 2.0 and makes different architectural choices. The Badges guide v1.1 (EUNIS SIG, July 2026), Badges and Digital Credentials in Higher Education, describes Europass/EDCI and the DC4EU/EBSI wallet lineage as two EDC lineages that operate under the same EU regulatory framework but are technically distinct.
EDCI architecture
| Layer | Choice |
|---|---|
| Format | JSON-LD based, aligned with ELM v3.x; not a fully conformant W3C VCDM credential (the W3C-conformant variant, EDC-W3C, is specified separately; see the EAA catalogue) |
| Signing | Qualified electronic seals (eIDAS 1.0) using QTSP-issued certificates |
| Delivery | Credential delivered as a file (.json or PDF with embedded JSON-LD); optional storage in the Europass Library |
| Trust | Centralised — Europass maintains the official Trusted Issuer List |
| Verification | Hosted Europass verifier, or any compliant tool that fetches the Trusted Issuer List |
| Wallet support | Not wallet-native; the Library is a centralised store |
Adoption today
- 40+ Member States and partner countries connected
- Multiple national platforms federated to Europass
- Used for diplomas, transcripts, microcredentials, Diploma Supplement, ESCO competence statements
EDCI vs DC4EU/EBSI — the architecture choice
| Europass / EDCI | DC4EU / EBSI / EUDI | |
|---|---|---|
| eIDAS generation | 1.0 | 2.0 |
| Signing | Qualified seal (QTSP) | QTSP/PSB + on-chain attestation |
| Delivery | File-based | Designed for wallet delivery |
| Trust registry | Centralised (Europass TIL) | Decentralised (EBSI TIR) |
| Revocation / suspension | Limited mechanisms | Bitstring Status List (formerly StatusList2021): revocation and suspension as distinct states |
| Citizen mediation | Optional | Native (LE→NP→LE) |
| Status | Production today (40+ countries) | DC4EU pilot concluded in 2025; no EU-wide production service yet |
EDCI is the right choice for institutions that need to deploy EDC today.
The DC4EU/EBSI lineage was designed for wallet delivery, but its pilot concluded in 2025, and a qualified attestation in the EUDI Wallet travels today as SD-JWT VC or mdoc.
An institution does not have to choose forever — both lineages can coexist, addressing different use cases.
Which data transfer models EDCI fits
EDCI suits the flows in which an institution issues to a learner or shares data with another institution. It was not built for the citizen-mediated wallet flow. The full comparison is on European Digital Credentials.
| Model | Fit with EDCI | Example |
|---|---|---|
| LE → NP (institution to learner) | Yes | Diploma, transcript or microcredential issued to the learner as a file, optionally kept in the Europass Library |
| LE → LE (institution to institution) | Yes, via Europass/EDCI; SDG/OOTS or a direct API are the alternatives | Partner university checking enrolment for an Erasmus exchange |
| LE → NP → LE (citizen-mediated) | Not the design target; this is the wallet lineage’s flow | Learner presents a credential from a wallet to a relying party |
Planning for long-lived credentials
Diplomas and professional qualifications stay relevant for decades, and schemas change over that time. Current wallet infrastructure does not natively support credentials valid for five years or more, so an institution that later moves a credential into a wallet inherits the same question. Whichever lineage you use, define how a graduate obtains an updated credential when one expires or its schema changes, and tell graduates in advance. This is a governance and communications task as much as a technical one. See Credential lifecycle.
