Bitcoin 
Ethereum 
Tether 
BNB 
Solana 
XRP 
USDC 
Lido Staked Ether 
Cardano 
Avalanche 
Key Points
-
Stripe machine payments arrive with the x402 protocol using USDC on Base
-
Developers charge autonomous agents through the PaymentIntents API with clear settlement tracking
-
CoinGecko API payments showcase one-cent requests using x402 across supported networks
-
Bloomberg reports a potential Stripe valuation of one hundred forty billion dollars
Stripe x402 USDC payments on Base introduce direct charging for agents within standard web requests.
Developers get deposit addresses via paymentintents API; agents send money using usdc to fund usage (agents). Teams track the status of transactions via APIs, webhooks, or the familiar Stripe dashboard at the time of settlement (teams). Coingecko’s API supports machine usage, with $0.01 usdc requests across multiple supported networks (machine usage). Stripe machine payments are shipped as a preview, to encourage testing via purl and sample code today (testing).
The process makes it easy for agents to purchase APIs, model context protocol calls, and simple http resources (agents). Workflows do not need to include complex gateways because the protocol is riding along side the normal request & response cycles (workflows). Businesses can keep refunds, reporting, and sales tax within their existing Stripe tools to help simplify financial operations (business).
ANOTHER MUST-READ ON ICN.LIVE
Hong Kong ready with a stablecoin license, what firms should prepare for now
What agents require when making payments?
Jeff Weinstein was clear in his description of the motivations behind the project, stating, “financial systems that are optimized for humans fail to meet agent needs today.” He identified microtransactions, constant availability, and quick finality, all of which match what agents require when making payments (agent needs). In my opinion, x402 provides predictable cost control for developers, while on-chain rails provide clear settlement for everyone (on-chain rails).
Stripe machine payments decrease friction for developers, since crypto details are optional for teams to decide whether they wish to use them (crypto details). The design honors existing developer behaviors, as the paymentintents api currently powers a large number of production integrations (payment intents API). Teams will be able to extend their existing code base and test workflows via Purl, Plus Node, and Python samples from Stripe.
Coingecko‘s x402 rollout serves as evidence, since agents pay per request with simple and transparent accounting. These changes represent a credible model for autonomous services to fairly pay for digital resources (credible model).
Stripe x402 usdc payments on Base
The x402 protocol uses http four hundred two to repurpose, which was originally used to signal payment required responses online. Now, the status directs agents to settle charges, then continue with normal programmatic access to data (normal programmatic access to data). Using the same status as an http four hundred two reduces new concepts, since every developer understands request headers and response codes from experience (request/response codes).
Businesses price their products in small increments and receive immediate signals when funds arrive for continued access (price products in small increments). Usdc on base offers quick settlement, low-cost transfers, and broad liquidity for programmatic transactions (low-cost transfers). The preview suggests broader coverage later, including more protocols, currencies, and blockchains across supported environments (preview).
Companies exploring agent monetization gain a simple path to bill usage without custom ledgers or wallets (custom ledgers/wallets).
An increase in the possible valuation of Stripe, due to investor interest around efficient payments for software-driven businesses worldwide (increase in possible valuation).
