Seven terms used as if interchangeable — they are not. This page defines each precisely, and the final table summarises the core distinctions. A second set of five distinctions, specific to verifiable credentials, closes the page. The foundational terms (Digital, Digitisation, Digitalisation) are covered in Concepts.
Badge
A badge is a visible token representing recognition, membership, or achievement. The concept predates digital systems by centuries: scout merit badges, military insignia, professional pins, and academic honours all share the same mechanic — a small, recognisable artefact whose meaning is understood within a community.
The defining property of a badge is its visual recognisability. A diploma is hung on a wall; a badge is worn. Badges are designed to be seen, shared, and accumulated. They function as social signalling devices: their value comes as much from being displayed as from being earned.
In the digital era, the badge metaphor has been retained — the icon, the visual collectability, the public sharing — and extended with structured metadata that travels with the image.
Digital Badge
A digital badge is a visual digital element that represents participation or achievement, typically within a closed ecosystem such as a learning management system or a gamification layer. It may carry no structured metadata beyond a name and an image, is not portable outside the system that issued it, and implies no verification mechanism.
A digital badge is the most basic form of digital recognition. It is analogous to a sticker or a stamp — it communicates meaning to those who understand the context, but carries no independent trust or verifiability.
Open Badge
An Open Badge is a digital badge that conforms to the 1EdTech Open Badges standard. The word ‘open’ refers to interoperability and portability, not to the absence of criteria. An Open Badge carries structured, machine-readable metadata (issuer, recipient, criteria, evidence) that travels with the image and can be verified by any party.
The key distinctions from a simple digital badge: it is portable across compliant platforms, it is verifiable (at least at the level of issuer and recipient), and it is not locked into any single vendor ecosystem. For depth, see Open Badges.
Credential
A credential is a formal attestation issued by a trusted authority confirming a qualification, competence, or right. Credentials carry institutional trust and, in relevant cases, legal weight.
Credentials exist in physical and digital forms: a paper diploma, a campus card and a signed certificate are all credentials, as is a cryptographically signed digital record. What defines a credential is not its format but the institutional authority and trust behind it. As the Badges guide v1.1 (EUNIS SIG, July 2026), Badges and Digital Credentials in Higher Education, puts it, “a credential is a container for trust.”
The word ‘credential’ is used loosely in many contexts. Here it is used in its strict sense: a claim about a person’s learning or achievement, issued by a party with recognised authority to make that claim.
Digital Credential
A digital credential is a credential issued, stored, and shared digitally. In its strong form — a verifiable credential, such as one aligned with the W3C Verifiable Credentials Data Model (W3C-VCDM) — it is tamper-evident and cryptographically verifiable without contacting the issuer.
This is the technically significant form. A scanned PDF diploma is digital in a trivial sense. A W3C-VC credential (W3C-VCDM data model) with a qualified digital signature is a digital credential in the full sense of independent, offline verifiability. For depth, see The W3C-VC stack and The SD-JWT stack.
European Digital Credential (EDC)
A European Digital Credential is the specific implementation of a digital credential that conforms to the European Union’s credential infrastructure. It is the recognised form for formal credential issuance in the EU regulatory space, including microcredentials under the EU Council Recommendation (2022).
What distinguishes EDC from a digital credential in general:
- ELM semantics — EDC is structured using the European Learning Model: EQF level, ECTS workload, learning outcomes, QA reference, assessment method, awarding body, ISCED-F subject area.
- EU trust framework — EDC issuers are registered in EU-recognised trust frameworks (Europass trusted issuer list, EBSI Trusted Issuers Registry).
- Regulatory alignment — EDC aligns with eIDAS (1.0 for Europass/EDCI; 2.0 for DC4EU/EBSI), the EU Council Recommendation on microcredentials, and Bologna framework references.
Two technically distinct lineages implement EDC: Europass / EDCI and DC4EU / EBSI; the DC4EU pilot itself ended in 2025. Delivery through the EUDI Wallet is a separate question: the wallet’s binding formats today are SD-JWT VC and mdoc, and support for the W3C data model in education is foreseen once new profiles for it exist. See European Digital Credentials for depth.
Microcredential
A microcredential is a type of learning achievement — not a format or a size of document. It is defined by the EU Council Recommendation (2022) as follows:
EU Council Recommendation on microcredentials (2022)
“A micro-credential is a record of learning outcomes acquired following a small volume of learning, assessed against transparent criteria, and shareable digitally.”
Required elements: learner identity · stated learning outcomes · workload (ECTS or notional hours) · EQF/NQF level · assessment method and criteria · quality assurance reference · issuer information
Short course ≠ microcredential.
Without stated outcomes, formal assessment, and a quality assurance reference, a learning activity is training — however valuable. Technology cannot substitute for the pedagogical layer.
The two layers of any educational credential
Every educational credential — diploma, transcript or microcredential — rests on two inseparable layers. Each is necessary; neither is sufficient on its own. The EU Council Recommendation (2022) codifies both, with mandatory force for microcredentials.
| Layer | Content | Consequence if missing |
|---|---|---|
| Pedagogical / Regulatory | Stated outcomes, assessed performance, QA reference, EQF level, ECTS workload, issuer information. Defined by the EU Council Recommendation. | Not a microcredential: it is training, and no framework will recognise it. |
| Technical / Trust | How the record is structured, signed and shared. Implemented via EDC (ELM + qualified signature + wallet). | No cross-border interoperability or independent verification. |
The pedagogical layer exists independently of format: a paper diploma has learning outcomes, an EQF level and a quality assurance reference, even if none of them is machine-readable. What the technical layer adds is not the content but the ability to verify, share and process it digitally and across borders.
The Core Distinctions
These concepts operate on different dimensions and are genuinely independent:
| Concept | Dimension | Portability | Verifiability |
|---|---|---|---|
| Digital badge | Visual element in a closed system | None — locked to issuing platform | None |
| Open Badge | Portable, structured digital badge (1EdTech standard) | High — interoperable across platforms | Basic to cryptographic (v3.0) |
| Credential | Formal attestation of qualification or competence | Depends on format | Depends on format |
| Digital credential | Credential issued, stored, and shared digitally (in its strong form, a verifiable credential — W3C-VC or SD-JWT stack) | High — holder-controlled | Cryptographic — offline verifiable |
| European Digital Credential | Digital credential structured with ELM and aligned with EU trust frameworks (Europass/EDCI or DC4EU/EBSI) | High — holder-controlled (wallet or file) | Cryptographic + accredited issuer + ELM semantics |
| Microcredential | Type of learning achievement (EU Council Rec. 2022) — not a format | Depends on implementation | Requires EDC for EU conformance |
Five distinctions for verifiable credentials
Once a credential is digital and verifiable, a second set of distinctions matters. Five are routinely collapsed in vendor material and policy documents; the VC guide v1.1 (EUNIS SIG, July 2026), Verifiable Credentials in Higher Education: W3C-VC and SD-JWT VC, names them and the institutional mistake each collapse produces.
1. The verifiable credential triangle
Three roles: the issuer signs the credential and hands it to the holder; the holder keeps it in a wallet and decides when, to whom and how much to present; the verifier checks the presentation independently. The issuer is not in the loop of verification — it does not know the presentation happened and does not need to be online. Both stacks implement this triangle; see Verifiable credentials.
What goes wrong when it is missed: institutions judge platforms on issuance features and never ask what verification looks like for a relying party in another country.
2. Data model versus proof mechanism
The data model defines how content is structured and where its meaning lives; the proof mechanism defines how it is secured — signature, holder binding, selective disclosure, unlinkability. When the two are independent, cryptography can be replaced without reissuing credentials; when they are welded together, that flexibility is gone by construction. See Two stacks, not two flavours.
What goes wrong when it is missed: two products that both “support selective disclosure” look equivalent, although only one can change its cryptographic suite in place.
3. Credential format versus credential type
The format is the container (W3C-VC or SD-JWT); the type is what is attested (a degree, a microcredential, an enrolment status). Any type can travel in either format, but types differ in what they demand — longevity, cross-border semantics, suspension. The type does not choose the format; its requirements should. See Choosing a stack.
What goes wrong when it is missed: the long-lived, regulated credential inherits a container chosen for whichever simple use case arrived first.
4. Selective disclosure versus unlinkability
Selective disclosure means revealing only some attributes; both stacks provide it. Unlinkability means two presentations of the same credential cannot be correlated, even by colluding verifiers — a stronger property. Article 5a(16) of Regulation (EU) 2024/1183 prohibits tracking and correlation of users after issuance and requires the wallet framework to enable unlinkability where an attestation does not require identifying the user. A credential with a byte-identical signature in every presentation is perfectly selective and perfectly linkable. See Selective disclosure vs unlinkability.
What goes wrong when it is missed: a data protection officer approves a solution because “it only shares what is needed”, without asking whether every presentation leaves a correlatable trace.
5. Trust framework versus credential format
The format is the container and its cryptography; the trust framework is what makes a verifier willing to rely on it — accredited-issuer registers, quality assurance, legal recognition under eIDAS. A flawless credential from an unaccredited issuer is technically valid and legally meaningless, and no framework can repair a format that cannot express what it requires. See Trust frameworks.
What goes wrong when it is missed: either “it is signed, therefore it is valid”, or “we will handle suspension procedurally” — both fail at the worst moment.
