Viewpoint

The Fraud that Isn't: Building Trust Infrastructure for AI Finance

Written by
No items found.
Andrew Lambert, SVP, Head of Product, Cross River
November 9, 2026
|
3
min read

A year or two ago, if our fraud system spotted a bot executing a transaction, we blocked it. Today, that same bot activity could be a legitimate customer using an AI agent to make authorized purchases.

Here’s an example:

A customer asks an AI agent to do research and gives it a budget. The agent buys access to databases, purchases information, subscribes to services, then delivers the summary. In a second and a half, it executes 10 microtransactions. From a traditional issuing platform fraud monitoring perspective, that velocity looks exactly like an attack. But it's really a user’s agent working as designed.

As a result of this significant shift in what could be “normal” behavior, the fundamental challenges we’re solving for agentic finance are two-fold:

  1. Agent platforms like Muse or Instinct sit outside the traditional payment model's roles. They're not merchants, not acquirers, but intermediaries executing transactions on delegated authority. That means the levers that shaped behavior for decades, including interchange rates and chargeback rules, don't influence them the same way.
  2. Context. As with the above, if the customer completed a transaction, it could be assumed that they were buying the intended good or service (except in cases of fraud or merchant error – which have extremely mature procedures to manage). In the agentic scenario, the customer has given that context to an agent and then trusted it to complete a set of actions, culminating in a purchase. This presents the challenge of how and when the context should be shared with a merchant or issuing system.

Meanwhile, from a regulatory perspective, established statutes like Reg E continue to apply, and issuer liability frameworks remain in effect whether a human or an agent initiated the transaction. The rules are unchanged, but the reality of processing these transactions is completely different.

At Cross River, we're building infrastructure to solve these new realities, already powering agents. Working with partners like Visa and Stripe, we're developing the components that make verifiable, continuous consent possible:  

- Agent directories that let merchants distinguish between authorized agents and malicious bots at checkout

- Tokenization with context: not just encrypted credentials, but embedded metadata that answers who the consumer is, who the agent is, what the consumer authorized the agent to do, and whether the agent is staying within those boundaries

- Transaction-level indicators that tell fraud systems this is a trusted agent acting on delegated authority  

- Continuous consent monitoring that tracks whether the user's permission is still valid across interactions spanning hours, days, or months.  

Without these signals embedded in the flow, you can't scale agentic finance safely.

The only point where the technical constraint is unforgiving is at the moment of approval: we have to bind together the end user who passed KYC, the agent's delegated authority, and the consent to transact in the time it takes to approve a payment, without slowing down commerce or adding friction that breaks the experience. Think of it like subscription indicators in authorization messages or secondary authentication. One provides context that tells the system this is an ongoing request, not a one-time purchase, and the other confirms authority. Those are the building blocks Cross River is creating.

AI agents are becoming the default interface between consumers and commerce. Cross River’s proprietary, composable infrastructure operates at the authorization layer where identity, risk, and payment execution converge. We're building the trust layer agentic finance requires, because the opportunity is real, and the window to get it right is now.

‍

About the author
No items found.
Subscribe to our newsletter
You can unsubscribe anytime.

Related Articles