A broker's fee turns on one fact that is easy to dispute and hard to prove: who introduced the party to the deal, and when. Months later the counterparty says "we already knew them," or the registration email is called backdated, and the procuring-cause claim collapses. This page seals the introduction by fingerprint the moment it is registered. Rewrite the borrower, point it at a different deal, lower the fee, or move the date, and the receipt flips to ALTERED and names exactly what changed — without ever storing a contact's email or phone, and without accusing anyone of anything.
The sealed introduction
Current registration fields
Sealed fingerprint: —
Try to rewrite the registration
These apply preset changes a counterparty might make after the fact. The seal re-checks instantly in your browser.
Test a close against the protection period
Given the sealed introduction, does a later close fall inside the protection period and match the registered party and deal? This states the timing and matching facts — the evidence a procuring-cause fee turns on — never a conclusion that a fee is legally owed.
Why you can trust the receipt
- It proves content and timing, not entitlement. The receipt fixes what was registered and when; whether a fee is owed is the parties' agreement and, if disputed, a question for them — never this engine's conclusion.
- No contact details, ever. A party is identified by name + a SHA-256 hash of the contact + a non-identifying label. The raw email or phone is never stored, transmitted, or shown.
- It moves no money and collects no fee. This is a proof the broker and counterparty act on — it authorizes nothing and settles nothing itself.
- The same logic runs everywhere. The browser engine on this page reproduces the canonical introduction engine's fingerprint and verdicts exactly — pinned by a determinism 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-intro-record.mjs regenerated.json shasum -a 256 intro-record.json regenerated.json # identical
The deal parties and figures are illustrative. The cryptography is real.
DealMatcher · Bonis Systems LLC — the parties never touch the money; the proof travels with the deal.