PayAI Launches x402 Batch Settlement on Solana in Public Preview, Bundling USDC Micropayments Into Channel Claims

PayAI PAYAI$0.00005627-0.7% opened a public preview of x402 batch settlement on Solana SOL$120.04+0.4% on 30 September 2026, giving merchants that charge per request a way to collect thousands of tiny USDC payments without writing each one to the chain. PayAI announced the launch in a thread on 30 September that closed with "x402 batch settlement is live on @solana today," linking developers to its docs. PayAI pitched the feature at anything that bills by usage: AI inference, agent tools, metered APIs, data retrieval and rendering, per the same thread.

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. In the per-payment flow PayAI is replacing, each of those charges settles as its own on-chain transaction. Batch settlement moves the per-request billing off-chain: a customer funds a channel once, the service tallies what is owed as requests come in, and the merchant sweeps the running total on-chain every so often. PayAI put the scale this way: "a million $0.001 payments can settle on-chain as one $1,000 claim."

How PayAI's x402 batch settlement works on Solana

PayAI's batch settlement runs on a reusable payment channel that a customer funds with between 0.01 and 100 USDC, according to PayAI's merchant documentation. Each request after that is covered by a signed voucher recording the cumulative amount owed. The merchant's server runs a claim job, which the documentation recommends every 10 to 60 seconds, that collects the accumulated vouchers on-chain and distributes the money to the merchant's USDC account.

The closest everyday comparison is a bar tab. The card is authorised once, each drink goes on the tab, and the bill settles at the end rather than at every round.

Vouchers can be signed two ways. In client mode the customer signs each one. In server mode the customer delegates to an operator key held by the merchant, which signs cumulative vouchers after metering actual usage, the pattern suited to AI inference, where the final cost is unknown until the job finishes. PayAI's thread made the same point in plainer terms: "if the honest answer to 'what will this cost?' is 'we'll know when it finishes'... this is for you."

The customer keeps an exit. If the merchant stops claiming, the customer can withdraw the unclaimed balance after a grace period the merchant sets between 15 minutes and 24 hours, per the PayAI documentation. PayAI, acting as the facilitator (the service that submits and pays for the on-chain transactions), sponsors channel setup and transaction fees. Under the x402 batch-settlement specification for Solana, only the payer's authorised key can sign a voucher that raises the settled amount, and the facilitator "can close at the current onchain watermark but cannot redirect funds."

BlockRunAI example: PayAI's fee estimate for batched x402 payments

PayAI's headline case is an AI inference provider. BlockRunAI settled 18.5 million payments in 30 days under the per-payment x402 model, costing about $18,400 in network fees, according to PayAI. PayAI estimates the same flow would cost less than $1 with batch settlement. Both numbers are PayAI's; the sub-$1 figure is its estimate for that volume batched, not a measured result.

The arithmetic explains the pitch. PayAI's figures work out to roughly a tenth of a cent in fees per payment, which is the same size as the $0.001 charge in PayAI's own example. For services pricing calls at fractions of a cent, per-payment settlement can cost as much as the thing being sold.

That matters most on Solana because that is where x402 traffic already concentrates. The Solana account reported on 22 September, citing Artemis data, that the network handled 76% of all x402 transactions over four weeks, 23.2 million in total, a share we covered at the time.

Public preview limits: USDC on Solana mainnet, 1,000 channels

PayAI describes its facilitator support as "a public preview with bounded channel capacity." The documentation lists USDC on Solana mainnet as the only supported asset, caps sponsored capacity at 1,000 channels across the service, allows at most four channels per claim transaction and ten open or closing channels per merchant. Merchants need the @x402/core and @x402/svm packages at version 2.28.0, kept in sync, and durable storage such as Redis or PostgreSQL; in-memory stores are for testing only. PayAI's thread suggests developers start on devnet before going live, and the documentation commits to at least 30 days' notice before PayAI stops admitting new batch channels.

The documentation also warns that "a successful claim is not merchant payment": the distribution step that follows must also succeed, and the merchant's USDC balance must actually rise by the expected amount. A CoinMarketCal listing carried by TradingView dated the preview to 30 September and noted that commercial throughput remains unverified while the feature is in preview.

x402 Foundation merge and the Solana payment-channels program

The batch-settlement scheme now sits in the shared x402 standard. PayAI says Solana batch settlement was merged into the x402 repository on 25 September, crediting four named contributors for the pull request. PayAI's own 28 September preview release describes packaging "the merged upstream x402 batch-settlement implementation." The repository belongs to the x402 Foundation, the standards body launched under the Linux Foundation in July.

The specification requires implementations to use a single canonical Solana program for channels, the payment-channels program maintained by the Solana Foundation at CHNLxYvVA28MJP9PrFuDXccuoGXAx7jBacfLEkahyGsX. Because the channel format lives in the shared standard, other x402 facilitators can build against the same program.

That program was already busy before the announcement. Solana Compass program analytics for the payment-channels program record 217 transactions from 24 to 29 September, peaking on 29 September at 66 transactions signed by 14 wallets. Those 217 transactions paid about 0.0021 SOL in network fees combined. The data covers every caller of the shared program, so it includes activity beyond PayAI's own.

For Solana, the change keeps metered agent payments settling on-chain without making each call carry its own transaction, on the network that already carries most x402 transactions. The open question for the preview is demand: whether merchants beyond PayAI's launch examples fill those 1,000 sponsored channels.