USDC on Arbitrum: settle the token identity first

Start with the native-USDC reference

Use Circle's current Arbitrum entry to verify native USDC. If an interface presents another identifier, find the documentation for that representation instead of assuming the names are interchangeable.

Issuer support does not imply that a particular recipient accepts the token, nor that Circle endorses the service.

Be precise about which step is timed

A same-network transfer, a platform deposit credit and a later transfer to Ethereum are separate events. A service's “instant” label is not useful unless it names the start and end of the measured interval.

For a crosschain route, check the protocol's current support and the receiving asset. CCTP's burn-and-mint model should not be assumed for an arbitrary bridge interface.

Keep enough information to explain a deposit

• The sending network and full token identifier.
• The transaction reference, amount and time.
• The recipient's deposit instructions as they appeared when you sent.
• The provider's order reference, if an intermediary was involved.

Arbitrum USDC: identify the version before the route

Arbitrum can expose more than one USDC representation in wallets and bridge histories. Match the exact Circle-listed native identifier or the documented bridged representation with the receiving platform's policy.

Arbitrum gas and a service's deduction are separate fields. A quick confirmation or a familiar token symbol does not prove that an intermediary will credit the output or keep no records.