Solana's new payment-channel system lets AI agents authorize purchases off-chain at high speed, but recovering money when an operator goes silent depends on an on-chain timer. A customer can reclaim an unspent deposit, but a merchant whose final bill misses the settlement deadline can lose the ability to collect from that channel entirely.
Solana's payment channels move repeated micropayments off the blockchain, authorizing each one with a signed message instead of a separate transaction. The system's Sept. 3 announcement reported more than one million payments per second through a proxy using 100,000 unique wallets. That figure measures speed, not what happens when an operator stops responding mid-transaction.
A benchmark, not a live payment record
The benchmark template behind that figure reports about 1.09 million verified vouchers per second on a 128-core AVX-512 host during a sustained 10-minute run. It measures the payment gate returning a response without an upstream service, not a million completed AI tasks or independently settled mainnet transactions each second.
A deployment using durable session storage instead of the default in-memory store must be benchmarked separately, since a durable write adds to the request path. The Solana Foundation said Alibaba Cloud API endpoints were live at launch, and the program repository lists a mainnet deployment. Still, the benchmark describes a test workload rather than measured commercial demand.
How a refund works when the operator disappears
A customer deposits a ceiling into an on-chain escrow, and spending authorizations accumulate against it as the service gets delivered. When both sides cooperate, the payee can submit final settlement and distribute funds in one transaction.
When the operator goes unresponsive, the customer instead requests a forced close and starts a grace period. The Sept. 3 session draft recommends 900 seconds, or 15 minutes, configured per channel, with the clock starting when the request lands on-chain rather than when the customer notices the outage. A customer holding no SOL needs to obtain it, or find another party willing to pay the fees, to initiate that escape.
The merchant's collection window narrows
Once the payer requests close, the ordinary settlement instruction stops accepting new vouchers. During the grace period, the merchant's final bill must instead pass through a payee-authorized settle-and-seal path before the deadline.
If that delivered service never reaches the final on-chain settlement total in time, it can become uncollectible from that channel, and the customer's refund is calculated against the recorded total rather than a later reconstruction of what was owed. Merchant funds already recorded as settled remain reserved for distribution after sealing, so an unresponsive operator does not erase every unpaid balance — only the portion that missed the deadline.
Separately, the instruction reference allows a drained channel's refundable SOL rent to stay committed until a 1,500-slot opening window has passed, a timer that concerns account deallocation rather than the customer or merchant payout itself.
Source: CryptoSlate
Trading involves risk.
Risk Disclaimer
