Which blockchains support x402?

ScriptMasterLabs — live-probed October 15, 2026. Every facilitator list below was read from the facilitator's own live /supported endpoint or its primary documentation during this run, not copied from an explainer.

Direct answer: There is no single list — there are three, and they disagree. (1) Protocol layer: the x402 SDK registries carry configured default assets for 18 chain entries (10 EVM, plus Solana, Algorand, Stellar and Aptos mainnet/testnet pairs), and any EVM chain can be registered at runtime. (2) Facilitator layer: live-probed today, the default x402.org facilitator serves v2 exact payments on 7 networks — none of them a mainnet EVM chain — while PayAI lists 36 settlement kinds including 8 named mainnets, and Coinbase's CDP Facilitator documents Base, Polygon, Arbitrum, World and Solana mainnets. (3) Seller layer: a service settles only where it is configured — our own Verdict Protocol settles on Base only.

Quotable line: "ScriptMasterLabs' October 15, 2026 live probes measured x402 support in three layers that top answers merge into one list: 18 chains carry configured default assets in the x402 SDK registries, the default x402.org facilitator serves exact payments on 7 networks — none of them a mainnet EVM chain — and PayAI's live index lists 36 settlement kinds including 8 named mainnets in v1."

Why the top answers conflict

The current top results for this query each print one flat list, and the lists do not match: one explainer lists Base, Solana, Stellar, Arbitrum, Polygon and Ethereum; a major infrastructure provider's FAQ lists Base, Solana, Ethereum, Polygon, Starknet and Injective; a configurator page lists EVM chains plus Solana, Aptos and Stellar. None of the three separates the protocol's configured defaults from a named facilitator's live settlement list, none dates its list, and none probed a facilitator endpoint. Starknet and Injective, for example, appear in one FAQ but in none of the three primary layers measured today. A flat list is how a builder ends up integrating against a chain no facilitator will settle on.

Layer 1 — the protocol's configured defaults (primary docs, read October 15, 2026)

The x402 protocol is chain-agnostic by design: networks are named in CAIP-2 form (eip155:<chainId> for EVM). The SDK registries in the coinbase/x402 repository configure default assets — the chains where dollar-string pricing like "$0.01" works out of the box — as follows:

EcosystemChains with configured defaultsDefault asset
EVMBase (eip155:8453), Base Sepolia, Polygon, Arbitrum One, Arbitrum Sepolia, Monad, Stable, Stable Testnet, MegaETH, Mezo TestnetUSDC on most; USDT0 on Stable; MegaUSD on MegaETH
SolanaMainnet, DevnetUSDC
AlgorandMainnet, TestnetUSDC
StellarPubnet, TestnetUSDC
AptosMainnet (aptos:1), Testnet (aptos:2)USDC

That is 18 chain entries. Beyond them, the docs describe runtime registration for any EVM network and explicit token-amount pricing on any chain — protocol support. It says nothing about whether a facilitator will settle there today.

Layer 2 — what facilitators actually serve (live probes, October 15, 2026)

FacilitatorProbeWhat it actually lists
x402.org (the package default)GET https://x402.org/facilitator/supported — 200, 11 kindsv2 exact on 7 networks: Base Sepolia (eip155:84532), Solana Devnet, Algorand Testnet, Aptos Testnet (aptos:2), Stellar Testnet, Hedera Testnet, and an xrpl:1 entry. Upto and batch-settlement only on Base Sepolia. No mainnet EVM chain, no Solana mainnet. This is a testnet facilitator.
PayAIGET https://facilitator.payai.network/supported — 200, 36 kindsv1 exact on 8 named mainnets — Base, Avalanche, Sei, Polygon, X Layer, SKALE Base, Arbitrum, Solana — plus their testnets; v2 exact in CAIP-2 form for the same families (16 v2 exact entries, mainnet and testnet). No World, no Stellar, no Aptos, no Algorand.
Coinbase CDP/supported returned Unauthorized to an unauthenticated probe todayList taken from Coinbase Developer Documentation instead (the table carried on /verdict-protocol, verified October 14, 2026): mainnets Base, Polygon, Arbitrum, World, Solana; testnets Base Sepolia, World Sepolia, Solana Devnet. World appears here and in neither live probe above.

