Free · Private · Browser only · Base mainnet USDC
Stop counting the same payment twice.
Paste your x402 seller or merchant transfer CSV. Spot duplicate transaction log IDs, the wrong USDC contract or destination, self-transfers, and deliveries that do not match the claimed transfer record. Your wallet address and CSV stay in this browser.
Important: A CSV is a claim, not a chain receipt. This tool does not connect to Base RPC, verify transaction finality, authorize a payment or prove taxable/realized revenue. Treat the subtotal only as an unverified candidate requiring independent chain and delivery evidence.
Optional zero-upload helper · No RPC calls
Have a public transaction receipt JSON, not a CSV?
Paste the JSON text from a eth_getTransactionReceipt response you obtained independently. We extract only structurally valid canonical Circle USDC ERC-20 Transfer logs into the CSV below, including the exact transaction hash and logIndex. We never contact a chain, fetch a receipt, or verify the claimed Base network, transaction authenticity, confirmations, recipient ownership, payment authorization or delivery. Every imported delivery_status is unknown until you independently check your own order records.
Use a published transaction receipt from a source you trust, after verifying it describes Base mainnet 8453. Never paste private keys, payment signatures, authentication headers, cookies or invoices. The tool cannot authenticate pasted data. Imported amounts are structurally decoded USDC micro units but are not independently verified.
No JSON receipt imported. Try the synthetic example; a valid event only becomes an unverified CSV claim.
1. Check your own CSV locally
Paste only a public receiver address. Never paste a private key, seed phrase, API credential or session token. We cannot access, verify or move funds.
Required headers: chain_id, token_address, tx_hash, log_index, from, to, amount_usdc, delivery_status. Optional: order_id. USDC amounts are decimal values (not base units), with at most 6 fractional digits. Recognized delivery claims: delivered, pending, partial, failed. Input without a log index cannot safely distinguish multiple transfers inside one transaction.
Maximum 500 rows, 32 KiB.
No transaction CSV has been analyzed. Start with the synthetic example.
3. Claim-only reconciliation
Local review — not a payment receipt
| CSV record | Event key | Claim USDC | Review state | Reason |
|---|
Only the first 80 rows are displayed. The totals include the entire bounded input; the exported report includes every row.
No chain nodes were queried. None of these values represent independent settlements, completed customer invoices, actual seller receipts, merchant balances or tax statements. Independently check Base transactions, finality, actual recipient and proof of delivery before accounting.
Real buyer feedback · Voluntary · No tracking
Which x402 or USDC issue actually costs you time — and what would you pay to fix it?
Select the issue that actually costs you time. We are testing real demand, not claiming thousands of users, fake reviews or income. Choose your role, problem, frequency and approximate willingness to pay for a demonstrably useful fix. This is only feedback, not an invoice, order or wallet transaction.
No signup and no analytics. Preparing the feedback creates a browser-local email draft. We do not receive anything until you open your email app, review and send. Never include private keys, recovery phrases, customer data, invoices, addresses or transaction hashes.
Nothing is sent. Select your choices and prepare an email only if you want to reply.
Prefer a public developer discussion? You may also reply to the real Base USDC buyer feedback issue on GitHub (GitHub sign-in required). A public issue comment is optional and does not buy anything or prove demand until a real user writes it. Please remove all customer information, signatures, keys and nonpublic transaction data first.
Same verified single-owner seller inbox: onecursor1@gmail.com. Submitted feedback is not automatically posted or treated as a paid purchase. A real payment requires separate authorization.
Have ambiguous payments or disputed delivery?
A machine-generated CSV report cannot settle a payment dispute. Request a source-linked evidence memo for 5 USDC for one public transfer or a 15 USDC scoped reconciliation for up to five public transactions, subject to a written quote and buyer approval. No order, payment, review, guarantee or past client engagement is implied by this page.
OpenTask links to the seller profile, not an instant checkout or an automatically purchased service. A real buyer must separately accept the scope, payee, Base chain and Circle USDC asset before any voluntary payment. No sensitive customer data or wallet keys should be emailed.
Machine buyers: Our existing single-owner Soul.Markets AI service profile offers a separately purchased 2.50 Base USDC AI-assisted review of up to 15 public buyer-supplied transfer rows. It checks record consistency only (no chain fetch or payment finality); inspect the published input schema and agree to that marketplace's x402 terms before making a deliberate purchase. This free browser tool itself performs no paid API calls. The external platform has reported zero prior orders for this SKU.
Separate low-cost machine report · 0.005 native Base USDC
Only need a generic CSV structural-quality report?
Our same-owner VM5 merchant offers an optional separate buyer-owned CSV structure API for 0.005 native Circle Base USDC. Its browser checkout can fetch and display a real unpaid HTTP 402 quote first, before connecting a wallet. It checks CSV formatting, duplicates and spreadsheet formula hazards; it does not verify blockchain transactions, buyer identity, ledger reconciliation, USDC receipt settlement, tax status or proof of delivery. This merchant ledger above remains free.
Consent boundary: Requesting a real quote sends the CSV you provide to the existing VM5 hosted API, even if you never pay. The checkout beta requires two separate explicit consents plus an independent Base wallet before requesting any signature. No wallet connection or payment happens from this free ledger page. End-to-end payment from an independent buyer has not been verified.
How to prepare a valid event-level CSV
One line should represent one ERC-20 Transfer log on Base. Provide chain ID 8453, the actual Base Circle USDC contract address, complete transaction hash, event log index, payer, payee, microprecision decimal amount and your independently recorded delivery state. Never replace a missing event index with a guessed zero.
The bracketed placeholders above are explanatory, not a valid CSV event. Use “Try synthetic example” for a fully valid invented dataset. Do not upload real private invoices or user identifiers to third-party sites to generate this input.
View the original open-source implementation, BaseScan ERC-20 token reference, or our separate generic local CSV structural checker. This is general data-quality tooling, not financial, legal, tax or security certification advice.