Sector playbooks
Voice and video are no longer proof of identity
Fraudsters have cloned the voice of a Jersey Chief Minister and a lawyer trusted by an Italian private bank. If your payment controls rely on recognising a voice or a face, they no longer work. Here is what does.
By Seb Lawson · 29 September 2026 · 4 min read
If your payment controls rely on recognising a client’s voice or face, they stopped working. AI can now clone both well enough to fool people who know the real person. The defence is not a detector. It is a process nobody can talk their way past.
Three cases worth knowing
Jersey. In 2025 a deepfake video of the Chief Minister, with an AI-generated voice and a fake Jersey Evening Post article, promised islanders £800 a week for a £200 stake in a government scheme that did not exist. In September the JFSC said reports of online fraud had tripled in three years, and pointed to AI as part of the reason.
Italy. According to an OECD incident record, fraudsters this February cloned the voice of a trusted lawyer and used a fake WhatsApp message and a phone call to deceive the then-president of the private bank Fideuram. Transfers followed, and the record puts the loss in the tens of millions of euros.
Hong Kong. In 2024 an employee at the engineering firm Arup joined a video call with what looked and sounded like the company’s CFO and several colleagues. Every one of them was a deepfake. By the end of the call the employee had made 15 transfers worth about US$25 million.
Look at what each attacker relied on. Authority: a minister, a lawyer, a CFO. Urgency: act now, keep it quiet. And a channel outside the normal process: a social media video, a WhatsApp message, a surprise video call. Those three are your warning signs. The technology changes every month. The pattern does not.
The control set
None of this is new. All of it is now essential. The rule underneath it: no payment, new payee or change of bank details moves on the strength of a voice or a face alone.
- Call back on the number on file. Never the number in the email, the message or the caller’s signature. If the number on file is the thing being changed, verify through a second, older channel.
- A challenge phrase for your highest-value clients. Agreed in person, stored securely, never sent by email. A clone can copy a voice. It cannot know a phrase it never heard.
- Two people release anything above a threshold. Set the threshold at the level of payments that would hurt, not just the ones that look odd.
- A cooling-off window on new payees. A day’s wait on a new account unless it is verified in person. Genuine urgency survives a day far more often than fraudsters would like.
- Written confirmation through your client portal. Not email, which can be spoofed or compromised. A channel you control.
Apply all of it with zero exceptions for seniority. The calls that work are the ones that sound like the most senior person in the room.
And they will impersonate you
The same tools work in the other direction. This year the JFSC has warned about scammers posing as bank fraud teams and impersonating a real Jersey investment firm, using real names, cloned websites and, the Commission warned, even AI-generated images or voices. Tell your clients now, in writing, how you will contact them about money and how you never will. A client who knows you never change bank details by phone is a client who hangs up.
Where automation earns its place
AI is useful on the defence side, just not as a detector. Its job is the dull part: making sure the verification happens every single time, and proving that it did.
A payment instruction workflow reads every inbound instruction and flags the ones that fit the pattern: a new payee, a changed account, unusual urgency, a first payment to a new jurisdiction, a request arriving by an unusual channel. It then forces the verification steps before the instruction can move, and records who verified what, when and how. The person still makes the call. The system makes it impossible to skip. That record also answers the first question any regulator or insurer will ask after an incident.
This is a tight, well-bounded build, exactly the kind of smallest painful workflow we would pick first. It sits naturally alongside KYC and client take-on, and it follows the same rule as everything else we build: a human makes the decision, and the system keeps the record.
Train with a live demonstration
One 30-minute session in which your team hears a cloned voice of someone they know will do more than a year of e-learning. With a willing partner’s consent, clone their voice from a short public clip and play it to the team. The point lands in about ten seconds.
The targets
100% of new or changed payment instructions verified on a second channel and logged. Under five minutes added to each one. Zero exceptions for seniority. Year-end is busy, and busy is when checks get skipped. Set these before December, not after.
If your instructions arrive by email and get verified by memory, that is the workflow to fix first. We build the verification workflow and its audit trail together. To talk it through, book a review.