How long do x402 payments take to finalize?
8/26/2026, 1:55:07 AM · llm:mimo:mimo-v2.5
The dispatch, itemised.
Breaking down: "How long do x402 payments take to finalize?"
Identified 4 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 4/8 positive proposal(s): 4 cached + 0 fresh, predicting 4/4 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 (4/4); paid reading may proceed within the budget.
Highly relevant: directly measures x402 settlement latency on Arc, providing empirical data on finalization time. Cached and free, making it a top-priority reuse. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3, 4; 0 fetch USDC, 1 attention slot).
Directly answers the question with cross-protocol commentary on x402 timing. Cached and free, providing foundational overview. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3, 4; 0 fetch USDC, 1 attention slot).
Relevant for sub-claim 2: USDC onchain settlement speed (seconds) informs network-specific finalization. Cached and free. — selected for the claim-aware evidence portfolio (targets claims 2, 3; 0 fetch USDC, 1 attention slot).
Relevant for sub-claims 0 and 3: describes x402 as a payment rail, offering protocol context. Cached and free, though less specific on timing. — selected for the claim-aware evidence portfolio (targets claims 1, 4; 0 fetch USDC, 1 attention slot).
Relevant for sub-claim 2: idempotency keys affect reliability but not directly timing; tangential. Cached and 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.
Stripe Blog has high historical weight but this article is about Visa DCAP, not x402 timing. Marginal relevance. Cached and free. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
CoinDesk article on MUFG blockchain settlement provides general blockchain finality context but not x402-specific. Historical rep moderate. Cached and free. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
Gardening topic completely irrelevant to x402 payments.
Retro gaming hardware irrelevant.
Cointelegraph article on Solana slot time (350ms) directly addresses blockchain network latency, relevant for sub-claim 1 on network influence. Price low, high historical rep. BUY. — 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.
Decrypt article on Treasury stablecoin rules provides regulatory context affecting settlement processes (sub-claim 3). Good historical rep. Price low. BUY. — 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.
Vitalik Buterin on low-risk DeFi offers Ethereum consensus insights relevant to finalization (sub-claim 1). Premium source, but price low. BUY. — 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.
Simon Willison on AI model pricing tangentially relevant to agent economics but not x402 timing. Low direct value; SKIP to save budget. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Latent.Space on ontologies and AI agents discusses agent systems but not x402 payment finalization specifically. Low relevance; SKIP. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Hugging Face blog on token efficiency is AI/ML focused, not relevant to x402 payments.
Esoteric mythology completely irrelevant.
Token donor protocol in AI development is unrelated.
Coinbase fee updates from 2022 are outdated and irrelevant to x402 settlement timing. Historical rep zero; 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
Reused cached Stablecoin Ledger — Why USDC settles instantly onchain (free) — S3
Reused cached Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail (free) — S4
Attention budget is full at 4 source(s); no broader context will be purchased.
Final check — "x402 payments involve a specific duration from initiation to…": 100% assessed by S1, S2
Final check — "The finalization time of x402 payments is influenced by the …": 100% assessed by S1, S2
Final check — "Factors such as network congestion and transaction fee prior…": 0% assessed
Final check — "The finalization time for x402 payments may vary depending o…": 100% assessed by S1, S2
Final coverage assessment — The gathered sources provide direct information about the finalization time of x402 payments, including specific durations (e.g., 180ms, 15 seconds), the influence of underlying networks (e.g., Arc testnet vs. Ethereum L1), and factors like block times. The claims are well-covered, with multiple sources addressing different aspects.
Synthesizing a grounded answer from 4 source(s)…
⚖️ Sources disagreed on The specific duration for x402 payment finalization. — S1 Approximately 180 milliseconds on Arc testnet. vs S2 About 15 seconds, similar to Ethereum L1 block time. → trusted S1 (The claim in S1 provides specific, benchmarked latency data (median, p95) from a named network (Arc testnet), making it more precise and contextually grounded for a particular implementation. S2 describes a general case based on Ethereum L1 block time, which is less specific to a dedicated x402 infrastructure.)
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 — 3 sub-claims remain below the evidence threshold, 1 disagreement adjudicated.
Arc Settlement Benchmarks contributed 60% → reward $0.012
Web Payments Review contributed 40% → reward $0.008
Settled $0.012 citation reward → Arc Settlement Benchmarks (77eaac32-1…)
Settled $0.008 citation reward → Web Payments Review (05962607-d…)
Done. Spent $0.02 across 2 confirmed/simulated payment(s) to creators.
Arc Settlement Benchmarks
batched
Web Payments Review
batched
> ⚠ Low confidence — 3 sub-claims remain below the evidence threshold, 1 disagreement adjudicated within budget. Treat this as provisional.
The finalization time for x402 payments varies significantly depending on the underlying network and implementation. On Arc's testnet, x402 batched settlements finalize in roughly 180 milliseconds . However, in a different implementation where each payment is its own Ethereum L1 transaction, it takes about 15 seconds to settle . Therefore, the duration is not universal and depends on factors like network consensus and transaction batching.
Evidence ledger — quotes verified before rewards
x402 payments involve a specific duration from initiation to final settlement.
100%“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 of x402 payments is influenced by the underlying blockchain or network used.
0%No reward-qualifying evidence
Factors such as network congestion and transaction fee prioritization can affect the finalization duration of x402 payments.
0%No reward-qualifying evidence
The finalization time for x402 payments may vary depending on the specific implementation or protocol details of x402.
0%No reward-qualifying evidence
Footnotes — each one pays its author
- 1Measuring x402 settlement latency on ArcArc Settlement Benchmarks60%+$0.012
- 2How long do x402 payments take to finalize?Web Payments Review40%+$0.008
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.