How long do x402 payments take to finalize?
9/16/2026, 2:49:50 AM · llm:deepseek:deepseek-v4-flash (fallback from llm:mimo:mimo-v2.5)
The dispatch, itemised.
Breaking down: "How long do x402 payments take to finalize?"
Identified 1 research target(s) to investigate; these are not established facts
Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.
Discovered 21 verified source(s)
Recalled 60 past runs on this subject — how these sources performed when they were available.
ERC-8004 reputation loaded — composite scores on this subject.
Claim-aware portfolio selected 2/3 positive proposal(s): 2 cached + 0 fresh, predicting 1/1 claim(s) above the evidence floor with $0.000000/$0.020000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (1/1); paid reading may proceed within the budget.
Arc Settlement Benchmarks directly measures x402 settlement latency/finality on Arc testnet — the exact question. Highest topical precision, cached so free to reuse, and it's the most-cited source on this subject (18/35 runs). — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).
Web Payments Review's article is literally titled 'How long do x402 payments take to finalize?' and previews end-to-end settlement timing for x402 — a direct match, cached and free. — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).
Agent Economy Weekly explains the x402 rail (server demands payment, agent pays inline), giving useful context on the payment flow that determines finalization timing. Cached, and a solid past citer (10/19). — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.020000 fetch-budget caps, so this proposal stays unspent.
Stablecoin Ledger notes USDC transfers settle in seconds with finality on most L2s — a relevant lower-bound proxy for x402 onchain settlement, though not x402-specific. Cached and cheap. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
Onchain Micropayments Digest covers batched settlement primitives, which is the mechanism x402 uses and a factor in finalization latency. Cached; weaker topical fit than the benchmark sources. — cached bytes are free, but this read does not clear the attention gate (EV 0.35, minimum 0.45, with a required claim target).
Keryx first-party engineering note is about buyer recovery and citation rewards, not x402 finalization timing; full text but off-topic for claim 0.
Idempotency keys for retries is a reliability topic, not settlement latency; no bearing on how long x402 payments take to finalize.
Gardening content, entirely unrelated to x402 payment finalization.
Retro console recapping, unrelated to payments or settlement.
Stripe agent integrations post is about developer tooling, not x402 finalization timing; no direct answer to claim 0.
Ethereum Foundation post on AI agents triaging protocol code; no settlement-latency content.
ECB merchant crypto-acceptance survey; about adoption, not x402 finalization time.
Latent.Space on ontologies/semantic web for agents; no payment settlement timing.
Simon Willison post on Anthropic model adoption; metadata-only and off-topic.
Hugging Face AI-tutor post; metadata-only and unrelated to x402 settlement.
Vitalik on low-risk DeFi; metadata-only, no x402 finalization timing.
Coinbase asset-listing risk post; unrelated to payment finalization latency.
Decrypt on Russia's crypto law; regulatory news, no x402 timing.
CoinDesk on dollar/euro onchain gap; stablecoin market structure, not settlement latency.
Esoteric mysticism content; irrelevant.
Tom Holland film-promotion piece; irrelevant.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (free) — S1
Reused cached Web Payments Review — How long do x402 payments take to finalize? (free) — S2
Sub-claim "How long do x402 payments take to finalize?": 70% covered by S1 — S1 directly answers with a concrete finalization time for x402 batched settlements on Arc: roughly 180 ms median (178 ms median, p95 240 ms), sub-second finality, not block-time-bound. S2 gives a conflicting ~15 s figure but is framed as a reading/view rather than a measurement, so it does not add a reliable answer. The core question is answered by S1, but the answer is specific to Arc/Gateway-batched x402 and does not establish a general x402 finalization time across other chains or non-batched flows, leaving a small scope gap.
Coverage is adequate (0.7) because S1 explicitly provides x402 finalization latency. No skipped source preview clearly promises a better or more general x402 finalization measurement; the closest candidates (Stablecoin Ledger on USDC L2 finality, Onchain Micropayments Digest on batched settlement) address adjacent topics rather than x402 finalization directly, so buying them is not justified under the remaining budget.
Final check — "How long do x402 payments take to finalize?": 90% assessed by S1
Final coverage assessment — The single sub-claim asks how long x402 payments take to finalize. S1 directly answers with a measured latency: roughly 180 ms median (178 ms median, p95 240 ms) for batched x402 settlements on Arc, with sub-second BFT finality. S2 offers a conflicting estimate of about 15 seconds, but it is framed as an opinion ('In our reading') and is not a direct measurement. The requested question is answered by S1 with concrete finalization timing, so coverage is high. No requested part remains missing.
Synthesizing a grounded answer from 2 source(s)…
Evidence relevance review unavailable; keeping the draft with citation rewards withheld.
⚖️ Sources disagreed on How long x402 payments take to finalize — S1 Batched x402 settlements on Arc finalize in roughly 180ms (median 178ms, p95 240ms), with sub-second BFT finality and no block-time dependency. vs S2 An x402 payment takes about 15 seconds to settle, similar to Ethereum L1 block time, because each payment is its own transaction waiting to be mined. → reported preference: S1 (S1 reports specific measured statistics (median 178ms, p95 240ms) from thousands of submitBatch calls on a named network (Arc testnet), while S2 is explicitly framed as a reading/view rather than a measurement.)
Below reward gate — S1 supports claim 1 at 0%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”
Below reward gate — S1 supports claim 1 at 0%: “Arc's BFT consensus delivers sub-second finality, so a Gateway-batched payment confirms in well under a quarter second — it is not block-tim…”
Below reward gate — S2 supports claim 1 at 0%: “In our reading, an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is its own tran…”
Rejected 0 invalid evidence span(s) and 2 unsupported citation marker(s); rejected markers cannot receive citation rewards.
No citation passed the evidence gate — the $0.020000 citation pool stays unspent; settled access tolls still stand.
Drafted answer citing 0 source(s)
Confidence: Low — no citation passed the evidence gate.
Done. Spent $0 across 0 confirmed/simulated payment(s) to creators.
Payouts to cited creators appear here.
x402 payments can finalize in roughly 180 milliseconds: across thousands of submitBatch calls on Arc testnet, batched settlements finalized with a measured median of 178ms and p95 of 240ms. Arc's BFT consensus delivers sub-second finality, so a Gateway-batched payment confirms in well under a quarter second and is not block-time-bound the way an Ethereum L1 transaction is.
A conflicting view holds that an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is treated as its own transaction waiting to be mined into a block. The two sources disagree on the underlying model: S1 describes batched settlements on Arc with sub-second finality, while S2 describes per-payment L1-style mining. The trusted figure is the Arc benchmark (~180ms), because it reports specific measured statistics (median and p95) from thousands of calls on a named network, whereas S2 is explicitly framed as "our reading" and a "view" rather than a measurement.
Evidence ledger — quotes verified before rewards
How long do x402 payments take to finalize?
0%No reward-qualifying evidence
Portable research receipt
Take the evidence trail with you
One deterministic JSON bundle binds the answer, visible decisions, exact article versions, claim evidence and a Circle-settlement snapshot under SHA-256. Retain the digest to detect later changes; the self-check is not a publisher or Keryx signature.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.