If AI agents check out without typing patterns or mouse movements to verify them, who ends up eating the fraud?
What fraud losses result when behavioral biometrics disappear in agent transactions?
This explores what happens to fraud, and to who pays for it, when an AI agent completes a purchase instead of a person, so the typing rhythm, mouse movement and other behavioral signals that fraud systems watch for are no longer there.
This explores what happens to fraud, and to who pays for it, when an AI agent checks out instead of a human and the behavioral clues fraud systems depend on disappear. First, a direct caveat: the corpus has no dollar figures or loss rates for this. No source here measures how much fraud rises when behavioral biometrics go away. What it does show is something many readers won't expect. The main loss isn't a new kind of fraud. It's a change in who absorbs the fraud that already exists, with the blind spot landing on whoever is least able to see.
The sharpest version of this is Does agentic commerce shift fraud liability onto merchants?. When an agent fills in the checkout form, signals like typing cadence and mouse movement no longer tell you whether a real, legitimate person is present. Yet under every proposed agent-commerce protocol, the merchant is still the Merchant of Record, the party legally responsible for the sale. So merchants carry the risk of transactions run by software while losing the detection tools they used to manage that risk. Does agent-initiated commerce break existing payment infrastructure? describes the same gap from the infrastructure side. Payment gateways and fraud engines were built around a person whose identity and intent can be observed, and agent-initiated transactions put pressure on exactly those assumptions. Federal Reserve Governor Waller groups the problem into three barriers: proving the agent is authorized, deciding who pays when something goes wrong, and detecting fraud patterns specific to agents. He treats all three as unsolved obstacles to scaling agent purchases (What blocks autonomous agents from handling purchases at scale?).
The industry's main answer is to replace watching behavior with checking signed proof. Google's AP2 protocol chains cryptographically signed 'Intent' and 'Cart' mandates into a tamper-proof record of what the user actually authorized (How can signed mandates prevent payment fraud by agents?). Note what this shifts. Behavioral biometrics asked 'is this a real human acting normally?' Mandates ask 'did a real human sign off on this?' That helps with disputes after the fact. It doesn't help in real time if a compromised or confused agent carries out a properly signed but bad instruction. Identity is a second gap. Can credential vaulting alone solve merchant-facing agent identification? argues that safely storing the consumer's card details doesn't tell the merchant which agent is at the door or whether it has permission to be there. The Amazon–Meta Muse dispute shows what happens without such a standard: retailers fall back on blocking agents through their terms of service (What identity standards do shopping agents actually need?).
The security research widens this from 'fraud signals vanished' to 'the agent itself becomes a place where attacks can happen.' Red-teaming work finds that an agent's identity often lives in context files that can be manipulated, and that its authorization often rests on the conversation rather than on enforcement at the system level (Why do agents fail at identity verification and authorization?). An attacker therefore doesn't need to imitate a human's typing. Steering the agent is enough. There's also a less obvious cost. One proposed fix, routing agent authentication through large login providers such as Google, would give those providers a cross-service view of what agents are doing (Do OpenID Providers gain surveillance power over AI agents?). Replacing behavioral surveillance at the merchant could create a new kind of surveillance at the identity layer.
So the honest answer is this. The corpus describes the losses as a transfer of risk to merchants plus a new attack surface. It does not yet quantify a fraud-loss number. If you want to see where that risk ends up in a real market, travel is a useful case. OTAs (online travel agencies such as Expedia) are keeping their Merchant of Record role as agents arrive (Are AI agents actually removing online travel agencies from bookings?), which means they're the ones holding this liability.
Sources 9 notes
Boboev argues that AI agents executing transactions remove behavioral fraud signals like typing cadence and mouse movement, leaving merchants holding liability as Merchant of Record across all proposed protocols. Merchants absorb autonomous-execution risk without access to the fraud-detection tools they historically used.
McKinsey argues that payment gateways and fraud engines built around explicit human identity and intent face significant strain when autonomous agents initiate transactions. The firm proposes cryptographically signed mandates as a replacement for human-observable signals fraud systems traditionally relied upon.
Federal Reserve Governor Waller names three concrete trust challenges blocking autonomous agent-delegated purchases: proving agent authority (authentication), determining payment responsibility (liability), and detecting agent-specific fraud patterns. Delegation introduces higher risks requiring extensive guardrails and trust mechanisms.
Google's Agent Payments Protocol chains signed Intent and Cart Mandates into tamper-proof records of user authorization. Built with 60+ payment firms, the protocol captures user intent upfront and verifies cart contents before payment, establishing accountability for agent-led transactions.
Secure credential storage is a unilateral consumer-security control that prevents agent exposure of secrets, but it cannot substitute for a visible, retailer-legible self-identification protocol that both the account holder and merchant must agree to separately.
Show all 9 sources
Amazon's block of Meta's Muse reveals that AI agents need standardized ways to identify themselves and prove authorization to retailers—separate from consumer-side credential security. Without such protocols, retailers enforce access through terms-of-service blocks rather than negotiated standards.
Red-teaming and NIST's 2026 initiative converge on the same three architectural gaps: identity is stored in manipulable context files, authorization relies on conversational context instead of system-level enforcement, and agents lack proportionality constraints. These are protocol-level problems requiring architectural solutions, not model improvements.
The paper's own limitations section identifies that routing all agent authentication through OpenID Providers (Google, Facebook, etc.) positions those providers to track and profile agent interactions across services. This surveillance capability emerges directly from the authentication architecture proposed as a security improvement.
Goswami's 2026 travel data shows independent hotels' OTA dependence rose to 63.4% even as AI agents emerged, with OTAs retaining merchant-of-record status through API integrations. Expedia's B2B segment grew 24% year-over-year, now 38% of revenue.
Papers this line draws on 8
The research behind the notes this line reads — ranked by how closely each paper relates.
- Authenticated Delegation and Authorized AI Agents
- Payments in the Age of AI Agents
- The agentic commerce opportunity: How AI agents are ushering in a new era for consumers and merchants
- How Agentic AI Will Reshape Payments
- AI Agents Want to Shop for You: The Future of Agentic Commerce
- Deep Dive: The hidden liability of agentic commerce
- The Coasean Singularity? Demand, Supply, and Market Design with AI Agents
- Accelerating the Adoption of Software and AI Agent Identity and Authorization (concept paper, draft)