What you already do is what a budget needs.
A budget payment follows the x402 exact scheme for Solana to the letter. Here is the whole of it, from your side.
| You | A budget |
|---|---|
Answer 402 with an exact price on Solana. | Reads it from the header, or from the body on the first version of the protocol. |
| Name your price in USDC. | Pays in the mint it holds, which is that one by default. |
Name payTo, your wallet. | Pays that wallet’s token account for the mint. |
Name your facilitator’s key as extra.feePayer. | Builds the transaction with it as fee payer. The agent needs no SOL. |
| Hand the payment to your facilitator. | Is checked and settled on the facilitator’s default path. |
| Answer with the result and the receipt. | Returns your response to the agent’s code as it is. |
What arrives.
One transaction with four instructions. Your facilitator sees the transfer it always sees, for the amount you asked, into your account.
| # | Instruction | Value |
|---|---|---|
| 1 | Compute unit limit | 20,000 units |
| 2 | Compute unit price | 1 micro-lamport per unit |
| 3 | TransferChecked | Your price, to your account |
| 4 | Memo | Your reference, or a random one |
TransferChecked
source the budget account (not the payer's own wallet account)
mint USDC
destination your token account (payTo's account for the mint)
authority the agent key (the source account's delegate)
amount your price, in full
The one thing that differs, and why it settles.
In most x402 payments the account the money leaves belongs to the key that signs. In a budget payment the signer is the account’s delegate: the money leaves an account the budget owns, and the agent key signs as the one approved to move it. The token program treats both the same way and so does the scheme.
A facilitator verifies a payment by its outcome: the mint, the amount, the destination account. It leaves the source account free, so a delegate’s transfer passes the same checks as an owner’s. The scheme is specified by the x402 Foundation: Exact Payment Scheme for SVM.
A service in a few lines
If you have not put a price on your API yet, this is the whole of it with the reference middleware. Nothing in it knows about Breaker.
import { Hono } from 'hono'
import { HTTPFacilitatorClient } from '@x402/core/server'
import { paymentMiddleware, x402ResourceServer } from '@x402/hono'
import { ExactSvmScheme } from '@x402/svm/exact/server'
const network = 'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp' // Solana mainnet
const usdc = 'EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v'
const server = new x402ResourceServer(new HTTPFacilitatorClient({ url: FACILITATOR_URL })).register(network, new ExactSvmScheme())
const app = new Hono()
app.use(
paymentMiddleware(
{
'GET /search': {
accepts: [{ scheme: 'exact', network, payTo: MY_WALLET, price: { asset: usdc, amount: '5000', extra: { decimals: 6 } } }],
description: 'Web search results for a query',
mimeType: 'application/json',
},
},
server,
),
)
app.get('/search', (c) => c.json({ results: [] }))
5000 is 0.005 USDC: amounts are in the mint’s base units, and USDC has 6 decimals.
Your own reference on every payment
Put a string of up to 256 bytes in extra.memo and the payment carries it on chain as its memo: an order id, a request id, a customer. Without one, each payment carries a random memo, so two payments of the same price are always two different transactions.
Who paid
| On the transaction | It is |
|---|---|
| The transfer’s authority | The agent key. One agent, one key: it is the steadiest name for a customer. |
| The transfer’s source | The budget account. It stays the same when the owner replaces the key. |
| The fee payer | Your facilitator. |
When an agent is at its limit
The SDK checks the price against the budget before it signs. An agent whose budget cannot cover your price sends you no payment at all: you see the first request and no second one. Your facilitator is never handed a transfer that would fail for the budget’s limit, its balance or its switch.
That check reads the chain at the moment of the call, so a price the agent can pay is a price that settles.
Selling by the stream.
A budget also opens a payment channel to you, through x402’s two streamed schemes on Solana. Its deposit counts against the agent’s limit like a payment, and what you do not settle goes back to the budget.
| You sell | To take budgets |
|---|---|
Metered calls by upto: a ceiling per request, the use settled | Name Breaker’s facilitator. Your seller scheme stays the reference one. |
Sessions by batch-settlement: one deposit, a voucher a call, claimed in batches | Name Breaker’s facilitator, and install @breaker/x402-seller in place of the reference seller scheme. |
Selling by the stream also opens you to budgets on lines. An owner can name the services a budget may pay, each with a cap per period, and a budget on lines pays those services by session or metered call and nothing else. Your payTo is what the owner names. How lines work.
A budget opens its channel through Breaker’s open_channel, whose inner instruction is the payment-channels program’s own open. Breaker’s facilitator is the reference facilitator with that one layout added to its open and top-up checks; the channel, the vouchers, the claims and the payout are the reference’s. A wallet’s channel passes it unchanged.
npm i https://breaker.to/x402-seller/breaker-x402-seller-0.2.0.tgz
import { HTTPFacilitatorClient } from '@x402/core/server'
import { x402ResourceServer } from '@x402/hono'
import { UptoSvmScheme } from '@x402/svm/upto/server'
import { BatchSvmScheme, MemoryChannelStore } from '@breaker/x402-seller'
const network = 'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp' // Solana mainnet
const facilitator = new HTTPFacilitatorClient({ url: 'https://facilitator.breaker.to' })
const store = new MemoryChannelStore()
const server = new x402ResourceServer(facilitator)
.register(network, new UptoSvmScheme({ receiverAuthorizerSigner, rpcUrl }))
.register(network, new BatchSvmScheme({ receiverAuthorizer, store }))
The routes are priced as before, with scheme: 'upto' or scheme: 'batch-settlement' in their offer. @breaker/x402-seller takes the reference scheme’s options and API unchanged. The whole seller, routes included, is on the x402 page.
Where agents already pay
- 76%
- of x402 transactions ran on Solana in the four weeks to 2026-09-22. Artemis, via Solana Compass, 2026-09-22
- 99.6%
- of x402 settlement is in USDC. TRM Labs, 2026-09-09