AI Agent Payments Explained: How x402, AP2 And Stablecoins Enable Autonomous Commerce

On Sept. 22, Coinbase gave AI trading agents a new skill: buying their own research. An agent can now pay a few cents in USDC (USDC) for an earnings summary, read it and place a stock trade inside limits its owner set. The protocol behind that payment, x402, has processed more than 230 million transactions in just over a year, Coinbase says.

Together with Google's Agent Payments Protocol (AP2), x402 is turning a forgotten web error code into plumbing for machine-to-machine commerce, and this piece explains how it works, who is building it and where it can break.

• Coinbase's Sept. 22 update lets AI agents trade U.S. stocks and pay for data per request through x402, a protocol Coinbase says has handled more than 230 million transactions and $54 million in volume.
• x402 moves stablecoin payments inside ordinary web requests, while Google's AP2 uses signed "mandates" to prove an agent had permission to spend, and the two are built to coexist.
• A Visa and Artemis report cut cumulative x402 volume to about $15 million from roughly $135.7 million, so real organic demand remains far smaller than headline figures. Stablecoin rules in the U.S. and EU are still settling, so this is early infrastructure, not a finished market.

What Are Agentic Payments, And Why Do AI Agents Need Them?

Agentic payments are transactions that software agents start and finish on behalf of a person or a company. The agent finds a service, accepts a price and pays, often in the middle of a larger task.

The idea sounds simple. The plumbing is not.

Card networks, bank transfers and checkout pages were designed around a human sitting at a screen. Google said as much when it launched AP2, writing that today's payment systems "generally assume a human is directly clicking 'buy' on a trusted surface."

Autonomous agents break that assumption in two ways. They need to buy many small things, such as one data point or one model call, and they need to do it at any hour without anyone typing in card details.

Subscriptions and API keys became the workaround. A developer signs up, stores a key and pays a monthly bill, even if the agent needs only a single query.

Coinbase framed the problem in its Sept. 22 launch note for Coinbase for Agents. Research and trading loops, it wrote, are "tedious for a person, yet trivial for an agent."

Central bankers have noticed. Federal Reserve Governor Christopher Waller told the Sibos conference in Miami on Sept. 29 that small machine-to-machine payments "could reach a much larger scale if shopping agents are working around the clock at machine speed."

Also Read: Gemini Agent Runs On Claude Too As Google Says Nearly 80% Of Clients Use Its AI

Image: Shutterstock

How Does x402 Work, And What Is The Role Of HTTP 402?

Every web request ends with a status code. Most people know 404, the "not found" error, and few notice 200, which quietly means everything worked.

Code 402, "Payment Required," was reserved for digital payments in the early web but never received a standard use. Coinbase released x402 in May 2025 to fill that gap with stablecoin payments carried inside normal HTTP traffic.

The logic is direct. A server that wants money answers with a 402 and a price, and the client pays and asks again.

Developers shipped x402 V2 on Dec. 11, 2025, roughly six months after launch. The upgrade made the protocol "multi-chain by default," able to support tokens native to Base or Solana (SOL), and compatible with legacy rails such as ACH and card networks.

V2 also added wallet-based sessions, so an agent that has paid once can return without repeating the full on-chain flow. Dynamic routing of the payee address opened the door to usage-based billing, subscriptions and prepaid plans.

Governance changed hands as well. Coinbase and Cloudflare announced plans for an x402 Foundation on Sept. 23, 2025, and the effort later moved under the Linux Foundation.

The Linux Foundation declared the x402 Foundation operational on Jul. 14, with 40 members. Premier members include Adyen, Amazon Web Services, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, MoonPay, Ripple, Shopify, Stripe and Visa, alongside the Monad Foundation, Solana Foundation and Stellar Development Foundation.

The protocol is no longer tied to one asset. Ripple said in the launch release that its x402 support lets agents "transact using XRP (XRP) and RLUSD (RLUSD) today."

Also Read: Vitalik Buterin Sees AI Threat To Cryptography, Rejects Rushed Wallet Moves

