# x402 facilitators compared, and how to pick one Coinbase CDP is the most used x402 facilitator and the default in most tutorials. thirdweb, PayAI and Cloudflare run alternatives, and the reference implementation can be self-hosted. The choice turns on chain coverage, pricing, documented replay handling and whether you can tolerate the facilitator being a single point of failure. Published: 2026-10-14 Last reviewed: 2026-10-14 Publisher: Roundhouse AI Ltd. Source: https://roundhouseai.io/resources/x402-facilitators-compared --- ## What you are choosing between A [facilitator](https://roundhouseai.io/resources/what-is-an-x402-facilitator) verifies a payment authorisation and settles it on-chain, paying the gas. Every x402 seller uses one, runs one, or does the work itself. The options as of October 2026, with the caveat that pricing and coverage change and the x402 ecosystem directory is the live list: | Facilitator | Notable for | Watch out for | | --- | --- | --- | | Coinbase CDP | Largest share of relayed volume, best documented | Concentration risk if everyone uses one | | thirdweb | Part of a wider web3 stack you may already run | Smaller x402-specific surface | | PayAI | Runs a large resource catalogue alongside | Catalogue and facilitator are separate concerns | | Cloudflare | Deferred payments for high-frequency use | Deferral means carrying credit risk | | Self-hosted | No third party, no fee, full control | You now operate a hot wallet | | Roundhouse | Settlement and index from one place | Smaller than CDP by volume | ## What actually differentiates them? Four things, in rough order of how much they will matter to you. **Chain coverage.** The protocol supports many chains; your facilitator supports some of them. This is the constraint that most often decides the question, and it is the first thing to check rather than the last. **Replay handling.** Security work published in 2026 found facilitator implementations where `verify` did not reserve the payment nonce, so one authorisation could unlock a resource more than once. Another class of issue let a party observing an authorisation submit it first and consume the nonce, breaking the legitimate settlement. Both were disclosed and fixed, and the lesson is to prefer a facilitator that documents its handling rather than one that does not mention it. **Pricing model.** Per-transaction fees, a spread on the settled amount, or free as a loss leader. Coinbase has published a free tier followed by a small per-transaction charge; check current figures directly rather than from an article. At these amounts the pricing rarely decides it, but a facilitator that is free today because it is buying distribution is a facilitator that may not be free later. **Failure behaviour.** What happens when it is slow, rate limited or down. This is the one that will actually hurt you, and it is the least documented across the board. > [!WARNING] > The failure mode to plan for is not an outage, which is obvious and alertable. It is silent delay: a settlement that will land in twenty minutes, on a request that needed an answer in two seconds. A seller that serves on verification and settles asynchronously has to decide what it does with the ones that never settle. ## Should you self-host? The honest answer is usually no, with specific exceptions. Self-hosting means running the reference implementation against your own RPC endpoint and a funded hot wallet. You take on nonce management, gas monitoring, reorg handling and the security of a wallet that signs continuously. In exchange you pay no fee and depend on nobody. That trade is worth it if you already operate on-chain infrastructure, if your volume makes per-transaction fees material, or if you have a reason not to put a third party in your payment path. [Should you run your own](https://roundhouseai.io/resources/run-your-own-x402-facilitator) goes through each case and what you take on. It is not worth it because you want to save a tenth of a cent on a thousand calls a day. Note the irony in the position: by removing the native-token requirement from your buyers you have taken it on yourself. The wallet that quietly runs out of gas is now the one you have to watch. [Who pays the gas](https://roundhouseai.io/resources/who-pays-gas-in-x402) sets out where that cost lands either way. ## How do you avoid a single point of failure? Advertise more than one. The `accepts` array can list several entries, and nothing stops two of them resolving to different facilitators on different chains. A client that cannot use the first can use the second. This costs you a second integration and a second reconciliation, and most sellers do not bother until the first outage. The ones for whom payment failure means lost revenue rather than a retry should bother sooner. ## Frequently asked questions ### Can I switch facilitators later? Yes, and it is a small change: the facilitator is behind your server, not in your published terms, unless your `accepts` entries name chains only one of them supports. Buyers do not need to know. ### Does the facilitator see my customers? It sees every payment authorisation, which includes payer addresses, amounts and the resource identifier. That is a meaningful amount of commercial information about your business, flowing to a third party. ### Can a facilitator steal a payment? Not the funds. The payee is inside the signed authorisation and cannot be altered. What it can do is decline to settle, settle late, or fail, which is why verification is not completion. ### Which facilitator is relaying most volume? Coinbase CDP by most measures through 2026, though the exact share differs by source and by whether transactions or dollars are counted. The live answer is in the settlement record rather than in anyone's announcement. ### Do I need a facilitator on every chain I accept? You need settlement capability on every chain you accept, which usually means a facilitator per chain. Coverage differs, so multi-chain sellers commonly run more than one. ## Where to check this yourself This is a question the settlement record answers directly. [/facilitators](https://roundhouseai.io/facilitators) attributes indexed settlements to the operator that relayed each one, so you can see current share rather than claimed share, along with the proportion that could not be attributed to any known operator. [/transactions](https://roundhouseai.io/transactions) lets you filter the raw record by route. --- Roundhouse indexes x402 settlements and ERC-8004 identities into one public record. - Every article: https://roundhouseai.io/resources.md - Every surface on this site: https://roundhouseai.io/llms.txt - The index, endpoints and schema: https://api.roundhouseai.io/v0 - A key of your own, $0.01 over x402, no account: https://api.roundhouseai.io/v0/test/x402 - Limits and the SQL surface: https://roundhouseai.io/docs/api