Escrow Release Verifier

The most common way money vanishes from a real-estate or government closing is a last-minute wire change: an attacker emails the parties new "updated" disbursement instructions, and the funds are released to the wrong account. This page demonstrates a deterministic check that stops it. When a deal opens, the verified payee's wire instructions are sealed by fingerprint. A disbursement is authorized only against that fingerprint — so any swapped field flips the verdict to BLOCKED, names exactly what changed, and does it all without storing or showing a bank account number, and without accusing anyone of anything.

Release conditions

—

Try to swap the wire

These apply preset changes a fraudster would make. The check re-runs instantly in your browser.

• It states facts, not fraud. A blocked release reports that the wire differs from the verified baseline and which field changed — never a conclusion that someone committed a crime.
• No account number, ever. A wire is identified by payee + routing + a SHA-256 hash of the account number + the last four digits. The full number is never stored, transmitted, or shown.
• It moves no money. This is a proof a licensed escrow agent acts on — the check authorizes nothing and releases nothing itself.
• The same logic runs everywhere. The browser engine on this page reproduces the canonical release engine's verdict and fingerprints exactly — pinned by a parity test, so the page cannot drift.

Verify the seal yourself

Download the record, the engine, and the generator, regenerate the record, and byte-compare — the sealed fingerprint is recomputed from the declared fields, not baked in.

node generate-release-record.mjs regenerated.json
shasum -a 256 release-record.json regenerated.json   # identical

The deal parties and dollar figures are illustrative. The cryptography is real.