{
  "id": 14416453,
  "title": "I sent an empty-wallet payment to 4,256 x402 routes. 38 sellers told me their facilitator was down.",
  "url": "https://urgent.news/2026/10/14/i-sent-an-empty-wallet-payment-to-4-256-x402-routes-38-sellers-told",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-14T09:38:29.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/lowkeybuilds/i-sent-an-empty-wallet-payment-to-4256-x402-routes-38-sellers-told-me-their-facilitator-was-down-3i1e"
  },
  "original_language": "en",
  "account": "On October 14, 2026, a report was issued about an experiment involving 4,256 payment routes to various sellers. The experiment involved sending an EIP-3009 authorization through a freshly created wallet with no USDC. All Base sellers in the Coinbase CDP Bazaar who had transacted with at least two different payers within the last 30 days were included in the test. Each of their routes received one payment that could not be successful due to the empty wallet.\n\nOut of the 4,256 routes tested, 2,262 were payable, with 935 of those rejecting the payment solely for lack of balance. A total of 916 routes did not respond within 20 seconds, 455 had other reasons for rejection, and 306 were rejected due to input validation errors. Additionally, 91 routes reported the payment failure as a facilitator outage.\n\nThe report highlights the issue of sellers providing different responses when confronted with an empty-wallet payment. Some sellers replied with HTTP 400, 502, or 503 errors, indicating that their facilitator was unavailable. Others returned generic error messages or did not respond at all. The report emphasizes that these responses are not necessarily indicative of a defective route but rather an incomplete understanding of how to handle such payments.\n\nThe fix suggested in the report involves fetching the facilitator's verification endpoint with a POST request and handling the JSON response appropriately. If the verification fails due to an empty wallet, the route should respond with a 402 status code and include the reason for rejection. This approach ensures that buyers are informed about the payment's status and that sellers can better manage their interactions with buyers who may be facing balance issues.",
  "summary": "Answering HTTP 402 is not the same as being payable. On 2026-10-14 I took every Base seller in the Coinbase CDP Bazaar with at least two distinct payers in the last 30 days and sent each of their routes one payment that cannot succeed: an EIP-3009 authorization signed by a brand-new wallet holding zero USDC, through the reference @x402/fetch client. No money can move. A healthy route rejects it…",
  "key_points": [
    "4,256 payment routes tested with empty-wallet authorization",
    "91 routes reported facilitator outage due to empty wallet",
    "Suggested fix involves fetching facilitator verification endpoint"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}