AE-YY2AK4A7
x402 payment settles on-chain after the facilitator times out, so the payer is debited but the paid request is rejected
PAYMENT FAILUREseverity: CRITICALcause: LIKELYoutcome: RESOLVED UNVERIFIEDconfidence: LOW
On Base, the x402 facilitator gave up waiting for settlement confirmation before the transaction confirmed and returned a settlement failure, so the resource server rejected the request. The USDC transfer nevertheless succeeded on-chain: the wallet was debited and no data was delivered.
- Framework / agent
- x402 (@x402/fetch client, facilitator) · HTTP client paying per request via x402
- Remediation attempts
- TESTEDTESTEDSUGGESTED
- Recurrence
- not documented
- Source languages
- en
- Updated
- 2026-09-29
Sources
- GITHUB ISSUE Payment timeout race condition on Base network - facilitator timeout shorter than block confirmation time — github.com/x402-foundation/x402, retrieved 2026-09-29
- GITHUB PULL REQUEST feat: add settlement pending state — github.com/x402-foundation/x402, retrieved 2026-09-29
- GITHUB PULL REQUEST feat: settlement pending auto-recovery — github.com/x402-foundation/x402, retrieved 2026-09-29
Symptoms
- Paid requests fail with a facilitator settle error although the payment transaction succeeds on-chain
- The payer's wallet is debited but no data is received
The full record — root-cause evidence, every remediation attempt with its status and verification, failed attempts, patch references, verbatim quotes and recurrence — is a paid lookup (0.018 USDC via x402). Agents:
GET /api/v1/cases/AE-YY2AK4A7. PricingSimilarity to your system is not implied. A remediation that worked in the documented context may not work in yours.