AntifrogACADEMYExplore Antifrog ↗
Theory Lesson 22
BANKING / 5 MIN

A match is a useful boundary

Verify the destination without treating a name match as a verdict on intent.

01

What is being compared

Verification of Payee checks supplied payee information against information held for the receiving account through the participating providers. Responses can distinguish a match, close match, no match or a check that could not be completed. These outcomes should remain distinguishable in both interface and records.

02

What is not established

A matching name does not establish that the invoice is genuine, the seller is honest or the customer is free from manipulation. Destination verification answers a narrower question. It is useful evidence, but expanding it into a blanket assurance of safety gives the user the wrong mental model.

03

A changed supplier account

A finance team receives new account details in an email that appears to come from a regular supplier. Even if the entered name matches the receiving account, the team should still follow its trusted process for verifying the requested change through an independently established contact channel.

04

Explain uncertainty accurately

A check that could not run is not the same result as a confirmed mismatch. Provide the relevant explanation and next step instead of colouring both outcomes as identical failures. Record the returned status and user journey so later reviewers can see what information was available at decision time.

Check your understanding

A supplier’s new account name matches. What remains unresolved?