Ewance

Verifiable Credentials: What They Are and How to Check One

A verifiable credential is a digital record of a skill or achievement that anyone can check to confirm who issued it and that it has not been altered. Here is how they work, how to check one and what a successful check does and does not tell you.

Aharon Acosta, PhD

Reviewed by Aharon Acosta, PhD Founder of Ewance · Updated November 17, 2026

The basics

What a verifiable credential is

A verifiable credential is a digital record of a skill or achievement that anyone can check to confirm who issued it and that it has not been altered.

The W3C, the web standards body, defines it as a tamper-evident credential whose authorship can be cryptographically verified. The record can state a degree, a course completion, a licence or a completed project. What makes it different from a PDF is that it carries a digital signature, so the check does not depend on trusting the file or the person who sent it.

  1. IssueThe issuer signs a record of the achievement
  2. HoldThe holder keeps it in a wallet, profile or file
  3. ShareThe holder sends it or a link to someone who asks
  4. VerifyThe verifier checks the signature, the issuer and the status
Three parties and four steps. The verifier can check the record without phoning the issuer.

The three roles: issuer, holder, verifier

The W3C data model describes the system with three main roles:

  • Issuer: the organization that makes claims about a person, creates the credential and sends it to the holder. A university, a training provider or a platform can be an issuer.
  • Holder: the person who possesses the credential and decides when to share it. Usually this is the learner or professional it describes.
  • Verifier: anyone who receives the credential and checks it, such as an employer, a recruiter or an admissions office.

The standard also describes a fourth element, a verifiable data registry. It is a system that helps create and check identifiers and the keys used to verify signatures. Where that registry lives depends on the design.

Certificate, digital badge or verifiable credential

People use these words loosely, so it helps to separate them. The columns below describe typical cases, and individual products vary.

Certificate (PDF or paper)Digital badgeVerifiable credential
What it isA document stating an achievementA graphic with data about an achievementA signed data record about an achievement
How you check itContact the issuer or compare by eyeOpen its page or metadata and see who issued itSoftware checks the signature, the issuer and the status
Easy to edit or fakeYes, unless it has a check codeHarder, if hosted by the issuerAny change breaks the signature
Can it be revokedOnly by telling peopleDepends on the issuerCan include a status that shows revocation
Who can check itUsually the issuerAnyone with the link or fileAnyone with the credential and the right software

These categories overlap. An Open Badge version 3.0 is itself a verifiable credential, so a badge can meet the stronger definition.

How checking works

How checking works in plain words

A check answers three questions.

  • Is the signature valid? The issuer signs the credential with a private key. Anyone can use the matching public key to confirm that the data has not changed since signing. The W3C Data Integrity specification describes this as making documents tamper-evident.
  • Who is the issuer? The credential points to the issuer and to the public key needed to check the signature. The verifier decides whether that issuer is one they recognize. W3C Decentralized Identifiers are one standard way to name an issuer and publish its keys without a central registration authority.
  • Is it still in good standing? A credential can include a status property so the issuer can say whether it is still valid. The W3C data model treats this as a separate step from checking the signature.

Software does most of this in seconds. You paste a link, scan a code or upload a file, and the tool reports what it found.

The standards, by name

Several public standards sit behind verifiable credentials:

  • Verifiable Credentials Data Model v2.0: a W3C Recommendation published on May 15, 2025. It defines the credential, the roles and the requirement that a conforming credential be secured by at least one securing mechanism.
  • Verifiable Credential Data Integrity 1.0: a W3C Recommendation, also from May 2025, describing how digital signatures protect a credential.
  • Decentralized Identifiers v1.0: a W3C Recommendation from July 2022 for identifiers that do not need a central registration authority.
  • Open Badges 3.0: published by 1EdTech, the education technology standards consortium. It packages an achievement as a verifiable credential and aligns with the W3C data model. It supports proof formats such as JSON Web Tokens and Linked Data signatures.

A credential that follows these standards can be checked by any tool that supports them, not only the issuer's own system.

How to check one

How to check one, step by step

The exact screens differ, but the steps are the same:

  • Get the credential from its source. Ask for the link, ID or file, and open the link yourself rather than relying on a screenshot.
  • Run it through a verification tool. Use the issuer's verification page or a checker for the standard it follows.
  • Read the signature result. A valid result means the data matches what the issuer signed.
  • Confirm the issuer. Check that the issuer name and address match the organization you expect, and that you know who it is.
  • Check the status. Look for revoked, suspended or expired.
  • Read the claim itself. Check that the name, the achievement and the date say what the person told you.
  • Decide what it means for your purpose, as the next section explains.

What a check can tell you

What a verifier can and cannot conclude

The W3C data model is direct about the limit: verifying a credential does not imply evaluating the truth of the claims in it. A valid check shows two things. The named issuer produced this record, and nobody has changed it since.

  • It does not show that the holder is competent today. It shows what an issuer recorded at a point in time.
  • It does not show that the issuer is reputable. A valid signature from an unknown organization proves little. You still need to judge the issuer.
  • It does not show that the assessment behind the credential was rigorous. Ask what the holder did to earn it.
  • It does not show that the person presenting it is the person named. Match the name to the person, and ask them to explain the work.

Treat a valid credential as a reliable pointer to evidence. Pair it with a work sample or a conversation about the work.

Privacy points for holders and verifiers

Credentials can contain personal data, so a few habits help:

  • Holders decide what to share. The W3C model gives holders fine-grained control over what information to present, and the standard discusses selective disclosure as a way to share only what is needed.
  • Share a link only with the people who need it. Anyone who has a public verification link can open it.
  • Be aware of correlation. The W3C model warns that identifiers and signatures can let different verifiers link the same person across contexts.
  • Verifiers should collect only what they need and follow local data protection rules.
  • Ask how to withdraw or revoke a credential before you accept one.

How Ewance certificates are checked

On Ewance, each completed challenge earns a certificate. Anyone with the link or ID can check it at verify.ewance.com without an account. Ewance signs each certificate and anchors it on-chain through LearnCoin, so it can be checked independently of Ewance. The same limits apply as for any credential: a valid certificate shows who issued it and that it is unaltered, and it is one piece of evidence to weigh alongside others.

Wrap-up

Common mistakes

  • Treating a PDF or a screenshot as proof without checking it.
  • Assuming a valid signature means the issuer is reputable.
  • Assuming a valid credential means the holder can do the job today.
  • Skipping the status check, so a revoked credential passes.
  • Sharing credential links publicly when only one reader needs them.
  • Using the words badge, certificate and verifiable credential as if they mean the same thing.

Reference

Frequently asked questions

What is a verifiable credential?
It is a digital record of a skill or achievement that carries a digital signature. Anyone can check who issued it and whether it has been altered.
How do I verify a digital certificate?
Open the link or ID in the issuer's verification page or a compatible checker, then confirm the signature result, the issuer and the status. Finally, make sure the name and achievement match what you were told.
Is a digital badge the same as a verifiable credential?
Not always. A badge can be just an image with a web page behind it. Open Badges 3.0 packages a badge as a verifiable credential, so some badges meet the stronger definition.
Can a verifiable credential be fake?
The record cannot be edited without breaking its signature. A real signature can still come from a disreputable issuer, so you need to judge who issued it.
Does a valid credential prove someone can do the job?
No. It shows what the issuer recorded and that the record is unchanged. Confirm the skill with a work sample or a conversation about the work.
Who maintains the standards?
The W3C publishes the Verifiable Credentials Data Model, Data Integrity and Decentralized Identifiers specifications. 1EdTech publishes Open Badges.

Sources

Check a certificate in seconds.