Skip to content

Glossary

What Is Certificate Correction Form?

In Verifycate, a certificate correction form is how a certificate holder asks for a change to their own issued certificate — a misspelt name, a new job title — for the issuer to approve or reject.

Also called: correction form, correction request, name change request

What it's for

Issued certificates have a nasty habit of being wrong in one field: the name spells "Jon" when the holder has always been "John", the job title has changed, the organisation renamed itself. The holder writes in; the issuer re-exports a file, re-uploads it somewhere, and prays the verification link doesn't break. Small fix, awkward trail.

A correction form hands the request to the person who actually knows what's wrong. They ask; you approve; the certificate changes properly — new version, same credential, history intact.

How it works

The form is linked from the holder's own certificate page, so it reaches exactly the people who can use it: holders, on their own certificates. Identity is confirmed with a one-time code to the email the certificate was issued to — a stranger can't rename someone else's certificate, because the form only exists where the holder already is.

The holder says what to change — name, and any detail the issuer exposes — leaving blank what should stay. Then the same two-way gate as every other form:

  • Apply automatically. The correction takes effect the moment it's submitted. Right when the fix is mechanical and the trust is high.
  • Review before applying. The request queues in an inbox — Correction Requests — and you approve or reject it, with a reason on rejection. Holders hear either way, in the portal, without a support thread.

One rule worth knowing before you approve: a correction is permanent. The approved change creates a new version of the certificate and the old one retires. If someone claims to be "Sir Reginald" when they were issued as "Reg", that's a decision, not a typo — approve it like one.

Corrections sit next to their siblings — the unlock form and request form — as one of the three public forms a certificate can carry, each with its own inbox. Every approved correction re-renders the certificate from the current template, so the fixed name appears everywhere it's printed. Holders track their request's state — requested, applied, rejected — in the recipient portal rather than in their email's sent folder.

Everything on this page runs in Verifycate. The first 300 certificates are free, no card. Start for free

Common questions

Does a correction change the certificate's verification link or ID?
No. The certificate keeps its ID and its page; the corrected details become the new version of that same certificate. Anything verifying it sees the current, corrected record.
Can a holder change anything they like?
Only the details the issuer chose to expose on the form. Everything else stays fixed, and with review mode on, nothing changes until you approve it anyway.
Can I stop a correction after approving it?
An approved correction is permanent — it replaces the previous version. If an approval was itself a mistake, the path is issuing a corrected version again or revoking, not undoing.
Do corrections cost credits?
No. Correcting an already-issued certificate doesn't issue a new one, so it doesn't draw on the credit balance.

Related terms

Let holders fix their own names — with your approval.

Correction requests arrive in one inbox, apply as a new version, and never spend a credit. Start with 300 free credits, no card.

We issued 2,000+ certificates for InCTF — winners, participants, the lot.” — Aravind BL, Amrita InCTF

Start for free

All glossary terms