Understanding the relative trust levels of different credential formats is essential for matching the format to the use case. The spectrum below runs from weakest to strongest independent verifiability:
| Format | Verification mechanism | Legal standing (EU) | Suitable for formal recognition? |
|---|---|---|---|
| PDF Certificate | None — visual inspection only | None | No |
| Open Badge (OB v2.1) | Hosted assertion — URL-based | None | No |
| Open Badge (OB v3.0) | Optional cryptographic signature (W3C-VCDM compatible) | None inherent | Limited — no ELM fields |
| EAA (non-qualified) via TSP under eIDAS 2.0 | Cryptographic signature; issuer registered as TSP but NOT in national QTSP list | eIDAS 2.0 Art. 45f — “shall not be denied” admissibility and cross-border recognition as evidence, but no equivalence to paper and no presumption of validity | Limited — admissible but not sufficient for processes requiring QEAA/PubEAA |
| EDC / Europass (EDCI) | Cryptographically signed; issuer in Europass trusted list | eIDAS 1.0 qualified seal | Yes |
| EDC, wallet lineage (DC4EU/EBSI, W3C VCDM) | Cryptographic + EBSI trust registry + QTSP/PSB signature | Designed for eIDAS 2.0 QEAA / PubEAA; in the EUDI Wallet, W3C VCDM is today optional and for non-qualified EAA only | Yes; delivery to the EUDI Wallet as a qualified attestation awaits the W3C VCDM profiles |
| QEAA / PubEAA in the EUDI Wallet (SD-JWT VC or mdoc) | Cryptographic + wallet trust framework (trusted lists, QTSP or public-body signature) | eIDAS 2.0 QEAA / PubEAA | Yes; highest assurance in the wallet today |
The last two rows reflect the current wallet rules. Since Implementing Regulation (EU) 2026/1731 (in force 11 August 2026), the binding annexes of the EUDI Wallet implementing acts name SD-JWT VC and ISO/IEC mdoc for person identification data and for attestations. W3C VCDM is not among them today, but the regulation’s recitals state that wallets should also support it, as the reference format for attestations in education, once new W3C VCDM profiles are available. ARF v3.0 currently treats W3C VCDM as optional and for non-qualified attestations only. See EUDI Wallet.
EDC is necessary but not sufficient
An EDC provides technical trust and interoperability. Legal validity additionally requires:
- An accredited issuer — recognised by the relevant national authority
- A functioning governance framework — awarding authority, QA reference
- Regulatory alignment — eIDAS conformant signature, ELM-compliant structure
A cryptographically signed credential issued by a non-accredited body is technically valid and legally meaningless.
The dependency also runs the other way. As the VC guide v1.1 (EUNIS SIG, July 2026), Verifiable Credentials in Higher Education: W3C-VC and SD-JWT VC, puts it, format and trust framework are complementary layers, and neither can stand in for the other: governance cannot supply a state that the format is unable to express. A university that must put a degree on hold during a disciplinary review needs a status mechanism with a native suspended state, not a procedural workaround. Bitstring Status List distinguishes suspension from revocation; Token Status List offers revocation only in the European profiles. See Credential lifecycle for how this plays out over a credential’s life.
Three tiers of attestation under eIDAS 2.0
Not all electronic attestations under eIDAS 2.0 carry the same legal weight. The regulation defines three tiers, each with distinct issuer requirements and legal effects:
| Tier | Issuer | Legal effect | In trusted list? |
|---|---|---|---|
| QEAA (Art. 45g) | Qualified TSP (QTSP) — accredited at national level | Equivalent to a lawfully issued paper attestation of attributes | Yes — LOTL + national TSL |
| PubEAA | Public sector body (or on its behalf) | Equivalent to QEAA when conditions are met; cross-border recognition | Yes — in the relevant national trusted list |
| EAA (Art. 45f) | Any Trust Service Provider (non-qualified allowed) | “Shall not be denied” admissibility and cross-border recognition as evidence; no presumption of validity | Not required — TSP need not be in QTSP list |
The non-discrimination clause (Regulation (EU) 2024/1183, Article 45f) is the key innovation for the non-qualified tier:
An electronic attestation of attributes shall not be denied legal effect and admissibility as evidence in legal proceedings solely on the grounds that it is in an electronic form or that it does not meet the requirements of qualified electronic attestations of attributes.
Regulation (EU) 2024/1183, Article 45f
This creates a cross-border recognition floor for EAAs even when the issuer is not a QTSP. A microcredential from a private non-accredited provider, carried in an EUDI Wallet, cannot be denied legal effect or admissibility as evidence in legal proceedings solely because it is electronic or not qualified; it does not carry the presumption of validity of a QEAA or PubEAA.
Three practical takeaways for choosing a tier:
- For diplomas, transcripts and formal qualifications → QEAA or PubEAA: formal recognition workflows benefit from qualified or public-body attestations, although eIDAS 2.0 does not itself mandate a category for diplomas
- For microcredentials from accredited educational authorities → QEAA (via QTSP) or PubEAA
- For microcredentials from private providers, corporate CPD, or informal recognition → EAA is a legitimate option; it carries the “shall not be denied” floor but not the full legal effect of QEAA
Open Badges carry real social value — with a caveat
Badges have genuine economic value in talent ecosystems. Employers use them, professional networks surface them, learners share them. This value is real and should not be dismissed.
However, this value is platform-dependent, not framework-dependent. It can diminish or disappear when platforms change their policies, are acquired, or cease to operate. Institutional strategy should not depend on the continued behaviour of commercial platforms.
The interoperability pillar order
A critical principle from the European Interoperability Framework (EIF): the four pillars of interoperability must be addressed in order. Technology is always the last layer:
| Pillar | Content | Consequence if skipped |
|---|---|---|
| 1. Legal | Aligned legislation, policies, and agreements. The prerequisite — if there is no legal basis, nothing else matters. | No legal validity; credentials not recognised across borders. |
| 2. Business | Aligned processes, responsibilities, and governance. Defines what needs to be exchanged and who is accountable. | Governance gaps; no clear awarding authority or accountability. |
| 3. Semantic | Shared meaning. ELM ensures that a ‘learning outcome’ in Spain means the same as in Finland. | No cross-border comparability; credentials become local artefacts. |
| 4. Technical | APIs, data formats, protocols. The last layer — not the first. | Technical solutions that cannot deliver cross-border value. |
See the interactive interoperability map (2D and 3D) for a visual exploration of the same model with credential-specific layers added on top.
Institutions that start with the technical layer — choosing a platform before defining governance — consistently face rework.
