TL;DR
The 2026 AFP Payments Fraud and Control Survey found that only 17% of organizations use AI to combat payments fraud, despite 76% experiencing attempted or actual fraud in 2025 and 74% being hit by business email compromise. This is a remarkable mismatch between a widespread, escalating threat and the adoption of a tool that helps fight it, especially as attackers increasingly use AI themselves, including deepfake voice and video.
The gap exists for understandable reasons, not negligence. Finance teams hesitate to adopt AI against fraud because of trust and the black-box problem (probabilistic AI that flags a payment as risky without an explanation is hard to act on in a function where decisions must be justified), auditability concerns (AI decisions that cannot be reconstructed are a problem for a function that gets audited), integration complexity, unclear ROI and not knowing where to start, fear of false positives disrupting legitimate payments, and the sheer newness of AI-versus-AI fraud. These barriers are real, and they cluster around a single theme: finance needs AI it can trust, explain, and audit, and much of the AI marketed for fraud does not clearly meet that bar.
The 17% who do use AI report concrete gains: better efficiency in fraud reporting, improved deepfake detection, and real-time identification of threats. The benefits are real for those who get past the barriers.
What would close the gap is AI that addresses the trust and auditability concerns directly: deterministic, explainable controls whose decisions can be reconstructed and justified, rather than opaque probabilistic scores, combined with detection. The path to higher adoption runs through trust, not through more impressive detection claims. This post examines why the 17% figure is so low, what the adopters are gaining, and what would move the number.
For the practical how-to, see The 2026 Payments Fraud Playbook: Deterministic AI Controls vs Manual Review (companion guide).
The gap, in numbers #
The 2026 AFP Payments Fraud and Control Survey, conducted in January 2026 among 465 treasury practitioners, lays out the mismatch starkly. On the threat side: 76% of US organizations experienced attempted or actual payments fraud in 2025. Business email compromise affected 74%, a significant increase from prior years and the leading fraud channel. Checks remain the most-targeted method at 58%. And for the first time, the survey examined AI-enabled fraud and deepfake technologies, voice and video used to impersonate executives and vendors, reflecting a threat that is itself becoming AI-powered.
On the defense side: only 17% of organizations use AI to combat payments fraud.
Put together, those numbers describe a finance function facing a pervasive, escalating, increasingly AI-driven threat while overwhelmingly relying on non-AI defenses, primarily manual review and traditional controls. More than three-quarters are getting attacked; fewer than one-fifth are using AI to help defend. As fraud itself becomes AI-powered through deepfakes and AI-crafted BEC, the defensive gap arguably widens even at constant adoption, because the threat side is getting a capability the defense side mostly lacks.
The natural question is why. If AI helps fight a threat that is hitting nearly everyone, why are so few using it? The answer is not that finance teams are careless. It is that several real barriers stand between them and adoption, and understanding those barriers is the key to closing the gap.
Why adoption lags: the real barriers #
1. Trust and the black-box problem
Finance runs on decisions that can be justified. When an AI flags a payment as 87% likely to be fraudulent without explaining why, a finance team is left with a number it cannot easily act on or defend. Holding a legitimate payment on an unexplained algorithmic hunch creates business friction; releasing a flagged one that turns out fraudulent looks negligent. Probabilistic AI that produces scores without reasons asks finance professionals to trust a black box in a domain where they are accountable for outcomes, and that is a hard ask. This trust gap is arguably the single largest barrier, because it is not solved by better accuracy claims, it is solved by explainability. See why “94% confident” is not an audit trail.
2. Auditability concerns
Payments and fraud controls get audited, and increasingly so under frameworks like the US Treasury’s 2026 AI Risk Management Framework for financial services. An AI control whose decisions cannot be reconstructed and explained is a liability in that context: “the model flagged it” or “the model cleared it” is not a satisfying answer to an auditor asking why a control did what it did. Finance teams are rightly cautious about deploying AI whose decisions they cannot reconstruct, because they will have to account for those decisions later. Opaque AI and audit requirements are in tension, and that tension holds back adoption. See the 2026 AI audit trail checklist.
3. Integration complexity
Payments flow through banks, ERPs, treasury systems, and AP platforms, and inserting AI into that flow is non-trivial. Concerns about integration effort, disruption to payment operations, and the work of connecting AI to existing systems make teams hesitant, especially when payment continuity is critical and any disruption is costly. The perceived complexity of deployment is a practical brake on adoption even where the will exists.
4. Unclear ROI and not knowing where to start
Fraud prevention ROI is inherently hard to quantify, the value is partly in losses that did not happen, which are difficult to measure. Combined with uncertainty about which AI capability to adopt first and where it would help most, this makes the business case feel fuzzy, and a fuzzy business case loses to clearer priorities in the budget process. Many teams simply do not know where to start, so they do not. For a structured approach, see The CFO’s Guide to Measuring ROI on Finance AI.
5. Fear of false positives
A fraud control that wrongly flags legitimate payments creates real operational pain: delayed payments, frustrated vendors, and manual work to clear the false alarms. Teams worry that AI fraud detection, particularly probabilistic detection tuned aggressively, will generate false positives that disrupt legitimate business, and that fear, justified or not, makes them cautious about turning it on. The concern is really another facet of the trust problem: without confidence in why the AI flags what it flags, teams fear it will flag the wrong things.
6. The newness of AI-versus-AI fraud
AI-enabled fraud (deepfakes, AI-crafted BEC) is genuinely new, examined in the AFP survey for the first time in 2026. Defenses against it are still maturing, and many teams are still understanding the threat, let alone deploying AI to counter it. The newness itself is a barrier: organizations are earlier on the learning curve than the threat is on its development curve.
The common thread across these barriers is trust, explainability, and auditability. Integration, ROI, and false-positive concerns are real, but they sharpen to a point: finance teams need AI they can trust, explain, and account for, and much of the AI marketed for fraud, being probabilistic and opaque, does not obviously clear that bar. That is the core of why the number is 17% and not far higher.
What the 17% are gaining #
The organizations that have adopted AI against fraud are reporting concrete benefits, which makes the low overall adoption more striking. According to the AFP survey, organizations using AI for fraud mitigation reported enhanced efficiency in fraud reporting (49%), improved detection of deepfake technology (45%), and real-time identification capabilities (43%).
Those are meaningful gains, especially the deepfake-detection and real-time-identification benefits, which target exactly the emerging AI-enabled threats that manual review struggles against. The adopters are getting better at catching the newest and hardest fraud, faster. This suggests the barriers above are surmountable and the payoff is real for teams that get past them, which in turn suggests the 17% figure reflects hesitation and friction more than a verdict that AI does not work. The teams using it are largely glad they are.
It also frames the opportunity: as the barriers are addressed, particularly trust and auditability, the gap between the 17% who benefit and the 83% who do not should narrow, and the teams that move earlier gain the defensive advantage while fraud continues getting more sophisticated.
What would close the gap #
If the barriers cluster around trust, explainability, and auditability, then what closes the gap is AI that addresses those directly, not AI with more impressive detection claims. A few things would move the number.
AI whose decisions can be explained and reconstructed. The trust and auditability barriers, the two largest, are fundamentally about explainability. AI that shows why it flagged or cleared a payment, in terms a finance professional and an auditor can follow and reconstruct, removes the black-box objection. This is where the architecture matters: deterministic, explainable approaches produce reconstructable decisions, while purely probabilistic black-box models do not. The path to adoption runs through explainable AI.
Deterministic enforcement alongside probabilistic detection. Much of the fraud-AI conversation centers on detection (scoring transactions for risk), which is valuable but probabilistic and hard to audit. Pairing it with deterministic control enforcement, AI that consistently applies verification and approval rules the same way every time, with every check logged, addresses the consistency and auditability concerns and gives teams an AI application they can trust because it is doing something explainable (enforcing a defined rule) rather than something opaque (scoring a hunch).
Lower-friction deployment and clearer starting points. Addressing the integration and where-to-start barriers, with focused, well-scoped initial applications rather than rip-and-replace projects, lowers the practical barrier to entry.
This is where a deterministic neurosymbolic agentic platform like Kognitos is relevant to the adoption question, honestly framed. Kognitos addresses the trust-and-auditability barrier directly: it enforces verification and control rules deterministically (the same inputs produce the same outcome every time) and in plain English-as-code, logging every decision so it is fully reconstructable for an auditor. That explainability and auditability is precisely what the black-box objection is asking for. Kognitos is not a dedicated fraud-detection product and does not replace bank fraud tools or probabilistic detection, which remain important; rather, it represents the kind of explainable, auditable, deterministic AI whose absence is part of why adoption has lagged. The broader point is not about one platform: it is that the gap closes when finance teams are offered AI they can trust, explain, and audit, and that is a solvable problem.
Book a working session with a Kognitos solutions engineer → Try Kognitos free
Putting it together #
The 17% figure is striking not because finance teams are careless but because real barriers, trust in black-box AI, auditability of AI decisions, integration complexity, unclear ROI, fear of false positives, and the newness of AI-versus-AI fraud, stand between a pervasive threat and a tool that helps fight it. Those barriers cluster around a single, solvable issue: finance needs AI it can trust, explain, and audit, and much of the AI marketed for fraud does not clearly meet that bar. The 17% who have adopted report real gains in efficiency, deepfake detection, and real-time identification, which shows the payoff is genuine. The gap will close as explainable, auditable, deterministic AI addresses the trust concerns head-on, and the teams that move earlier gain the advantage while fraud keeps getting more sophisticated. The low number is not a verdict on AI’s usefulness against fraud; it is a measure of a trust gap that the right kind of AI can close. For the broader banking-operations context, see The Top AI Automation Tools for Banking Back-Office Operations, and the Finance & Accounting Automation Solutions overview.
Sources & disclaimer #
- Association for Financial Professionals (AFP)2026 AFP Payments Fraud and Control Survey (conducted January 2026 among 465 treasury practitioners, underwritten by Truist).
- U.S. Department of the Treasury2026 AI Risk Management Framework for financial services.
Last updated: June 2026. Statistics are from the 2026 AFP Payments Fraud and Control Survey (conducted January 2026 among 465 treasury practitioners, underwritten by Truist) as publicly reported. Figures should be validated against the primary source. This article is informational and does not constitute financial, security, or compliance advice.
