x402 and Agentic Payments: How Merchants Get Paid by AI Agents

A new kind of customer started buying things in 2026, and it does not have a wallet in the human sense. It is an AI agent acting on behalf of a person or a business, fetching data, calling APIs, and paying for what it uses in real time. Agentic payments for merchants describe exactly this shift, where the buyer on the other side of a transaction is software, not a person tapping a card. On June 15, 2026, AWS made the shift concrete by letting publishers on Amazon CloudFront and AWS WAF charge AI agents per request, settled in USDC over Coinbase's x402 Facilitator on the Base network.

This matters because the way agents pay breaks the assumptions cards were built on. An agent cannot hold a credit card, cannot pass a 3-D Secure check, and cannot sit in a bank chargeback flow. So the only practical way a machine can pay is with a programmable, instantly final, sub-cent transfer of value. That makes accepting agent payments a crypto-gateway problem rather than a card problem, and it is the reason every merchant thinking about machine customers needs to understand x402 now rather than later.

What are agentic payments, in plain terms?

Start with the most basic fact. A payment is a transfer of value plus proof that the transfer happened. For a human, that proof has historically come from a bank, which authorizes a card and stands ready to reverse the charge if something goes wrong. An AI agent has no bank standing behind it in that way, so it cannot offer the same proof a card network expects.

That single gap drives everything else. Because an agent cannot authenticate the way a cardholder does, it pays instead with money that settles on a blockchain, where the proof of payment is the on-chain confirmation itself. Once that confirmation lands, the value has moved and no intermediary can claw it back. If you want the mechanics of why on-chain settlement is final, our explainer on how crypto payments work and the on-chain mechanics behind them walks through it step by step.

So an agentic payment is a transaction where the buyer is autonomous software that pays in stablecoins, verifies settlement on-chain, and acts on the result without a human in the loop. The agent might be buying a single API call, a slice of premium content, or compute. What unites these cases is speed and size, because agents transact in tiny amounts at machine frequency, which only works if each transfer costs a fraction of a cent and clears in well under a second.

How does x402 actually work?

x402 is named after an HTTP status code that has existed since the early web but was almost never used. When a browser or an agent requests a resource, the server can reply with a status code. Code 200 means success, and code 404 means not found. Code 402 was reserved decades ago for "Payment Required" and then left dormant, because there was no internet-native way to actually pay inside a web request. x402 fills that gap.

Here is the flow in order. An agent requests a protected resource, and instead of returning the content, the server responds with HTTP 402 and a small machine-readable description of what payment is required. The agent reads that, signs a stablecoin transfer, and retries the request with proof of payment attached. A component called a facilitator verifies the transfer on-chain, and once it confirms, the server releases the content in the same request cycle.

In the AWS rollout, this happens at the edge. A publisher behind CloudFront or AWS WAF can charge an agent per page, per query, or per API call, and the agent pays in USDC on Base. Coinbase's x402 Facilitator verifies the payment, settlement lands in roughly 200 milliseconds, and per-request fees stay below a cent according to AWS. Those two numbers are the whole point, because micropayments only make economic sense when the fee is smaller than the thing being sold.

The reason 402 sat unused for thirty years is that the web had no settlement layer fast and cheap enough to bill a single request. Stablecoins on a low-fee chain finally provide one.

Why stablecoins and not a card token?

Cards settle in days and carry interchange fees measured in percentages plus fixed cents per transaction. That fixed-cent floor alone makes a one-cent sale impossible on card rails, since the fee would dwarf the price. Stablecoins remove the floor because the network fee on a chain like Base is a tiny fraction of a cent, and settlement finalizes in milliseconds rather than days. The understanding of why that finality holds is covered in our piece on transaction finality in crypto payments, which matters here because an agent has to trust the payment cleared before it releases value.

x402 vs AP2 vs card rails, which does what?

x402 is not the only agentic payment effort, and the standards are not all competitors. Some define how an agent proves intent and authority, while others define how value moves. The table below compares the three approaches a merchant is most likely to hear about, so the differences are clear before any integration decision.

Dimension	x402	AP2 (Agent Payments Protocol)	Traditional card rails
Core purpose	Settle payment inside a web request	Prove an agent's authority to pay	Authorize and clear card charges
Settlement asset	Stablecoins such as USDC	Asset-agnostic, including stablecoins	Fiat through bank networks
Settlement speed	Around 200ms on Base	Depends on chosen rail	One to three days
Per-transaction cost	Sub-cent network fee	Depends on chosen rail	Percentage plus fixed cents
Chargeback risk	None, settlement is final on-chain	Defined by the underlying rail	High, banks can reverse
Backing	x402 Foundation, Fireblocks joined	60+ partners including PayPal, Coinbase, Mastercard, Amex	Card networks and issuing banks

Read the table as a layering, not a contest. Google's AP2 focuses on the trust question, which is how a merchant knows an agent is genuinely authorized to spend a person's money. x402 focuses on the movement question, which is how the value actually transfers and settles. Card rails answer both for human buyers, yet they answer neither well for machine buyers, because the fixed fee and the chargeback flow assume a human and a bank that simply are not present.

Who is building this, and how fast is it moving?

The momentum is broad rather than a single vendor's bet. Chainalysis reported that x402 processed roughly 100 million agentic transactions on Base in about three quarters, the strongest available signal that this is real volume rather than a demo. Reporting has also cited figures near 590,000 buyers and 100,000 sellers across x402 endpoints, though those counts come from fewer sources, so treat them as directional.

