USDC transfer found. Which invoice, if any?
Compare a merchant's invoice register and its separately prepared Base USDC Transfer CSV inside this browser. Quarantine mismatched network, token, recipient and repeated event identities rather than guessing that a payment settled.
No chain RPC, blockchain authenticity check, third-party API, local storage, wallet connect, analytics, cookie, invoice-posting action or payment on this page.
Preview your authorized CSVs locally — free
Use the fictional demo first. Inputs are capped at 256 KiB and 750 CSV records each. Do not enter private financial data on shared computers. We cannot validate whether your CSV was forged or whether a payment actually exists onchain.
An invoice_id beside a transfer must come from a separate buyer-authorized association or merchant memo; it is NOT inherent to the blockchain. No amount-only guesses or automatic allocations across invoices. Partial transfers with the same invoice reference can sum, but all amounts remain unverified.
No report yet. No data stored.
What can be flagged
- Candidate exact amount, partial/underpaid or overpaid invoices.
- Repeated chain + transaction hash + log index — review, never silently delete.
- Same transaction hash, distinct log indices: genuine separate event candidates.
- Declared wrong network, wrong token (including noncanonical bridged assets) or wrong recipient; zero-address burn/mint and self-to-self transfers must never be counted as independent customer receipts.
- Missing, invalid, ambiguous, duplicated or unknown invoice references and CSV fields.
Critical boundaries
- Only Base mainnet 8453 and native Circle USDC contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.
- Exact 6-decimal integer arithmetic; no floating point or exchange-rate assumptions.
- All statuses are unverified CSV candidates, including candidate exact matches.
- Report omits raw transaction hashes, recipient addresses and invoice IDs; local row numbers and candidate amounts can still be commercially sensitive.
- Never automatically import to ledgers, delete events, initiate refunds or claim tax/accounting assurance.
Inspect the original source and synthetic regression tests.
Interested in a small, buyer-authorized pilot?
The USD 49 up-to-50-payment manual exception-review hypothesis is an indicative proposed price, not proven demand or a binding contract. A lawful customer must agree in writing on non-sensitive data handling, precise scope, cancellation, payee identity and independent payment-rail verification. Native Circle Base USDC could be used only at an exact separately agreed amount; this page does not collect payment. No existing paid reconciliation customers claimed.
Your own email app opens a prefilled direct enquiry draft; nothing is sent until you choose Send. The separate optional FormSubmit form may ask for an additional spam check and requires explicit third-party consent. If you cannot use either channel, do not send private invoices, passwords or wallet histories to unverified contacts.
The voluntary contact page explicitly requires consent to an outside email-form provider; don't send real invoices, addresses, passwords or wallet recovery information in the enquiry.