Verified
The registered person approved this exact request on their trusted device. You can act on it.
حالات الاستخدام
Invoice fraud
When a supplier's bank details change, check the change with the supplier — not with whoever sent the email announcing it.
The problem
The email announcing the change is the attack
A compromised or spoofed mailbox sends a polite note: "our bank has changed, please update our details." The invoice is real, the amount is right, the tone is familiar. The only thing wrong is the account number, and it will not be noticed until the supplier chases payment weeks later.
What changes
Verify out of band, against the old relationship
The confirmation request goes to the supplier contact registered before the change was announced, not to the address that announced it. An attacker in the mailbox does not control that channel, and cannot approve on the supplier's behalf.
How this works
Confirming changed bank details
- A change of details arrives By email, letter, or an updated invoice.
- A verification is raised Old account, new account, invoice reference and amount, all in one request.
- The registered supplier contact answers On their own device, seeing both the old and the new details side by side.
- The answer is recorded Approved or rejected, with an audit trail that survives the dispute that follows if something later goes wrong.
Possible outcomes
Four answers, and one of them is silence
A verification request has more than two endings. Treating anything other than an explicit approval as approval is how verification systems fail people.
Rejected
The registered person saw this request and refused it. Treat it as fraudulent and report it.
Not verified
Nothing was proven, either way. Do not act on the request until you confirm it independently.
No response and Not verified are never shown as approval, and they never turn into approval by waiting.
Honest limits
What this does not fix
This depends on having registered the supplier contact before the fraud, and on that contact's own account not being compromised. It does not validate whether a bank account belongs to the company it claims to. If the supplier has no REAL AUTH account, you get no response — which means unverified, and you should still telephone a number you already had.
Related use cases
Payment fraud
Confirm the exact amount, beneficiary and destination account, bound together, before the money moves.
اعرف المزيد →Business impersonation
CEO fraud, fake suppliers, fake support desks. Check that the person is real and that they hold the authority…
اعرف المزيد →Sensitive actions
Changing a payout account, adding an administrator, issuing a production key — approve the exact change, not t…
اعرف المزيد →Try it against your own application
A free sandbox, real flows, and no card required.