Verifiable Certificates: Making a PDF Mean Something
Signing, a public verification page, and an issuance record — the difference between a credential an employer can check and an image anyone can edit.
A generated PDF with a learner's name on it can be reproduced by anyone with an image editor in minutes. What gives a certificate value is not its design but the ability to verify it at its source.
The unique identifier is the foundation
Give every certificate a random, non-sequential identifier. A sequential one reveals how many you have issued and lets people guess at others. Print it on the certificate as both text and a QR code, because copying or scanning is the first thing a verifier does.
A public verification page
- A stable URL per certificate that opens without login — an employer will not create an account to check.
- Showing only learner name, course, issue date, and issuing body, and nothing else.
- Showing status explicitly: valid or revoked, because revocation has to be visible.
- No browsing or searching of certificates — verification of a known identifier only.
Signing prevents editing, not copying
Digitally sign the certificate data and store the signature with it, so any change to name or date becomes detectable. It does not stop someone passing off a valid certificate as their own — that is what the verification page prevents, because the name shown comes from your records rather than from the file.
A certificate that cannot be checked against its issuer is a nice picture, not a credential.
Issuance is an event, not a file
Do not regenerate the certificate from live data on every download. Record an issuance event that freezes the name, course, date, and the completion criteria in force at the time. Renaming a course later must not alter a certificate issued a year ago — the certificate documents what happened then.
Revocation needs an announced policy
One day you will need to revoke: discovered cheating, or an issuance error. Define who holds that power, log the reason, time, and actor, and surface the status on the verification page. Silent deletion is worse than revocation, because it makes a published link fail with no explanation.
If you want a credential a third party can verify without asking you, the standard is W3C's Verifiable Credentials data model, and its practical application in education is 1EdTech's Open Badges.
If you are building an education product whose certificates depend on trust, the verification page is what turns them from decoration into value. Talk to us.
FAQ
Do I need a blockchain for this?
Usually not. A verification page on your own domain achieves the goal; blockchain matters when the issuer itself is not meant to be trusted.
What if a learner changes their name?
Issue a new certificate with a new identifier and revoke the old one with a recorded reason, rather than editing an issued record.
Is a QR code worth including?
Yes — it is the shortest path from a printed certificate to the verification page, and most verifiers are looking at paper.