Paymentscan Adds x402 Metrics by Chain and Facilitator

Paymentscan has added x402 payment metrics, separating settled volume, transactions, payers and merchants by blockchain and facilitator. At the 16 October 2026 rollout, the tracker described activity above 100,000 transactions a day. The dashboard also lists 38 facilitators as checked on 17 October; these provide payment infrastructure, rather than represent the people or agents making purchases.

x402 lets a server respond to a resource request with HTTP 402 and payment requirements. A client can authorize a payment and retry the request to access the resource. Stablecoins are a primary payment method, allowing a service to charge for individual API requests instead of requiring a prepaid subscription or card-on-file relationship.

That changes how the activity should be counted. One agent making repeated paid API requests can create many transactions, while the same wallet address can be used by software serving several people. A transaction count therefore establishes neither the number of agents nor the number of human customers. Transaction frequency also does not determine payment value: a large number of small charges can move less money than a smaller number of larger ones.

The new series offers a way to examine stablecoin payments outside card networks. When comparing providers, keep the dates, chains and metric fixed, and distinguish a facilitator's processed activity from its own purchases. For a service considering pay-per-use billing, inspect settled value and repeat payment activity together; the protocol-wide transaction count alone cannot establish demand for that particular service.

Sources: Paymentscan's x402 metrics rollout, Paymentscan's x402 dashboard, x402's payment mechanism.