Certificate QR verification and signed data
Choose a QR payload, test readability, minimise personal data and understand Ed25519 integrity.
The practical rule
A QR code should make verification easier, not become an extra database of personal information. The safest option contains a number or a verification link; a signed data package should be used only when the disclosure is understood.
Always test scanning after PDF export, because size and background can change the real-world result.
Recommended workflow
- 1
Choose number, link, data or signed package mode.
- 2
Limit the payload to information needed for verification.
- 3
Use strong contrast and a sufficient code size.
- 4
For integrity, generate an Ed25519 key and keep the private key outside the document.
- 5
Scan the code from both screen and a test print.
- 6
Explain what verification proves and what it does not prove.
Example and decision criteria
A practical QR can point to a verification page with the certificate number. A signed package can reveal later changes to data, but it does not by itself prove the real-world identity of the issuer.
Mistakes to avoid
- including unnecessary personal information
- a code that is too small or low contrast
- printing the code over decorative artwork
- confusing data integrity with issuer identity
Create a document now
Use a ready template, import data and export a test PDF locally.