Home/Web4 & RWA/热点新闻
热点新闻

Crypto Long & Short: What happens when an AI agent pays for the wrong thing

CoinDesk

2026年10月28日
Crypto Long & Short: What happens when an AI agent pays for the wrong thing

Note: The views expressed in this column are those of the author and do not necessarily reflect those of CoinDesk, Inc., CoinDesk Indices or its owners and affiliates. This is your institutional news

Note: The views expressed in this column are those of the author and do not necessarily reflect those of CoinDesk, Inc., CoinDesk Indices or its owners and affiliates. This is your institutional newsletter, Crypto Long & Short. This week: * Albert Castellana of GenLayer Labs on who covers the loss when an AI agent's payment goes wrong * Top headlines institutions should pay attention to by Francisco Rodrigues * "Hyperliquid volume vs. HYPE price" in Chart of the Week Thanks for joining us! AI agents can pay for things online but can't dispute a charge - by Albert Castellana, co-founder and CEO, GenLayer Labs Card networks just backed a payment system with no standard way to dispute a charge. In July, the Linux Foundation switched on the x402 Foundation, which governs the standard that AI agents use to pay for things online. Visa, Mastercard and American Express are among its 17 premier members, the top governance tier. All three now help govern a payment standard with no standard dispute process. Once a stablecoin payment settles onchain, there is no issuer to call and no network chargeback to file. Mastercard said at the launch that internet-native payments will need the same secure, trusted and interoperable foundation as today's digital commerce. Trust in card payments has a specific mechanism behind it, and has had one for over 50 years. The right to dispute a credit card charge has been law in the U.S. since 1974, when the Fair Credit Billing Act passed. It's one reason people became willing to buy from strangers online. If the parcel never turns up, you can call your bank and the money comes back. The x402 protocol leaves that out on purpose, and the reasoning was sound. Payments can settle in hundreds of milliseconds and cost a fraction of a cent, which makes machine-scale micropayments possible. When Coinbase published the protocol in May 2025, usage was sparse, and it was a fair trade. There is another difference that matters even more. Every safeguard the card industry built assumes a person notices something is wrong and complains. In x402, the buyer is often software, and software doesn't read statements. In July, researchers at the Swiss Federal Institute of Technology in Lausanne (EPFL) and Zhejiang University published the first systematic security study of live x402 deployments. They tested 15 facilitators, the intermediaries that verify a payment and push it onchain, and every one broke at least one of eight safety rules the researchers defined. On Base, close to 2% of settlement attempts reverted in late 2025, which is around 1.9 million payments. All seven of Coinbase's official reference kits for sellers lack any way to undo what the server already did when a payment fails to settle. One of them, the Flask kit up to version 0.2.1, releases the goods once a payment proof verifies, before settlement is confirmed. If settlement then fails, the seller has delivered and won't be paid. Early infrastructure often has bugs. The bigger problem is that payment, delivery and settlement can disagree. The reverse problem is more interesting for what comes next: the payment settles perfectly, but the agent receives something wrong, incomplete or useless. The x402 protocol supports card rails as well as stablecoins, and card payments keep their protections. However, 97% of observed x402 transactions run on Base and Solana, where stablecoin payments are final. None of which is an argument against x402. Payment finality is not commercial finality. A blockchain can prove that money moved. It cannot decide whether the data was correct, the service was delivered or either side kept its part of the deal. Card networks answered the dispute question over five decades, and every answer cost somebody money. Who absorbs the loss? Who decides whether the service arrived? How long does a buyer have to complain, and what counts as evidence? At a tenth of a cent, none of those answers can involve a lawyer, and most of them can't involve a human at all. Agent payment volumes are still small enough that a bad month would be survivable. The companies in that top tier hold most of the world's institutional knowledge about what a dispute process costs and what it buys. The question is whether they build its machine-native replacement before the losses force them to. We spent the last few years making money programmable. Now we need to make recourse programmable too. Headlines of the week by Francisco Rodrigues This week's headlines show banks taking tokenization onto public blockchains and into consumer apps, while BlackRock moves to sell bitcoin exposure with downside protection. Regulators and stock issuers, meanwhile, began drawing lines around what these new products can do. * HSBC rolls out its first stablecoin to over 3 million everyday app users: The bank launched RedCoin, a Hong Kong dollar stablecoin, on its PayMe app, letting more than 3.3 million users send money and pay at more than 100,000 merchants. Tokenized investments are planned next. * JPMorgan brings JPM Coin, representing dollar deposits, to Ethereum: The bank made its dollar deposit token available to institutional clients on Ethereum, extending it beyond Base and JPMorgan's private Kinexys network, which processes more than $7 billion a day. * OCC issues first final rule implementing the GENIUS Act: The regulator said existing stablecoin rewards programs get no automatic protection. It will assess them case by case once the rule takes effect Jan. 18. * BlackRock seeks to shield bitcoin investors from losses with proposed ETF: The asset manager filed for the iShares Bitcoin Managed Protect ETF, which would offer capped bitcoin-linked gains with downside protection. The filing didn't disclose the protection level or the cap. * Wells Fargo, Cisco and Marvell join objections to OKXICE's tokenized-stock plan: Six more companies opted out of the planned venue, bringing disclosed objections to 22 and highlighting an early obstacle for tokenized-stock trading under the SEC's new framework. Hyperliquid volume vs. HYPE price: volumes flat, potential U.S. flow ahead Hyperliquid volumes and HYPE price are flat for now (HYPE ~$77.6, daily perp volume ~$8 billion) but potential US flow could come soon, with Kraken's parent Payward planning to be the first CFTC-regulated deployer on a permissioned HIP-3 variant (Bitnomial running the markets, pending approval). Looking for more? Receive the latest crypto news from coindesk.com and market updates from coindesk.com/institutions.