How long do x402 payments take to finalize?
9/1/2026, 1:33:45 AM · llm:mimo:mimo-v2.5
The dispatch, itemised.
Breaking down: "How long do x402 payments take to finalize?"
Identified 2 sub-claim(s) to support
Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.
Discovered 20 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/5 positive proposal(s): 2 cached + 0 fresh, predicting 2/2 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 (2/2); paid reading may proceed within the budget.
Arc Settlement Benchmarks is the most directly relevant cached source, providing lab-measured latency and finality data for x402 payments on Arc. High citation rate (58%) and reputation on this subject; it's the best free option for answering the question. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Web Payments Review's article title exactly matches the question, and it's cached. Despite lower historical citation rate (39%), its direct topical focus and free reuse make it a valuable secondary source to complement Arc Settlement Benchmarks. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Stablecoin Ledger's cached article on USDC's instant on-chain settlement provides context on fast stablecoin payments, relevant to x402's use of USDC. Decent citation rate (36%) and reputation, and it's free. — 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.
The Coinbase Blog's cached article on real-time reconciliation touches on transaction synchronization, which is tangentially related to settlement timing. However, it has zero citations on this subject, so it's low priority. — 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.
Agent Economy Weekly's cached article explains x402 as an agent payment rail, but it focuses on the mechanism rather than settlement timing. Low historical citation rate (14%) and reputation, but free and somewhat relevant. — 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.
Cointelegraph's cached article on crypto payments among euro merchants is not about x402 settlement timing, though it mentions payment acceptance. High reputation overall, but this specific article is off-topic and low relevance. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Decrypt's cached article on Russia's crypto law is about trading vs. payments regulation, not settlement timing. It has good reputation, but this article is not useful for answering the question. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
CoinDesk's cached article discusses stablecoins and tokenization with settlement cycles, but it's a general market analysis. Low historical citation rate (28%) and reputation, and only marginally relevant to x402 finalization time. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
Distributed Systems Notes on idempotency keys is about preventing double-spends, not settlement timing. Zero citations on this subject, and only weakly related. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Stripe Blog's cached article is about solo founding traits, not payments or x402. Despite Stripe's high reputation on payments, this article is irrelevant to the question. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Latent.Space article on AI agents and ontologies is about semantic web, not x402 payments or settlement timing. Completely off-topic and not cached, so SKIP.
Simon Willison's Weblog on Anthropic's AI model is about LLM tool adoption, not payments. Not cached and irrelevant, so SKIP.
Hugging Face article on AI tutors is about machine learning, not payments. Not cached and irrelevant, so SKIP.
Vitalik Buterin's article on low-risk DeFi is about Ethereum use cases, not x402 settlement timing. Not cached and only loosely related, so SKIP.
Inner Axiom article is esoteric philosophy, not payments or technology. Not cached and completely irrelevant, so SKIP.
Conzit Labs article on a Python invisibility cloak is about computer vision, not payments. Not cached and irrelevant, so SKIP.
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 "x402 payments require a certain amount of time to finalize": 75% covered by S1, S2 — Both sources provide explicit finalization times for x402 payments, confirming that finalization is time-bound. S1 reports ~180ms on Arc testnet, while S2 claims ~15 seconds on Ethereum L1. The conflicting data creates a moderate understanding but not a definitive single answer.
Sub-claim "The finalization time for x402 payments is a measurable dura…": 85% covered by S1, S2 — Both sources treat finalization as a measurable metric, providing numerical estimates (178ms median, p95 240ms for S1; 15 seconds for S2). The claim is well supported, though the exact value depends on the implementation.
Coverage is adequate for both sub-claims, with each receiving supporting data from at least two sources. The minor conflict in times (180ms vs. 15s) reflects different contexts (Arc testnet vs. Ethereum L1) and does not require additional purchases to resolve. The remaining budget of $0.02 is sufficient for one low-cost source, but none of the skipped sources are directly relevant to x402 finalization times, so no purchases are needed.
Final check — "x402 payments require a certain amount of time to finalize": 60% assessed by S1, S2
Final check — "The finalization time for x402 payments is a measurable dura…": 100% assessed by S1, S2
Final coverage assessment — The gathered sources present contradictory information about x402 payment finalization time: one source (S1) indicates ~180ms finality via Arc's BFT consensus, while another source (S2) claims ~15 seconds similar to Ethereum L1 block time. This creates ambiguity about the actual finalization duration. More evidence is needed to reconcile these conflicting claims or understand the context under which each applies.
Synthesizing a grounded answer from 2 source(s)…
⚖️ Sources disagreed on The finalization time for x402 payments — S1 Sub-second, roughly 180ms on Arc testnet. vs S2 About 15 seconds on Ethereum L1. → trusted S1 (S1 provides specific, quantitative benchmark data from a testnet, while S2 presents a general reading about Ethereum L1. The specificity of the measured latency in S1 makes it more reliable for its stated context.)
Verified — S1 supports claim 1 at 100%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”
Verified — S2 supports claim 1 at 100%: “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…”
Drafted answer citing 2 source(s)
Confidence: Low — 1 sub-claim remain below the evidence threshold, 1 disagreement adjudicated.
Arc Settlement Benchmarks contributed 55% → reward $0.011
Web Payments Review contributed 45% → reward $0.009
Settled $0.011 citation reward → Arc Settlement Benchmarks (45602078-8…)
Settled $0.009 citation reward → Web Payments Review (1225be50-1…)
Done. Spent $0.02 across 2 confirmed/simulated payment(s) to creators.
Arc Settlement Benchmarks
batched
Web Payments Review
batched
> ⚠ Low confidence — 1 sub-claim remain below the evidence threshold, 1 disagreement adjudicated within budget. Treat this as provisional.
The finalization time for x402 payments varies by implementation. On Arc's testnet, x402 batched settlements finalize in roughly 180 milliseconds . In contrast, an x402 payment on Ethereum L1 can take about 15 seconds, similar to the block time .
Evidence ledger — quotes verified before rewards
x402 payments require a certain amount of time to finalize
60%“Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms).” [S1] Measuring x402 settlement latency on Arc
“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 transaction waiting to be mined into a block.” [S2] How long do x402 payments take to finalize?
The finalization time for x402 payments is a measurable duration
0%No reward-qualifying evidence
Footnotes — each one pays its author
- 1Measuring x402 settlement latency on ArcArc Settlement Benchmarks55%+$0.011
- 2How long do x402 payments take to finalize?Web Payments Review45%+$0.009
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.
Exact receipt still current
2 exact cited article versions still match Keryx's current index.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.