The challenge for AI agents is deciding who pays for automated errors

Imagine asking an AI assistant to book a decent hotel for a weekend away. You give it a budget and say you’d like somewhere near the center, then it finds a room, pays, and sends you the confirmation.

The hotel is within budget and in a solid location, but the room has no window, breakfast costs extra, and cancellation is impossible.

The software may have followed its instructions closely enough to leave you arguing about a purchase you would never have made yourself. As payment companies build services for AI agents, that gap between permission and satisfaction becomes part of the product they have to sell.

In a report released Sept. 8, Mastercard forecasts that one in ten people will routinely use AI agents to shop and pay by 2030.

Shopping online can mean comparing a dozen tabs, decoding fees, and wondering whether the product description has omitted something essential. Software that does the tiresome part deserves a chance, but once it can spend money, its mistakes become purchases someone has to undo.

Crypto is one way to give that software a payment method. The hard work is deciding how much authority it has and who is responsible when a completed transaction becomes the start of the problem.

Teaching a wallet what you meant

AI agents are software allowed to take actions toward a goal. Travel assistants cross an important boundary when they go from recommending rooms to reserving and paying for them on your behalf.

Payment permission needs to describe the purchase you authorized. Spending ceilings of $200 can prevent $500 bookings, while leaving room for disagreement over cancellation terms and checkout fees. Software also needs to know which room features it can compromise on.

People routinely leave details unstated because another person would infer them or ask before committing. Payment systems need instructions they can verify, which means translating an ordinary request into limits without making the user write a contract before every purchase.

Google’s Agent Payments Protocol addresses part of that work through digitally signed records called mandates. These connect users’ instructions with proposed purchases and payments. Users can approve specific carts or authorize purchases under conditions set in advance.

For the hotel example, that could mean a record of the maximum total price and the exact room approved. If the AI agent books something else, the signed record gives the participants evidence beyond their competing recollections of what happened in a chat.

Card networks are also working on their own agent arrangements. Mastercard describes authorization and authentication as part of Agent Pay, alongside controls over what an assistant is allowed to do.

The word “token” appears here too. Card tokens replace sensitive card credentials with identifiers used to process payments, and dollar stablecoins are transferable assets designed to track the dollar.

The limits built around either method determine how much freedom an agent gets. Carefully configured crypto wallets can restrict spending more tightly than poorly configured card services.

Card-based products can provide their own controls alongside established dispute processes, and users delegate authority across that arrangement, including the settings that govern individual purchases.

The payment can succeed while the purchase fails

Some things agents buy may be too small or too dull for people to approve individually. Travel assistants might pay other software services for current room availability as part of finding the right booking.

The x402 payment standard enables this through standard web requests. Services reply that payment is required and supply the terms. The requesting software can then submit payment for verification and receive the information it wanted.

The user doesn’t have to open a subscription with every small service involved. That can be an appealing alternative to maintaining accounts for one-off use, especially when each request costs only a few cents.

Small purchases still need a budget. In this hypothetical example, an AI assistant pays two cents each time it checks a data service:

Illustrative prices and usage, not a quote from an actual provider.

Per-payment limits would permit both outcomes. Total budgets and attempt limits can stop the second, provided the software tracks spending across the task, which is important when services return errors and the assistant keeps trying.

Repeated attempts need to be distinguished from completed purchases, with controls against duplicate charges. Receipts must also connect spending to the task so users can see whether the money bought information or funded a loop.

Under x402’s exact-payment scheme, executed transfers are irreversible, though sellers can refund buyers by sending money back in new transfers. Its batch-settlement scheme has separate provisions for refunds and withdrawals from escrow, where funds are held under specified release conditions.

Getting money back depends on the seller’s policy and any contractual or escrow arrangements governing the funds. Basic token transfers have no card-style dispute process of their own, so the surrounding service must provide a route for complaints and repayment.

The Consumer Financial Protection Bureau describes circumstances in which a credit-card purchase can be disputed, and the issuer may reverse a charge. Those processes aren’t a universal promise that every disappointing purchase, including one delegated to software, will be refunded.

An agent booking a hotel needs more than a successful payment receipt. The customer needs proof of the advertised room, the cancellation terms, and the instruction that authorized the booking. The payment network can establish that money moved, but resolving the purchase can require evidence from several other participants.

Nobody wants to manage the AI agent shopping assistant

The hotel example starts as an attempt to save time. It fails if the traveler has to spend hours reading logs to establish why the assistant chose a windowless room.

People buy this kind of convenience to spend less time on a task. Supervising a junior purchasing department would be an expensive substitute, especially if every mistake requires reconstructing a chain of software decisions.

People want to approve expensive purchases and let small, repetitive ones proceed within a budget. Refundable reservations could go through automatically, while nonrefundable bookings require confirmation.

Those controls track how expensive a mistake would be and how easily it could be undone.

The interface has to preserve those distinctions through checkout. Spending ceilings should include fees, and permissions need to expire when the job ends. Receipts should identify the merchant and explain the purchase in terms the customer recognizes, so resolving a dispute starts with what was bought rather than a search through payment addresses.

An AI assistant recommending a hotel can rank options by the user’s preferences, by payments from sellers, or by some combination disclosed in its business model. Automating the purchase just makes the incentives less visible if the customer never sees the alternatives.

The commercial model belongs alongside the spending permissions. Before letting an agent choose and pay, buyers need to understand whether sellers can pay for placement and how those payments affect the options presented.

The same applies to the software services an agent buys along the way. The user may be happy to pay a few cents for better information, but it may be less happy if the assistant repeatedly purchases data that doesn’t improve the booking.

A system that handles these details well can support both card networks and stablecoins. Cards connect to established merchant and dispute arrangements, and crypto payment standards can make small, programmatic purchases easier to arrange across services.

Neither payment method can substitute for understanding the task.

For travelers, successful assistants would remember the room requirements, explain the total commitment, and resolve a booking that went wrong. The payment would be one step in a job completed on their behalf.

That's the convenience worth paying for: closing the app and getting on with the weekend.