What Happens During A Machine-To-Machine Payment, Step By Step?

Under x402, a paid API call looks almost identical to a free one. The difference is a short negotiation that happens inside the HTTP headers.

Circle's developer documentation describes the flow in five steps:

• The agent requests a resource, such as a stock quote or a model output.
• The server replies with a 402 status and a PAYMENT-REQUIRED header listing accepted schemes, price, network and destination address.
• The agent picks an option, signs a payment payload with its wallet and resends the request with a PAYMENT-SIGNATURE header.
• The server verifies the payment directly or through a facilitator, which checks the signature and settles the transfer on-chain.
• The server returns the data along with a PAYMENT-RESPONSE header confirming the payment.

Facilitators do the heavy lifting. They let a data seller accept stablecoins without running its own blockchain infrastructure, and Coinbase's Sept. 22 note calls the company "the #1 facilitator, processing more than half of all x402 transactions."

For USDC, the signature relies on a token standard called EIP-3009, or transferWithAuthorization. It lets a facilitator submit the agent's signed approval on-chain without a separate allowance step, which helps explain why USDC became the default x402 asset.

A live example arrived this autumn. Market data provider Massive launched x402 access to its U.S. stock data on Sept. 1, built with Coinbase, with "no account to create and no API key to manage."

Agents pay per request in USDC on dedicated routes, and Coinbase Developer Platform's facilitator verifies and settles each payment before Massive returns the data. Kevin Leffew, who works on developer partnerships at Coinbase and co-authored x402, called the integration "a critical building block for the future of agentic finance and trading."

Compute and inference follow the same pattern, but the amounts can get tiny. Circle's Nanopayments, now live on mainnet, allows gas-free USDC transfers as small as $0.000001 by aggregating payments off-chain and settling them on-chain in batches.

Circle executive Gagan Mac said in the Linux Foundation release that agents using x402 and USDC "can make payments that clear in seconds for a fraction of a cent."

Also Read: Tesla, Apple And Nvidia Tokens Hit Solana As Securitize Starts 12-Stock Trading

How Does Google's AP2 Protocol Differ From x402?

Google announced AP2 on Sept. 16, 2025, with more than 60 organizations, including Adyen, American Express, Coinbase, Etsy, Mastercard, PayPal, Revolut, Salesforce and Worldpay. It can run as an extension of Google's Agent2Agent (A2A) protocol and the Model Context Protocol (MCP).

The two protocols solve different problems. x402 handles how money moves inside a web request, while AP2 handles whether an agent was allowed to spend that money at all.

Google built AP2 around three questions. Authorization asks whether the user gave the agent authority for this specific purchase, authenticity asks whether the request reflects the user's real intent, and accountability asks who answers for a fraudulent or wrong transaction.

The answer is a set of "mandates," which Google describes as tamper-proof, cryptographically signed digital contracts backed by verifiable credentials. An Intent Mandate records what the user asked for, and a Cart Mandate locks in the exact items and price the user approved.

AP2 is payment-agnostic, covering cards, real-time bank transfers and stablecoins. For crypto, Google worked with Coinbase, MetaMask and other groups on the A2A x402 extension, which it called "a production-ready solution for agent-based crypto payments."

Google has since handed the protocol to a standards body. It donated AP2 to the FIDO Alliance on Apr. 28 and released version 0.2, which adds "Human Not Present" payments based on pre-authorized instructions.

In short, AP2 is the permission slip and x402 is the cash register.

Also Read: OpenAI's 719 AI Math Proofs Under Fire: Was Navier-Stokes Lost In Translation?

How Do AI Agents Prove Authorization And Operate Within Spending Limits?

Every protocol in this field is chasing one question. How does a seller know a machine is spending with real permission?

AP2's answer depends on whether a human is watching. When a user delegates a task, such as buying concert tickets the moment they go on sale, the signed Intent Mandate sets price limits, timing and other conditions, and the agent can then generate a Cart Mandate automatically.

