A supplier does not change their bank account by email.
Payment redirection is the highest-value fraud in the category and the easiest to describe: one message, one new account number, one transfer that cannot be recalled. VeridLock treats a payment detail that differs from your recorded baseline as the strongest signal it has.
IBAN, SWIFT and account numbers are extracted and diffed against the vendor account you registered.
A mismatch cannot clear without human sign-off, whatever else the message looks like.
Where OCR is enabled, details inside a scanned invoice are analysed alongside the message body.
Most security controls trade a small amount of user friction for a small reduction in risk. Payment verification does not: the friction is one confirmation, and the risk it removes is the entire value of the transfer. It is the clearest cost-benefit case in the platform.
Vendor bank accounts are registered in the Trust Center as part of onboarding a supplier. From then on, any payment detail appearing in correspondence is compared against that record — a match passes without comment, and a difference is surfaced immediately with both values shown.
A bank-detail change rarely arrives alone. It usually travels with urgency, an explanation for the change and a request to keep the matter between correspondents. The content engine scores that language independently, so the combination produces a decisively higher verdict than either signal alone.
Record each vendor's bank details when the relationship is established.
Payment identifiers are pulled from message text and attachment text.
Extracted details are diffed against the baseline.
A change requires out-of-band verification before anything is sent.
The outcome
The transfer that would have been irrecoverable never leaves, because someone was asked one question first.
Set up your organization in minutes — no inbound migration required.