In the last sixty days, three separate rails for an AI agent to spend money on a user's behalf shipped to production. Stripe announced Multi-Party Payments (MPP) for agentic commerce in mid-April. Coinbase's x402 protocol crossed a billion daily 402 responses on Cloudflare alone. Visa Intelligent Commerce went live with its Trusted Agent Protocol, giving every Visa-issuing bank a standard way to authorize a purchase made by an AI agent on a card the bank already holds. Three rails, three different settlement models, all aimed at the same thing: letting an autonomous agent transact for a human without a human in the loop.
If your brand sells anything online and does not yet have a story for at least one of these rails, you are about to find a new way to be invisible. Not invisible to a buyer reading reviews on G2. Invisible to the agent the buyer asked to do the shopping for them. The agent will pick a vendor that is set up to be paid. Yours will not be.
Three rails, sixty days
These are not roadmap items. They are live infrastructure that any agent author can call today.
Stripe MPP is the marketplace settlement rail. It handles the three-party flow that an agent transaction always is: user authorizes spend, agent executes the order, seller fulfils. Stripe takes a fee in the middle, the same way it does for any platform. The relevant change is not that Stripe added a payment method. It is that Stripe added a settlement primitive specifically for transactions where the buyer is not a human pressing a button.
Coinbase's x402 is the open-protocol rail. HTTP 402 has been a reserved status code since the original web spec. x402 finally puts it to use: a server returns 402 with a machine-readable price and a payment address, the client (an agent, a browser, anything) settles in stablecoin, the resource unlocks. Cloudflare reports more than a billion 402 responses a day across its network. Most of those are AI bots hitting paywalled content. The protocol is the standardized way for the bot to pay and get on with it.
Visa Intelligent Commerce is the issuer rail. Visa's Trusted Agent Protocol gives banks and merchants a way to recognize and authorize a card transaction initiated by an AI agent on a Visa-issued card the user already holds. The brand the agent buys from does not need crypto, does not need to integrate a new platform. The card on file works. Mastercard Agent Pay is the parallel move. Between them, most of the world's card volume is becoming addressable by agents through the existing card schemes.
Why three rails and not one
Each rail solves a different kind of agent purchase. Mixing them up is the first mistake brands make when they hear about this.
Stripe MPP is built for marketplace-shaped commerce. A user asks an agent to book a hotel, shop a multi-seller catalog, or buy a course from a creator. The seller is one of many on a platform. The platform clips a fee. The agent acts as the buyer-side intermediary. Stripe's payment graph already supports this for human buyers. MPP extends it to agent buyers.
x402 is built for machine-to-machine transactions where the price tag is small and the negotiation has to happen in milliseconds. The AI lab pays the publisher 0.003 cents per scraped page. The agent pays the API provider per inference call. The browser agent pays the news site for one article. These flows do not run economically through Visa rails. They are designed for stablecoin micropayments and HTTP-level negotiation. AP2, the Agent Payments Protocol that Google, Anthropic, and OpenAI are co-developing, builds on top of x402 as one of its supported settlement options.
Visa Intelligent Commerce is built for first-party retail. A user asks an agent to reorder their dog food, buy a flight, pay a tradesperson. There is one merchant, one buyer, one card on file. The merchant is not a marketplace. The agent does not want to learn crypto. The card the user already trusts is the cleanest rail. ITC is the issuer's hand-off to that flow.
Most brands sit in one or two of these categories. Agents come from all three. An e-commerce brand that only thinks about Visa ITC will lose the user who asked Comet to buy them a software license from a marketplace. A SaaS API that only supports x402 will lose the agent that wanted to charge a corporate card. The decision is not which rail to support. It is which rail to support first.
What "agent-payable" actually means
A brand is agent-payable when three things are true at the same time. Get any one wrong and the agent times out, the user gets a vague error, and your brand becomes the one the agent did not pick next time.
First, your checkout has to be reachable by an agent. That means no captcha gate, no third-party challenge that fires on the first non-human signal, no JavaScript-only price field that an agent's reader cannot parse. The plumbing has to expose a stable, machine-readable surface. Most ecommerce stacks already do this through structured product feeds. Most do not yet tag agent traffic distinctly from bot traffic, which means the WAF blocks the agent the same way it blocks a scraper.
Second, your prices have to be quotable in a form the agent can present to the user. A JSON-LD Product schema with current price, currency, availability, and SKU ID is the minimum bar. If the agent has to scrape a rendered DOM to get your price, you have already lost. The agent will quote a stale number, the user will be charged the live one, the user will blame you.
Third, your terms have to be parseable enough for the agent to confirm what the user authorized. Refund policy, shipping window, subscription cadence. The agent does not need to read your full T&Cs. It needs the small set of facts that distinguish a legitimate buy-now from a buy-now-and-discover-it-renews-monthly. The AP2 spec is making this an explicit field in the payment authorization. Brands that already have clean structured terms can plug in. Brands whose policies live in a PDF cannot.
Three failure modes for brands that wait
The first failure mode is the agent gives up. Internal benchmarks from agent vendors show that when an autonomous purchase flow stalls, the agent retries once or twice and then routes the user to a competitor that completed. The user does not see a debug log. They see "I went ahead and booked you with the other one." That is the default outcome today for brands that have not shipped an agent-payable surface.
The second failure mode is the agent succeeds, but on stale data. The user authorizes a 99 dollar purchase, your live price is 109 because a coupon expired, the card gets charged 109, the agent reports back 99. The user files a complaint and writes a review. Your brand absorbs a quality problem that was actually a data-freshness problem. This is the AI Overviews zero-click drama again, except the lost click is a real chargeback.
The third failure mode is the aggregator becomes your channel. Operator, Comet Pay, Composio Commerce, and a growing stack of "buy-anything" agent layers are filling the gap brands left open. They route the user's intent through their service, settle with you through whatever rail works, and add their own fee on the way. Your relationship is no longer with the buyer. It is with the aggregator. Look at how the 2010s integration economy reshaped CRM and payments and assume the same is happening one layer up, faster.
What to actually do this quarter
1. Decide which rail your category sits on. E-commerce and retail need Visa ITC and Stripe MPP. Marketplaces and platforms need Stripe MPP. SaaS APIs and content products need x402. If you sell across all three, pick the one with the most current agent traffic and ship that first.
2. Ship a machine-readable price and availability feed. JSON-LD Product schema for retail, OpenAPI with explicit price fields for APIs, x402 quote endpoints for content. If your prices are only legible to a human looking at a rendered page, no agent can quote you to a user.
3. Tag agent traffic at the edge instead of blocking it. Stop treating Operator and Claude Computer Use the way your WAF treats a scraper. Tag the signal, route it to a checkout flow that can answer in machine-readable form, and instrument the conversion separately from human traffic.
4. Pilot one rail end to end. Pick one product line, one payment rail, one agent surface. Get a real agent transacting against a real checkout. The thing that breaks first is rarely the payment integration. It is usually the address validation, the SKU mapping, or the terms field. Find those before scaling.
5. Instrument agent settlements as a first-class analytics surface. Treat agent purchase as a new traffic category. Track conversion rate, average order value, refund rate, chargeback rate. Agents produce cleaner attribution data than humans because they leave a deterministic trail. Use it.
6. Decide your aggregator stance. If Operator and Comet are already routing buyers to you, you can either treat them as a channel and pay the toll, or build a direct agent-payable surface and bypass them. The right answer depends on your margin and your brand power. Pretending the aggregators are not there is not an answer.
The new checkout
Apple Pay launched in 2014. Within three years, retailers without a tap-to-pay button were measurably losing high-intent mobile buyers. The button was free to add. The cost of not adding it was a discount on every transaction that bounced because the user did not want to type a card number on a phone.
Agent payment rails are the 2026 version of the same shift, one layer higher. The brands that ship a Stripe MPP integration, an x402 endpoint, or a Visa ITC handshake this quarter will be the default vendors when the agent picks for the user. The brands that wait will be the second-choice options the user has to manually override. Most users will not override. They will let the agent buy from whoever was set up to be bought from.
Search-era SEO was about getting your URL into the index. Closed-model GEO was about getting your brand into the training data. MCP was about getting your tools into the agent's runtime. Agent commerce is the next surface, and it is the one that ends in a charge on a card. The window for being default-payable in your category is open right now. It closes the same way these windows always close: quietly, and faster than the brands sitting it out think.
Want to know which AI agents are already trying to transact with your brand?
Presenc AI tracks every crawl, citation, and agent call hitting your site, and our forthcoming Verify API confirms which agent settlements landed against a real citation before money moves. See the early signal of the agent commerce era before it shows up in your revenue report.
