Solana has rolled out batch payments for the x402 standard with PayAI Network and BlockRunAI, letting AI agents make many small USDC payments before settling them together in a single on-chain transaction. The change moves per-payment costs on very small transfers from a few cents each toward under one dollar for full batches, according to reporting by AInvest and Bitcoin.com News, which is what makes sub-cent payments practical at all.
x402 is the open payment standard that lets software, including AI agents, pay for an API call in stablecoins at the moment it makes the request. Until now, each payment settled on its own, which priced out use cases where an agent pays fractions of a cent per call. The new layer bundles those payments into periodic channel claims, settling the accumulated total rather than each line item.
How batch settlement works
PayAI opened x402 batch settlement on Solana in public preview on September 30, letting merchants bundle USDC micropayments into periodic channel claims. An agent and a service open a channel, the service extends credit across many requests, and the accumulated balance is claimed on-chain on a schedule. The mechanism is closer to how card networks batch merchant settlements after accumulating transactions through the day than to anything genuinely new in payments design.
BlockRun is adopting PayAI’s payment channels to cut USDC transaction costs for payments that run through its infrastructure, according to coverage from ourcryptotalk. The change turns Solana’s low base fees, already cheap by chain standards, into something usable for payments where the underlying transfer itself is worth less than network costs would be on other chains.
The competitive framing matters too. Rewards for facilitators extending credit in these channels have fallen sharply in some markets as more players enter, reflecting competition for volume. Cheaper infrastructure cuts everyone’s unit economics and shifts value toward whoever aggregates the most payment flow.
Why agents need payments at all
AI agents have been running through infrastructure without their own ways to pay for access. An agent that scrapes data, calls an API, or executes a trade needs to compensate whoever provided the service. Real deployments have relied on prepaid API keys or monthly subscriptions, which break once agents need to pay for something on demand or interact directly with other agents in machine-to-machine commerce.
Inline payments solve that. An agent that needs weather data for a flight booking pays for the one call it makes. An agent buying compute capacity pays per second rather than reserving blocks it will waste. The problem was always the economics of charging small enough amounts and having the network cost not swallow the payment. That is what batching addresses directly.
There is also a design upside beyond cost. Payments embedded in the request itself mean no account provisioning, no API key management, no subscription lifecycle. A service can accept payment from any agent that arrives with USDC, which widens who can use it without requiring a signup flow. For open ecosystems that want agent participation without identity gatekeeping, that is a structural difference rather than a pricing tweak.
Where the x402 standard comes from
x402 originated as a protocol Coinbase built on HTTP’s status code 402, which has sat unused since the web’s early days as a placeholder for payments. The standard was open-sourced, and other chains adopted versions of it. Base and Ethereum both run x402-compatible integrations now. Solana’s addition of batching is a Solana-side optimization on top of a portable standard, not a fork of the specification.
That portability matters for whoever builds companies on it. A developer integrating x402 into an application is not committed to Solana alone; a payment that works from a Base wallet can settle on Solana rails where fees are cheaper, then be withdrawn or routed onward. Standards layers age better than chain-specific ones, which is part of why the standard spread through crypto’s API economy rather than splitting into incompatible native implementations.
The x402 Foundation recently consolidated governance of the standard as adoption grew, according to Solana Compass coverage of the batch launch, which suggests the parties involved view it as settled infrastructure rather than a passing experiment.
What is still unresolved
Two questions remain open. The first is dispute handling. When an agent pays for a service in a channel and the service fails to deliver, recovering the payment depends on whatever dispute mechanism the channel operator runs. Inline payments via smart contracts already faced this, and batching adds a settlement delay where the boundary between a refund and a charge depends on timing. Nothing in the rollout answers it cleanly.
The second question is what regulators do about payments this small. Micropayments in stablecoins sit below any threshold that triggers reporting on individual transactions, but the aggregate behavior of an agent spending constantly raises questions about whether scaling rules designed for humans apply. Nothing in the batch payments rollout touches this; it keeps agents within existing USDC transfer rules and leaves policy for later.
A third consideration is trust in the counterparty. Because channels extend credit before on-chain settlement, an agent that cannot establish the service operator’s reliability is exposed between payment and claim. Existing deployments work because the counterparties are known infrastructure providers. At scale, credit terms and reputation systems will need to grow alongside the payment plumbing.