Does Stripe support AI agent payments?

Yes. Stripe co-created the Agentic Commerce Protocol with OpenAI, offers an Agentic Commerce Suite for merchants, issues Shared Payment Tokens that scope payment credentials, and supports machine payments over HTTP 402 through the Machine Payments Protocol and x402, including stablecoin payments that settle to merchants in fiat.

Does Stripe support x402?

Yes. Stripe's machine payments documentation lists x402 support with USDC on Base, alongside the Machine Payments Protocol with stablecoins on Tempo and Solana. Merchants can charge agent clients per request and receive settlement through their Stripe account. Check current docs for supported networks.

What is a Stripe Shared Payment Token?

A scoped payment grant that lets an agent pay without seeing the buyer's card details. It can be limited to one seller, an amount, and an expiry. It is used in the Agentic Commerce Protocol and Stripe's agent features, and card payments through it have a minimum amount.

Stripe Agent Payments: What Stripe Offers for AI Agents

Stripe supports agent payments through several products: the Agentic Commerce Protocol with OpenAI for agent checkout, the Agentic Commerce Suite for merchants selling through AI agents, Shared Payment Tokens that scope credentials to a seller and amount, and machine payments supporting the Machine Payments Protocol and x402. Stablecoin acceptance settles to merchants in fiat.

Agentic Commerce Protocol

Stripe co-launched the Agentic Commerce Protocol with OpenAI on September 29, 2025. ACP defines how agents create and complete checkout sessions with merchants. Stripe's role includes providing the payment token model and merchant tooling so businesses already on Stripe can accept agent orders.

Agentic Commerce Suite

Announced in December 2025, the Agentic Commerce Suite gives merchants one integration to sell through multiple AI agents, covering product discoverability, checkout, and payment with Shared Payment Tokens. Stripe named retailers and commerce platforms among early users.

Shared Payment Tokens

A Shared Payment Token is a scoped grant: it can be limited to a seller, an amount, and an expiry, so an agent can pay without holding the buyer's card. Stripe's documentation notes a minimum card amount for payments through these tokens, which matters for very small charges.

Machine payments

Stripe's machine payments documentation covers charging software clients over HTTP 402. It lists support for the Machine Payments Protocol, which Stripe co-authored with Tempo, using stablecoins on Tempo and Solana, and for x402 using USDC on Base. The x402 integration runs on a preview API version, and stablecoin acceptance outside the United States is also in preview, so check availability before building on either. Merchants can serve agent clients without account signups.

Stablecoin acceptance

Stripe accepts several stablecoins, including USDC on multiple networks such as Base, and settles them to the merchant's Stripe balance in fiat. Availability varies by country and Stripe documents per-transaction limits. This suits merchants who want stablecoin customers without holding crypto.

Tempo

Tempo is a payments-focused, EVM-compatible layer 1 blockchain incubated by Stripe and Paradigm. Its mainnet launched on March 18, 2026, alongside MPP. Stablecoin payments on Tempo are one of MPP's payment methods.

Bridge and Privy

Stripe closed its acquisition of Bridge, a stablecoin infrastructure company, in February 2025, and announced the acquisition of Privy, a crypto wallet provider, in June 2025. These give Stripe stablecoin orchestration and embedded wallet capabilities.

When Stripe fits

Stripe fits merchants and API providers that already use Stripe, want fiat settlement, need card and stablecoin acceptance in one place, and value managed compliance. It is a strong default for selling to agents.

When a non-custodial rail fits

Agent builders who want their agents to pay many services directly, keep funds in self-custody, and enforce spending limits cryptographically may prefer a non-custodial wallet paying x402 endpoints in USDC on Base. The two approaches meet at the protocol: an agent paying via x402 can pay a Stripe merchant that accepts x402.

Cards versus stablecoins for agents

Cards bring familiarity and dispute rights but have minimum amounts and slower settlement. Stablecoins settle quickly and handle tiny amounts on low-fee networks. Many providers accept both, letting each agent use what its principal prefers.

Implementation steps for merchants

Merchants on Stripe can enable agentic commerce features, connect catalogs for discoverability, accept Shared Payment Tokens at checkout, and, for API products, configure machine payments with price and accepted methods per endpoint. Test mode allows full testing without real funds.

Considerations

Check country availability, fees, transaction limits, and which agent platforms are supported. Specifications and products in this area are changing quickly, so confirm current documentation before committing to an architecture.

Safety when agents pay for Stripe Agent Payments

Whatever the merchant uses, the paying agent needs bounded authority: scoped tokens on the card side, and capped, revocable session keys on the stablecoin side. Merchant-side protocols do not limit what a compromised agent might try to buy elsewhere.

Link and agent wallets

Stripe's documentation notes that Shared Payment Tokens can be issued from Link, Stripe's saved-payment network, including an agent wallet feature. This lets consumers authorise agents to pay with saved methods under scoped limits, rather than sharing card numbers with each agent platform.

Fees and limits

Stripe charges fees on agent payments in line with its pricing for the relevant payment method, and documents transaction limits for stablecoin acceptance and minimum amounts for card payments via Shared Payment Tokens. For high-volume, very small machine payments, compare these against onchain settlement costs on a low-fee network.

Architecture patterns

A common pattern pairs Stripe on the selling side with flexible payers on the buying side. A merchant exposes ACP checkout for consumer agents and x402 or MPP endpoints for API access, all settling into Stripe. Agents pay with scoped card tokens or with stablecoins from bounded wallets, depending on what their principals prefer.

Testing agent payments on Stripe

Stripe test mode lets merchants simulate agent checkouts with test tokens and exercise machine payment endpoints without moving real money. For stablecoin flows, pair test mode with testnet assets where supported, and verify error handling for declined, expired, or over-limit payments before launch.

Frequently asked questions

Does Stripe support AI agent payments?: Yes. Stripe co-created the Agentic Commerce Protocol with OpenAI, offers an Agentic Commerce Suite for merchants, issues Shared Payment Tokens that scope payment credentials, and supports machine payments over HTTP 402 through the Machine Payments Protocol and x402, including stablecoin payments that settle to merchants in fiat.
Does Stripe support x402?: Yes. Stripe's machine payments documentation lists x402 support with USDC on Base, alongside the Machine Payments Protocol with stablecoins on Tempo and Solana. Merchants can charge agent clients per request and receive settlement through their Stripe account. Check current docs for supported networks.
What is a Stripe Shared Payment Token?: A scoped payment grant that lets an agent pay without seeing the buyer's card details. It can be limited to one seller, an amount, and an expiry. It is used in the Agentic Commerce Protocol and Stripe's agent features, and card payments through it have a minimum amount.