How long do x402 payments take to finalize?
9/17/2026, 8:59:49 AM · llm:mimo:mimo-v2.5 + llm:deepseek:deepseek-v4-flash on 4 steps
The dispatch, itemised.
Breaking down: "How long do x402 payments take to finalize?"
Identified 2 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 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 directly measures x402 settlement latency/finality on Arc testnet — the single most on-point source for both the timing question (claim 0) and rail-dependent variation (claim 1). Already cached, so reuse free; top-tier topical fit despite mid reputation (36/100). — selected for the claim-aware evidence portfolio (targets claims 1, 2; 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 across x402 and similar rails — directly addresses claim 0 and the rail-comparison in claim 1. Cached, so free; lower reputation (15/100) warrants lower weight. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Agent Economy Weekly explains x402 as an inline HTTP 402 agent payment rail, giving protocol context relevant to how authorization/payment stages work (claim 0). Cached and free; decent citation history (53%). — 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 states USDC settles in seconds with finality on most L2s — useful for the stablecoin-rail branch of claim 1 (rail-dependent finalization). Cached, free; only an abstract so narrow. — 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 underpin x402/Gateway batched finality timing (claim 0) and rail differences (claim 1). Cached, free; tangential but relevant. — cached bytes are free, but this read does not clear the attention gate (EV 0.35, minimum 0.45, with a required claim target).
Stripe Blog has the best reputation here (54/100) but this specific post is about Visa DCAP interchange/authorization-rate optimization, not x402 finalization timing — no target claim is supported by the preview.
Cointelegraph piece is about Decta/OpenPayd stablecoin treasury settlement, not x402 payment finalization stages or timing; preview supports neither claim.
CoinDesk article concerns the dollar/euro onchain stablecoin gap, unrelated to x402 finalization timing or rail-stage distinctions.
Coinbase Overseer post is about real-time reconciliation of distributed state, not x402 payment finalization timing; no claim target supported.
Idempotency keys for retries is a general distributed-systems topic, not x402 finalization timing; preview supports neither claim.
Keryx first-party note is about buyer recovery/quoting a paid research job, not x402 settlement latency; full text but off-topic for these claims.
Ethereum Foundation post on AI agents triaging protocol code has no bearing on x402 payment finalization timing.
Latent.Space piece on ontologies/semantic web for agents is unrelated to x402 settlement timing; never cited on this subject.
Simon Willison post on Anthropic model adoption is metadata-only and off-topic for x402 finalization timing.
Hugging Face TutorMoments post on AI tutors is metadata-only and unrelated to x402 payment timing.
Vitalik post on low-risk DeFi is metadata-only and does not address x402 finalization stages or timing.
Decrypt piece on Robinhood Chain L2 is about tokenized assets, not x402 payment finalization timing; no claim supported.
Gardening article, wholly irrelevant to x402 payment finalization.
Retro console recapping article, wholly irrelevant to x402 payment finalization.
Esoteric Tree-of-Life article, wholly irrelevant to x402 payment finalization.
Conzit piece on India's UPI merchant-fee model concerns a different payment network and does not address x402 finalization timing.
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, as stated in the…": 50% covered by S1, S2 — S1 gives a concrete finalization figure for x402 batched settlements on Arc (~180ms median, p95 240ms) and notes sub-second finality, but does not distinguish authorization, confirmation, and settlement stages. S2 gives a conflicting ~15s settlement figure tied to Ethereum L1 block time, also without stage distinctions. Together they provide partial timing answers but no explicit authorization/confirmation/settlement breakdown.
Sub-claim "Does the finalization time for x402 payments vary depending …": 30% covered by S1, S2 — S1 contrasts Arc batched settlement (sub-second, not block-time-bound) with Ethereum L1, and S2 describes an Ethereum L1-like ~15s settlement, giving topical context that timing may differ by rail. However, no explicit comparison across Lightning Network, on-chain, or stablecoin rails is provided, so the requested rail-by-rail differences are not answered.
Coverage is below 0.5 for the rail-variation sub-claim and only partial for the stage-distinction sub-claim. The Stablecoin Ledger source ($0.003) directly addresses stablecoin settlement finality, and the Onchain Micropayments Digest ($0.005) covers batched settlement economics/timing; both fit the $0.02 remaining budget and are the most relevant affordable gaps. Other skipped sources are off-topic or only tangentially related.
Filling gap — buying Stablecoin Ledger — Why USDC settles instantly onchain ($0.003)…
Paid $0.003 to Stablecoin Ledger — Why USDC settles instantly onchain (settled 69f34b85-8…) — S3
Filling gap — buying Onchain Micropayments Digest — Nanopayments and the $0.000001 floor ($0.005)…
Paid $0.005 to Onchain Micropayments Digest — Nanopayments and the $0.000001 floor (settled bccc0fbc-6…) — S4
Final check — "How long do x402 payments take to finalize, as stated in the…": 60% assessed by S1, S2
Final check — "Does the finalization time for x402 payments vary depending …": 20% assessed by S1
Final coverage assessment — S1 directly answers the first sub-claim with a specific finalization time (~180 ms median, p95 240 ms) for x402 batched settlements on Arc, and distinguishes confirmation from block-time-bound L1 transactions. S2 gives a conflicting ~15 second settlement estimate but is framed as a reading/view, not protocol documentation, and does not distinguish authorization/confirmation/settlement stages. S3 and S4 provide only general stablecoin or nanopayment context, not x402 finalization timing. For the second sub-claim, no source compares finalization times across payment rails such as Lightning, on-chain, or stablecoin; S1 mentions Arc/Gateway batching and Ethereum L1 contrast, but does not provide rail-by-rail differences for x402. The assessment does not establish a complete supported answer for every requested part.
Synthesizing a grounded answer from 4 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
⚖️ Sources disagreed on x402 payment finalization time — S1 x402 batched settlements finalize in roughly 180ms (median 178ms, p95 240ms) via Arc BFT consensus and Gateway batching, not block-time-bound. vs S2 x402 payments take 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 provides specific measured statistics (median 178ms, p95 240ms across thousands of calls) and is internally consistent with its described BFT/Gateway batching architecture, whereas S2 offers only an approximate figure based on an Ethereum-L1 per-transaction model that S1 explicitly says does not apply.)
Verified — S1 supports claim 1 at 80%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”
Verified — S1 supports claim 1 at 70%: “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…”
Verified — S2 supports claim 1 at 80%: “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…”
Below reward gate — S3 supports claim 2 at 20%: “USDC is a fully-reserved dollar stablecoin that settles peer-to-peer onchain in seconds.”
Below reward gate — S4 supports claim 2 at 20%: “Nanopayments push the minimum economical payment to about $0.000001 by signing off-chain authorizations and settling them in batches.”
Rejected 0 invalid evidence span(s) and 2 unsupported citation marker(s); rejected markers cannot receive citation rewards.
Drafted answer citing 2 source(s)
Confidence: Low — 1 sub-claim remains below the evidence threshold.
Arc Settlement Benchmarks contributed 50% → reward $0.01
Web Payments Review contributed 50% → reward $0.01
Settled $0.01 citation reward → Arc Settlement Benchmarks (92703495-a…)
Settled $0.01 citation reward → Web Payments Review (2336b0a1-d…)
Done. Spent $0.028 across 4 confirmed/simulated payment(s) to creators.
Arc Settlement Benchmarks
batched
Web Payments Review
batched
> ⚠ Low confidence — 1 sub-claim remains below the evidence threshold within budget. Treat this as provisional.
The sources disagree on how long x402 payments take to finalize, and neither fully distinguishes authorization, confirmation, and settlement stages.
For the overall finalization time (claimIndex 0): One source reports that x402 batched settlements on Arc testnet finalize in roughly 180 milliseconds, with a measured median of 178ms and p95 of 240ms . The same source attributes this to Arc's BFT consensus delivering sub-second finality, so a Gateway-batched payment confirms in well under a quarter second and is not block-time-bound like an Ethereum L1 transaction . A second source instead states that 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 . These two figures are irreconcilable as stated. The 180ms figure is more specific (measured median and p95 across thousands of calls) and internally consistent with the described BFT/Gateway batching architecture, so it is the more trustworthy account; the 15-second figure appears to assume a per-transaction on-chain model that the Arc source explicitly says does not apply. Neither source breaks the timeline into separate authorization, confirmation, and settlement stages, so that part of the question is unanswered.
On whether finalization time varies by payment rail (claimIndex 1): The sources do not directly compare x402 finalization across named rails such as Lightning Network, on-chain, or stablecoin. The Arc source contrasts Gateway-batched settlement with Ethereum L1 block-time-bound transactions, implying a rail-dependent difference , and the second source frames x402 as Ethereum-L1-like at ~15 seconds . A third source states that USDC settles peer-to-peer onchain in seconds and that instant final settlement lets an agent pay and immediately receive a resource without counterparty risk, but it does not mention x402 or quantify a rail comparison. A fourth source describes off-chain authorizations settled in batches for nanopayments, which is consistent with the batching model in but gives no finalization timing. No source provides a Lightning Network figure or a structured rail-by-rail comparison, so that portion of the question remains unanswered.
Evidence ledger — quotes verified before rewards
How long do x402 payments take to finalize, as stated in the protocol specification or implementation documentation, including any distinction between authorization, confirmation, and settlement stages
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
“Arc's BFT consensus delivers sub-second finality, so a Gateway-batched payment confirms in well under a quarter second — it is not block-time-bound the way an Ethereum L1 transaction is.” [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?
Does the finalization time for x402 payments vary depending on the underlying payment rail (e.g., Lightning Network, on-chain, stablecoin) and if so, what are the differences
0%No reward-qualifying evidence
Footnotes — each one pays its author
- 1Measuring x402 settlement latency on ArcArc Settlement Benchmarks50%+$0.01
- 2How long do x402 payments take to finalize?Web Payments Review50%+$0.01
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.