How long do x402 payments take to finalize?

Archived dispatch

Lowconfidence— Contains synthetic demo material; its measurements cannot support factual conclusions.

9/13/2026, 11:22:27 AM · llm:mimo:mimo-v2.5

§ IIThe reading2 cited

Lowconfidence— Contains synthetic demo material; its measurements cannot support factual conclusions.deep researchpreview plan 1/1 claimsportfolio 2/4 · evidence 100%

Illustrative demo content: synthetic sources and measurements are not factual research evidence. Source provenance and payment status are separate; inspect the receipt for settled, pending or simulated payments. Settlement does not authenticate a source's claims.

The typical processing time for an x402 payment to reach final settlement depends on the implementation. On Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds . In contrast, an x402 payment as its own transaction on Ethereum L1 takes about 15 seconds to settle, similar to an Ethereum L1 block time .

Evidence ledger — recorded source excerpts

Research targets are unverified topics. Coverage is an estimate of excerpt support, not proof of entailment, factual truth or a complete answer.

Requested topic (unverified): “What is the typical processing time for an x402 payment to reach final settlement from initiation?”
0% estimated
No qualifying excerpt recorded

No inspectable non-demo excerpts are recorded for source inspection.

Research evidence matrix

Compare unverified research targets with cited sources and inspect recorded excerpts. An empty cell means no inspectable excerpt was recorded; it does not establish whether a claim is true, false, or disputed. Coverage and agent confidence do not prove entailment, measured accuracy or complete synthesis.

Research target by cited source evidence matrix
Research target (unverified)	Inspection status	[S1] Measuring x402 settlement latency on ArcPublication: Arc Settlement BenchmarksPublished: Not recorded	[S2] How long do x402 payments take to finalize?Publication: Web Payments ReviewPublished: Not recorded
What is the typical processing time for an x402 payment to reach final settlement from initiation?	Illustrative demo excerpt	Inspect 1 excerpt Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms).	Inspect 1 excerpt 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.

Reference export

2 article references. Recorded titles, links and dates; observed scholarly records also include supplied authors, DOI and journal metadata with read limits. Review metadata before using in a paper. Import RIS into Zotero with File → Import.

Cited sources and references

1Measuring x402 settlement latency on ArcArc Settlement BenchmarksSynthetic demo content ? illustrative only50%$0.01 planned
2How long do x402 payments take to finalize?Web Payments ReviewSynthetic demo content ? illustrative only50%$0.01 planned

Spent$0.02

To creators100%

Decisions0 bought · 2 cached · 15 skipped

llm:mimo:mimo-v2.5Arc Testnet · historical

Decision log · 44 steps

§ IThe decision$0.02 settled / $0.04

50%$0.02 under cap

Decompose

Breaking down: "How long do x402 payments take to finalize?"

Decompose

Identified 1 research target(s) to investigate; these are not established facts

Decompose

Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.

Discover

Discovered 21 verified source(s)

Discover

Recalled 60 past runs on this subject — how these sources performed when they were available.

Discover

ERC-8004 reputation loaded — composite scores on this subject.

Pre-check

Claim-aware portfolio selected 2/4 positive proposal(s): 2 cached + 0 fresh, predicting 1/1 claim(s) above the evidence floor with $0.000000/$0.020000 fetch USDC reserved.

Pre-check

Free-preview pre-check maps an actionable source to every sub-claim (1/1); paid reading may proceed within the budget.

DecideCACHE

Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc$0.003 · EV 90%

Arc Settlement Benchmarks directly measures x402 settlement latency and finality on Arc testnet, which is the core of the question. It has a strong citation history (56% on this subject) and is already cached. Perfect match for claim 0. — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).

DecideCACHE

Web Payments Review — How long do x402 payments take to finalize?$0.002 · EV 85%

Web Payments Review article title exactly matches the question and the preview indicates it covers end-to-end settlement timing for x402. Already cached and has a decent citation history (39% on this subject). Provides direct, general overview for claim 0. — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).

DecideSKIP

Stablecoin Ledger — Why USDC settles instantly onchain$0.003 · EV 60%

Stablecoin Ledger explains USDC instant settlement on L2s, which is relevant background for understanding x402 finality (likely uses stablecoins). Already cached, but only provides context, not specific x402 timing. Moderate relevance for claim 0. — 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.

DecideSKIP

Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail$0.004 · EV 50%

Agent Economy Weekly describes x402 as an agent payment rail, which confirms its existence and purpose. Already cached. The preview doesn't mention timing, but the article likely covers operational details. Provides supplementary context for claim 0. — 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.

DecideSKIP

Cointelegraph.com News — Crypto payments barely register among euro area merchants, ECB finds$0.002 · EV 10%

Cointelegraph article covers crypto payment adoption stats, not x402 settlement mechanics or timing. The preview discusses ECB findings on merchant acceptance. Not relevant to claim 0. Better sources available.

DecideSKIP

