Meta Muse agent checkout: Amazon blocked it, Shopify and PayPal opened the door — what merchants should decide now

Three weeks of Meta Muse: the timeline merchants should know

Meta introduced Muse on September 8, 2026 as a personal agent that "takes tasks and projects off their plate." It runs in its own secure virtual machine with its own browser, can "open a browser, fill out forms, and negotiate" for the user, and keeps working after the app is closed. It comes back "when it needs approval, like before it sends an email or makes a purchase," according to Meta's launch announcement. It launched in the US on iOS, Android, the web and WhatsApp, with a free tier and paid plans.

Then it grew faster than almost anyone expected, and the retail and payments industry had to take a position in public:

How big is it? App-intelligence firms quoted by TechCrunch put downloads between roughly 2.3 million and 4.3 million by September 24, depending on the estimate. That's small next to Amazon's customer base and large next to any agent-commerce product before it. For a merchant, the important part isn't the exact number. A mainstream consumer app now buys things from ordinary online stores, and the industry has had to pick sides.

How Meta Muse agent checkout actually pays

Muse doesn't have money of its own. It borrows the user's, through three consumer wallets:

• Stripe Link (at launch). According to Stripe's announcement, Muse can check out instantly with the user's saved payment method at the more than 1 million businesses that accept Link. For every other business, Link issues Muse "a single-use virtual card scoped to the approved purchase." The user approves the transaction total in the chat, and "Muse never sees their underlying payment details." Meta says Muse is the first agent covered by Link's purchase protections, such as price-drop refunds and no-fee returns.
• Shop Pay (September 21). Shopify CEO Tobi Lütke: "We are excited to announce we are partnering deeply with Muse to enable agentic checkout with Shop Pay on all Shopify stores."
• PayPal (September 22). PayPal said the partnership lets "PayPal customers … seamlessly shop and check out using their Muse personal AI agents across PayPal merchants worldwide."

Look at it from the merchant's side of the counter. Nothing about how the money moves is new. A Muse order arrives as a Link payment, a Shop Pay order, a PayPal transaction or a card payment, usually from a single-use virtual card. The card network's rules apply, with the same interchange, processing fees, refunds and disputes as any online order. The virtual card controls how much the agent can spend. It doesn't make the payment final. We compared that design with agent-held money in virtual cards for AI agents vs x402.

Amazon said no, and its reasons are specific

On the night of Sunday, September 20, Muse users trying to shop on Amazon started seeing pop-ups. Amazon told GeekWire: "Continued access by an unauthorized AI agent violates Amazon's Conditions of Use, to which our customers have agreed." Its position is that third-party apps that buy on a customer's behalf "should operate openly and respect service provider decisions."

Amazon's complaints were specific. It says Meta didn't tell it Muse would shop there, and that the agent doesn't identify itself while browsing. It also says Muse appears to capture and store customers' login credentials. Meta says credentials go into secure storage the agent itself can't read. Neither side has published enough technical detail to settle that dispute. Amazon's Conditions of Use already include agent rules: an agent must identify itself and stop when asked.

Context matters here. In August, a federal appeals court reversed the injunction Amazon had won against Perplexity's shopping browser, holding that the user directing the agent is the one accessing the site. Amazon also earned more than $68 billion in advertising last year, which depends on people browsing its pages. And Amazon runs its own agents: its "Buy for Me" feature shops on brands' own sites, identifies itself, and lets brands opt out.

So Amazon's "no" really means "not on your terms." It can afford that. A marketplace with its own traffic, ads and agents doesn't need someone else's agent to bring buyers. Most merchants aren't in that position. Many don't even hold the switch: if you sell on Shopify, the platform opened agentic checkout on every store at once.

What letting the agent in gets you, and what it doesn't change

For most online stores the realistic answer to Muse is yes. Here's what that yes buys, and what stays the same.

What you get

• Reach. Millions of people now have an assistant that can buy from you without visiting your homepage.
• No build. If you already accept Link, Shop Pay, PayPal or cards, agent orders arrive through the checkout you have.
• Conversion. Stripe pitches higher conversion and authorization rates, since a wallet with a saved payment method removes most of the checkout friction.

What doesn't change

• Card economics. The fees for a human checkout apply to an agent's checkout too. The agent is a new buyer interface, not a cheaper rail.
• Reversibility. An agent order is a card-not-present transaction that can be disputed for weeks or months afterward, often up to about 120 days. The customer can truthfully say they approved the agent and still dispute the item it picked. Whether "approved the total in chat" counts as strong evidence of authorization hasn't been tested at scale. Meta's own launch security write-up acknowledges that prompt injection "remains an open problem in the industry." We covered who carries those losses in agentic commerce chargeback liability.
• The relationship moves. When an agent compares, picks and re-shops, loyalty belongs to whoever owns the agent. On September 22 the S&P 500 financials index fell nearly 2%, Schwab about 6%, Expedia 3.7% and Booking 3.9%, as investors priced in agents that switch providers for the customer. Bloomberg Intelligence expects personal agents to become new digital "toll collectors" on the transactions that pass through them. Meta hasn't hidden the plan: at Connect, Mark Zuckerberg said Meta would eventually make money from Muse "by taking a small fee from transactions," according to TechCrunch.

