How long do x402 payments take to finalize?
9/2/2026, 8:47:52 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/6 positive proposal(s): 3 cached + 1 fresh, predicting 4/4 claim(s) above the evidence floor with $0.002000/$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.
Directly addresses the exact question: 'How long do x402 payments take to finalize?' with cross-protocol commentary. Good reputation (25/100) and citation history on this subject. Already cached, so free. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Solana slot time reduction directly addresses network latency and finalization speed, relevant to sub-claim about variation by blockchain. Cointelegraph has good reputation (35/100). Not cached, price low at $0.002. — selected for the claim-aware evidence portfolio (targets claims 3, 4; $0.002000 fetch USDC, 1 attention slot).
Describes x402 as a payment rail, may contain finalization details. Low reputation (6/100) but already cached, so free. — selected for the claim-aware evidence portfolio (targets claims 1, 4; 0 fetch USDC, 1 attention slot).
Stablecoins are core to x402 settlement. Good reputation (28/100) and citation history. Already cached, so reuse for free. — selected for the claim-aware evidence portfolio (targets claim 3; 0 fetch USDC, 1 attention slot).
Topical match is exact: directly measures x402 settlement latency on Arc. Highest reputation source (40/100) with strong historical citation rate on this subject. Already cached, so reuse for 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.
Real-time blockchain settlement for JGB trades is tangentially related to finalization times. Low reputation (16/100) but already cached, so 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 good reputation (35/100) historically, but this specific article is about solo founders, not x402 finalization. Not a direct match, so skip.
Coinbase Blog article on real-time reconciliation is about distributed systems, not x402 finalization times. Low relevance despite payment tags.
Decrypt article is about crypto payments to terror group, completely irrelevant to x402 finalization times. High reputation source but poor topical match.
Vitalik article on low-risk DeFi is about Ethereum's value proposition, not x402 finalization latency. Not cached, price $0.004, low relevance.
Nanopayments and batching may affect settlement timing. Already cached, so free. Low reputation (8/100) but free to use. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
Idempotency keys are about preventing double-spends, not finalization times. Low relevance to question despite system tags. Already cached but not worth the context.
Gardening article is completely irrelevant to x402 payments. Skip despite being cached.
Esoteric article on ISIS mythology is completely irrelevant. Skip.
Angular performance article is completely irrelevant. Skip.
Ontologies article is about AI agents and semantic web, not x402 finalization times. Not cached, price $0.004, low relevance.
Simon Willison article about Anthropic's AI model adoption is irrelevant to x402 payment finalization. Not cached, skip.
Hugging Face article about voice agents and TTS is irrelevant to payment finalization. Not cached, skip.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Web Payments Review — How long do x402 payments take to finalize? (free) — S1
Paying $0.002 toll to read Cointelegraph.com News — Solana cuts blockchain slot time to 350 milliseconds…
Paid $0.002 to Cointelegraph.com News — Solana cuts blockchain slot time to 350 milliseconds (settled a0591ff4-a…) — S2
Sub-claim "X402 payments have a specific finalization time or latency": 100% covered by S1
Sub-claim "The finalization time is measured in a specific unit such as…": 100% covered by S1
Sub-claim "The finalization time may vary depending on the blockchain o…": 70% covered by S1, S2
Sub-claim "The finalization time is a key performance metric for X402 p…": 40% covered by S1
The gathered information directly addresses the core question about X402 payment finalization time, providing specific timing details and context about variability across networks. Sub-claims 1 and 2 are fully supported, sub-claim 3 is reasonably inferred, and sub-claim 4 is partially supported through contextual comparison.
All sub-claims already well-covered (sufficiency passed with 0 gaps) — skipping re-evaluation to save latency.
Final check — "X402 payments have a specific finalization time or latency": 80% assessed by S1
Final check — "The finalization time is measured in a specific unit such as…": 30% assessed by S1
Final check — "The finalization time may vary depending on the blockchain o…": 20% assessed by S2
Final check — "The finalization time is a key performance metric for X402 p…": 0% assessed
Final coverage assessment — The gathered sources only directly address the first sub-claim about the finalization time being specific (15 seconds). They do not provide clear information about the other sub-claims regarding the unit of measurement (e.g., seconds vs. blocks), variation based on blockchain, or its role as a key performance metric. Therefore, the coverage is insufficient to answer the full question confidently.
Synthesizing a grounded answer from 2 source(s)…
Verified — S1 supports claim 1 at 100%: “an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is its own transaction waiting …”
Verified — S1 supports claim 2 at 100%: “an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time”
Drafted answer citing 1 source(s)
Confidence: Low — 3 sub-claims remain below the evidence threshold.
Web Payments Review contributed 100% → reward $0.02
Settled $0.02 citation reward → Web Payments Review (3ef2e4a3-6…)
Done. Spent $0.022 across 2 confirmed/simulated payment(s) to creators.
> ⚠ Low confidence — 3 sub-claims remain below the evidence threshold within budget. Treat this as provisional.
X402 payments take about 15 seconds to finalize, as each payment is a separate transaction waiting to be mined into a block, similar to Ethereum L1 block time .
Evidence ledger — quotes verified before rewards
X402 payments have a specific finalization time or latency
80%“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.” [S1] How long do x402 payments take to finalize?
The finalization time is measured in a specific unit such as seconds, minutes, or blocks
30%“an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time” [S1] How long do x402 payments take to finalize?
The finalization time may vary depending on the blockchain or network used
0%No reward-qualifying evidence
The finalization time is a key performance metric for X402 payments
0%No reward-qualifying evidence
Footnotes — each one pays its author
- 1How long do x402 payments take to finalize?Web Payments Review100%+$0.02
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
1 exact cited article version 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.