Field note

Your fraud AI can't see what your data hides

Fraud-prevention AI demos dazzle, then meet reality - the bank's wire, ACH, card, and instant-rail data live in separate systems. A model that cannot see the whole customer cannot catch a fraudster who moves across all of them.

Jun 19, 2025 · Navin Agrawal · AI systems · 3 min read

Your fraud AI can't see what your data hides

Visual brief

Visual brief

Your fraud AI can't see what your data hides

As of June 2025

The fraud AI is not the problem. The fragmented data underneath it is - and a model that sees one rail at a time loses to a fraudster who works across all of them.

The fraud-prevention demos look amazing until you remember where the data actually lives: wire in one system, ACH in another, cards in a third. How is a model supposed to spot a pattern it cannot even see?

What the fraud model sees

One rail at a time. Wire transfers sit in the legacy core. ACH runs through a separate monitoring platform. Card activity belongs to a different vendor with different rules. The instant rails, TCH-RTP and FedNow, arrive as brand-new data streams bolted on last. Each system has its own view, its own rulebook, and its own idea of “normal.”

How the fraudster operates

Across all of them, on purpose. They test your wire limits, probe ACH for weak controls, then execute through instant payments where the money is gone in seconds. Their cross-channel coordination is better than most banks’ fraud systems, because the bank’s systems were never wired to compare notes.

Fraud AI's blind spot (June 2025)

The four monitoring silos a fraud model has to reason across, and the adoption-versus-data-readiness gap behind the problem.

As of June 2025: a bank's fraud AI watches four separate rails - wire (legacy core), ACH (separate platform), cards (different vendor), and RTP/FedNow (new data streams) - each monitored in isolation. 90% of banks now use AI for fraud detection; 87% cite data management as their biggest implementation challenge (Feedzai, State of AI 2025).
Four rails, four monitoring systems. The model is handed one page of the case file at a time.

Fraud AI's blind spot (June 2025)

Fraud AI's blind spot (June 2025)

As of June 2025: a bank's fraud AI watches four separate rails - wire (legacy core), ACH (separate platform), cards (different vendor), and RTP/FedNow (new data streams) - each monitored in isolation. 90% of banks now use AI for fraud detection; 87% cite data management as their biggest implementation challenge (Feedzai, State of AI 2025).

The disconnect is structural, not cosmetic. Banks are deploying sophisticated machine-learning models on top of data architectures that were never designed to share a customer. Fragmented data leads to fragmented protection, and in fraud prevention partial visibility is almost as dangerous as none - it produces confident alerts on incomplete pictures.

Fraudsters don't operate in silos. Asking a model to catch them while showing it one rail at a time is like asking a detective to solve a case from random pages of the file.

AI adoption

90%

of banks now use AI for fraud detection - the model is no longer the hard part (Feedzai, State of AI 2025).

The real bottleneck

87%

cite data management as their biggest AI implementation challenge, not the algorithm.

The blind spot

4 silos

wire, ACH, cards, and instant rails monitored separately, so no single model sees the whole customer.

The banks making real progress are not just buying a better model. They are rebuilding the data layer first - a unified platform where the fraud model can see wire, ACH, card, and instant-rail behavior as one customer, not four strangers. The sequence matters: unify the data, then point the AI at it. Do it the other way around and you have bought an expensive detector for patterns it structurally cannot see.

Was this useful?

Choose once.

Related Posts

View All Posts »
Most AI agents never reach production. Payments is where that gets expensive

Most AI agents never reach production. Payments is where that gets expensive

The widely cited figure is that 88 percent of AI proofs of concept never reach production. Agentic payments inherit that gap, and the teams that cross it are not winning on model selection. They are winning on payments-specific infrastructure that makes an agent idempotent, governable, and rollback-safe at the rail boundary.

Multi-model is the new multi-rail

Multi-model is the new multi-rail

Every payment system routes across multiple rails - ACH fails, traffic moves to wire, and wire is dear for small amounts so you route to RTP. Most AI systems still call one model and hope it stays up. The LLM gateway is the same routing engine payments has run for decades, and it needs the same three things to count.

Agents do the wiring, architects carry the tradeoffs

Agents do the wiring, architects carry the tradeoffs

AI agents are arriving faster than most banking career ladders can adapt, and the market is already rewarding people who work with them. The career moat was never wiring up another API call. It is the judgment calls agents cannot own - which rail to trust, how much latency to spend, who the regulator will be.

AI agents can buy now, and fraud systems were not built for it

AI agents can buy now, and fraud systems were not built for it

Stripe, OpenAI, and Google shipped protocols that let AI agents complete purchases inside a conversation. The rails are already fast enough. The problem is that fraud detection was architected around a human clicking buy on a trusted surface, and agents break that assumption.