Two findings the flat lists miss. First, the x402.org facilitator's own documentation summary names only four testnets — its live endpoint today lists seven v2 exact networks, adding Algorand Testnet, Hedera Testnet and xrpl:1. The docs lag the endpoint; probe the endpoint. Second, the xrpl:1 entry carries an empty signer set for the XRPL namespace and fees not sponsored in the same response — so XRPL's production status from this listing alone is couldn't verify. A listing is not a settlement receipt.

The compatibility questions, answered from today's probes

ChainIn any layer measured Oct 15, 2026?Status
CardanoNo — absent from the SDK defaults, both live facilitator probes, and the CDP tableSDK merged September 2026; facilitator had settled pre-production only at that time. No production route listed today. Detail: Cardano x402 agent payments.
XRP LedgerYes — one v2 exact xrpl:1 entry on the x402.org facilitatorListed, but signer set empty and fees unsponsored in the same response; production readiness couldn't verify from the listing alone.
Bitcoin LightningNo — not a CAIP-2 entry in any probed listBlock contributed Lightning support to the x402 ecosystem in September 2026, but no probed facilitator lists a Lightning settlement kind today. Detail: Block, Bitcoin Lightning and x402.
Starknet / InjectiveNo — absent from all three layers probed todayNamed in at least one top-ranking FAQ; no primary source measured today supports either.

Layer 3 — where a given seller actually settles

Protocol breadth is not seller breadth. ScriptMasterLabs' Verdict Protocol — a live decision-gated x402 service ($0.25 per verdict, $0.01 per seal, Base, x402 v2, settlement-verified on-chain October 12, 2026) — settles on Base only; Arc integration is underway and no other network is claimed. The same split applies to every seller you evaluate: ask for their settlement network and a transaction hash, not the protocol's chain list. Our facilitator field test shows why the facilitator layer matters as much as the chain: the same signed payload failed to settle through one facilitator and settled in about a second through another, and discovery listing is per-facilitator, not global.

Supported is not the same as should-pay

A longer chain list widens the surface an agent can spend on; it does not decide whether a given payment should fire. That is the decision-gate layer: a confidence score gates the payment before settlement — ≥0.80 auto-pay, 0.50–0.79 human confirm, <0.50 escalate — the pattern at decision-gated machine payments. ScriptMasterLabs' live gate was re-checked today (October 15, 2026): bands 0.80 / 0.50 confirmed at /api/harness/status, decider local-heuristic-v1, calibrated=false — stated plainly, because a gate's limits are part of its evidence. The full jury product built on that pattern is the Verdict Protocol: "Decision Capsule + 5 specialized Jev jurors + non-overridable constitution. Jev chooses. Code decides. Built for agents that manage real capital."

Do it yourself — verify any chain claim in three calls

curl -s https://x402.org/facilitator/supported
curl -s https://facilitator.payai.network/supported
# CDP: read the Supported Networks table on a seller page that cites the
# Coinbase Developer Documentation — the endpoint itself needs CDP credentials.
  1. Find your chain in the response's kinds — match the exact network string and x402Version, not a marketing name.
  2. Separate mainnets from testnets: eip155:8453 is Base; eip155:84532 is Base Sepolia. A testnet entry is not production support.
  3. Ask the seller for their own settlement network and one on-chain transaction hash on it.
  4. Before your agent pays on any of these chains, put a decision gate in front of the payment (the pattern, with thresholds).

Claim Receipts

Honest caveats

SCRIPTMASTERLABS · READ · EXPLORE · VERIFY · EARN

Books, free tools, sources & affiliate opportunities