Accepting an on-chain payment should be as boring as accepting a credit card. Today it isn’t. You hold native tokens for gas, you track nonces, you write a different settlement path for every chain, and you reconcile failures that have nothing to do with your product.
Solvador removes all of it. We are an x402 facilitator: a single endpoint that verifies a payment, sponsors the gas, and settles it on-chain — across nearly every EVM network and Solana, including the chains other facilitators don’t reach.
What x402 is, in one paragraph
x402 revives the long-dormant HTTP 402 Payment Required status code as a real payment handshake. A client requests a resource, the server replies 402 with payment terms, the client attaches a signed payment in an X-Payment header, and a facilitator verifies and settles it. Your server never touches a private key or a gas balance — it just reads a header and serves the response.
The whole point of a facilitator is that the hard parts — gas, nonces, chain-specific settlement — stop being your problem.
The one request that matters
Here is the entire integration surface from your side. You forward the payment header to one URL:
POST https://api.solvador.com/settle
X-Payment: eyJ4NDAyIjoiMS4w...
Chain: solana-mainnet
// 200 OK — gas sponsored by Solvador
{ "settled": true }That’s it. No viem wallet client holding ETH, no @solana/web3.js fee-payer to keep funded, no per-chain branching.
What we sponsor
- Gas, everywhere. We hold and manage the native balances so you never do.
- Verification. We check the signature, amount, asset, and expiry before anything settles.
- Settlement. We broadcast, wait for inclusion, and return a clean result — or a typed error you can actually handle.
Why “further reach”
Most facilitators support the obvious handful of chains. The network your users are actually on is often not in that handful. We built Solvador to cover the long tail — the EVM networks and L2s that get skipped — so “supported chains” matches “chains your customers use.”
This blog — The Ledger — is where we’ll show our work: the protocol details, the settlement internals, and the edge cases behind that single endpoint.