No timeout on /verify (hangs indefinitely)

Quirk · GET /api/x402/facilitator-no-verify-timeout · Facilitator Dependency

The merchant's /verify fetch has no AbortController or timeout; when the facilitator is slow the handler ties up the connection forever.

Explanation

The merchant's /verify fetch is issued with no AbortController or AbortSignal.timeout(). When the facilitator is slow or stalled, the Node.js event loop continues but this handler never resolves, tying up the HTTP connection indefinitely. The merchant must wrap every outbound facilitator call with a timeout (e.g., AbortSignal.timeout(5000)) and return a 504 or 503 if it fires.

What to watch

The request hangs — no response arrives. You will need to Ctrl+C or wait for your client's own timeout to fire.

Facilitator

The facilitator is mocked for this scenario — its response is simulated, so no live Radius testnet settlement occurs.

Metadata

Back to catalog