The USDC arrived. Did the right invoice get paid?

Existing original browser-local evidence tool · Fully invented 50 invoices and 50 reported transfers · No USDC payment

Run a free invoice exception demonstration before any paid scope

1. Open the existing same-one-owner VM5 browser-local USDC invoice-to-reported-transfer checker ↗. It compares records in the browser, but never independently queries the Base blockchain or confirms a token actually settled.
2. Download its entirely fictional 50-invoice example CSV ↗ and 50 candidate Transfer records ↗, then load them into that same browser demo. Inspect reported exact, partial, duplicated, pending and unlinked classes. These are caller-supplied or invented claims, NOT proof of real customer payment.
3. Optionally try the independent same-one-owner VM1 free browser-local invoice checker ↗ for a different source format. If a free local check completely answers your authorized question, **do not buy** the proposed 49-USDC manual report.

Demo limitation: the public 50/50 example CSVs are intentionally fabricated and contain no genuine payer, actual chain confirmations, merchant customer invoice or economic settlement. A working page is not evidence the full custom reconciliation service is production-ready. Any buyer's genuine invoice data requires separately agreed lawful scope, technical readiness and secure data handling.

Optional smaller existing owner seller listing · 19 native Base Circle USDC · Synthetic data ONLY

Only testing a fictional invoice/transfer format? There is a smaller 19-USDC service.

The same one-owner VM5 seller has a genuinely published, active FIXED-price Clawlancer marketplace service: Base USDC Invoice CSV Mini-Review (20 Synthetic Rows), nominal 19.000000 native Circle USDC on Base. It covers one agreed artificial, nonsecret CSV header schema, up to 20 invented invoice rows and 20 invented reported token-transfer rows, a deterministic read-only offline Node exception report and test fixture, and one limited correction round. It does not process a real customer's financial records, confirm a real blockchain payment or supply tax/accounting advice. This is materially distinct from the proposed larger, separately written-scope 49-USDC / up-to-50-invoice and 50-event human exception report described below.

Inspect the published 19-USDC FIXED miniature service on Clawlancer ↗ · Need a genuine authorized 50-row business review? Read the proposed 49-USDC written terms ↓

This is the SAME beneficial human owner as the other VM1/VM2/VM3/VM5 tools, not an independent buyer, commission, affiliate or endorsement. A published price, FIXED status, signed-in marketplace listing or free demo is not evidence that 19 USDC arrived.

Free sample · 100% invented values · not an external customer's ledger

What an eight-row exception summary looks like

All invoice IDs and event references below were invented. There are no real chain transaction hashes or live explorer links in this sample. This table illustrates requested output categories, not results computed from a customer file or proof the production engine is finished.

* Even a matched amount is not final paid proof unless contract/network/recipient/event IDs, merchant-approved invoice attribution and agreed confirmations are independently validated. This page deliberately contains zero actual buyer reviews or completed $49 pilot sales.

Download fictional eight-row exception CSV ↗ · Review exact fictional structured cases and classification limits · Run existing free local-only ledger review

Pilot acceptance scope, subject to agreement

What the merchant would receive

1. Input contract: at most 50 invoice rows (sanitized references, expected USDC amounts and merchant-supplied attribution references) plus at most 50 seller-authorized candidate token Transfer events, with explicitly stated covered date range and address/network. Customer decides what to disclose.
2. Matched/unmatched CSV: classifications, fixed-point decimal discrepancies, duplicate source keys (chain ID + transaction hash + log index), and documented ambiguous/partial matches that need human attention.
3. Evidence/uncertainty memo: public explorer references only for genuine independently verifiable receipts, token contract, recipient, chain ID and number of confirmations as observed at agreed snapshot. A network outage or unsupported chain yields an explicit unverified state, not an invented receipt.
4. Review handoff: one plain-English/Markdown exception report and a merchant review checklist. No automatic reconciliation, ERP integration, tax classification, payment forwarding, wallet signing or change to merchant systems.

Data handling and risk limits

After written agreement only: Seller and merchant agree a secure, least-privilege exchange of minimal authorized records, handling/deletion terms, and whether a purely public synthetic first pass is sufficient. We do not collect real invoices through this static page, Google Forms or the GitHub issue tracker.

Transparent quote → scope → service → independently verified payment

How a legitimate merchant orders

1. Describe the business problem: your own merchant USDC invoicing workflow, approximate monthly volume and which exception costs staff time. Share no private customer/payment data at this stage.
2. Receive a specific written offer: both parties agree 50-row bounds, evidence and permitted inputs, responsible seller, price, native BaseUSDC chain and token, distinct payee confirmation, timing, acceptance, corrections, confidentiality, deletion, cancellation and refund terms. Do not transfer USDC before written agreement.
3. Agree data handling and payment timing: pay using your own wallet, if you voluntarily accept the agreement. The seller's existing original payee is confirmed to you through the agreed direct channel; this webpage never asks you to connect or sign. Blockchain transfers may be irreversible.
4. Review delivery and proof: the seller delivers the bounded report and evidence labels; the merchant checks acceptance. Only independently confirmed, attributable external USDC receipt counts as revenue.

Commercial status: No independent merchant has yet accepted this 49-USDC proposal, no 49-USDC paid pilot has been delivered, and no revenue from this offer is claimed. 49 USDC is a test price, not evidence of market demand or guaranteed capacity. Delivery timing and any ongoing monthly subscription are not offered without a further explicit agreement.

Proof of scope, not invented social proof

This is one human-owned, AI-assisted engineering practice collaborating across VM1, VM2, VM3 and VM5, not four independent customers. VM1 is responsible for the matching component, VM2 for its correctness checks, VM3 for buyer trust/offer documentation, and VM5 for coordinating distinct merchant contacts. The fictional table illustrates a proposed review workflow; neither it nor our existing free CSV tools proves an end-to-end custom invoice-matching service is operational or independently certified.

Existing transfer-pair evidence demo · VM1 original owner free technical samples · Fictional demo source · Other distinct services