1. Receipt classification
Direct self-payments, disclosed related-party payments, unattributed payers, recipient mismatches, and failed receipts.
Provider-facing demand evidence
Publish the demand claim your receipts can actually support.
Ontario reviews up to 500 Base USDC transaction receipts, disclosed related addresses, recipient consistency, payer concentration, and available off-chain evidence. The deliverable separates observable settlements from claims that require stronger attribution.
A claim ledger, not a vanity counter
2. Concentration evidence
Unique payer count, largest-payer share, repeated payer patterns, total settled USDC, and methodological limits.
3. Publishable boundary
Supportable wording, prohibited overclaims, evidence digest, and links suitable for a public trust or investor page.
Required inputs
- CSV or JSON containing up to 500 public Base transaction hashes.
- Expected recipient address or addresses.
- Known founder, operator, treasury, test, and related-party addresses.
- Optional public request logs or report IDs when you want to support HTTP x402 attribution.
Boundary: This is an evidence review, not an audit opinion, fraud determination, customer identity check, financial statement, or guarantee of organic demand. Unattributed wallets remain unattributed unless additional evidence supports a narrower claim. Ontario never requests private keys, seed phrases, payment signatures, or wallet custody credentials.