Verifying the payee and proving what the payer saw are different jobs
A title agency verifies the receiving account thoroughly, and the buyer still wires to a different one — because the buyer was never looking at the verified instructions in the first place.
Does verifying the payee stop closing wire fraud?
It stops one half. Account verification services such as CertifID confirm that a bank account belongs to who it claims to — the agency's side. Most residential losses happen on the buyer's side, where different instructions were substituted before the wire was ever sent.
- Account verification operates on the agency's side and answers whether a given account is legitimate.
- The diversion happens on the buyer's side, where a different set of instructions was substituted before the wire was sent.
- The two controls address different halves of the transaction and are strongest deployed together.
Part of Title, escrow and closing wires
Splitting the transaction in two
A closing wire has two sides, and each has its own failure mode.
| Side | Question | Failure mode |
|---|---|---|
| Agency → destination | Is this account legitimately the payee's? | Funds sent to a fraudulent account by the agency |
| Buyer → agency | Which instructions was the buyer looking at? | Buyer wires to an account the agency never published |
Account verification services address the first row well. Ownership checks, bank confirmation and payee matching are exactly right for that question.
The second row is where most residential closing losses occur, and it is structurally outside what account verification can see. The agency never sees the fraudulent instructions because they were never sent to the agency.
Following the money in a typical diversion
- The agency prepares correct instructions and verifies its own account.
- The attacker, reading the buyer's or agent's mail, learns the amount and date.
- The attacker sends the buyer a lookalike message with different account details.
- The buyer instructs their bank using those details.
- The funds arrive at the attacker's account. The agency's verified account was never involved.
At no point does the agency's verification engage. It confirmed a fact about an account that the transaction bypassed entirely.
What a payer-side receipt adds
The complementary control records what the buyer was shown and confirms they saw it.
# Agency side — account verification
payee account → ownership confirmed, name match, bank confirmed
# Buyer side — seen-and-signed receipt
instructions rendered from the agency's issued statement
buyer signs on their own device with user verification
receipt → agency, lender, buyer's bank
# Together:
the account is real AND the buyer saw the real instructions
Neither is redundant. An agency could verify a fraudulent account it was itself deceived into using; a buyer could sign instructions for an account the agency never checked. Both controls cover the other's blind spot.
Comparing the two honestly
| Property | Account verification | Payer-side receipt |
|---|---|---|
| Covers | Agency → payee | Buyer → agency |
| Detects | Fraudulent or mismatched accounts | Buyer looking at substituted instructions |
| Requires from the buyer | Nothing | One signing action on their device |
| Evidence after a loss | The account was checked | What the buyer saw and confirmed |
| Works if the buyer is phoned directly | No | Yes — there is a canonical artefact to check against |
| Works if the agency is deceived about the account | Partially — that is its purpose | No — it records what was issued |
Read the last two rows together. Each control fails exactly where the other holds.
The integration question
In practice a title agency should not be running two separate processes. The workable arrangement is one flow where the agency's verified account details are what get rendered into the statement the buyer signs.
- Agency verifies the destination account as it does today
- The verified details populate the statement issued to the buyer
- The buyer signs that statement on their own device
- The receipt references both the verification result and the buyer's confirmation
That produces a single artefact answering both questions, which is what a lender, an insurer or a court would want to see.
What neither control does
Neither prevents a buyer who ignores the process. A determined attacker on the phone, with a convincing story and time pressure, can persuade someone to act outside any system.
Neither recovers funds after the fact. Speed of detection matters enormously for recall, and both controls improve detection speed — a mismatch surfaces before the wire rather than at closing.
And neither addresses the initial mailbox compromise, which is where these attacks begin. That is an email security problem, and the reason both controls exist is that mailbox compromise keeps happening anyway.
Following the money in a typical diversion
The agency prepares correct instructions and verifies its own account. An attacker reading the buyer's or agent's mail learns the amount and date, then sends the buyer a lookalike message with different details. The buyer instructs their bank using those details. The funds arrive at the attacker's account, and the agency's verified account was never involved.
| Scenario | Account verification | Payer-side receipt |
|---|---|---|
| Agency uses a fraudulent account | Catches it | Records what was issued |
| Buyer is redirected by a lookalike email | Never engages | Catches it |
| Buyer is phoned and redirected | Never engages | Gives the buyer a rule to follow |
| Buyer ignores the process entirely | Never engages | Records what they were given |
Objections and honest limits
“So we should choose one.” Neither is redundant. An agency could verify a fraudulent account it was itself deceived into using; a buyer could sign instructions for an account the agency never checked. The workable arrangement is one flow where the verified account details populate the statement the buyer signs.
“Neither recovers the funds.” Correct. Both improve detection speed, which is where recovery outcomes are actually determined — a mismatch surfaces before the wire rather than at closing.
Running both as one flow
- Verify the destination account as you do today. Unchanged.
- Populate the buyer's statement from the verified details. So the two controls cannot disagree.
- Have the buyer sign on their own device. One gesture, rendering the instructions they are about to act on.
- Keep both results in one receipt. Verification outcome and buyer confirmation, on the file.
Terms used here
- Payee verification
- Confirming that a bank account belongs to the party it claims to, typically by ownership check and name match.
- Payer-side receipt
- Evidence of what the person sending funds was shown, and that they confirmed it, captured before the wire leaves.
- Diversion
- Redirecting a legitimate payment to an attacker's account, usually by substituting instructions rather than by breaching a system.
Frequently asked questions
Is account verification not enough? It answers whether an account is legitimate, which is the agency's side. Most residential losses happen on the buyer's side, where different instructions were substituted.
Do we need both? They cover each other's blind spots. Account verification fails when the buyer is redirected; the payer receipt fails if the agency itself was deceived about the account.
How much does the buyer have to do? One signing action on their own device, rendering the instructions they are about to act on.
Does this recover diverted funds? No. It improves the chance of catching the mismatch before the wire, which is where recovery outcomes are actually determined.
Where this fits in Manav
Manav is the payer-side half: the agency's verified account details are rendered into a statement the buyer signs on their own device, and the resulting receipt sits on the file alongside the verification result.