A verification QR code should lead to a stable record that confirms exactly what was issued. The QR image itself is only a link. Trust comes from the verification page, the issuer information behind it, and a unique record that cannot be reassigned to another recipient.
What a verification record should contain
- A unique certificate identifier that is never reused.
- The recipient name, certificate title, issue date, and issuing organization.
- A clear status such as valid, revoked, corrected, or expired.
- A way to distinguish an updated certificate from the original record.
A verifier should not need an account to check a certificate. However, issuers should sign in before creating verification records so ownership, limits, and corrections can be managed securely.
Protect recipient privacy
Publish only the information needed to verify the credential. Do not expose recipient email addresses, spreadsheet columns, phone numbers, or internal notes. If a certificate contains sensitive information, use a random unguessable identifier and consider showing only a partial name until the verifier enters an additional value.
Make the QR code reliable
- Use a high-contrast dark QR code on a light background.
- Keep a quiet white margin around the code.
- Do not make the code too small; test it from a printed page and a phone screen.
- Use a permanent HTTPS URL on a domain you control.
- Open several generated files before distributing a large batch.
Correcting or revoking a certificate
Do not silently replace verification data. Mark the old record as corrected or revoked, then issue a new identifier. This preserves an audit trail while preventing an outdated certificate from appearing valid.
Verification in a bulk workflow
When creating a large batch, every recipient needs a different verification URL and QR image. Generate the records first, confirm that the expected count exists, and then render the certificates. If any record fails, stop the export and show the exact recipients that need to be retried rather than producing blank QR areas.
Cert Generate can create unique verification records for signed-in issuers during the certificate generation workflow. Always review a sample of the final files before emailing or printing the full batch.