Coinbase Business, the exchange’s merchant offering, added USDT acceptance and new merchant tools in an update detailed on August 11, 2026. The update builds on a feature that went live in late July: merchants can accept payments from AI agents through x402, an open protocol for machine-to-machine payments, with funds settling in USDC, using the same checkout pages they already have. Over the past year, most of the work on agentic payments has come from the card networks, which are adding mandates and agent credentials to their existing rails. Coinbase is coming at the problem from the other end: rather than adapting the card to the machine, it connects checkout to a protocol built for machines and settles in a stablecoin.
Agent acceptance, a developer kit, and USDT
- Agent acceptance, live since late July: the checkout pages a merchant already uses can take payments from software agents over x402, settled in USDC to the merchant’s account.
- Developer kit, announced July 23: an x402 SDK from Coinbase Developer Platform adds payment acceptance to an API, an MCP server, or a web service in three lines of code, the company says.
- USDT acceptance, added August 11: payment links, checkout pages, and invoices now accept Tether’s stablecoin, which is converted to USDC automatically at settlement.
- Merchant tools, added August 11: reusable payment links with usage limits, flexible amounts (a minimum, a maximum, or a price the payer picks), a reusable product catalog, and collection of the details needed to fulfill an order.
x402 puts a long-dormant HTTP status code to work
The protocol is built on an HTTP status code that sat unused for decades. 402 Payment Required has been in the web’s specifications since the early versions, explicitly reserved for future use. x402 finally gives it a job: a machine-readable payment negotiation that runs inside the ordinary exchange between a client and a server.
- The agent requests a paid resource (an API, an article, a computation, a dataset).
- The server responds with
402and the payment terms: amount, accepted asset, and settlement address. - The agent pays in stablecoin, with no human involved, out of the budget its principal gave it.
- The agent resends the request with proof of payment in a header, and the server delivers the resource.
Card networks and x402 are making different bets
Agentic payments are developing along two lines that can coexist. The first keeps existing payment instruments and adds a layer of verifiable mandates, so an issuer knows the agent is acting for an identified cardholder and within limits that cardholder has set. The second, the x402 approach, assumes the payer does not need to be a cardholder at all. A balance and a protocol are enough.
| Card rails adapted for agents | x402 with stablecoin settlement | |
|---|---|---|
| Instrument | Tokenized card, mandate tied to the cardholder | Stablecoin balance held by the agent or its principal |
| Authorization | Issuer, after the cardholder authenticates upfront | Merchant’s server verifies the payment |
| Smallest viable amount | Limited by fixed per-transaction fees | Micropayments, Coinbase says |
| Reversal | Chargeback and the network’s dispute process | None: settlement is final |
| Legal framework | Payment services rules, well-defined liability | Crypto-asset rules, less settled liability |
No chargebacks for merchants means no recourse for payers
Coinbase pitches the lack of chargeback risk as a selling point: a stablecoin settlement cannot be clawed back. For merchants, that promise is real, and it is an old one; bank transfers have always offered it. For payers, it cuts the other way. There is nothing like the refund rights card networks provide when goods never arrive or a payment was never authorized.
Compliance is the second open question. Accepting a payment from an agent means accepting a payment whose human principal is not part of the transaction. Know-your-customer, sanctions, and anti-money-laundering obligations all assume a customer who can be identified. Agentic protocols move that identification upstream, to the moment the mandate is granted, rather than to the point of acceptance. The design is coherent, but merchants can rely on it only once regulators accept it.
The numbers also put the offering in proportion. At 5,000 businesses and 100,000 cumulative payments, the offering is an advanced experiment, not a mass-market rail. What stands out is less the volume than the signal: accepting a payment from a machine is no longer a lab project. It is a setting a merchant can switch on in a dashboard.