AI Agents Now Have Wallets. Here's What That Means for Your Checkout.

On March 18, 2026, Stripe and Visa launched the Machine Payments Protocol with over 100 partners. The short version: AI agents can now hold funds and pay for things programmatically, without navigating a checkout page. The long version is what matters for your store.

Every piece of coverage so far has been written for fintech audiences and crypto enthusiasts. None of it has addressed the question that actually matters to merchants: what does this change about how people buy from you?

This is that piece.

What Happened on March 18

Stripe, Visa, and a coalition of 100+ partners — including major payment networks, infrastructure providers, and commerce platforms — launched MPP, the Machine Payments Protocol. It's an open standard for machine-to-machine payments built on traditional payment rails.

The core idea: an AI agent acting on behalf of a consumer can pay a merchant directly, without rendering a checkout page, filling out a form, or managing a browser session. The agent sends a request. The server says "this costs money." The agent's wallet authorizes payment. The transaction completes.

This isn't a whitepaper or a proposal. MPP is live infrastructure. Stripe supports it natively. Visa's network can process MPP transactions today.

How HTTP 402 Payments Work

The technical mechanism is surprisingly simple, and it's built on a piece of HTTP that's been reserved since 1997.

HTTP status code 402 — "Payment Required" — has existed in the HTTP spec for nearly 30 years. It was never formally implemented because there was no standard for what a payment request between machines should look like. MPP fills that gap.

Here's the flow:

Agent requests a resource. An AI shopping agent, acting on a consumer's behalf, sends an HTTP request to a merchant's payment endpoint. "I want to buy this product."
Server returns 402. Instead of a checkout page, the server responds with HTTP 402 and a structured payment envelope: price, currency, accepted payment methods, terms.
Agent's wallet evaluates and authorizes. The agent checks its wallet balance, the consumer's spending rules, and the payment terms. If everything checks out, it signs and submits payment.
Transaction completes. The merchant receives confirmation through their payment processor (Stripe, in most cases). The product ships or the digital good is delivered.

No cart. No session. No CAPTCHA. No "continue as guest." No five-step checkout funnel with an upsell modal on step three. The agent didn't need any of that. It needed a price, a payment method, and authorization from its human.

MPP vs x402

MPP isn't the only standard competing for this space. Coinbase and Cloudflare launched x402 around the same time — same pattern, different infrastructure.

MPP (Stripe/Visa): Traditional payment rails. Credit cards, debit cards, bank transfers. Works with the payment processor you already use. Settlement in fiat currency through existing merchant accounts.

x402 (Coinbase/Cloudflare): Crypto-native rails. Settlement in stablecoins (primarily USDC). Built for on-chain transactions. Cloudflare provides the CDN-level integration for serving paywalled content.

Both use HTTP 402. Both enable agents to pay without a checkout page. The difference is plumbing.

For most merchants, MPP is the one that matters. Your Stripe account already supports it. Your customers' banks already clear those transactions. Your accounting software already processes card payments. x402 is relevant if your business operates in crypto-native markets or if you want to accept stablecoin payments. For everyone else, it's an interesting technical development that doesn't require action.

The two standards may converge over time, or they may serve different market segments permanently. Either way, the merchant-side takeaway is the same: the checkout page is no longer the only path to a completed purchase.

What This Means for Merchants Today

Honestly? Almost nothing operationally.

MPP is live. The protocol works. Stripe can process these transactions. But the consumer-facing piece — AI agents with funded wallets — hasn't shipped yet.

No consumer AI agent has wallet integration available to end users today. ChatGPT doesn't have a wallet. Gemini doesn't have a wallet. Claude doesn't have a wallet. The infrastructure for agents to pay is built. The actual agents that consumers use haven't connected to it yet.

This is a familiar pattern in payments infrastructure. The rails get laid before the trains run. Contactless payments existed for years before tap-to-pay became ubiquitous. EMV chip readers were in stores long before every card had a chip. MPP is in that early infrastructure phase.

There is nothing you need to build, change, or configure right now.

What It Means in 6-12 Months

When agent wallets do ship — and they will, because Stripe, Visa, and every major AI lab are aligned on making this happen — the checkout page becomes a fallback, not the primary conversion path.

Think about what the purchase funnel looks like when an agent can pay:

