Choosing an x402 facilitator: what builders should check

Start with the service you need to deliver

A facilitator helps a seller verify and settle payment payloads. It is part of the payment infrastructure, while the seller remains responsible for the API response and the product experience. A directory entry is a useful starting point, but it does not replace an integration review. Choose infrastructure that matches your production requirements, rather than choosing only by a transaction leaderboard.

Match protocol, scheme, network and asset

Two services can both advertise x402 and still support different combinations. Check the protocol version, payment scheme, exact mainnet identifier and token contract or mint. Confirm the token decimals and authorization method. A facilitator’s public supported endpoint can help establish current capabilities. Testnet examples are useful during development, but they do not establish that the same configuration is available on mainnet.

Understand credentials and fees

Public discovery does not necessarily mean verification and settlement are anonymous. Some providers require merchant credentials, while others expose selected operations without an API key. Keep private credentials on your server. Ask how fees are collected, who pays network gas and what happens when an account reaches its quota. Avoid describing a paid service as free simply because the buyer does not submit the chain transaction directly.

Treat uncertain settlement as its own outcome

A successful verification is different from successful settlement. A transport timeout is also different from a confirmed rejection. The integration should preserve those distinctions. Keep request identifiers, receipts and transaction references, and document how to reconcile an authorization before retrying. A fallback provider must not settle the same authorization again merely because the first provider’s response did not arrive.

Separate infrastructure from seller metrics

A facilitator can process payments for many sellers, and a seller can use more than one facilitator. The submitting address, payer and receiving merchant can all be different. Compare measurements only when their attribution rules and time windows match. Operator tests can demonstrate an integration, but they should not be presented as independent buyer demand or customer revenue.

A practical review checklist

Before launch, confirm the supported configuration, credential setup, documented fees and receipt format. Run a small end-to-end integration test and inspect both the delivered response and the chain record. Test failure recovery as carefully as the happy path. Finally, keep the facilitator URL and support contact in the buyer guide so another developer can reproduce the integration without guessing.