Running a programme · For a brand's operations team
Certificates
A certificate batch is a run of codes for a document rather than a product — a degree, a calibration report, a training certificate. The issuer uploads its records first, and each record gets its own code.
How it works #
- On the product's page, start a new batch, choose Certificate and download the Excel template:
record_id,name,certified_on,expiry_date, and up to twelve columns of your own — College, Degree, Marks. - Fill in one row per certificate and upload it. The preview writes nothing; a file with any rejected row issues nothing, so nobody on the list is left out.
- Confirm the count and issue. Each record gets its own code, in the order of your file — one credit per certificate.
- Print the export. The record ID sits beside each QR and names each QR file, so every code finds its own document. Then activate the batch: until then a scan says "not found".
- To correct a name later, download the batch's own records from its page, fix them and upload. Rows are matched by record ID.
What the verifier sees #
GENUINE when the certificate is on the issuer's record, and a separate Status — Valid or Expired — because being authentic and still being valid are two different questions. A revoked certificate says REVOKED in red, never GENUINE. Below it: the holder's name, the record ID, the dates, and your own fields under your own column names.
Why a forged QR cannot lie #
The QR carries nothing but an opaque code. Every field a verifier reads is fetched from the issuer's record at scan time. The worst a forger can do is point at a real certificate — which then shows the real holder's name, and does not match the paper in their hand.
It shows nothing beyond the certificate #
No scan count, no location, no "verified 14 times", no other certificate. A verification page that leaks how often a degree has been checked is a page that tells an employer who else is hiring. A code on a batch that is not activated yet answers exactly like an unknown one.
Revocation #
Revoking needs a reason, shows on the public page immediately, and can be undone — revoking the wrong record is a mistake a person makes at a keyboard. Both actions are audited, and the undo is its own action rather than an edit.
Last reviewed 21 Sep 2026 · Something wrong? connect@avrascan.com