XAgent is the open execution market for Agentic Commerce. It turns merchant products, pricing, inventory, order logic, settlement, and fulfillment capability into commerce interfaces that AI agents can read, call, and purchase from. Agents quote, authorize, settle, fulfill, and prove the purchase — machine-to-machine.

What is agentic commerce?

Agentic commerce is a model where AI agents — not humans clicking through web pages — discover services, place orders, and settle payments autonomously. XAgent makes this real through five execution pillars: Quotable, Authorizable, Settleable, Fulfillable, Provable.

How is XAgent different from Stripe or Coinbase Commerce?

Stripe was built for humans clicking checkout buttons. Coinbase Commerce is a crypto payment gateway. XAgent is the protocol-native execution market where AI agents transact: protocols standardize the request, XAgent operationalizes the transaction. The moat is merchant operations — catalog, quote, authorization, order, settlement, delivery, receipt, refund, reconciliation, fraud signal, jurisdiction metadata.

How do AI agents pay merchants on XAgent?

Agents pay using the x402 protocol — an HTTP 402 challenge/response standard. The agent receives a signed payment instruction, authorizes a stablecoin transfer (USDG or USDT) via EIP-3009, and the merchant is paid in seconds with zero gas fee to the buyer (OKX facilitator covers it).

Do I need to write code to list my store?

No. One-click OAuth in your Shopify or WooCommerce admin turns your store into a merchant capability that AI agents can quote, order, pay, settle against, and prove — zero code, zero contracts.

What Stripe's Open USD default means for stablecoin choice

Stripe says Open USD will be the default for businesses using stablecoins on its platform. Six weeks after the announcement the consortium has published no launch date and no chain list of its own.

By XAgent Team · 2026-08-11

Stripe posted eleven words on June 30 that matter more to merchants than most of the stablecoin news since: "We're making Open USD the default for businesses using stablecoins on Stripe. Coming soon." For a large number of businesses, the stablecoin decision is about to be made upstream of them. Six weeks later, the consortium behind Open USD has still not published a launch date, and the chain list everyone is quoting does not come from the consortium at all.

What has actually been said, and by whom

Open USD was announced on June 30, 2026 by Open Standard, whose founding CEO Zach Abrams wrote: "We're thrilled to bring together over 140 businesses to launch Open USD. It's a stablecoin built for the internet economy, designed by the businesses growing it." We covered the consortium's shape and its settlement implications when it launched.

The default claim exists in two versions with different scopes, and the difference is worth holding onto.

On the consortium's own site, Stripe's President of Technology and Business, Will Gaybrick, is quoted saying: "That's why Open USD will be the default stablecoin for businesses running on Stripe; they are the ones shaping the next 15 years of economic growth." That reads as all Stripe businesses.

On Stripe's own channel, the wording is narrower: the default is "for businesses using stablecoins on Stripe". Businesses already reaching for a stablecoin get a different one by default; businesses not using stablecoins are not being moved onto one. There is no Stripe newsroom item, blog post or press release about Open USD — we checked the full 2026 newsroom listing — so the narrower phrasing on Stripe's own account is the most direct thing Stripe has said.

The launch date has not moved in six weeks

Open USD is not live. As of today the consortium's own FAQ answers the question "When will Open USD launch?" with one sentence: "Open USD will launch later this year." The announcement post closed the same way: "Open USD will be live later this year."

That is the same guidance given on June 30. No month, no quarter, no date, and no exchange quoting the asset.

A default that has not shipped is still a real signal — Stripe does not announce defaults casually, and "coming soon" from a company with that merchant base is a distribution commitment. But it is a commitment, not a rail. A merchant planning settlement for this quarter is planning around a stablecoin whose issuer has published no launch date.

The chain list is not the consortium's

This is the part most coverage gets wrong, and it is worth being precise because merchants make integration decisions on chain lists.

Open Standard's website names no blockchain in prose. Not on the homepage, not in the announcement post, not on the partners page. Every "Open USD launch chains" list in circulation has been assembled by journalists from separate posts by the individual chains and partners.

Those individual statements are real and quotable. Solana's own account said: "BREAKING: Open USD is launching natively on Solana from day one." Coinbase said Open USD "is coming to @Base and other leading chains this year" — note the timing language differs, and note the absence of ordering.

What follows from that is narrower than the lists imply. Solana has claimed day-one native launch in its own voice. Base has claimed arrival this year. Beyond those, a merchant is reading a compiled list, not an issuer roadmap — and the compilations have already changed once, with chains appearing and disappearing between write-ups. If your integration plan depends on Open USD being on a particular chain at launch, that dependency currently rests on a partner's announcement rather than the issuer's.

Why a processor-set default changes the merchant question

Stablecoin choice has so far been the merchant's, and mostly it has been a choice between one dominant asset and the friction of anything else. A default set by the processor is a different mechanism. It does not remove the choice; it changes which way the inertia points, and inertia is what settles most integration decisions.

For agent traffic this matters more than for card traffic, because the agent does not care. An agent arriving to buy something has a funded wallet and a settlement path; whether the merchant's processor prefers one dollar token or another is invisible to it and irrelevant to whether the purchase completes. What the merchant experiences is a second asset to reconcile, price, and account for — and, for a while, a second set of chains.

That is the case for keeping settlement behind an operations layer rather than wiring it into your storefront. As we have argued since settlement stopped being the bottleneck, the rail is the part of agentic commerce most likely to change under you, and the least valuable to have hard-coded. The merchant-side work — issuing a binding quote, checking the purchase against a mandate, creating the order, returning proof — is identical whichever dollar token clears.

What's next

Three things are worth watching, in order of how soon they will affect a merchant.

Whether Open USD ships at all this year, against a "later this year" that has not tightened in six weeks. Whether Stripe's default lands with the narrow scope its own post describes or the broader one on the consortium's page. And whether the consortium ever publishes a chain list in its own voice — because until it does, every integration plan built on one is built on secondary sourcing.

None of that changes what the merchant has to be able to do. If your business should be able to take an agent's purchase on whichever rail it arrives with, and produce a record afterwards, list your store on XAgent and let the open execution market route the settlement.