None of this is a reason to block agents. It's a reason not to let a platform-owned agent be the only way customers reach you.

The other model: agents that pay the seller directly

Muse is one model of agent payments: the agent borrows a human's wallet and checks out through card-network rails, in pages built for people. There's a second model already running on the open internet: the agent holds a small balance of stablecoins and pays the seller directly, per request.

That's x402. A seller's endpoint answers an unpaid request with HTTP 402 Payment Required and a price. The agent pays, typically in USDC, and the seller serves the response. There's no wallet partnership to sign, no card, no checkout page, and no dispute window, because an on-chain payment is final. The seller doesn't need a platform to open the door on its behalf. It publishes a price.

Be honest about scale. TRM Labs analyzed $52.7 million across 198.9 million x402 settlements on Base, Solana and Polygon since May 2025, in research published September 9. It found 99.6% of the value settled in USDC, and only about 0.6% to 7.5% of the activity that looked like real commerce showed agent-like behavior. It's early. And it fits digital goods today: data, APIs, AI tools, content. It doesn't fit sneakers. The buyers are arriving, though. On September 22 Coinbase gave trading agents x402 payments, which we covered in selling market data to AI agents.

The two models answer different questions. Muse answers "how does a consumer's assistant buy from a store that was built for humans?" x402 answers "how does software pay software, per request, without anyone's permission?" Merchants will see both. The second one is the one you can set up yourself.

Where Payzum fits, and where it doesn't

The boundary first: Payzum doesn't plug into Muse, and Muse doesn't pay in stablecoins. Muse pays through Link, Shop Pay and PayPal. If agent shoppers reach your store that way, they come through the processor you already use.

What Payzum gives you is the direct lanes, settled non-custodially to a wallet you control:

• A checkout you own, with final settlement. Hosted checkout (redirect, modal or inline), payment links and buttons, invoices that expire and detect overpayment, recurring subscriptions, and drop-in plugins for common e-commerce platforms. Customers pay in crypto; you can auto-convert to USDC or USDT. The money goes straight to your wallet in seconds, with no chargebacks, because an on-chain payment can't be reversed by a third party. For in-person sales, the Payzum POS creates a new QR for every sale.
• x402 for agents that pay per request. If you sell data, an API or a digital tool, Payzum works as the x402 middleware in front of your existing endpoint. You enter the endpoint, its API key or bearer token, and a price in the dashboard. Payzum publishes an x402 URL, returns the 402 to agents, and settles each payment through an external facilitator (currently Coinbase's) in USDC on Base, straight to your wallet. Then it forwards the paid call to your real endpoint with your key. No code, and no protocol to implement.
• Records you can trust. Signed webhooks update your systems, and the dashboard keeps 2FA, encrypted secrets and a full audit log.

Payzum never holds, pools or controls your money. There's no processor balance to freeze and nothing to withdraw. The settlement is the payment. Payzum is crypto-only and doesn't pay out to bank accounts; if you need local currency, you convert through the provider of your choice.

What to decide this quarter, step by step

1. Find out whether agents can already buy from you. On Shopify, Shop Pay agentic checkout is live on all stores. If you accept PayPal, Muse can check out with it. If you accept cards, Link can hand the agent a single-use card. For most merchants the answer is already yes.
2. Pick a stance for each channel. The options are open, open only to agents that identify themselves, or closed. Amazon's rule, that agents must identify themselves and stop when asked, is a reasonable template even if you choose "open."
3. Tag agent orders and keep the evidence. Where your platform shows that an order came through an agent, record it. Keep the order confirmation, delivery proof and any approval record. If disputes come, they'll come on these orders.
4. Build one direct lane you own. For repeat buyers, wholesale accounts and cross-border customers, add a stablecoin checkout, payment link or invoice that settles to your wallet with no dispute window.
5. If you sell data, APIs or digital tools, publish a per-request price. An x402 endpoint lets any agent with USDC pay you, with no platform partnership needed.
6. Review every month. Track the share of sales that come through agents, the disputes on those orders and the fees they carry. Then adjust your stance.

Agent checkout on card rails vs x402 vs a direct stablecoin checkout

Common objections

"Muse doesn't pay in stablecoins, so why does this matter to me?"

Because it shows who controls agent traffic when it runs on card and wallet rails: the agent's maker, the wallet providers and your platform. You don't have to fight that. What's worth doing is making sure it isn't your only path to customers. A direct lane with final settlement is the part you control.

"I'm on Shopify. The decision is already made."

For Shop Pay agent orders, yes. What's still yours is what you do next: how you record those orders, how you handle disputes, and whether you give your best customers a direct way to pay that doesn't run through someone else's agent or wallet.

"Agent volume is tiny. Why act now?"

Because a direct lane takes an afternoon to set up, and the gatekeeping arrived before the volume did. In two weeks the largest marketplace blocked an agent while the largest store platform and one of the largest wallets opened to it. The terms for reaching agent shoppers are being set now.