A verifiable credential (VC) is a cryptographically secured, tamper-evident claim about a subject, issued by a party and verifiable by any third party without contacting the issuer. The term is format-agnostic: it does not imply any particular data model or serialisation.
What makes a credential “verifiable”
- Cryptographic integrity — the credential carries a digital signature (or equivalent proof) that any holder of the issuer’s public key can verify. Tampering breaks the proof.
- Issuer identity — the credential carries a stable identifier for the issuer (DID, X.509 SubjectDN, or other) whose public key can be retrieved or anchored in a trusted registry.
- Subject binding — the credential binds its claims to a subject. In wallet contexts this is typically the holder’s public key (key binding); in file-based contexts it’s a strong identifier.
- Independent verification — the verifier does not need to call the issuer. All trust evaluation can be done with cached data: public keys, trust lists, status lists.
The three-party model
Issuer → Holder → Verifier. The credential moves from issuer to holder (typically into a wallet); the holder presents it (entire credential or selective disclosure) to a verifier; the verifier checks cryptographic validity + issuer trust + holder binding, all without contacting the issuer.
That final point is where the model earns its keep. As the VC guide v1.1 (EUNIS SIG, July 2026), Verifiable Credentials in Higher Education: W3C-VC and SD-JWT VC, observes, checking a paper certificate, or most PDFs, still depends on the issuer: someone phones the registry, writes to the international office or searches a vendor portal. In the triangle, verification happens without the issuer. The graduate presents, the employer checks, and the university neither learns of the presentation nor has to be online for it. Both stacks described below respect this triangle in full; it is the common ground between them.
See The W3C-VC stack for an illustration of the model (Fig. W3C VCDM).
Two stacks dominate today
W3C-VC and SD-JWT are not two flavours of the same object. Each is a complete stack that answers two independent questions in opposite ways: where does meaning live — inside the signed credential, through JSON-LD @context, or outside it, as flat claims documented elsewhere — and is the proof a detachable layer over the data model, or is the proof mechanism the format itself? Two stacks, not two flavours explains the map.
- The W3C-VC stack — VCDM 2.0, meaning inside the credential (JSON-LD), proof as a replaceable layer (Data Integrity cryptosuites such as ecdsa-rdfc-2019, eddsa-rdfc-2022 and bbs-2023)
- The SD-JWT stack — flat JSON claims typed by
vct, semantics out of band, salted-hash selective disclosure welded to the format; fast to production and well supported by today’s wallets
The two stay distinct even where they share a mechanism: an SD-JWT credential is not a W3C-VC, although a W3C-VC can be secured with SD-JWT. See A frequent confusion.
Both stacks provide selective disclosure: the holder reveals only the attributes a verifier needs. Of the two stacks, only W3C-VC secured with bbs-2023 provides unlinkability at the level of the proof — presentations of the same credential that cannot be correlated with each other. This matters legally: 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. The two properties are often confused; see Selective disclosure vs unlinkability.
Adjacent technologies
- mdoc / mDL (ISO/IEC 18013) — CBOR-encoded, NFC/BLE-friendly; the basis of mobile driving licences and identity cards, and, with SD-JWT VC, one of the two formats the binding EUDI Wallet annexes name. A separate ISO lineage, not a verifiable credential in the W3C/IETF sense, and out of scope for this section.
- Open Badges v3.0 (1EdTech) — technically a W3C VC for educational achievements; see Open Badges
VC is the umbrella. The stack choice follows from the credential type’s requirements — lifespan, audience, semantic density, status needs, regulatory exposure — not from which wallet is popular this year.
Most universities will run two lanes: SD-JWT for short-lived, intra-scheme, semantically light credentials (student ID, enrolment, access), and W3C-VC for long-lived, cross-border, regulated ones (degrees, formal microcredentials, professional qualifications) — see Choosing a stack, which also sets out the EUNIS SIG position for formal, regulated credentials, and W3C-VC vs SD-JWT.
Key points
- A verifiable credential is checked without asking the issuer: the issuer is not in the loop of verification.
- W3C-VC and SD-JWT are two stacks, differing on where meaning lives and whether the proof is a layer or the format.
- Both offer selective disclosure; of the two, only W3C-VC with bbs-2023 offers unlinkability at the level of the proof.
- mdoc/mDL is a separate ISO lineage, not a VC in the W3C/IETF sense.
