An AI assistant can request a paid service without sending you through a checkout page for every request. x402 supplies a payment format for that process. Solana is one of the networks that can settle those payments.
The recent development is batch settlement. PayAI announced Solana batch settlement on October 22, 2026, allowing repeated requests against a funded payment channel. Its current integration guide describes a public preview with capacity limits.
For wallet users, the useful questions are familiar: what can the app spend, who receives the money, and how do you stop paying? Understanding those questions matters more than the AI label.
What x402 does
The official x402 introduction describes an open standard for charging for web resources. Those resources can include data, content, or an API. An API is an interface that lets one program request work from another.
x402 uses HTTP, the system browsers and web services use to exchange requests and responses. Its name comes from the 402 Payment Required response. The service uses that response to explain what payment it accepts.
AI agents are one use case. Ordinary programs and human-directed applications can use the same standard. You do not need an AI model to make a payment through x402.
For example, a research app might purchase one market-data result instead of requiring a monthly subscription. Whether that is useful depends on the service's actual pricing and the quality of the result.
Follow one payment from request to response
The HTTP 402 documentation describes how the service communicates its accepted payment scheme, amount, asset, network, and receiving address. A scheme is the set of rules for authorizing and settling that payment.
In a simple exact-payment flow:
- Your app requests a paid resource.
- The service returns its payment requirements.
- Your app selects an acceptable requirement and signs a payment payload.
- The app retries the request with that payload.
- The service verifies and settles the payment before returning a successful paid response.
Authorization and settlement are different. Authorization permits the payment. Settlement records the movement of value on the blockchain. A batch scheme can accept an authorization now and settle accumulated charges later.
This distinction also explains why a payment notification and a useful answer are separate things to inspect. Check both the payment outcome and whether the service delivered what you requested.
What a facilitator does
A facilitator helps a service verify payment information and submit transactions. The x402 facilitator documentation describes it as an optional service. A merchant can instead operate the required infrastructure itself.
The facilitator is not the AI assistant and is not necessarily the seller. It performs a payment role between the app and the service. Different providers support different production networks and payment schemes.
For a user, this creates a practical check: identify the seller and the payment provider separately. A familiar payment provider does not establish that a seller's information is accurate or useful.
Solana support does not mean every route works
The network and token documentation distinguishes Solana mainnet from devnet and lists USDC as its default Solana asset. Support also depends on the chosen facilitator.
That means “supports x402” is not enough information. Your app, service, and payment provider must agree on the network, asset, and scheme. An amount of USDC held on another network does not automatically become a Solana payment.
The default public x402.org facilitator is for testnet development. Production services need a compatible production provider or their own infrastructure. Check current support rather than using a tutorial's test settings with real funds.
Why batch settlement matters for repeated requests
An exact payment can suit a single purchase. A task with hundreds of small requests has a different cost pattern. Repeating settlement for every request can add overhead.
PayAI's batch announcement describes a reusable channel funded with USDC. Requests record amounts owed through signed vouchers. The merchant later claims and distributes accumulated payments on-chain. Funding, payouts, and closure still involve blockchain operations.
The potential benefit is fewer on-chain operations per request. It is not a promise of free inference or instant answers. The model, data service, and payment provider can each have costs or limits.
Check how you withdraw unspent funds before you make a deposit. A channel deposit is different from paying one quoted amount and finishing the purchase.
The signing mode changes whom you trust
The Solana batch-settlement specification describes client-signed vouchers and an optional server-signer mode. In the latter, a merchant operator can sign cumulative charges under a channel authorization.
The PayAI integration guide makes the implication explicit: customers must trust that operator and cap the total funded balance. The on-chain program does not establish that the merchant measured its service usage correctly.
An individual request limit and a total deposit limit protect different amounts. A small maximum charge per request does not prevent many requests from adding up. Include top-ups when you review the total money available to the service.
Give an automated task a budget
Consider a hypothetical research task priced at 0.002 USDC per request. Five hundred requests would cost 1 USDC before any other charges. Five thousand would cost 10 USDC. The individual price stayed small while the total changed substantially.
Before enabling automatic payments, define:
- The services the task may contact.
- The maximum charge for one request.
- The total spending limit for the task.
- Whether deposits can refill automatically.
- When the task must stop and ask you.
Use a separate, limited wallet for experimental automation when your app supports it. Our multi-wallet strategy guide explains how separating activities limits the assets exposed to one app.
Do not treat a budget displayed in a dashboard as proof that every signing route enforces it. Check the application's documented controls and review actual charges.
Check receipts, refunds, and fees
The x402 FAQ describes exact payments as irreversible once executed. A seller can issue a separate refund, but that is a business process. Ask about refunds before purchasing an expensive or uncertain result.
For a payment channel, the PayAI guide describes closing, outstanding merchant payouts, a withdrawal grace period, and the return of remaining funds. Do not assume closing means an immediate refund.
Keep payment receipts and transaction signatures. You can inspect public on-chain transactions in Solana Explorer. If a response times out, check the existing transaction before approving a replacement payment.
x402 itself has no built-in standard fee, according to its introduction. The service, network, and facilitator can still charge. Read the complete price and sponsorship conditions rather than assuming “gasless” means free usage.
Payments and account cleanup are separate tasks
An automated payment does not automatically close the token accounts involved. Solana's close-account documentation describes closure as a separate instruction, with conditions including a zero ordinary token balance.
Use our wallet cleanup checklist when you retire a wallet or finish an experiment. SolPurge can close eligible empty token accounts. It does not operate x402 channels, withdraw their deposits, or cancel an agent's spending permissions.
The practical benefit of x402 is programmatic payment for individual services. Keep the payment rules visible and the money available to automation limited to the task you intended.
Sources
- x402: introduction
- x402: HTTP 402 and payment communication
- x402: facilitator responsibilities
- x402: network and token support
- x402: FAQ
- x402 Foundation: Solana batch-settlement specification
- PayAI: Solana batch announcement, October 22, 2026
- PayAI: Solana batch integration guide
- Solana: close a token account