Check a receipt
Nothing is uploaded. Your files are read and checked on your own computer. The only thing this page requests from the network is our published public key.
Choose a receipt.json file to begin.
Build your own verifier
The record format is an open specification (text CC BY 4.0, test vectors CC0): every field, the canonicalization, signature, timestamp and criteria-commitment rules, and five test vectors. Any party can implement a verifier without our software. See the acceptance record specification, and the model acceptance clause a buyer can adapt.
What a valid receipt tells you
- Signature valid: the receipt was issued by Trilatic with the key published at /.well-known/trilatic-receipt-key.json and has not been changed since.
- Delivered file matches: the PDF you hold is byte for byte the file that was checked. Change one byte and this fails.
- Timestamp present: an independent public time-stamp authority recorded the receipt’s fingerprint, so it cannot be backdated. If the authority could not be reached when the receipt was issued, the receipt says “none”; it is still signed.
- Human review: a receipt starts as “pending”, covering the automated criteria only. A reviewer’s result is added by issuing a new revision of the same receipt.
Each criterion result is one of pass, fail, not-evaluated or error. The page shows each as “Check passed”, “Check failed”, “Check not evaluated” or “Check error”. The overall result reads “All listed automated checks passed” only if every required check passed; “One or more listed checks failed” if one did not; and “Incomplete: some required checks not evaluated” otherwise, never a pass. This page also shows who the checker was, whether the file’s producer is a different party (a receipt for a file Trilatic produced itself is marked self-checked), whether the criteria file still matches the hash in the receipt, and whether the criteria were committed before the check (the criteria document and its timestamp are public).
A receipt reports outcomes against the public acceptance criteria for the named files only. It is not a compliance determination and not legal advice. This page checks the signature and the file hash; it does not validate the time-stamp authority’s own signature, which you can do with the stored .tsr file and standard tools.
Try it with a sample
Download a sample receipt, then choose it above. Add the matching delivered PDF to see the file check match, or any other PDF to see it not match.
- Passing: receipt.json, receipt.tsr, delivered PDF, receipt summary (PDF)
- Passing: receipt.json, receipt.tsr, delivered PDF, receipt summary (PDF)
- Failing file: receipt.json, delivered PDF, receipt summary (PDF)
- Self-checked (the file was produced by the checker itself; the page shows a warning): receipt.json, receipt.tsr, delivered PDF
- Earlier format (schema /1.1, still verified): receipt.json, receipt.tsr, delivered PDF
- Earlier format (schema /1, still verified): receipt.json, receipt.tsr, delivered PDF
Current receipts (schema /1.2) declare their canonicalization (JCS, RFC 8785), their digest and signature suite, who checked and who produced the file, and the criteria they were checked against, whose hash was publicly timestamped before the check. The sample files are public Maryland State Board of Elections reports.