{"id":852,"date":"2026-10-19T22:59:35","date_gmt":"2026-10-19T11:59:35","guid":{"rendered":"https:\/\/nexiant.ai\/resources\/blogs\/?p=852"},"modified":"2026-10-19T23:03:11","modified_gmt":"2026-10-19T12:03:11","slug":"deepfake-executive-fraud-payment-controls","status":"publish","type":"post","link":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/","title":{"rendered":"Why Deepfake Executive Fraud Needs Payment Controls as Well as Identity Checks"},"content":{"rendered":"\n<style>\n  .nx-blog * { box-sizing: border-box; margin: 0; padding: 0; }\n  .nx-blog { font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif; font-size: 16px; line-height: 1.75; color: #1a1a2e; max-width: 820px; margin: 0 auto; }\n  .nx-blog h2 { font-size: 1.55rem; font-weight: 700; color: #00184C; margin: 2.5rem 0 0.75rem; padding-bottom: 0.4rem; border-bottom: 3px solid #073EA1; }\n  .nx-blog h3 { font-size: 1.15rem; font-weight: 700; color: #073EA1; margin: 1.75rem 0 0.5rem; }\n  .nx-blog h4 { font-size: 0.98rem; font-weight: 700; color: #00184C; margin: 1.25rem 0 0.35rem; }\n  .nx-blog p { margin-bottom: 1rem; }\n  .nx-blog ul, .nx-blog ol { margin: 0.5rem 0 1rem 1.4rem; }\n  .nx-blog li { margin-bottom: 0.4rem; }\n  .nx-blog strong { color: #00184C; }\n\n  .nx-hero { background: linear-gradient(135deg, #00184C 0%, #073EA1 100%); color: #fff; border-radius: 12px; padding: 1.75rem 2rem; margin-bottom: 2rem; }\n  .nx-hero .nx-tag { display: inline-block; background: rgba(255,255,255,0.15); color: #AEC9FF; font-size: 0.75rem; font-weight: 600; text-transform: uppercase; letter-spacing: 0.08em; padding: 4px 12px; border-radius: 20px; margin-bottom: 0.6rem; }\n  .nx-hero .nx-meta { font-size: 0.95rem; color: #AEC9FF; margin: 0; }\n\n  .nx-callout { border-left: 4px solid #073EA1; background: #f0f4ff; border-radius: 0 8px 8px 0; padding: 1rem 1.25rem; margin: 1.5rem 0; }\n  .nx-callout.nx-callout--warning { border-left-color: #A30000; background: #fff5f5; }\n  .nx-callout .nx-callout-title { font-size: 0.8rem; font-weight: 700; text-transform: uppercase; letter-spacing: 0.07em; color: #073EA1; margin-bottom: 0.4rem; }\n  .nx-callout.nx-callout--warning .nx-callout-title { color: #A30000; }\n  .nx-callout p { margin: 0; font-size: 0.95rem; color: #1a1a2e; }\n\n  .nx-media { margin: 1.5rem 0 1.75rem; }\n  .nx-media img { width: 100%; height: auto; display: block; border-radius: 12px; border: 1px solid #d0daf5; background: #f5f8ff; }\n  .nx-media .nx-caption { font-size: 0.82rem; color: #666; text-align: center; margin-top: 0.6rem; line-height: 1.5; font-style: italic; }\n\n  .nx-flow { display: grid; grid-template-columns: repeat(4, 1fr); gap: 12px; margin: 1.5rem 0 1.75rem; position: relative; }\n  .nx-flow-step { background: #fff; border: 1px solid #d0daf5; border-radius: 12px; padding: 1rem; text-align: center; position: relative; }\n  .nx-flow-step::after { content: \"\u2192\"; position: absolute; right: -14px; top: 50%; transform: translateY(-50%); color: #073EA1; font-weight: 700; font-size: 1.2rem; }\n  .nx-flow-step:last-child::after { display: none; }\n  .nx-flow-number { width: 30px; height: 30px; border-radius: 50%; background: #073EA1; color: #fff; font-size: 0.8rem; font-weight: 700; display: flex; align-items: center; justify-content: center; margin: 0 auto 0.6rem; }\n  .nx-flow-step h4 { font-size: 0.9rem; color: #00184C; margin-bottom: 0.35rem; }\n  .nx-flow-step p { font-size: 0.8rem; color: #555; margin: 0; line-height: 1.5; }\n\n  .nx-grid { display: grid; grid-template-columns: repeat(auto-fit, minmax(185px, 1fr)); gap: 12px; margin: 1.25rem 0 1.75rem; }\n  .nx-card { background: #fff; border: 1px solid #d0daf5; border-radius: 10px; padding: 1rem; }\n  .nx-card-icon { width: 36px; height: 36px; border-radius: 8px; background: #073EA1; display: flex; align-items: center; justify-content: center; margin-bottom: 0.6rem; }\n  .nx-card-icon svg { width: 18px; height: 18px; fill: #fff; }\n  .nx-card h4 { font-size: 0.88rem; font-weight: 700; color: #00184C; margin-bottom: 0.2rem; }\n  .nx-card p { font-size: 0.8rem; color: #555; margin: 0; line-height: 1.5; }\n\n  .nx-table-wrap { overflow-x: auto; margin: 1.25rem 0 1.75rem; }\n  .nx-table { width: 100%; border-collapse: collapse; font-size: 0.9rem; }\n  .nx-table thead tr { background: #00184C; color: #fff; }\n  .nx-table th { text-align: left; padding: 10px 14px; font-weight: 600; }\n  .nx-table td { padding: 9px 14px; border-bottom: 1px solid #e0e7f5; color: #1a1a2e; vertical-align: top; }\n  .nx-table tbody tr:nth-child(even) { background: #f5f8ff; }\n  .nx-badge { display: inline-block; font-size: 0.73rem; font-weight: 600; padding: 2px 9px; border-radius: 20px; }\n  .nx-badge--red { background: #fde8e8; color: #A30000; }\n  .nx-badge--blue { background: #EEF2FF; color: #073EA1; }\n\n  .nx-signal-panel { background: #f5f8ff; border: 1px solid #d0daf5; border-radius: 12px; padding: 1.25rem; margin: 1.5rem 0 1.75rem; }\n  .nx-signal-panel h3 { margin-top: 0; color: #00184C; }\n  .nx-signal-grid { display: grid; grid-template-columns: repeat(auto-fit, minmax(180px, 1fr)); gap: 10px; margin-top: 1rem; }\n  .nx-signal { background: #fff; border-radius: 10px; padding: 0.9rem; border-left: 4px solid #073EA1; }\n  .nx-signal strong { display: block; font-size: 0.88rem; margin-bottom: 0.25rem; }\n  .nx-signal span { font-size: 0.8rem; color: #555; line-height: 1.5; }\n\n  .nx-scenario { background: linear-gradient(135deg, #00184C 0%, #073EA1 100%); color: #fff; border-radius: 12px; padding: 1.5rem; margin: 1.75rem 0; }\n  .nx-scenario h3 { color: #fff; margin-top: 0; margin-bottom: 0.6rem; }\n  .nx-scenario p { color: #E7EFFF; margin-bottom: 0.8rem; }\n  .nx-scenario ul { margin-bottom: 0; }\n  .nx-scenario li { color: #E7EFFF; }\n\n  .nx-stack { margin: 1.5rem 0 1.75rem; }\n  .nx-stack-layer { display: flex; align-items: flex-start; gap: 14px; background: #fff; border: 1px solid #d0daf5; border-radius: 12px; padding: 1rem; margin-bottom: 10px; }\n  .nx-stack-icon { width: 38px; height: 38px; border-radius: 10px; background: #073EA1; color: #fff; font-weight: 700; font-size: 0.85rem; display: flex; align-items: center; justify-content: center; flex-shrink: 0; }\n  .nx-stack-layer h4 { margin: 0 0 0.25rem; color: #00184C; font-size: 0.95rem; }\n  .nx-stack-layer p { margin: 0; font-size: 0.86rem; color: #444; line-height: 1.6; }\n\n  .nx-obligations { margin: 1.25rem 0 1.75rem; }\n  .nx-obl-item { background: #fff; border: 1px solid #d0daf5; border-left: 4px solid #073EA1; border-radius: 0 10px 10px 0; padding: 1rem 1.25rem; margin-bottom: 10px; }\n  .nx-obl-item h4 { font-size: 0.93rem; font-weight: 700; color: #00184C; margin-bottom: 0.3rem; }\n  .nx-obl-item p { font-size: 0.87rem; color: #444; margin: 0; line-height: 1.6; }\n\n  .nx-inline-link { color: #073EA1; text-decoration: underline; font-weight: 600; }\n  .nx-inline-link:hover { color: #00184C; }\n\n  .nx-faq { margin: 1.25rem 0 1.75rem; }\n  .nx-faq-item { border: 1px solid #d0daf5; border-radius: 8px; margin-bottom: 8px; overflow: hidden; }\n  .nx-faq-q { width: 100%; background: #fff; border: none; text-align: left; padding: 1rem 1.25rem; font-size: 0.95rem; font-weight: 600; color: #00184C; cursor: pointer; display: flex; justify-content: space-between; align-items: center; gap: 1rem; }\n  .nx-faq-q:hover { background: #f5f8ff; }\n  .nx-faq-q .nx-chevron { flex-shrink: 0; width: 20px; height: 20px; border-radius: 50%; background: #EEF2FF; display: flex; align-items: center; justify-content: center; transition: transform 0.25s; }\n  .nx-faq-q .nx-chevron svg { width: 10px; height: 10px; stroke: #073EA1; fill: none; }\n  .nx-faq-q[aria-expanded=\"true\"] .nx-chevron { transform: rotate(180deg); background: #073EA1; }\n  .nx-faq-q[aria-expanded=\"true\"] .nx-chevron svg { stroke: #fff; }\n  .nx-faq-a { display: none; padding: 0 1.25rem 1rem; font-size: 0.92rem; color: #333; line-height: 1.7; background: #fff; }\n  .nx-faq-a.open { display: block; }\n\n  .nx-cta { background: linear-gradient(135deg, #00184C 0%, #073EA1 100%); border-radius: 12px; padding: 2rem; text-align: center; margin-top: 2.5rem; }\n  .nx-cta h3 { color: #fff; font-size: 1.3rem; font-weight: 700; margin-bottom: 0.5rem; }\n  .nx-cta p { color: #AEC9FF; font-size: 0.95rem; margin-bottom: 1.25rem; }\n  .nx-cta a { display: inline-block; background: #E11A1A; color: #fff; font-weight: 700; font-size: 0.95rem; padding: 0.7rem 1.8rem; border-radius: 6px; text-decoration: none; transition: background 0.2s; }\n  .nx-cta a:hover { background: #A30000; }\n  .nx-divider { border: none; border-top: 1px solid #e0e7f5; margin: 2rem 0; }\n  .nx-disclaimer { font-size: 0.8rem; color: #888; font-style: italic; text-align: center; margin-top: 1.5rem; }\n\n  @media (max-width: 720px) {\n    .nx-flow { grid-template-columns: 1fr; }\n    .nx-flow-step::after { content: \"\u2193\"; right: 50%; top: auto; bottom: -18px; transform: translateX(50%); }\n    .nx-stack-layer { flex-direction: column; }\n  }\n<\/style>\n\n<div class=\"nx-blog\">\n\n  <!-- HERO -->\n  <div class=\"nx-hero\">\n    <span class=\"nx-tag\">Enterprise Fraud and Risk Strategy &nbsp;\u00b7&nbsp; October 2026 &nbsp;\u00b7&nbsp; Global<\/span>\n    <p class=\"nx-meta\">Deepfakes attack the question of who is speaking. Payment controls need to hold even when the answer sounds exactly right.<\/p>\n  <\/div>\n\n  <!-- INTRODUCTION -->\n  <p><strong>Deepfake executive fraud<\/strong> turns a payment decision into an identity question. A cloned voice, a synthetic video call or a convincing message from a senior figure asks staff to decide whether the person is real. If the answer seems to be yes, the money moves.<\/p>\n  <p>That design puts the whole loss on one control, and it is the control generative AI is best at attacking. For fraud and risk leaders, the practical response is to make payment approval hold up even when the requester looks and sounds exactly right.<\/p>\n  <p>Two documented cases, Fideuram in 2026 and Arup in 2024, follow the same pattern. The request looked legitimate, the verification step was supplied by the attacker, and any reduction in the loss came from the payment side, where <a class=\"nx-inline-link\" href=\"https:\/\/nexiant.ai\/solutions\/fraudshield\/transaction-monitoring\/\">transaction monitoring<\/a> and recall sit.<\/p>\n\n  <!-- TOP VISUAL -->\n  <div class=\"nx-media\">\n    <img decoding=\"async\"\n      src=\"data:image\/svg+xml,%3Csvg xmlns='http:\/\/www.w3.org\/2000\/svg' width='820' height='460' viewBox='0 0 820 460'%3E%3Cdefs%3E%3ClinearGradient id='bg' x1='0' y1='0' x2='1' y2='1'%3E%3Cstop offset='0' stop-color='%2300184C'\/%3E%3Cstop offset='1' stop-color='%23073EA1'\/%3E%3C\/linearGradient%3E%3C\/defs%3E%3Crect width='820' height='460' rx='22' fill='url(%23bg)'\/%3E%3Ctext x='410' y='70' text-anchor='middle' font-family='Arial, sans-serif' font-size='30' font-weight='700' fill='%23ffffff'%3EThree control layers%3C\/text%3E%3Crect x='86' y='132' width='165' height='92' rx='18' fill='%23ffffff' opacity='0.92'\/%3E%3Crect x='328' y='132' width='165' height='92' rx='18' fill='%23ffffff' opacity='0.88'\/%3E%3Crect x='570' y='132' width='165' height='92' rx='18' fill='%23ffffff' opacity='0.84'\/%3E%3Crect x='207' y='272' width='165' height='92' rx='18' fill='%23ffffff' opacity='0.86'\/%3E%3Crect x='449' y='272' width='165' height='92' rx='18' fill='%23ffffff' opacity='0.90'\/%3E%3Ccircle cx='168' cy='162' r='16' fill='%23073EA1'\/%3E%3Ccircle cx='410' cy='162' r='16' fill='%23073EA1'\/%3E%3Ccircle cx='652' cy='162' r='16' fill='%23073EA1'\/%3E%3Ccircle cx='290' cy='302' r='16' fill='%23073EA1'\/%3E%3Ccircle cx='531' cy='302' r='16' fill='%23073EA1'\/%3E%3Ctext x='168' y='198' text-anchor='middle' font-family='Arial, sans-serif' font-size='17' font-weight='700' fill='%2300184C'%3EIdentity%3C\/text%3E%3Ctext x='410' y='198' text-anchor='middle' font-family='Arial, sans-serif' font-size='17' font-weight='700' fill='%2300184C'%3EChannel%3C\/text%3E%3Ctext x='652' y='198' text-anchor='middle' font-family='Arial, sans-serif' font-size='17' font-weight='700' fill='%2300184C'%3EPayment%3C\/text%3E%3Ctext x='290' y='338' text-anchor='middle' font-family='Arial, sans-serif' font-size='17' font-weight='700' fill='%2300184C'%3EDetection%3C\/text%3E%3Ctext x='531' y='338' text-anchor='middle' font-family='Arial, sans-serif' font-size='17' font-weight='700' fill='%2300184C'%3ERecall%3C\/text%3E%3Ctext x='410' y='410' text-anchor='middle' font-family='Arial, sans-serif' font-size='20' font-weight='600' fill='%23AEC9FF'%3EPayment holds when identity fails%3C\/text%3E%3C\/svg%3E\"\n      alt=\"Deepfake executive fraud visual showing three control layers, requester identity, instruction channel and payment authority, supported by detection and recall\"\n      loading=\"lazy\"\n      width=\"820\"\n      height=\"460\"\n    >\n    <p class=\"nx-caption\">An impersonation has to pass three control layers: who is asking, how the request arrived and whether the payment fits its mandate. Detection and recall limit the loss when the first layer fails.<\/p>\n  <\/div>\n\n  <!-- FLOW -->\n  <div class=\"nx-flow\">\n    <div class=\"nx-flow-step\">\n      <div class=\"nx-flow-number\">1<\/div>\n      <h4>Impersonate<\/h4>\n      <p>A message or call appears to come from a senior executive asking for an urgent transfer.<\/p>\n    <\/div>\n    <div class=\"nx-flow-step\">\n      <div class=\"nx-flow-number\">2<\/div>\n      <h4>Confirm<\/h4>\n      <p>The attacker supplies the verification, such as a cloned voice on a follow-up call or a deepfake video meeting.<\/p>\n    <\/div>\n    <div class=\"nx-flow-step\">\n      <div class=\"nx-flow-number\">3<\/div>\n      <h4>Approve<\/h4>\n      <p>Seniority and urgency carry the payment past normal approval friction.<\/p>\n    <\/div>\n    <div class=\"nx-flow-step\">\n      <div class=\"nx-flow-number\">4<\/div>\n      <h4>Pay out<\/h4>\n      <p>Funds move to new beneficiaries, often in another jurisdiction, before anyone checks.<\/p>\n    <\/div>\n  <\/div>\n\n  <!-- QUICK ANSWER -->\n  <div class=\"nx-callout\">\n    <div class=\"nx-callout-title\">Quick answer<\/div>\n    <p>Deepfake executive fraud uses AI-generated voice, video or messages to impersonate a senior figure and instruct a payment. It succeeds because identity, communication channels and payment approval usually sit with different teams, and each assumes another has checked. The defence is a payment decision that does not depend on whether the requester seems genuine: verification through a channel the organisation chooses, no seniority override, and hold rules on new beneficiaries, new jurisdictions, urgency and secrecy.<\/p>\n  <\/div>\n\n  <h2 id=\"what-is-deepfake-executive-fraud\"><span class=\"ez-toc-section\" id=\"What_is_deepfake_executive_fraud\"><\/span>What is deepfake executive fraud?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n  <p>Deepfake executive fraud is payment fraud in which criminals use AI-generated voice, video or messages to impersonate a senior executive, or someone the executive trusts, and instruct staff to transfer funds. It extends business email compromise beyond email into phone calls, video meetings and messaging apps.<\/p>\n  <p>FinCEN has been explicit that this typology targets financial institutions as well as their customers. In its <a class=\"nx-inline-link\" href=\"https:\/\/www.fincen.gov\/system\/files\/shared\/FinCEN-Alert-DeepFakes-Alert508FINAL.pdf\" target=\"_blank\" rel=\"noopener\">November 2024 alert on deepfake media<\/a>, the US Financial Crimes Enforcement Network noted reports of criminals using generative AI to impersonate an executive or trusted employee and instruct victims to transfer large sums. The same alert describes business email compromise schemes that use accounts belonging, or purporting to belong, to company leadership, vendors or lawyers.<\/p>\n  <p>Both cases below fit that description. One used a message app and a cloned voice; the other used a video conference.<\/p>\n\n  <h2 id=\"what-the-fideuram-case-shows\"><span class=\"ez-toc-section\" id=\"What_the_Fideuram_Case_Shows_About_How_These_Frauds_Work\"><\/span>What the Fideuram Case Shows About How These Frauds Work<span class=\"ez-toc-section-end\"><\/span><\/h2>\n  <p>On 25 September 2026, <a class=\"nx-inline-link\" href=\"https:\/\/www.privatebankerinternational.com\/news\/intesas-private-banking-ai-scam\/\" target=\"_blank\" rel=\"noopener\">Reuters reported<\/a>, citing two sources, that fraudsters had used AI to impersonate senior figures and obtain about \u20ac95 million from Fideuram, the private banking arm of Intesa Sanpaolo. The scheme began in February 2026, when Fideuram&#8217;s then chairman received a WhatsApp message that appeared to come from Intesa Sanpaolo&#8217;s chief executive, asking for urgent help with an overseas transaction.<\/p>\n  <p>A follow-up call that appeared to come from a senior partner at a prominent law firm confirmed the instruction. According to the sources, AI was used to replicate the lawyer&#8217;s voice. The chairman then instructed the finance department to make a series of transfers, mainly to accounts in China and Hong Kong. Fideuram detected irregularities quickly and alerted banks and authorities in several countries, and more than half of the funds were later recovered. Intesa Sanpaolo and Fideuram declined to comment.<\/p>\n  <p>The Arup case in Hong Kong had the same structure through a different channel. In January 2024 a finance employee joined a video conference with people he believed were the company&#8217;s chief financial officer and other colleagues. Hong Kong police later said all of them were deepfake recreations. He made 15 transfers totalling HK$200 million (about US$25.6 million) to five bank accounts, and <a class=\"nx-inline-link\" href=\"https:\/\/edition.cnn.com\/2024\/05\/16\/tech\/arup-deepfake-scam-loss-hong-kong-intl-hnk\" target=\"_blank\" rel=\"noopener\">Arup confirmed<\/a> that fake voices and images had been used.<\/p>\n\n  <!-- CARD GRID -->\n  <div class=\"nx-grid\">\n    <div class=\"nx-card\">\n      <div class=\"nx-card-icon\"><svg viewBox=\"0 0 20 20\"><path d=\"M10 1L3 5v6c0 4.25 3 8.22 7 9 4-.78 7-4.75 7-9V5l-7-4zm0 2.18l5 2.78V11c0 3.13-2.18 6.07-5 6.93C7.18 17.07 5 14.13 5 11V5.96l5-2.78z\"\/><\/svg><\/div>\n      <h4>Attacker-supplied confirmation<\/h4>\n      <p>The call that appeared to verify the Fideuram request was part of the fraud, so seeking a second voice worked against the bank.<\/p>\n    <\/div>\n    <div class=\"nx-card\">\n      <div class=\"nx-card-icon\"><svg viewBox=\"0 0 20 20\"><path d=\"M3 3h14v2H3zm0 4h14v2H3zm0 4h10v2H3zm0 4h7v2H3z\"\/><\/svg><\/div>\n      <h4>Authority from the top<\/h4>\n      <p>The instruction reached someone who could direct the finance team, so ordinary approval friction did little to slow it.<\/p>\n    <\/div>\n    <div class=\"nx-card\">\n      <div class=\"nx-card-icon\"><svg viewBox=\"0 0 20 20\"><path d=\"M10 2a8 8 0 100 16A8 8 0 0010 2zm1 11H9V9h2v4zm0-6H9V5h2v2z\"\/><\/svg><\/div>\n      <h4>Payment-side detection<\/h4>\n      <p>What limited the loss was spotting irregular transfers and contacting other banks quickly, after the money had moved.<\/p>\n    <\/div>\n    <div class=\"nx-card\">\n      <div class=\"nx-card-icon\"><svg viewBox=\"0 0 20 20\"><path d=\"M13 6a3 3 0 11-6 0 3 3 0 016 0zm5 10a7 7 0 00-14 0h14z\"\/><\/svg><\/div>\n      <h4>Video as verification<\/h4>\n      <p>At Arup, a video call with deepfake colleagues was treated as the verification step itself.<\/p>\n    <\/div>\n  <\/div>\n\n  <h2 id=\"three-control-layers\"><span class=\"ez-toc-section\" id=\"The_Three_Control_Layers_an_Impersonation_Has_to_Pass\"><\/span>The Three Control Layers an Impersonation Has to Pass<span class=\"ez-toc-section-end\"><\/span><\/h2>\n  <p>Every impersonation-led payment passes through three layers. In most organisations, each layer belongs to a different team.<\/p>\n  <p>The failure pattern is delegation between layers. Finance processes the payment because a senior person approved it. The senior person approved it because the voice or face was familiar. The channel the instruction travelled through, often a messaging app or a personal number, belonged to nobody. A deepfake only has to defeat the first layer if the other two have been built to trust it.<\/p>\n\n  <!-- TABLE -->\n  <div class=\"nx-table-wrap\">\n    <table class=\"nx-table\">\n      <thead>\n        <tr>\n          <th>Control layer<\/th>\n          <th>Question it answers<\/th>\n          <th>What a deepfake does to it<\/th>\n          <th>A control that still holds<\/th>\n          <th>Typical owner<\/th>\n        <\/tr>\n      <\/thead>\n      <tbody>\n        <tr>\n          <td><strong>Requester identity<\/strong><\/td>\n          <td>Is this really the person they claim to be?<\/td>\n          <td>Imitates the face, voice or writing style of someone staff know<\/td>\n          <td>Treat recognition as one signal, never as approval<\/td>\n          <td><span class=\"nx-badge nx-badge--red\">Often unowned<\/span><\/td>\n        <\/tr>\n        <tr>\n          <td><strong>Instruction channel<\/strong><\/td>\n          <td>Did the request and its confirmation arrive through channels we control?<\/td>\n          <td>Moves to messaging apps, personal numbers or attacker-hosted calls, and supplies its own &#8220;verification&#8221;<\/td>\n          <td>Call back on contact details from internal records, never details supplied with the request<\/td>\n          <td><span class=\"nx-badge nx-badge--blue\">Cyber security and IT<\/span><\/td>\n        <\/tr>\n        <tr>\n          <td><strong>Payment authority<\/strong><\/td>\n          <td>Does this payment fit an existing mandate, limit and beneficiary pattern?<\/td>\n          <td>Uses seniority, urgency and confidentiality to bypass approval steps<\/td>\n          <td>Hold rules that apply regardless of who approved the payment<\/td>\n          <td><span class=\"nx-badge nx-badge--blue\">Treasury, finance operations and fraud<\/span><\/td>\n        <\/tr>\n      <\/tbody>\n    <\/table>\n  <\/div>\n\n  <!-- SIGNAL PANEL -->\n  <div class=\"nx-signal-panel\">\n    <h3>Warning signs in an impersonation-led payment request<\/h3>\n    <p>None of these signals depends on recognising a face or voice, which is why they belong in the payment process.<\/p>\n\n    <div class=\"nx-signal-grid\">\n      <div class=\"nx-signal\">\n        <strong>Unexpected request from authority<\/strong>\n        <span>The ACSC lists unexpected payment requests from someone in a position of authority as a warning sign.<\/span>\n      <\/div>\n      <div class=\"nx-signal\">\n        <strong>Pressure for secrecy<\/strong>\n        <span>Requests to keep a payment confidential, or to get around protective processes, should be reported rather than actioned.<\/span>\n      <\/div>\n      <div class=\"nx-signal\">\n        <strong>Channel switching<\/strong>\n        <span>FinCEN notes deepfake users may try to change communication methods partway through a verification check.<\/span>\n      <\/div>\n      <div class=\"nx-signal\">\n        <strong>New beneficiary or jurisdiction<\/strong>\n        <span>A first payment to a new account or country, with a hard deadline, is visible to the payment process even when identity has been fooled.<\/span>\n      <\/div>\n    <\/div>\n  <\/div>\n\n  <h2 id=\"why-identity-checks-are-not-enough\"><span class=\"ez-toc-section\" id=\"Why_Identity_Checks_Cannot_Carry_the_Decision_on_Their_Own\"><\/span>Why Identity Checks Cannot Carry the Decision on Their Own<span class=\"ez-toc-section-end\"><\/span><\/h2>\n  <p>FinCEN also points to the limits of live verification. Audio or video checks can expose inconsistencies, but people using deepfake identities may try to avoid them or change communication methods partway through. Deepfake detection is worth having, and it keeps improving, but it is a contest between generation and detection tools. A payment process that depends on winning that contest every time has no margin for error.<\/p>\n  <p>Identity controls at onboarding answer a different question. <a class=\"nx-inline-link\" href=\"https:\/\/nexiant.ai\/resources\/blogs\/liveness-detection-digital-onboarding-deepfake-fraud\/\">Liveness detection<\/a> checks whether a real person is present when an identity is verified, and <a class=\"nx-inline-link\" href=\"https:\/\/nexiant.ai\/resources\/blogs\/synthetic-identity-fraud-detection-aml-compliance\/\">synthetic identity controls<\/a> test whether the identity itself is genuine. Executive impersonation borrows a real, known identity during a live instruction, so neither control sits in its path.<\/p>\n  <p>That leaves the payment layer as the place where the decision has to hold.<\/p>\n\n  <!-- SCENARIO -->\n  <div class=\"nx-scenario\">\n    <h3>Illustrative example: rehearsing an impersonation<\/h3>\n    <p>Phishing simulations test whether staff click links. They rarely test whether a convincing senior voice can push a payment through.<\/p>\n    <p>A more useful exercise has a simulated executive ask the finance team for an urgent, confidential transfer to a new overseas beneficiary, then checks each layer in turn:<\/p>\n    <ul>\n      <li>Is the call-back made to a number from internal records, or to one supplied with the request?<\/li>\n      <li>Does the new beneficiary and jurisdiction trigger a hold, whoever approved?<\/li>\n      <li>Can the request be pushed through on seniority alone?<\/li>\n      <li>When someone refuses, does the escalation path work without penalty?<\/li>\n    <\/ul>\n  <\/div>\n\n  <h2 id=\"payment-controls-that-hold\"><span class=\"ez-toc-section\" id=\"How_to_Make_Payment_Controls_Hold_When_Identity_Fails\"><\/span>How to Make Payment Controls Hold When Identity Fails<span class=\"ez-toc-section-end\"><\/span><\/h2>\n  <p>The aim is a payment decision that stays sound even if the requester is a perfect imitation. Five design choices do most of the work, and none of them depends on recognising the person asking.<\/p>\n\n  <!-- CONTROLS LIST -->\n  <div class=\"nx-obligations\">\n    <div class=\"nx-obl-item\">\n      <h4>1. Verify through a channel you choose<\/h4>\n      <p>Confirmation that arrives with the request, or through contact details the requester supplies, is not independent. Call back on a number held in internal records, or confirm through a channel registered in advance. The Australian Signals Directorate&#8217;s Australian Cyber Security Centre (ACSC) <a class=\"nx-inline-link\" href=\"https:\/\/www.cyber.gov.au\/resources-business-and-government\/maintaining-devices-and-systems\/system-hardening-and-administration\/email-hardening\/protecting-against-business-email-compromise\" target=\"_blank\" rel=\"noopener\">advises organisations to set a clear and consistent process<\/a> for staff to verify and validate requests for payment.<\/p>\n    <\/div>\n    <div class=\"nx-obl-item\">\n      <h4>2. Remove the seniority override<\/h4>\n      <p>The ACSC lists unexpected payment requests from someone in a position of authority as a warning sign, and says staff need a way to report pressure for secrecy or requests to get around protective processes. If a chief executive can waive a control, so can anyone convincingly pretending to be one. Senior requests should face the same checks, and staff need explicit permission to apply them.<\/p>\n    <\/div>\n    <div class=\"nx-obl-item\">\n      <h4>3. Attach hold rules to the payment, not the person<\/h4>\n      <p>Define payment characteristics that trigger mandatory independent verification and a short hold, whoever approved: a new beneficiary, a new jurisdiction, a value outside the normal pattern for that account, a request for confidentiality, a hard deadline. The payment process can see these signals even when the identity layer has been fooled.<\/p>\n    <\/div>\n    <div class=\"nx-obl-item\">\n      <h4>4. Monitor the institution&#8217;s own outbound payments<\/h4>\n      <p>In many financial institutions, transaction monitoring is built around customer activity, while treasury and corporate payments run through a separate approval route. Impersonation targets that second route. Fideuram&#8217;s partial recovery depended on spotting irregular transfers quickly and alerting other banks, so detection and recall deserve as much design effort as approval. Our analysis of <a class=\"nx-inline-link\" href=\"https:\/\/nexiant.ai\/resources\/blogs\/app-fraud-money-mule-detection\/\">APP fraud and money mule detection<\/a> explains why action at the receiving end matters too.<\/p>\n    <\/div>\n    <div class=\"nx-obl-item\">\n      <h4>5. Rehearse the scenario end to end<\/h4>\n      <p>Phishing simulations test whether staff click links. They rarely test whether a convincing senior voice can push a payment through. Run exercises like the one above, and check whether each layer behaves as designed, including the escalation path when someone refuses.<\/p>\n    <\/div>\n  <\/div>\n\n  <h2 id=\"who-should-own-impersonation-risk\"><span class=\"ez-toc-section\" id=\"Who_Should_Own_Deepfake_Impersonation_Risk\"><\/span>Who Should Own Deepfake Impersonation Risk<span class=\"ez-toc-section-end\"><\/span><\/h2>\n  <p>Because the layers sit with different teams, impersonation risk often has no single owner. Cyber security sees social engineering, fraud sees a payment risk and treasury sees an operational process.<\/p>\n  <p>Assign one accountable owner for the end-to-end payment instruction journey, with each layer&#8217;s control owner reporting into that view.<\/p>\n\n  <!-- CONTROL STACK -->\n  <div class=\"nx-stack\">\n    <div class=\"nx-stack-layer\">\n      <div class=\"nx-stack-icon\">01<\/div>\n      <div>\n        <h4>Requester identity<\/h4>\n        <p>Individual judgement today, often with no formal owner. Recognition should count as one signal, never as approval.<\/p>\n      <\/div>\n    <\/div>\n    <div class=\"nx-stack-layer\">\n      <div class=\"nx-stack-icon\">02<\/div>\n      <div>\n        <h4>Instruction channel<\/h4>\n        <p>Cyber security and IT. Owns the rule that verification uses contact details from internal records.<\/p>\n      <\/div>\n    <\/div>\n    <div class=\"nx-stack-layer\">\n      <div class=\"nx-stack-icon\">03<\/div>\n      <div>\n        <h4>Payment authority<\/h4>\n        <p>Treasury, finance operations and fraud. Owns hold rules, outbound monitoring and recall.<\/p>\n      <\/div>\n    <\/div>\n    <div class=\"nx-stack-layer\">\n      <div class=\"nx-stack-icon\">04<\/div>\n      <div>\n        <h4>End-to-end owner<\/h4>\n        <p>One accountable owner for the whole payment instruction journey, with each layer&#8217;s control owner reporting into that view.<\/p>\n      <\/div>\n    <\/div>\n  <\/div>\n\n  <h2 id=\"common-control-gaps\"><span class=\"ez-toc-section\" id=\"Common_Control_Gaps_Behind_Deepfake_Executive_Fraud\"><\/span>Common Control Gaps Behind Deepfake Executive Fraud<span class=\"ez-toc-section-end\"><\/span><\/h2>\n  <p>The same gaps appear when identity, channel and payment controls are designed separately:<\/p>\n  <ul>\n    <li>Verifying a request through contact details that arrived with the request.<\/li>\n    <li>Allowing senior executives to waive payment checks.<\/li>\n    <li>Applying hold rules to customer payments but not to treasury or intra-group payments.<\/li>\n    <li>Treating deepfake detection as the deciding control rather than one signal.<\/li>\n    <li>Leaving impersonation risk without a single accountable owner.<\/li>\n  <\/ul>\n\n  <div class=\"nx-callout nx-callout--warning\">\n    <div class=\"nx-callout-title\">Detection is not the deciding control<\/div>\n    <p>Deepfake detection can help, but FinCEN notes that people using deepfakes may try to avoid live verification or change communication methods. Payment controls should hold even when a deepfake goes undetected.<\/p>\n  <\/div>\n\n  <h2 id=\"customer-payments\"><span class=\"ez-toc-section\" id=\"The_Same_Pattern_Applies_to_Customer_Payments\"><\/span>The Same Pattern Applies to Customer Payments<span class=\"ez-toc-section-end\"><\/span><\/h2>\n  <p>When the target is a corporate customer rather than your own treasury, the institution sits on the payment side as the sending or receiving bank. FinCEN lists business email compromise among the scams in which deepfake social engineering is used against customers and employees. The three-layer map still applies, but the controls you own are mostly in the third layer: payment-level checks, monitoring and recall.<\/p>\n  <p>For Australian obligations, our guide to <a class=\"nx-inline-link\" href=\"https:\/\/nexiant.ai\/resources\/blogs\/scam-complaints-evidence-trail-spf\/\">Scams Prevention Framework evidence<\/a> covers what regulated sectors should be able to show. For a wider view of AI-enabled identity fraud, see MemberCheck&#8217;s analysis of <a class=\"nx-inline-link\" href=\"https:\/\/membercheck.com\/blog\/next-generation-fraud-synthetic-identities-deepfakes-ai-scams\/\" target=\"_blank\" rel=\"noopener\">synthetic identities, deepfakes and AI-enabled scams<\/a>.<\/p>\n\n  <h2 id=\"how-nexiant-supports\"><span class=\"ez-toc-section\" id=\"How_Nexiant_Supports_Impersonation-Resilient_Payment_Controls\"><\/span>How Nexiant Supports Impersonation-Resilient Payment Controls<span class=\"ez-toc-section-end\"><\/span><\/h2>\n  <p>Nexiant brings together specialist capabilities across <a class=\"nx-inline-link\" href=\"https:\/\/nexiant.ai\/solutions\/membercheck\/id-verification\/\">identity verification<\/a>, <a class=\"nx-inline-link\" href=\"https:\/\/nexiant.ai\/solutions\/membercheck\/pep-sanctions-screening\/\">PEP and sanctions screening<\/a> and <a class=\"nx-inline-link\" href=\"https:\/\/nexiant.ai\/solutions\/fraudshield\/transaction-monitoring\/\">transaction monitoring<\/a> through MemberCheck and FraudShield, supporting the identity and payment layers of this model.<\/p>\n  <p>Verification rules, approval policies and escalation paths remain the organisation&#8217;s own controls to design and govern.<\/p>\n\n  <h2 id=\"questions-for-risk-leaders\"><span class=\"ez-toc-section\" id=\"Questions_Risk_Leaders_Should_Ask_About_Their_Payment_Controls\"><\/span>Questions Risk Leaders Should Ask About Their Payment Controls<span class=\"ez-toc-section-end\"><\/span><\/h2>\n  <p>Risk leaders can put these questions to their own organisation:<\/p>\n  <ul>\n    <li>Which high-value payment routes can one person authorise, and who can override them?<\/li>\n    <li>How many verification steps rely on a channel or contact detail the requester could control?<\/li>\n    <li>Do hold rules on new beneficiaries and jurisdictions apply to treasury and intra-group payments as well as customer payments?<\/li>\n    <li>How quickly can outbound payments be identified, recalled and reported to other institutions?<\/li>\n    <li>When were these controls last tested against a realistic impersonation scenario?<\/li>\n  <\/ul>\n  <p>The answers show where a convincing voice could still move money.<\/p>\n\n  <hr class=\"nx-divider\">\n\n  <h2 id=\"frequently-asked-questions\"><span class=\"ez-toc-section\" id=\"Frequently_Asked_Questions\"><\/span>Frequently Asked Questions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n  <!-- FAQ: visible FAQ and JSON-LD schema are aligned -->\n  <div class=\"nx-faq\">\n    <div class=\"nx-faq-item\">\n      <button class=\"nx-faq-q\" aria-expanded=\"false\">What is deepfake executive fraud?<span class=\"nx-chevron\"><svg viewBox=\"0 0 10 6\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M1 1l4 4 4-4\"\/><\/svg><\/span><\/button>\n      <div class=\"nx-faq-a\">It is payment fraud in which criminals use AI-generated voice, video or messages to impersonate a senior executive, or someone the executive trusts, and instruct staff to transfer funds. It extends business email compromise beyond email into phone calls, video meetings and messaging apps.<\/div>\n    <\/div>\n    <div class=\"nx-faq-item\">\n      <button class=\"nx-faq-q\" aria-expanded=\"false\">Can deepfake detection software stop executive impersonation?<span class=\"nx-chevron\"><svg viewBox=\"0 0 10 6\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M1 1l4 4 4-4\"\/><\/svg><\/span><\/button>\n      <div class=\"nx-faq-a\">It can help, but it should not be the deciding control. FinCEN notes that people using deepfakes may try to avoid live verification or change communication methods, and detection tools face generation methods that keep improving. Payment controls should hold even when a deepfake goes undetected.<\/div>\n    <\/div>\n    <div class=\"nx-faq-item\">\n      <button class=\"nx-faq-q\" aria-expanded=\"false\">Does a call-back still work against voice cloning?<span class=\"nx-chevron\"><svg viewBox=\"0 0 10 6\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M1 1l4 4 4-4\"\/><\/svg><\/span><\/button>\n      <div class=\"nx-faq-a\">Yes, if the organisation chooses the number. A call-back to a number held in internal records reaches the real person. A call from, or to, contact details supplied with the request can reach the attacker, as the confirming call in the Fideuram case showed.<\/div>\n    <\/div>\n    <div class=\"nx-faq-item\">\n      <button class=\"nx-faq-q\" aria-expanded=\"false\">Why should senior executives face the same payment checks as everyone else?<span class=\"nx-chevron\"><svg viewBox=\"0 0 10 6\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M1 1l4 4 4-4\"\/><\/svg><\/span><\/button>\n      <div class=\"nx-faq-a\">Because impersonators target authority. The ACSC treats unexpected payment requests from people in positions of authority as a warning sign. Removing overrides also protects executives, since their identity is what attackers copy.<\/div>\n    <\/div>\n    <div class=\"nx-faq-item\">\n      <button class=\"nx-faq-q\" aria-expanded=\"false\">Who should own deepfake impersonation risk in a financial institution?<span class=\"nx-chevron\"><svg viewBox=\"0 0 10 6\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M1 1l4 4 4-4\"\/><\/svg><\/span><\/button>\n      <div class=\"nx-faq-a\">One accountable owner for the end-to-end payment instruction journey, supported by control owners in cyber security, fraud, treasury and finance operations. Without that owner, each team can reasonably assume another has done the checking.<\/div>\n    <\/div>\n  <\/div>\n\n  <!-- CTA -->\n  <div class=\"nx-cta\">\n    <h3>Test your payment controls against executive impersonation<\/h3>\n    <p>Speak with a Nexiant expert about connecting identity, channel and payment controls so a convincing voice is never enough to move money.<\/p>\n    <a href=\"https:\/\/nexiant.ai\/contact-us\/\">Speak to our fraud prevention team<\/a>\n  <\/div>\n\n  <p class=\"nx-disclaimer\">This article was accurate at the time of publication in October 2026 and is intended for general informational purposes only. It does not constitute legal, regulatory or compliance advice. Organisations should seek qualified professional guidance in relation to their specific obligations.<\/p>\n\n<\/div>\n\n<script>\n  document.querySelectorAll('.nx-faq-q').forEach(function(btn) {\n    btn.addEventListener('click', function() {\n      var expanded = this.getAttribute('aria-expanded') === 'true';\n      this.setAttribute('aria-expanded', !expanded);\n      this.nextElementSibling.classList.toggle('open', !expanded);\n    });\n  });\n<\/script>\n\n<script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is deepfake executive fraud?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"It is payment fraud in which criminals use AI-generated voice, video or messages to impersonate a senior executive, or someone the executive trusts, and instruct staff to transfer funds. It extends business email compromise beyond email into phone calls, video meetings and messaging apps.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Can deepfake detection software stop executive impersonation?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"It can help, but it should not be the deciding control. FinCEN notes that people using deepfakes may try to avoid live verification or change communication methods, and detection tools face generation methods that keep improving. Payment controls should hold even when a deepfake goes undetected.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does a call-back still work against voice cloning?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes, if the organisation chooses the number. A call-back to a number held in internal records reaches the real person. A call from, or to, contact details supplied with the request can reach the attacker, as the confirming call in the Fideuram case showed.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Why should senior executives face the same payment checks as everyone else?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Because impersonators target authority. The ACSC treats unexpected payment requests from people in positions of authority as a warning sign. Removing overrides also protects executives, since their identity is what attackers copy.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Who should own deepfake impersonation risk in a financial institution?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"One accountable owner for the end-to-end payment instruction journey, supported by control owners in cyber security, fraud, treasury and finance operations. Without that owner, each team can reasonably assume another has done the checking.\"\n      }\n    }\n  ]\n}\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>Enterprise Fraud and Risk Strategy &nbsp;\u00b7&nbsp; October 2026 &nbsp;\u00b7&nbsp; Global Deepfakes attack the question of who is speaking. Payment controls need to hold even when the answer sounds exactly right. Deepfake executive fraud turns a payment decision into an identity question. A cloned voice, a synthetic video call or a convincing message from a senior [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":855,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_aioseo_title":"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant","_aioseo_description":"Deepfake executive fraud defeats identity checks. See why payment controls must hold when a voice sounds right, with lessons from Fideuram and Arup.","om_disable_all_campaigns":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-852","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fraudprevention"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"Deepfake executive fraud defeats identity checks. See why payment controls must hold when a voice sounds right, with lessons from Fideuram and Arup.\" \/>\n\t<meta name=\"robots\" content=\"max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n\t<meta name=\"author\" content=\"Zeeshan Rizvi\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"AI-Assisted Fraud Prevention and Risk Management - Nexiant\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant\" \/>\n\t\t<meta property=\"og:description\" content=\"Deepfake executive fraud defeats identity checks. See why payment controls must hold when a voice sounds right, with lessons from Fideuram and Arup.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/nexiant.ai\/resources\/blogs\/wp-content\/uploads\/2025\/11\/Nexiant-Dark-Logo-Apr.png\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/nexiant.ai\/resources\/blogs\/wp-content\/uploads\/2025\/11\/Nexiant-Dark-Logo-Apr.png\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-10-19T11:59:35+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-10-19T12:03:11+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Deepfake executive fraud defeats identity checks. See why payment controls must hold when a voice sounds right, with lessons from Fideuram and Arup.\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/nexiant.ai\/resources\/blogs\/wp-content\/uploads\/2025\/11\/Nexiant-Dark-Logo-Apr.png\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BlogPosting\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#blogposting\",\"name\":\"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant\",\"headline\":\"Why Deepfake Executive Fraud Needs Payment Controls as Well as Identity Checks\",\"author\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/author\\\/zeeshan\\\/#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/#organization\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/Deep-Fake-Video-scaled.jpg\",\"width\":2560,\"height\":1790},\"datePublished\":\"2026-10-19T22:59:35+11:00\",\"dateModified\":\"2026-10-19T23:03:11+11:00\",\"inLanguage\":\"en-AU\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#webpage\"},\"articleSection\":\"Fraud Prevention\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/category\\\/fraudprevention\\\/#listItem\",\"name\":\"Fraud Prevention\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/category\\\/fraudprevention\\\/#listItem\",\"position\":2,\"name\":\"Fraud Prevention\",\"item\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/category\\\/fraudprevention\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#listItem\",\"name\":\"Why Deepfake Executive Fraud Needs Payment Controls as Well as Identity Checks\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#listItem\",\"position\":3,\"name\":\"Why Deepfake Executive Fraud Needs Payment Controls as Well as Identity Checks\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/category\\\/fraudprevention\\\/#listItem\",\"name\":\"Fraud Prevention\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/#organization\",\"name\":\"AI-Assisted Fraud Prevention and Risk Management\",\"description\":\"Nexiant\",\"url\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/wp-nexiant.nexiant.ai\\\/wp-content\\\/uploads\\\/2025\\\/11\\\/Nexiant-Dark-Logo-Apr.png\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#organizationLogo\"},\"image\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#organizationLogo\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/company\\\/nexiantai\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/author\\\/zeeshan\\\/#author\",\"url\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/author\\\/zeeshan\\\/\",\"name\":\"Zeeshan Rizvi\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5060e430addd1087c0299e5ea76cd12ea794a85047ffecd5cfbbf24f4c1fbb2f?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"Zeeshan Rizvi\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#webpage\",\"url\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/\",\"name\":\"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant\",\"description\":\"Deepfake executive fraud defeats identity checks. See why payment controls must hold when a voice sounds right, with lessons from Fideuram and Arup.\",\"inLanguage\":\"en-AU\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/author\\\/zeeshan\\\/#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/author\\\/zeeshan\\\/#author\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/Deep-Fake-Video-scaled.jpg\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#mainImage\",\"width\":2560,\"height\":1790},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/deepfake-executive-fraud-payment-controls\\\/#mainImage\"},\"datePublished\":\"2026-10-19T22:59:35+11:00\",\"dateModified\":\"2026-10-19T23:03:11+11:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/#website\",\"url\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/\",\"name\":\"AI-Assisted Fraud Prevention and Risk Management\",\"description\":\"Nexiant\",\"inLanguage\":\"en-AU\",\"publisher\":{\"@id\":\"https:\\\/\\\/nexiant.ai\\\/resources\\\/blogs\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant","description":"Deepfake executive fraud defeats identity checks. See why payment controls must hold when a voice sounds right, with lessons from Fideuram and Arup.","canonical_url":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/","robots":"max-snippet:-1, max-image-preview:large, max-video-preview:-1","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BlogPosting","@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#blogposting","name":"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant","headline":"Why Deepfake Executive Fraud Needs Payment Controls as Well as Identity Checks","author":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/author\/zeeshan\/#author"},"publisher":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/#organization"},"image":{"@type":"ImageObject","url":"https:\/\/nexiant.ai\/resources\/blogs\/wp-content\/uploads\/2026\/10\/Deep-Fake-Video-scaled.jpg","width":2560,"height":1790},"datePublished":"2026-10-19T22:59:35+11:00","dateModified":"2026-10-19T23:03:11+11:00","inLanguage":"en-AU","mainEntityOfPage":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#webpage"},"isPartOf":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#webpage"},"articleSection":"Fraud Prevention"},{"@type":"BreadcrumbList","@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/nexiant.ai\/resources\/blogs\/#listItem","position":1,"name":"Home","item":"https:\/\/nexiant.ai\/resources\/blogs\/","nextItem":{"@type":"ListItem","@id":"https:\/\/nexiant.ai\/resources\/blogs\/category\/fraudprevention\/#listItem","name":"Fraud Prevention"}},{"@type":"ListItem","@id":"https:\/\/nexiant.ai\/resources\/blogs\/category\/fraudprevention\/#listItem","position":2,"name":"Fraud Prevention","item":"https:\/\/nexiant.ai\/resources\/blogs\/category\/fraudprevention\/","nextItem":{"@type":"ListItem","@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#listItem","name":"Why Deepfake Executive Fraud Needs Payment Controls as Well as Identity Checks"},"previousItem":{"@type":"ListItem","@id":"https:\/\/nexiant.ai\/resources\/blogs\/#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#listItem","position":3,"name":"Why Deepfake Executive Fraud Needs Payment Controls as Well as Identity Checks","previousItem":{"@type":"ListItem","@id":"https:\/\/nexiant.ai\/resources\/blogs\/category\/fraudprevention\/#listItem","name":"Fraud Prevention"}}]},{"@type":"Organization","@id":"https:\/\/nexiant.ai\/resources\/blogs\/#organization","name":"AI-Assisted Fraud Prevention and Risk Management","description":"Nexiant","url":"https:\/\/nexiant.ai\/resources\/blogs\/","logo":{"@type":"ImageObject","url":"https:\/\/wp-nexiant.nexiant.ai\/wp-content\/uploads\/2025\/11\/Nexiant-Dark-Logo-Apr.png","@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#organizationLogo"},"image":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#organizationLogo"},"sameAs":["https:\/\/www.linkedin.com\/company\/nexiantai"]},{"@type":"Person","@id":"https:\/\/nexiant.ai\/resources\/blogs\/author\/zeeshan\/#author","url":"https:\/\/nexiant.ai\/resources\/blogs\/author\/zeeshan\/","name":"Zeeshan Rizvi","image":{"@type":"ImageObject","@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/5060e430addd1087c0299e5ea76cd12ea794a85047ffecd5cfbbf24f4c1fbb2f?s=96&d=mm&r=g","width":96,"height":96,"caption":"Zeeshan Rizvi"}},{"@type":"WebPage","@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#webpage","url":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/","name":"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant","description":"Deepfake executive fraud defeats identity checks. See why payment controls must hold when a voice sounds right, with lessons from Fideuram and Arup.","inLanguage":"en-AU","isPartOf":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/#website"},"breadcrumb":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#breadcrumblist"},"author":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/author\/zeeshan\/#author"},"creator":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/author\/zeeshan\/#author"},"image":{"@type":"ImageObject","url":"https:\/\/nexiant.ai\/resources\/blogs\/wp-content\/uploads\/2026\/10\/Deep-Fake-Video-scaled.jpg","@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#mainImage","width":2560,"height":1790},"primaryImageOfPage":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/#mainImage"},"datePublished":"2026-10-19T22:59:35+11:00","dateModified":"2026-10-19T23:03:11+11:00"},{"@type":"WebSite","@id":"https:\/\/nexiant.ai\/resources\/blogs\/#website","url":"https:\/\/nexiant.ai\/resources\/blogs\/","name":"AI-Assisted Fraud Prevention and Risk Management","description":"Nexiant","inLanguage":"en-AU","publisher":{"@id":"https:\/\/nexiant.ai\/resources\/blogs\/#organization"}}]},"og:locale":"en_US","og:site_name":"AI-Assisted Fraud Prevention and Risk Management - Nexiant","og:type":"article","og:title":"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant","og:description":"Deepfake executive fraud defeats identity checks. See why payment controls must hold when a voice sounds right, with lessons from Fideuram and Arup.","og:url":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/","og:image":"https:\/\/nexiant.ai\/resources\/blogs\/wp-content\/uploads\/2025\/11\/Nexiant-Dark-Logo-Apr.png","og:image:secure_url":"https:\/\/nexiant.ai\/resources\/blogs\/wp-content\/uploads\/2025\/11\/Nexiant-Dark-Logo-Apr.png","article:published_time":"2026-10-19T11:59:35+00:00","article:modified_time":"2026-10-19T12:03:11+00:00","twitter:card":"summary_large_image","twitter:title":"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant","twitter:description":"Deepfake executive fraud defeats identity checks. See why payment controls must hold when a voice sounds right, with lessons from Fideuram and Arup.","twitter:image":"https:\/\/nexiant.ai\/resources\/blogs\/wp-content\/uploads\/2025\/11\/Nexiant-Dark-Logo-Apr.png"},"aioseo_meta_data":{"post_id":"852","title":"Deepfake Executive Fraud: Payment and Identity Checks | Nexiant","description":"Deepfake executive fraud defeats identity checks. See why payment controls must hold when a voice sounds right, with lessons from Fideuram and Arup.","keywords":null,"keyphrases":{"focus":{"keyphrase":"deepfake executive fraud","score":0,"analysis":[]},"additional":[]},"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":"","og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"BlogPosting","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":"-1","robots_max_videopreview":"-1","robots_max_imagepreview":"large","priority":null,"frequency":"default","local_seo":null,"breadcrumb_settings":null,"limit_modified_date":false,"ai":{"faqs":[],"keyPoints":[],"schemas":[],"titles":[],"descriptions":[],"socialPosts":{"email":{"subject":"","preview":"","content":""},"linkedin":[],"twitter":[],"facebook":[],"instagram":[]}},"created":"2026-10-19 11:47:51","updated":"2026-10-19 12:44:07","focus_keyword":"deepfake executive fraud","additional_keywords":null,"truseo_locale":null,"seo_analyzer_scan_date":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/nexiant.ai\/resources\/blogs\/\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/nexiant.ai\/resources\/blogs\/category\/fraudprevention\/\" title=\"Fraud Prevention\">Fraud Prevention<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tWhy Deepfake Executive Fraud Needs Payment Controls as Well as Identity Checks\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/nexiant.ai\/resources\/blogs\/"},{"label":"Fraud Prevention","link":"https:\/\/nexiant.ai\/resources\/blogs\/category\/fraudprevention\/"},{"label":"Why Deepfake Executive Fraud Needs Payment Controls as Well as Identity Checks","link":"https:\/\/nexiant.ai\/resources\/blogs\/deepfake-executive-fraud-payment-controls\/"}],"_links":{"self":[{"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/posts\/852","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/comments?post=852"}],"version-history":[{"count":2,"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/posts\/852\/revisions"}],"predecessor-version":[{"id":854,"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/posts\/852\/revisions\/854"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/media\/855"}],"wp:attachment":[{"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/media?parent=852"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/categories?post=852"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nexiant.ai\/resources\/blogs\/wp-json\/wp\/v2\/tags?post=852"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}