Claude commerce agents ship without a wallet — payments just became the seller's job

What's inside the Claude commerce agents blueprint — and what isn't

The release is concrete. Claude Commerce Agents is an open-source repository (Apache-2.0) containing reference implementations of two agents. The shopping agent sits inside a retailer's site or app: it searches the catalog, handles multi-item requests, compares options, builds the cart and answers order and returns questions in the same conversation. The merchant agent faces the operator: inventory suggestions, pricing, marketing campaigns. Reference builds cover retail, travel, telecom and ticketing, and the same code deploys via the Claude API, Amazon Bedrock, Microsoft Foundry or Google Cloud Vertex AI.

The distribution is what makes it news rather than a demo. Anthropic's announcement lists Visa, Mastercard, Shopify and Accenture as partners taking the blueprint to their clients, and two production users on day one: Shopify, and Priceline, which rebuilt its Penny assistant on Claude. Anthropic's own figures — carts up to 35% larger and shoppers 60% more likely to complete a purchase — come from one partner and aren't independently verified, but the direction matches what every retailer piloting shopping agents has been reporting: agents are good at filling carts.

Now the list of what is not in the box: no payment protocol, no checkout, no wallet, no catalog, no ad layer. Anthropic is explicit that no transaction routes through it. The purchase is completed on the seller's side — in Anthropic's framing, through "an existing checkout flow or an agentic payments provider."

Why the missing wallet is the real announcement

When the AI vendor with two card networks as launch partners open-sources everything except payments, that's not an oversight — it's a boundary being drawn. The reasoning layer (search, compare, decide, fill the cart) is now free and Apache-licensed. The money layer is explicitly someone else's product. As PYMNTS put it, Anthropic built the shopping brain and skipped the wallet.

Part of the logic is trust: in the survey data PYMNTS cites, only 45% of consumers accept an AI agent completing a purchase for them, and 95% voice at least one concern about agentic commerce. We covered the same asymmetry in the agentic commerce trust gap — people happily let agents shop and refuse to let them pay. An AI vendor that inserts itself into the payment leg inherits that entire trust problem, plus regulatory exposure, plus dispute liability. Anthropic declined all three.

Part of the logic is evidence. OpenAI launched in-chat Instant Checkout, and retired it around March 2026 — roughly five months in — after flagship partner Walmart reportedly saw conversion inside the chatbot run about three times below its own site. ChatGPT now hands shoppers to the merchant's checkout. Google runs agentic checkout through its Universal Commerce Protocol with the retailer still merchant-of-record; Microsoft's Copilot Checkout works the same way across 500,000+ merchants. Different companies, one conclusion: the agent shops; the seller settles.

The division of labor is now official — and one side of it is yours

Put September's release next to the rest of 2026 and the shape of agentic commerce is settled. The buyer side is finished infrastructure: agents can browse, compare, negotiate and fill carts, and the blueprints to build them are free. The standards for authorizing them exist — x402 for the machine-payable web, AP2 above it for proving a human authorized a purchase, both covered in our x402 Foundation analysis. What nobody shipped — deliberately, repeatedly — is the seller's rail.

That leaves two concrete gaps on the seller side, and they're different problems:

• The cart handoff. A Claude-built shopping agent fills a 35%-larger cart, then hands the human a checkout designed for a person with a card: forms, 3-D Secure, retries. Every point of friction in that handoff burns the value the agent just created — that's exactly where Walmart's 3× conversion gap lived.
• The machine buyer. The merchant agent in Anthropic's own blueprint manages inventory, pricing and marketing. To do that at scale it consumes APIs — data feeds, enrichment, tooling. Those agents have no card and can't pass a CAPTCHA. If your product is an API, "payment stays with the seller" means you need an endpoint a machine can pay without a human in the loop at all.

How Payzum makes the seller side agent-ready

