1. Your receivables
Arc mainnet · chain 5042 · canonical system USDC events · 18 decimal places
Amounts are exact decimal strings. Timestamps require UTC Z.
2. Receipt evidence
Arc emits both a canonical system event (18 decimals) and, for ERC-20 calls, a 6-decimal mirror. This adapter uses only the system event, so one payment is never counted twice.
Fetch public Arc mainnet data (optional)
The RPC provider sees the requested public address / block range / transaction hash, never your invoice CSV. Network identity is checked before reads.
Maximum 1,000 blocks per range. Fetching replaces the current transfer evidence. These are read-only requests; no gas is spent.
Imported JSON is unverified input. Only canonical system events belong in Arc input; JSON alone cannot establish token provenance.
3. Review and attribute
A matching amount is a candidate, not proof of business attribution. Select the receipts you recognize, then explicitly confirm their invoice allocation. Partial payments remain partial. A receipt can belong to only one invoice.