On the institutional side, several names moved in June 2026. Mastercard launched Agent Pay for Machines, Fireblocks joined the x402 Foundation, and Google's AP2 reported 60-plus partners spanning PayPal, Coinbase, Mastercard, and American Express. The AWS launch sits on top of all of that, because putting per-request agent billing into CloudFront and AWS WAF places the capability in front of a very large share of the web's infrastructure at once.

The composition of the volume is worth a caution. Chainalysis noted that some early growth came from token-minting activity rather than pure commerce, and that larger transactions of a dollar or more now make up the bulk of value moved. That tells a merchant two things. The raw transaction count overstates how much is genuine retail-style buying today, and the value is steadily shifting toward real economic activity, which is the trend that makes preparing now worthwhile.

What does a merchant actually need to get paid by agents?

Work backward from the agent's constraints and the requirements fall out cleanly. An agent will not wait days for settlement, will not tolerate a fee larger than its micro-purchase, and cannot complete a card flow. So a merchant that wants machine revenue needs a payment setup that meets the agent on its own terms.

• Stablecoin acceptance, because agents pay in USDC or similar tokens, so the merchant must be able to receive and hold dollar-pegged value natively.
• Instant settlement and clear finality, because the agent needs confirmation before it acts, and the merchant needs to know the funds are irreversible.
• Multi-chain reach, because today's agent traffic concentrates on Base, yet tomorrow's may settle elsewhere, and re-integrating per chain is costly.
• Covered network gas and a single integration, because handling gas tokens per chain and stitching together separate APIs is exactly the operational drag that kills a micropayment business case.

None of this requires a merchant to bet on one standard winning. The standards layer is still settling, and the safe position is to be ready for stablecoin-settled machine traffic in general, then plug into specific protocols like x402 as they mature and as a gateway adds native support.

Where a gateway like AIO fits

To be clear about scope, AIO does not advertise native x402 support today, and this article does not claim it does. What AIO does provide is the underlying posture a merchant needs to be agent-ready. It settles in stablecoins instantly, runs multi-chain through a single API across networks including Base, and covers the network gas through a pre-funded pool so a merchant never has to manage gas tokens per chain. It is also non-custodial, so the merchant controls the funds that land.

Those properties map directly onto the agentic requirements above. A merchant already set up to price in dollars and settle in stablecoins, with gas handled and chains abstracted behind one integration, is positioned to accept machine-originated stablecoin payments without rebuilding its stack the day a protocol like x402 becomes relevant to its business. You can read the architecture behind that in our overview of AIO's crypto payment infrastructure.

What are the real risks and open questions?

Honesty about the gaps builds more trust than overselling the trend. Authorization is the largest open question, because a merchant accepting agent money needs confidence that the agent was truly permitted to spend it. That is the exact problem AP2 and similar mandate-based schemes are trying to solve, and it is not fully settled.

Reconciliation is the second. When buyers are software transacting thousands of times an hour, a merchant's finance team needs every payment traced, grouped, and auditable rather than arriving as an undifferentiated stream. Clear transaction and sub-transaction records, end-to-end trace IDs, and a real-time ledger view stop machine traffic from becoming an accounting headache.

Compliance is the third. Sub-cent payments at machine frequency still raise the same questions human payments do around sanctions screening, record-keeping, and tax reporting, and the rules for autonomous-agent commerce are early. A sensible merchant treats agentic revenue as in-scope for the same controls it already applies to crypto payments.

FAQ

Where this goes next

The web is gaining a payment layer it never had, and the first customers using it at scale are machines. As agent traffic shifts from token-minting experiments toward genuine commerce, the merchants who win the machine economy will be the ones already able to accept stablecoin payments without friction. That readiness is the practical takeaway, because the standards will keep evolving but the underlying requirement of fast, final, sub-cent settlement will not.

If you want to understand the foundations this all rests on, start with how crypto payments work on-chain and why transaction finality is what makes agent payments possible in the first place. AIO.cash is a non-custodial crypto payment gateway built for merchants, with 0.3% on pay-ins and 0% on payouts, multi-chain settlement through a single API, and covered network gas so you never touch it. Explore the AIO infrastructure overview to see how a merchant gets positioned for stablecoin-settled payments, including the machine customers arriving now.

Frequently Asked Questions

What does x402 mean for merchants?

x402 lets a merchant charge an AI agent for a single web request, API call, or piece of content, with the agent paying in stablecoins that settle on-chain in milliseconds. For merchants, it opens a new buyer type, the machine customer, that card rails cannot serve because of fixed fees and chargeback flows.

Can AI agents pay with a credit card instead of crypto?

Not practically. An agent cannot hold a card, pass a 3-D Secure check, or sit inside a bank chargeback process, and card interchange includes a fixed cent fee that makes sub-cent sales impossible. That is why agentic payments default to instantly final, sub-cent stablecoin transfers.

How is x402 different from Google's AP2?

They solve different layers. AP2 proves an agent is authorized to spend on someone's behalf, while x402 moves and settles the actual payment inside a web request. A complete agentic checkout can use an authority protocol like AP2 alongside a settlement protocol like x402.

How many agentic transactions have actually happened?

Chainalysis reported roughly 100 million agentic transactions on Base across about three quarters, the strongest available figure. Other counts such as hundreds of thousands of buyers and sellers come from fewer sources, so treat them as directional rather than confirmed.

Does AIO support x402 today?

AIO does not advertise native x402 support at this time. What it provides is the readiness a merchant needs for machine customers, including instant stablecoin settlement, multi-chain coverage through one API, covered network gas, and non-custodial control of funds.