How QR certificate verification works

The flow

1. Issue: when a certificate is created (for a diamond, a course, a product batch), the system calculates its hash, a unique fingerprint of the document.
2. Record: the hash, certificate ID and timestamp are written to a blockchain ledger.
3. Print: a QR code linking to a verification page is printed on the certificate or packaging.
4. Verify: anyone scans the QR code. The page shows the recorded details and checks that the certificate's hash matches the one on the ledger.
5. Result: "Verified: unchanged since issue" or "Mismatch: this document has been altered".

What the verifier sees

• Certificate ID and key details
• Issuer name
• Issue date
• Event history, such as transfers or status changes
• Verification status

Privacy

Personal or commercially sensitive data doesn't need to be on the ledger. Usually only the hash and minimal reference data are stored on-chain, with full details kept in a secure database.

Limitations

Verification proves the document hasn't changed since it was recorded. It does not prove the original information was correct, which still depends on the issuer's processes.