Coinbase relies on account-level guardrails instead. Its Sept. 22 note lists the controls an owner can set for an agent:

• Isolate the agent in a specific portfolio for crypto-only trading.
• Configure which assets the agent can access.
• Set spending limits.
• Require approval for individual actions.

Sandboxed accounts for equities are "coming soon," the company said. Trades in stocks and ETFs route through Coinbase Capital Markets Corp., with Apex Fintech Solutions handling clearing and custody.

Card networks are building their own permission layers. Mastercard's Agent Pay for Machines, launched Jun. 10, stores the permissions humans grant their agents on blockchains, starting with Polygon (POL), Solana and Base, Fortune reported.

Visa said in a Dec. 18, 2025 release that it and more than 10 partners introduced its Trusted Agent Protocol in October 2025. The framework helps merchants tell legitimate AI agents acting for consumers apart from malicious bots.

Permissions do not settle liability, though. Coinbase's own disclaimer warns that "AI agents may make mistakes or fail" and that users "assume all risk for transactions your agents execute."

Also Read: Bitget, Block Scholes Model Shows Tokenized Stocks Nearly Halve Capital Needs

Image: Shutterstock

How Do Agentic Payments Differ From Credit Cards And Conventional Payment APIs?

A card payment assumes an identified human, a stored card number, a merchant account and a dispute process. That design suits a $50 checkout but struggles with a one-cent data call made thousands of times a day.

A conventional payment API still requires onboarding. The buyer creates an account, receives credentials and gets billed later, while the seller manages keys, invoices and collections.

x402 strips most of that away. The payer is a wallet, the price travels inside the request, and settlement happens on-chain before the data is returned.

Incumbents are adapting rather than stepping aside. Stripe and OpenAI released the Agentic Commerce Protocol in late September 2025 to power Instant Checkout in ChatGPT, with a Shared Payment Token that lets ChatGPT start a payment without exposing the buyer's card details.

OpenAI's documentation says it prepares a one-time delegated payment request with "a maximum chargeable amount and expiry." That is card-era security retrofitted for agents.

Stripe is also hedging toward crypto rails. Tempo, the payments blockchain incubated by Stripe and Paradigm, launched its mainnet on Mar. 18 alongside the Machine Payments Protocol, an open standard co-authored with Stripe that supports stablecoins as well as cards.

Visa contributed specifications to that protocol for paying with credit or debit cards, Fortune reported. Kevin Miller, Stripe's head of payments, said in the x402 Foundation release that Stripe wants to "help businesses accept payments from agents and empower agents to become economic actors on the internet."

The practical split looks like this. Cards and tokens will likely keep high-value consumer checkout, while stablecoin rails fit high-frequency, low-value machine calls where fixed card fees make no sense.

Also Read: Crypto ETF Momentum Returns After $50B Flows, JPMorgan Says

How Might x402 Transform Digital Publishing, Paid Research And Financial Data?

Publishers were among the first to test the 402 code in public. Cloudflare's Pay Per Crawl, launched in private beta in July 2025, lets sites charge AI crawlers per request and returns a 402 with a price to bots that have not agreed to pay.

Cloudflare evolved that model into Pay Per Use on Jul. 1, so publishers get paid when content "actually creates value, not just when it's fetched." Early partners include Ceramic.ai, which pays publishers when their content appears in its AI search results, and You.com, which will let agents pay on demand for premium content.

The company also changed defaults. From Sept. 15, Cloudflare began blocking "mixed-use" AI crawlers on ad-supported pages for new and free-tier sites unless the AI company pays.

Search Engine Journal reported that Cloudflare has now moved Pay Per Use and its Monetization Gateway into beta. Under Pay Per Use, the AI company defines the use and sets the price, and publishers choose whether to accept.

Not every bot plays along. Stack Overflow, an early Pay Per Crawl user, said some crawlers simply stopped sending traffic once they received a 402 instead of a block.

Financial data may be the stronger fit. Market data, analyst sentiment and options flow are valuable for minutes, and Coinbase's own demo showed an agent paying "a few cents" for that data before placing fractional stock buys.