Today: Consumer asks agent to find a product → agent searches and compares → agent recommends options → consumer clicks a link → consumer navigates to store → consumer adds to cart → consumer enters shipping → consumer enters payment → consumer confirms order. Eight steps minimum. Every step is a dropout point.

With agent wallets: Consumer asks agent to buy a product → agent searches, compares, and selects → agent pays via MPP → order confirmed. Three steps. The consumer never visits your store.

The consumer never visits your store. That's still a completed sale — but it changes what "conversion optimization" means entirely. You're not optimizing a page anymore. You're optimizing data so an agent picks you over a competitor the consumer never sees.

Merchants who still require a full cart-to-checkout-to-payment page flow won't lose all their sales. But they'll lose the ones where an agent could have completed the purchase in seconds and instead hit a wall that required browser automation or, worse, handing the consumer a link and saying "you'll have to buy this one yourself." That's a lost transaction.

The One Thing to Watch: Shopify + Stripe

Shopify is already a design partner for Tempo, Stripe's agent-native payments product. That relationship is the single most important signal in this space for merchants.

When Shopify enables MPP for its merchants — and the partnership structure makes this a question of when, not if — every Shopify store gets agent payment capability automatically. The same way Shopify auto-deployed UCP via Agentic Storefronts in March, they'll auto-deploy MPP support when Tempo is ready.

If you're on Shopify, this means agent payments will arrive as a platform update. No migration, no implementation project, no new app to install.

If you're not on Shopify, you'll need to implement MPP support yourself. That means integrating with Stripe's Tempo API (or whichever payment processor ships MPP support), updating your server to return proper 402 responses with payment envelopes, and testing the full agent payment flow end-to-end. It's not prohibitively complex — Stripe tends to make these integrations clean — but it's real engineering work that Shopify merchants won't have to do.

This is the same dynamic we saw with UCP. Shopify merchants got it for free. Everyone else had to build it. The gap between "Shopify merchant" and "everyone else" in agent readiness is about to widen again.

What to Do Now

Don't build MPP integration. It's too early, the consumer-side wallet infrastructure isn't here, and the Tempo API is still in partner preview.

But don't do nothing either. Agent payments are the last step in a chain. Before an agent can pay for your product, it needs to find your product, understand your product, compare your product, and decide your product is the right choice. That entire chain needs to work before payment matters.

Here's what's worth your time today:

Confirm your payment processor supports MPP. If you're on Stripe, you're covered — MPP is native. If you're on another processor, check whether they've announced MPP support or joined the partner coalition. If they haven't, that's a conversation to have now, not when agent wallets ship.

Watch for Shopify's MPP announcement. If you're a Shopify merchant, this will be your upgrade path. Tempo partnership is public. The rollout timeline isn't. Stay current on Shopify Editions and changelog updates.

Make sure agents can find and evaluate your products without browsing your store. This is the real work. An agent that can't discover your products will never reach the payment step. Structured product data — JSON-LD, UCP manifest, rich metafields — is what agents use to understand what you sell. If your product data is thin, unstructured, or locked behind JavaScript rendering, you have a discovery problem that no payment protocol can solve.

Think about your product data as an API, not a page. MPP completes the shift from "stores are websites that humans browse" to "stores are services that agents query." Every layer of your commerce stack — discovery, evaluation, comparison, payment, fulfillment — is becoming an API call. The merchants who internalize this earliest will adapt fastest.

Check Your Readiness

Agent payments are coming. The infrastructure is live. The wallets are months away, not years. When they arrive, the merchants who are ready will process transactions that the unprepared ones never see.

The payment layer is the last piece of agent commerce. The first pieces — discovery, structured data, protocol support — are what you can control right now.

Run a free agent readiness check at agenticcom.ai/check to see where your store stands across all the protocols that feed into agent purchasing decisions. It takes 30 seconds and covers UCP, structured data, AI crawler access, and the full agent commerce stack. The stores that score well today are the ones that will convert agent payments tomorrow.

For a complete map of how MPP fits into the broader protocol ecosystem alongside UCP, ACP, and MCP, see our Agentic Commerce Protocol Stack guide.

Sources: Machine Payments Protocol launch announcement (March 18, 2026), Stripe Tempo partner documentation (2026), x402 specification (Coinbase/Cloudflare, 2026), HTTP/1.1 RFC 7231 Section 6.5.2.