Summary
A W3C Verifiable Credential expresses issuer claims in a machine-verifiable format; proof validation, issuer trust and status remain distinct checks.
Connect issuer claims with supported proof and receiving-system verification.
The structure behind a verifiable achievement
An achievement credential connects the issuer’s claim with its subject, supported proof and applicable status. The holder presents the record, and a compatible verifier checks the proof and available issuer resources. A failed proof or unavailable resource changes what the receiving organisation can establish.
Keep the institutional meaning outside the cryptographic shortcut
Use the institutional issuance lifecycle to decide who approves an award and who handles corrections. A securing mechanism cannot decide whether assessment evidence justified the achievement.
Connect the standard to related records
An Open Badges achievement credential specializes the achievement context. A Comprehensive Learner Record can connect records while retaining provenance. Reviewed skill relationships remain distinct from cryptographic proof.
Institutional adoption in practice
The customer case studies show how institutional programmes use credential workflows. Standards define the record structure; issuer authority and assessment give the represented achievement its meaning.
Existing operational reference
What are W3C Verifiable Credentials?
A W3C Verifiable Credential (VC) represents issuer claims about a subject in a machine-verifiable format. A supported securing mechanism lets a verifier check integrity and signing authority. That check is distinct from deciding whether an issuer is trusted, whether the credential belongs to the presenter, and whether its evidence meets an institution’s requirements.
For universities, professional bodies and training providers, this is part of digital credential infrastructure, not simply a signed image. A degree, certification or assessed achievement can carry issuer and evidence context for another institution or employer to evaluate.
Issuer, holder, subject and verifier
- Issuer: makes the claims and secures the credential using a supported mechanism.
- Subject: the entity the claims concern; often a learner, but not necessarily the holder.
- Holder: possesses credentials and can present them to a verifier.
- Verifier: checks the presentation, credential proof, issuer authority, validity and applicable status against its own acceptance policy.
The W3C data model describes these roles; it does not automatically verify the identity of each participant. The issuer still needs an appropriate process for identifying subjects and establishing achievement evidence.
Credential components and verification
A credential typically identifies its issuer, type and subject claims. Depending on the model version and implementation, it may include validity information, evidence, schemas, status references and a securing mechanism.
- Obtain the credential or presentation in a supported format.
- Validate the data structure and the supported cryptographic securing mechanism.
- Resolve the relevant issuer verification material and establish why that issuer is authoritative.
- Check validity and applicable revocation or suspension resources.
- Assess subject binding, achievement criteria and evidence against the receiving institution’s policy.
Keys, status services and other referenced resources can require network access. A QR code or webpage is an access path, not by itself proof. See credential verification for the institutional trust process.
Portability and interoperability
Portability means a credential can move beyond the interface that originally issued it. Successful interoperability still requires compatible data formats, securing mechanisms, identifier resolution, exchange protocols and receiving-system policies.
The W3C VC Data Model 1.1 and Data Model 2.0 describe model versions. A product’s use of a VC-based standard does not establish that it supports every version, proof suite or wallet. Institutions should test the actual issue, export, presentation and verification paths.
Open Badges, skills and learner records
Open Badges 3.0 applies a VC-based model to achievement claims, including criteria, issuer and evidence information. The 1EdTech certification registry lists CertifyMe’s Open Badges 3.0 Issuer and CLR 2.0 Issuer/Displayer roles. It is not a general “W3C-certified” designation.
Skills taxonomy mapping relates an achievement to reviewed skills concepts. A Comprehensive Learner Record brings achievements together while retaining their provenance. Workforce intelligence compares that skills context with occupations and separately sourced market information; a signed credential does not guarantee employability.
Verifiable credentials versus PDFs
| Question | PDF or certificate image | VC-based credential |
|---|---|---|
| Integrity | An unsigned image alone has no cryptographic integrity check; a PDF can also be digitally signed. | A supported securing mechanism permits machine verification. |
| Issuer trust | Requires a reliable source or verification process. | Still requires trusted issuer identification and relevant authority. |
| Status | May be maintained separately by the issuer. | Can reference status information where implemented; availability still matters. |
| Privacy | Depends on its content, access and sharing arrangements. | Selective disclosure and encryption depend on format and implementation. |
| Receiving systems | Usually document workflows. | Must support the actual format, proof and acceptance policy. |
Verifiable credentials in institutional workflows
Registrars govern awards and corrections, academic teams establish assessed meaning, and supported APIs and integrations connect record workflows with institutional systems. Security controls support access and data handling, while career services help learners present achievements in occupational context.
CertifyMe brings approved achievement information into a supported credential format with issuance, sharing and verification workflows. Criteria and subject associations remain part of the record context, while corrections and applicable status processes support its ongoing lifecycle.
Authoritative standards references
- W3C Verifiable Credentials Data Model 2.0
- W3C Verifiable Credentials Data Model 1.1
- 1EdTech Open Badges standard
- 1EdTech Comprehensive Learner Record standard
Updated 3 October 2026. Standards explain an architecture; product certification roles and implementation scope should be checked separately.
Plan your next step
See how CertifyMe’s structured achievement records support your institution’s credential workflows. Request an institutional demo.