That points to a new pricing layer for research providers and specialist publishers. A single report, chart or on-chain query could carry its own price tag for machine buyers, alongside human subscriptions rather than replacing them.

Also Read: Cursor's Europe Chief Ismail Elmas Leaves SpaceX Behind To Sell For OpenAI

What Are The Security, Fraud, Regulatory And Transaction-Cost Challenges?

The first problem is measurement. Headline x402 figures include a lot of noise, and Artemis Analytics put it bluntly on X: "Most of the x402 numbers circulating are noise."

Artemis analyst Lucas Shin built a wash trading filter that flags wallets paying themselves or cycling funds between addresses. Applied to one 30-day window in early 2026, it cut x402 volume to $1.6 million, against the $24 million shown on x402.org and cited by Bloomberg on Mar. 7, and about $3 million measured by Allium Labs.

A Visa-commissioned report with Artemis, published Jul. 14, removed 39% of x402 transactions and 89% of dollar volume as wash, test or internal transfers. Visa funded the study and the filter is not public, so the figures deserve caution in both directions.

Security and legal risks pile up on top. The IMF's April 2026 note "How Agentic AI Will Reshape Payments" and academic researchers have flagged several:

• Manipulation of an agent's inputs, which could redirect payments or trigger unauthorized purchases.
• Weak traceability between a user's instruction and the final transaction.
• Correlated behavior, where many agents react to the same signal at once.
• Liability gaps, since most rules assume a human authorized each payment.
• Privacy leaks, because frequent micropayments can link web metadata to on-chain wallets.

Regulation is still catching up. The GENIUS Act, signed Jul. 18, 2025, takes effect on the earlier of Jan. 18, 2027, or 120 days after final rules, and it bars issuers from paying holders interest or yield.

Agencies have only proposed rules so far, the Office of the Comptroller of the Currency issued its main proposal on Feb. 25, and none were final by the Jul. 18, 2026 statutory deadline, according to industry trackers. In the EU, MiCA's stablecoin rules applied from Jun. 30, 2024, and transitional relief for crypto service providers ended Jul. 1, 2026.

Circle secured an e-money license from France's banking regulator in July 2024, making USDC compliant with MiCA. That matters, because the default x402 asset is legal to use on both sides of the Atlantic.

Costs are falling but not vanishing. Coinbase's facilitator advertises fee-free settlement on Base and Solana, yet someone still pays network gas, which is why Circle and Cloudflare are pushing batching and deferred settlement.

Gatekeeping is another risk. Waller warned that an online retailer "might require shoppers to use its proprietary AI agent and block other agents."

Also Read: Crypto Tax Rate In Greece Falls To 10% In A Draft Bill After A Higher June Plan

Could Agentic Payment Protocols Become Standard Infrastructure For Autonomous Commerce?

The institutional signals point that way. The Linux Foundation appointed payments veteran Michael Hursta as executive director of the x402 Foundation on Oct. 1, citing more than 50 active members.

Visa, Mastercard, Stripe, Google and Coinbase now sit inside the same x402 tent, even while promoting their own protocols. AP2 lives at the FIDO Alliance, and x402 sits at the Linux Foundation, a common path for technologies that hope to become neutral standards.

What is emerging is a stack, not a single winner. Visa's Trusted Agent Protocol and Mastercard's tokens verify the agent, AP2 proves the user's intent, and x402 or Tempo's protocol moves the money.

The weak point is demand. Filtered volume remains small, and much of the activity still comes from developers testing their own tools. Infrastructure rarely proves itself through dollar volume in its first year. The real test is whether data vendors, publishers and AI companies keep answering 402s with payments once the novelty fades.

The evidence so far supports a measured bet. Agentic payments will likely become a standard layer for low-value machine calls, while cards keep most consumer checkout, and the two will coexist for years.

Read Next: Yandex Shares Fall Over 3% After Drone Fire Shuts Its Largest Data Center