Upload the file and its receipt
What verification proves
A match proves that the file in front of you is exactly the file registered at the time shown on the certificate — not a single byte changed.
Three ways to verify
Verification always compares one file with one receipt:
- File + certificate PDF — the usual way.
- File + receipt ID — when you only have the ID (for example from an e-mail).
- File + a receipt from My Receipts — when you are signed in and the receipt is in your history.
To check whether two files are identical, calculate the SHA-256 of each with the free SHA-256 tool and compare the hashes.
Verify it yourself, step by step
You can check every link of the chain with standard tools and a public blockchain explorer.
1. Hash the file. Calculate the file's SHA-256:
- Windows:
certutil -hashfile yourfile.png SHA256 - macOS:
shasum -a 256 yourfile.png - Linux:
sha256sum yourfile.png
Compare it with the SHA-256 line on the certificate. If they differ, stop: this is not the registered file.
2. Open the blockchain record. Click the Link to the blockchain record on the certificate. It opens the Polygon transaction on Polygonscan. Check that:
- it was sent from the SecureAuthor anchoring address
0xa3bb4f9ef78b51b9b9b75757f10db03705b2aabb; - the block time is after the timestamp on your certificate.
3. Read what was written. On Polygonscan, open More details → Input Data and choose View Input As → UTF-8. You will see a short JSON record:
{
"periodStart": "2026-08-16T12:00:00.027Z",
"periodEnd": "2026-10-17T12:00:00.028Z",
"periodHash": "f555a2889c47833725d6091b49a3d0288ef19e8dff3b0595267a0251d3f4a03c",
"linkToCheck": "https://api.secureauthor.com/api/daily-hash/f555a288…"
}
- your certificate's timestamp must be earlier than
periodEnd(usually it lies betweenperiodStartandperiodEnd); periodHashmust equal the Summary hash printed on your certificate.
4. Find your file in the batch. Open linkToCheck. It returns the batch list: every
receipt anchored in this transaction, with its ID, SHA-256 hash and timestamp. Your
receipt ID and your file's hash must be in the list.
5. Check that the batch list is genuine. The period hash is simply the SHA-256 of the
batch list exactly as linkToCheck returns it. Save the response to a file without
changing it and hash it:
curl -s "https://api.secureauthor.com/api/daily-hash/<periodHash>" -o batch.json
sha256sum batch.json # macOS: shasum -a 256 batch.json
# Windows: certutil -hashfile batch.json SHA256
The result must equal periodHash in the transaction. Because the transaction cannot be
changed, nobody can add, remove or alter a receipt in the batch without the hashes no
longer matching. Keep batch.json next to your certificate.
That is the whole chain: your file → its SHA-256 → the batch list → its SHA-256 = the period hash → a Polygon transaction with a block time nobody can change.
Example transaction on Polygonscan
If the hashes do not match
- Did you re-save, export or compress the file? Look for the original export.
- Was it sent through a messenger or social network? They often recompress images and video. Use the file from your own device or cloud backup.
- Is it the right version? Each version of a file has its own certificate.