The email is genuine. The request inside it is not.
One root, many frauds
Every fraud below works the same way: someone impersonates a trusted party to trigger an action, a payment, a change of details, the acceptance of a document. They are one problem wearing different clothes.
$55bn+
One shape behind all of them
Nine situations, one shape: the channel is authentic and the instruction inside is not the organisation’s. Each card says what can be established TODAY — and each of those answers is bounded by the same fact: the questions are built, and no organisation is enrolled.
Nine names, one question
Open the situation you are in.
What settles all of them
The same question settles all of them, and it has a clear yes-or-no answer, not a matter of opinion.
When the channel is a live call
Someone calls — your bank, a director, head office — and asks you to act in the minute: move money, change bank details, approve an exception. A voice cannot be sealed. So the answer is not to seal the call; it is to make the caller prove, in that same minute, who they are.
During the call, the real party sends you a sealed proof — a link you open in seconds, with no account — that reads: your contact is this person, this role, of this organisation; the organisation vouches for them; they have just made a request concerning you, with the moment and a fresh element tied to this exchange. A stranger holds neither the organisation’s key nor an enrolled device, so the proof does not come. No valid proof means it is not them — ask for it every time.
What Atestan does not do here. It does not seal a voice, and it does not move onto the payment rails to stop a transfer. It makes a request made over a live channel verifiable, and it lets the real organisation set one habit: a genuine instruction always arrives with its proof; no proof, not us.
The phone check that goes with the proof
For bank-detail changes above all: call the supplier on a number you already had, never the number in the request, and confirm one detail with the spoken code. The code reveals nothing by itself; it confirms, it does not give anything away.
CEO fraud, supplier impersonation, a redirected payroll, a property sale diverted at the last minute: the attacker’s job is always the same, make a request nobody approved look ordinary. And the question that exposes it never changes: what evidence is there for this request?