Beyond x402 Volume: Solana’s Bet on Agent Spending Sessions

This piece traces how x402 on Solana turned into a full payment stack over six months, and looks at Payment Channels, the newest piece, which lets an agent spend a budget for a whole task instead of paying per call.

Solana added x402 support in November 2025, joining a protocol built mainly around Coinbase and Base. For months afterward, it stayed a secondary venue: no protocol governance, no cloud-scale endpoints, no session infrastructure of its own.

By mid-September, that had changed: a Linux Foundation-stewarded protocol, a formal x402 Foundation with Solana in its top tier, a cloud services layer through Pay.sh and Alibaba Cloud, and a new channel primitive for recurring agent spending.

The milestones that built the stack

November 2025. Solana added x402 support, becoming one more chain in a protocol still centered on Base.

February 2026. Solana already handled roughly 49% of x402 transactions by count, though Base still led in dollar volume.

April. x402’s stewardship moved from Coinbase alone to the Linux Foundation.

May. Solana Foundation and Google Cloud launched Pay.sh, an API proxy for Gemini, BigQuery, BigTable, and Cloud Run where an agent’s wallet stands in for an account. The same month, x402 added batch settlement as a protocol scheme, and AWS previewed payments in Bedrock AgentCore.

July. The x402 Foundation launched operationally on July 14, 40 members, three tiers, Solana in the top Premier tier alongside AWS, Google, Stripe, Visa, Mastercard, Circle, Cloudflare, and Coinbase.

August. Ramp launched an alpha letting businesses provision USDC agent wallets on Solana. AWS’s Bedrock AgentCore payments reached general availability, listing Solana only in the release notes as one of three payment methods. On August 25, Solana passed Base in daily x402 transaction count for the first time in six months, as BlockRun began routing most of its traffic to the network, a shift that held into a sustained weekly high peaking in early September.

PayAI Network’s September 14 update puts BlockRun’s run-rate at more than 5.46 million monthly transactions, 592 buyers, $109,620 in reported volume.

September. Solana Foundation launched Payment Channels, with Alibaba Cloud as launch partner providing endpoints through Pay.sh.

1,000,000 payments per second. Live on Solana today with Payment Channels. Agentic payments have a friction problem. Every call an agent makes needs a signature and a settlement. It works well enough for a single payment, but it’s broken for an agent making hundreds of metered calls.

Solana Foundation, @SolanaFndn, Sep 4.

The ecosystem beneath the headline

Metrics alone don’t build a network: an agent still needs to discover services, authorize payments, route transactions, and evaluate counterparties.

Solana’s x402 ecosystem now spans over 80 projects across five core layers.

Surface, where agents spend: @framesag, @meleemarkets, @trypurch, @agentmail, @PlayBabylon, @UnbrowseAI, @theheylolapp, @dtelecom, @attndotmarkets, @usetapestry, @MiloOnChains, @byreal_io, @Hyre_agent, @xona_agent, @alphakek_ai, @bankrbot, @JatevoId, @relayaisolana, @WURKDOTFUN, @JupiterExchange, @jito, @Pumpfun, @usebreezebaby, @krexa_xyz, @x402jobs, @flovia402, @PhoenixTrade, @rye, and @SeekerClaw.

Builder, tooling and infra: @dflow, @dexteraisol, @ClawRouter_, @openclaw, @solanaclawagent, @TryNoahAI, @BlockRunAI, @clawpumptech, @corbitsdev, @anagramxyz, @agentbox_fyi, @EitherwayAI, @virtuals_io, @BitRobotNetwork, @codecopenflow, @swarms_corp, @OOBEonSol, @Daydreamsagents, @elizaOS, @TektonicCompany, @Helius, @realmsdaos, @faremeterxyz, @AlliumLabs, @coingecko, @MessariCrypto, @NoditPlatform, @Quicknode, and @nansen_ai.

Rails, payment settlement: @stripe, @FireblocksHQ, @moonpay, @GoogleCloud, @SolanaFndn, and @magicblock.

Custody, wallets and credit: @crossmint, @PayAINetwork, @t54ai, @paysponge, @agentcashdev, @icpay_, @clawvaults, @atxp_ai, and @zerion.

Trust, identity and security: @metaplex, @zauthinc, @stormrae_ai, @fairscalexyz, @VeryAI, @Quantu_AI, @merit_systems, @8004_scan, @x402scan, @x402eco, @agentscoretrust, and @saidinfra.

It is noteworthy less for its scale than its implication: x402 on Solana is no longer just a protocol deployment, it has become a full stack.

Payment Channels: the newest milestone

Most of what’s shipped so far, Ramp, BlockRun, the Pay.sh endpoints, handles single, discrete payments. Payment Channels are for a different shape of work: an inference job billed by the token, a research task touching several paid services before it returns an answer. A wallet authorizes a budget for the session instead of a payment per call, and actual usage settles on-chain once, at the end.

For metered spending with an unknown final price, x402’s upto flow is the current implementation. The bigger unlock is batch settlement, introduced as a core x402 scheme in May, but still not live. PayAI says Payment Channels will be its underlying smart contracts: instead of paying gas on every payment, a merchant could settle millions of them for one fee under a cent.

That still requires the scheme to ship across facilitators, merchants, SDKs, and clients. Deployed doesn’t mean live, and live doesn’t mean adopted.

Payment Channels: 1 million payments per second. AI will not wait at a checkout screen. The future of internet payments needs to be built for unprecedented scale. But agentic payments today have a friction problem. Every call an agent makes needs a signature and a settlement.

Rish, @rishinsharma, Sep 4.

What changes next

Ramp alpha usage: how many agents actually spend, not just how many wallets get provisioned.

Merchant and endpoint adoption of Payment Channels specifically, not overall x402 transaction counts.

Batch settlement’s actual implementation across facilitators and SDKs, since the scheme itself is already specified.

Payment Channels’ own on-chain data, tracked separately from x402 volume overall.

Solana has shown agents can pay at scale. The next signal worth watching is simpler: whether merchants and agent developers actually use Payment Channels as their default, not how high the throughput number goes.