Payzum is a non-custodial, crypto-only payment processor, and it happens to cover both gaps the AI vendors just handed to sellers — with the money landing in a wallet the seller controls, not a processor balance.

For the cart handoff: hosted checkout, payment links and buttons, and invoices with expiration and overpayment detection. An agent that has built a cart can surface a Payzum payment link or hosted checkout for the human's final approval — which is precisely the consent model buyers say they want (compare with an agent, approve the payment yourself). The customer pays in stablecoins or any supported crypto; the seller can auto-convert to USDC/USDT to remove volatility. Settlement is on-chain and final: no chargebacks, no "agent-initiated transaction" dispute category to argue about later, funds confirmed in seconds on Base or Polygon.

For the machine buyer: x402. Payzum sits as middleware in front of your existing API. You configure your endpoint, your API key and a price in the dashboard — no code, no protocol to implement. Payzum publishes an x402 URL, answers unauthenticated calls with 402 Payment Required, settles the agent's USDC payment on Base through an external facilitator (currently Coinbase's), then proxies the paid request to your real endpoint with your key. The agent pays per call; the USDC lands in your wallet. Around 1,000 transactions a month are free, then roughly $0.001 per transaction plus gas. We covered the mechanics in depth in let AI agents pay for your API.

Both flows share the property that matters most in a market this young: non-custodial settlement. Whatever agentic commerce turns into, the revenue it generates for you sits in your wallet from the first confirmation — not in an intermediary's omnibus account waiting for a payout schedule.

Getting agent-payable, step by step

1. Create a Payzum account and connect your wallet. Settlement addresses you control, per network — Base for x402 and agent traffic, plus Solana, Polygon, Ethereum and others for checkout.
2. For human-approved carts: create a hosted checkout or payment links, and optionally turn on auto-convert to USDC/USDT so every sale lands as dollars regardless of what the customer pays with.
3. For machine buyers: register your API endpoint, paste your existing API key/bearer, and set a per-call price. Payzum publishes the x402 URL — share it in your docs and agent directories so agents can discover and pay it the same day.
4. Wire up signed webhooks. Payment confirmations hit your backend with signed payloads, so fulfillment, order updates and analytics fire the moment a payment is final — whether a human or an agent sent it.

Where this lands first

Anthropic chose its reference verticals for a reason — they're where shopping agents already work. Mapped to real payment flows:

• Retail / e-commerce: a storefront runs a Claude-based shopping agent that assembles a multi-item cart; checkout is a Payzum hosted page where the customer approves once and pays in USDC — final settlement, no card fraud on a purchase a human technically didn't type in.
• Travel and ticketing: an assistant like Priceline's Penny quotes an itinerary; the confirmation step is a payment link with an expiration window, matching the fare hold — and no chargeback exposure 90 days later on a "my agent booked this" dispute.
• API and data providers: the merchant agents themselves become customers. A pricing-intelligence API, a product-content generator, an inventory-forecast model — each priced per call behind an x402 URL, earning USDC from every merchant agent that queries it. The same model we analyzed when Coinbase opened selling to AI agents.

Card checkout vs agent-ready selling — comparison

Objections, answered

"My checkout already converts fine. Why touch it?"

Keep it — this isn't rip-and-replace. Payzum is drop-in and runs beside your card stack: a stablecoin option at checkout, payment links for the agent handoff, an x402 URL for your API. The point of September 2 is that cart construction is being automated for your competitors at zero software cost. The sellers who win that traffic are the ones whose payment leg doesn't leak the value the agent creates.

"Isn't agentic payment volume mostly noise anyway?"

A fair read of the data — a big share of x402's early transaction count was speculative minting, and we've said so in our analysis of the volume decline. But the Anthropic release moves the needle on the part that was actually missing: distribution of real commerce agents through Shopify, Priceline, Visa, Mastercard and Accenture. Blueprints with those channels create real buyers. Getting agent-payable costs a dashboard config today; retrofitting it after your niche's agent traffic arrives costs market share.