Directory

Showing 1–2, most evidence first; contradicted and not yet assessed last · names and descriptions as their source publishes them

• Commerce Escrow Status402.com.tr🆕 First tooling for Base's Commerce Payments protocol (AuthCaptureEscrow): reconciles two-phase auth/capture payments — in escrow, captured, charged, voided, refunded, or payer-RECLAIMABLE because the operator missed the capture window. Filter by payment= (infoHash), payer=, receiver= or operator=, or omit everything for the network feed. The order-reconciliation read merchants and agents need before trusting onchain commerce.Livechecked 13 Nov 2026, 02:50 UTCEvidence 1/4x402x402 Bazaar1 payerCoinbase-attested wallet
• Payment Operator Audit402.com.tr🆕 Commerce Payments flows are DRIVEN by an operator — it authorizes escrow, captures for merchants and takes the fees. This audits one before you rely on it: 90-day volumes, fees taken, capture-vs-reclaim record (missed capture windows = merchants left unpaid), distinct payers and merchants. verdict: healthy_operator / mixed / sloppy_operator / no_activity. No other tool reads this new Base commerce protocol.Livechecked 13 Nov 2026, 02:49 UTCEvidence 1/4x402x402 Bazaar1 payerCoinbase-attested wallet