Loading...
Loading...
Change one character in a document. Watch the cryptographic hash shatter. This is how Truthlocks detects every tamper, every time.
100% client-side using the Web Crypto API. No data leaves your browser.
{
"receipt_id": "rcpt_8f3a2b1c-e4d5-4a6f-b7c8-9d0e1f2a3b4c",
"type": "verification.completed",
"timestamp": "2026-04-07T14:32:18.042Z",
"subject": {
"entity_type": "document",
"entity_id": "doc_f47ac10b-58cc-4372-a567-0e02b2c3d479",
"name": "Q1-2026-Financial-Report.pdf"
},
"issuer": {
"org_id": "org_truthlocks_inc",
"key_id": "key_ed25519_prod_2026Q2",
"algorithm": "Ed25519"
},
"claims": {
"content_hash": "sha256:b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9",
"authorship_verified": true,
"tamper_detected": false,
"confidence_score": 0.9987
},
"metadata": {
"sdk_version": "2.4.1",
"verification_latency_ms": 38,
"transparency_log_index": 1048576
}
}Every receipt is hashed with SHA-256. The hash is uniquely determined by the content — change a single bit and the entire hash changes unpredictably.
Recompute the hash at any time, on any machine. If it matches the stored digest, the data is provably untampered. No trust required — only math.
In production, Truthlocks layers Ed25519 signatures, Merkle tree anchoring, and multi-witness attestation on top of SHA-256 for forensic-grade non-repudiation.
Integrate cryptographic verification into your application in minutes with the Truthlocks SDK and REST API.