Decrypt — Putin Signs Russia's First Crypto Law: Trading Is Legal, Payments Stay Banned$0.002 · EV 10%

Decrypt article covers Russian crypto law, not x402 settlement timing. The preview mentions trading legality and payment bans. No relevance to the technical question of finalization time for claim 0.

DecideSKIP

CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data — Crypto Long & Short: Inside the 300-to-1 onchain gap between the dollar and euro$0.002 · EV 10%

CoinDesk article discusses onchain gaps between dollar and euro stablecoins, not x402 settlement latency. The preview focuses on euro vs. dollar adoption. Not directly helpful for claim 0.

DecideSKIP

The Coinbase Blog - Medium — Real-time reconciliation with Overseer$0.003 · EV 10%

Coinbase Blog article is about internal system reconciliation, not x402 payment finalization. The preview discusses distributed systems synchronization. While technical, it's not specific to x402 timing for claim 0.

DecideSKIP

Garden & Soil Monthly — Building a no-dig raised bed$0.002 · EV 0%

Gardening article is completely unrelated to payments or x402. No relevance whatsoever for claim 0.

DecideSKIP

Retro Game Hardware — Recapping a 1990s console$0.002 · EV 0%

Retro gaming hardware article is irrelevant to x402 payments or settlement timing. No connection to claim 0.

DecideSKIP

Stripe Blog — Solo founding is at an all-time high: Top performers have these traits in common$0.002 · EV 10%

Stripe Blog article is about solo founding traits, not payment processing times. The preview discusses founder revenue statistics. Not relevant to x402 finality for claim 0.

DecideSKIP

Conzit Labs — India's UPI Sees Shift Towards Sustainable Payment Model$0.002 · EV 10%

Conzit Labs article covers India's UPI payment model sustainability, not x402 settlement timing. The preview discusses merchant fees. Not helpful for claim 0.

DecideSKIP

Simon Willison's Weblog — Anthropic’s best AI model struggles to attract users as cheaper tools thrive$0.003 · EV 10%

Simon Willison's Weblog article is about AI model usage trends, not payments. The preview discusses Anthropic's model adoption. No relevance to claim 0.

DecideSKIP

Hugging Face - Blog — TutorMoments: Do AI tutors know when to help and when to hold back?$0.003 · EV 10%

Hugging Face blog article is about AI tutoring systems, not x402 payments. The preview discusses when AI tutors should help. No connection to claim 0.

DecideSKIP

Vitalik Buterin's website — Obfuscation: building the final boss of cryptography (Part I)$0.004 · EV 10%

Vitalik Buterin's website article is about cryptographic obfuscation, not x402 payment finalization. The preview mentions 'final boss of cryptography' but it's not about settlement timing. Not directly relevant for claim 0.

DecideSKIP

Inner Axiom — The Codex — The Journey of the Soul$0.002 · EV 0%

Inner Axiom article is about esoteric cosmology, completely unrelated to x402 payments. No relevance for claim 0.

DecideSKIP

Keryx Engineering (first-party) — Recovering a Keryx paid research job$0.002 · EV 40%

Keryx Engineering first-party article covers buyer recovery for Keryx paid research jobs, which might touch on x402 payment flows. Already cached. The preview doesn't mention settlement timing specifically, but could provide operational context. Low confidence for claim 0. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).

Fetch

Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)

Fetch

Reused cached Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (free) — S1

Fetch

Reused cached Web Payments Review — How long do x402 payments take to finalize? (free) — S2

Re-evaluate

Sub-claim "What is the typical processing time for an x402 payment to r…": 50% covered by S1, S2 — The gathered sources provide two directly conflicting claims about x402 settlement time: S1 states batched settlements finalize in roughly 180 ms on Arc testnet, while S2 claims about 15 seconds similar to Ethereum L1 block time. The question asks for 'typical processing time' without specifying a chain or implementation, so both are relevant but inconsistent. The content partially answers the question by providing specific numbers, but the conflict and lack of context about which scenario is typical for real-world x402 usage leaves the answer ambiguous. No other source in the skipped list appears directly relevant to x402 payment finalization timing; most are about general crypto news, gardening, or unrelated topics. The skipped sources' previews do not indicate they address x402 settlement latency. Therefore, coverage is partial (0.5) due to conflicting information and insufficient context to resolve it, and buying more sources is unlikely to improve coverage given the budget and available previews.

Re-evaluate

The two gathered sources provide conflicting answers to the question (180 ms vs. 15 seconds), making the coverage ambiguous and partial. However, the skipped sources' previews do not suggest they contain relevant information about x402 payment finalization times; most are about unrelated topics like gardening, console repair, or general crypto news. Buying any of them would likely not resolve the conflict or add new specific data on x402 latency. The remaining budget is $0.02, but no skipped source appears cost-effective for filling this gap. Thus, no further purchases are recommended.

Sufficiency

Final check — "What is the typical processing time for an x402 payment to r…": 100% assessed by S1, S2

Sufficiency

