How to Issue Verifiable Digital Credentials: A Plain-English Guide for Schools and Training Programs
"Verifiable digital credential" has become a common phrase in education technology, and it often arrives wrapped in jargon: DIDs, JSON-LD, proofs, chains. Underneath, the idea is simple. A verifiable credential is a certificate that anyone can check on their own, in seconds, without calling the school that issued it.
This guide explains what makes a credential verifiable, what blockchain anchoring adds (and what it does not), and the steps an institution follows to start issuing them.
What "verifiable" actually means
Think about how a hiring manager checks a paper certificate or a PDF today. They either trust it, or they email the registrar and wait. Both options are bad: one invites fraud, the other wastes everyone's time.
A verifiable credential solves this with a digital signature. When the credential is issued, it is signed with a private key that only the issuer controls. Anyone can then use the matching public key to confirm two things:
- The credential came from the issuer it names.
- Nothing in it has been changed since it was issued. Change one character, the course name or the date, and the signature no longer matches.
The W3C, the body behind most web standards, defines this format in the Verifiable Credentials Data Model 2.0. For education and training, 1EdTech's Open Badges 3.0 builds on it with a standard way to describe an achievement: its name, what it means, and the criteria someone met to earn it.
Verifiable also means revocable
Signatures prove a credential was real when it was issued. They do not, on their own, say whether it is still valid. That is the job of a status list. The W3C Bitstring Status List lets an issuer publish a compact list that marks specific credentials as revoked. A verifier checks the signature and then checks the list. If you issue a credential by mistake, you can withdraw it, and everyone who checks it afterward will see that.
What blockchain anchoring adds, plainly
Some credential platforms, including ours, also record each credential on a public blockchain. It is worth being precise about what that does.
What it gives a learner: a record of the credential that does not live only in one company's database. If the platform that issued it disappeared, a public record that the credential was issued would still exist. That is a real concern for anyone who watched a free badge service shut down.
What it gives an employer: an independent, timestamped record of when the credential was issued and by which issuing contract, which they can check without trusting the candidate or the platform's own website.
What it does not do: it does not put the learner's grades or personal details on a public ledger, and it does not ask the learner to buy cryptocurrency or manage a crypto wallet themselves. A well-built platform keeps the technical layer out of the learner's way. Learners should be able to sign up with an email address and never think about a blockchain at all.
What it is not needed for: the signature already proves authenticity. Anchoring is an extra layer of durability and independent proof, not the thing that makes a credential trustworthy in the first place.
How to start issuing verifiable credentials: five steps
Step 1: Decide what you will credential
Start with completions you already track: courses, certificates, programs, workshops. Write one sentence per credential describing what a holder can do or has completed. That sentence becomes the description and criteria, and it is what an employer reads.
Step 2: Design your credential templates
Each credential type needs a template: name, description, criteria, and the visual design the learner sees. Keep names specific ("Intro to Financial Accounting, 12 hours") rather than generic ("Certificate of Achievement").
Step 3: Connect your completion data
Decide where issuing gets triggered from:
- An LMS integration, so completions flow in without manual entry
- An API call from your LMS or an automation tool when a course is completed
- A list of emails or a CSV upload for cohorts, live events, and one-off awards
The fewer manual steps, the fewer mistakes.
Step 4: Issue, and let learners claim
The learner receives an email, signs up or signs in, and the credential appears in their profile. From there they can share a public link or add it to LinkedIn.
Step 5: Tell the people who will check it
A credential only helps if employers know they can trust it. Put a short line in your completion email and on your program page explaining that every credential can be verified online for free.
What to look for in a platform
Before you sign with any provider, confirm that:
- Credentials are issued in an open standard (Open Badges 3.0 on W3C Verifiable Credentials 2.0), so learners are not locked into one vendor's format
- Every credential is signed, and the signed document can be retrieved by a verifier
- There is a documented revocation method
- Verification is free and works without an account
- Learners need nothing but an email address to receive a credential
- Pricing is clear about what is metered
How Student Center issues credentials
Student Center builds each credential as a W3C Verifiable Credentials 2.0 document with the Open Badges 3.0 OpenBadgeCredential type, signed with an Ed25519 Data Integrity proof. Each credential has a status list entry for revocation, and the signed document is available from the credential's public endpoint. Credentials are also minted as tokens on Base, a public blockchain network, which provides the independent on-chain record described above. Network fees for issuing are included in the plan, and learners pay nothing to receive a credential.
Learners sign up with an email address. Employers and anyone else can check a credential from its public link or the Student Center verify page, free. Institutions issue by pasting emails or uploading a CSV, in bulk to existing learners, through the TalentLMS integration, or through an issuance API that an LMS or Zapier can call. You can see how issuing works on the institutions page.
If you are curious how other teams use the Base network for things beyond credentials, our sister marketplace dPlaza writes about it on the dPlaza blog.
The short version
A verifiable credential is a signed, standard digital certificate that anyone can check on their own. Revocation keeps it honest after issuance. Blockchain anchoring adds an independent, durable record, but the signature is what proves authenticity. To start issuing, define your credentials, build templates, connect your completion data, let learners claim, and tell employers that checking is free.
