Study of 267 x402 Servers Finds 69% Fail to Process Payments Due to Header Flaws
A production audit of 267 live x402 payment servers, conducted by researcher touchstone for Zambo, found that 175 hosts — about 69% — were unresponsive to the X-PAYMENT header used by most clients. The root cause is a spec ambiguity that left two header names, X-PAYMENT and PAYMENT-SIGNATURE, for the same concept, causing server implementations to diverge silently. A separate sweep of 150 hosts confirmed 93 servers read only PAYMENT-SIGNATURE, meaning valid payments were ignored and servers returned a 402 error as if no payment had been made. The report also flagged that servers generating a fresh nonce in each 402 challenge produce non-deterministic responses, making compliance testing unreliable and indistinguishable from payment failure. Developers recommend a one-line fix to read both headers and advocate for deterministic, nonce-free challenge payloads to improve interoperability and testability.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in