Confirm that a final signed LendRight PDF is byte-for-byte identical to the final document recorded by LendRight. Your browser calculates the document’s SHA-256 fingerprint on your device — the PDF itself is never sent to LendRight.
Your PDF stays on your device. Your browser calculates its SHA-256 fingerprint locally, and only the fingerprint and agreement reference are sent to Lend Right for comparison.
This is a weaker check, for when you don’t have the signed PDF on hand. Type the reference and the SHA-256 fingerprint printed on the Electronic Signing Certificate: it only confirms those printed values match a completion record — it does not inspect your actual file, so it can’t tell you the PDF you hold is unchanged. If you have the file, use “Verify document” above instead — that’s the stronger check.
A successful exact-document verification means the selected PDF is byte-for-byte identical to the final agreement recorded by LendRight when the signing process was completed. Your browser calculates a SHA-256 fingerprint from the selected file and sends only that fingerprint and the agreement reference to LendRight for comparison. Even a very small change to the file produces a different SHA-256 fingerprint.
The completion certificate and signing record separately describe the evidence collected during signing, which may include timestamps, consent records, verification methods and connection information. A successful match supports evidence of document integrity. It does not independently guarantee identity, enforceability or repayment, and it depends on the integrity of LendRight’s stored completion record and verification system.