SmartCheck
The public verification page
Anyone can check evidence of yours without asking you, and without you showing them the document.
Evidence only you can check is of little use. Hence a public page where anyone — a client, an auditor, an expert witness, a court — can check for themselves whether something is sealed, with no account, without asking you, and with you taking no part.
How it works, in one sentence
Important
The check runs **on the file's fingerprint, not on the file**. Whoever verifies does not upload your document anywhere: they compute its fingerprint and look it up. The practical consequence is twofold — you share the content with nobody in order to be believed, and the page cannot show what the document says, because it does not have it.
What the page finds
| If the hash matches… | What it shows |
|---|---|
| A certified piece of evidence | That it exists and since when it has been sealed |
| A document version | That this specific version is registered |
| A traceability event | The sealed event and its moment |
| A sealing batch | Everything that batch sealed, not just one item |
| Nothing | That there is no record: which is also an answer |
The two ways in
- 1
With the QR
Scan it and it goes straight to that item's check. It is what goes on a delivery note, a label or a report.
- 2
With the fingerprint
Whoever holds the file computes its fingerprint and checks it. You need not send them any link.
Watch out
The case that wrong-foots first-time users: if the file has been re-saved, compressed, or printed and scanned, **the check will say there is no record** even though it reads identically. That is not a failure: it is exactly the point. So when you send evidence to a third party, send the file as it is, without shrinking it.
What the page does NOT show
That is precisely why it can be left public: it shows that something is sealed and since when, not what it says or whose it is.
Worth knowing
Generating the public QR is an action and consumes, like certifying. Putting it where someone will actually scan it — a label, a certificate, a report that goes outside — pays; putting it on everything by default does not.
›Does it still work if we stop being customers?
The check is on the fingerprint and the seal; it does not depend on you staying.
›Can someone verify something we never gave them?
Only if they have the file or the link. Without the fingerprint there is nothing to look up.
›What if the page says there is no record?
Either the file changed or it was never sealed. Both are useful information.
A real case
The situation
A client doubts whether a certificate you sent is the original.
What you do
- You tell them to check the file's fingerprint on the public page
What you get
They verify it themselves in a minute, with nothing more to send and no access to grant.
The situation
A client wants to verify without asking you for anything.
What you do
- Gives them the verification reference
What you get
They verify themselves, with no intermediary.
The situation
There is a fear that verifying requires showing the document.
What you do
- Verifies with the fingerprint alone
What you get
Verification does not reveal the content.
The situation
The verifier does not know what the result means.
What you do
- Explains exactly what it asserts
What you get
The proof is not credited with more than it says.
The situation
The check errors because of a re-saved file.
What you do
- Verifies the original without opening it
What you get
The result is correct.
The situation
You want a record that somebody verified.
What you do
- Records who was given the reference
What you get
The handover is documented too.
This article answers
- how a third party verifies a sealed document
- public authenticity check page
- what the verification qr shows
- checking a seal without an account