Final coverage assessment — The sub-claim asks for the typical processing time for an x402 payment to reach final settlement from initiation. Two sources provide direct, but contradictory, answers. S1 reports that x402 batched settlements finalize in roughly 180 ms on Arc testnet. S2 reports that an x402 payment takes about 15 seconds to settle, similar to Ethereum L1 block time. Both answers are explicitly supported by their respective sources. The requested information (typical processing time) is covered by both sources, albeit with conflicting data, which does not change the coverage score. There are no other requested parts missing.

Synthesize

Synthesizing a grounded answer from 2 source(s)…

Evidence

Relevance review returned; only checked excerpts can retain support, and review cannot raise it.

Adjudicate

⚖️ Sources disagreed on Finalization time for an x402 payment — S1 On Arc testnet, batched settlements finalize in roughly 180 milliseconds. vs S2 An x402 payment takes about 15 seconds to settle on Ethereum L1. → reported preference: S1 (S1 provides specific, measured data from Arc testnet, while S2 presents a generalized view for Ethereum L1. The question asks for typical time, and S1's data is more precise for a specific, described system.)

Evidence

Verified — S1 supports claim 1 at 90%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”

Evidence

Verified — S2 supports claim 1 at 90%: “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…”

Synthesize

Drafted answer citing 2 source(s)

Verdict

Confidence: Moderate — source preferences are explained, but conflicting evidence limits confidence.

Attribute

Arc Settlement Benchmarks contributed 50% → reward $0.01

Attribute

Web Payments Review contributed 50% → reward $0.01

Settle

Settled $0.01 citation reward → Arc Settlement Benchmarks (e5377880-3…)

Settle

Settled $0.01 citation reward → Web Payments Review (0d946bbc-c…)

Done

Done. Spent $0.02 across 2 confirmed/simulated payment(s) to creators.

Read checkpoints

Read checkpoint evidence is unavailable for this report. Historical, private and unsupported native runs are not reconstructed.

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.

View JSON ↗Download

Recorded purchase outcomes

Did the exact article versions bought for this answer appear in its citations? This view scores retained BUY decisions against payment observations recorded in the same dispatch trace.

Recorded settlement bookkeeping only; Circle and chain settlement have not been independently rechecked here.

This is a partial retained trace sample, not a full payment ledger. An absent matching payment does not prove that no payment occurred; excluded and unconfirmed costs remain unknown.

Recorded network: eip155:5042002
Dispatch recorded at: 2026-09-13T04:22:27.258Z

Frozen testnet archive, captured 2026-10-03T00:26:18.665Z. This is historical testnet evidence, separate from current mainnet activity.

Archive source commit: f9dca8d04f4657abbf0153175feec65728ba6a99
Archive database SHA-256: c5d9c0d2bf01099de526d7510321eabd1b0e3519f2792d40b61e49062d766272

Participant cohort: unknown. No outside-customer usage is inferred.

0 scored exact-version purchases from 0 recorded BUY decisions; 0 BUY decisions unscored. 2 of 2 trace payment observations excluded.

Each unique source + item + content version with positive matching recorded settled access counts once. Duplicate BUYs, missing identities, zero/unconfirmed access and incompatible payment observations cannot create a scored purchase. CACHE and SKIP decisions are outside this sample.

Exact-version citation hit rate: Unmeasured
Recorded access cost of uncited purchases: Unmeasured

Predicted value and observed citations

Bins compare the recorded predicted value with citation occurrence in this one dispatch. Small samples do not validate a probability model.

Value band	Predicted mean (0–1)	Citation rate
0–0.2	Unmeasured	Unmeasured
0.2–0.4	Unmeasured	Unmeasured
0.4–0.6	Unmeasured	Unmeasured
0.6–0.8	Unmeasured	Unmeasured
0.8–1	Unmeasured	Unmeasured

Missed value, cost per supported claim, budget alternatives and counterfactual outcomes are unmeasured. No extra reading or learning was performed.

View outcome JSON Download outcomes

A new follow-up runs on Arc mainnet with today’s sources and budget. Only the historical question supplies context.

Ask a follow-upNew dispatch · creators paid again

Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.

From the archive

Related dispatches

Dispatch · Arc testnet historySep 30, 2026

What does Web Payments Review establish about the assumption that every x402 payment needs its own transaction, and what remains uncertain?

2 sources cited0.0200 test USDC recorded creator rewards

Dispatch · Arc testnet historySep 30, 2026

What does Web Payments Review establish about conflicting published estimates of x402 settlement time, and what remains uncertain?

2 sources cited0.0220 test USDC recorded creator rewards

Dispatch · Arc testnet historyOct 1, 2026

How does conflicting published estimates of x402 settlement time work in practice, and which published material supports the explanation?

2 sources cited0.0200 test USDC recorded creator rewards

Dispatch · Arc testnet historySep 30, 2026

Can you give a concrete example of blockchains for tiny automated payments using published source material?

2 sources cited0.0150 test USDC recorded creator rewards

Browse the full archive ▸