On Arbitrum One, USDC has six decimal places and comes in two forms with different token contracts: native USDC and bridged USDC.e. For a treasury, the distinction matters because a balance that looks like “USDC” in a wallet may not be the asset a payout recipient or accounting system expects.
Native USDC and USDC.e are separate assets
Native USDC is issued on Arbitrum One; USDC.e is Ethereum-native USDC represented there through Arbitrum’s canonical lock-and-mint bridge. They share a dollar target and familiar ticker, but they are separate ERC-20 contracts with separate balances and liquidity.
Identify them by chain and contract address, never by symbol alone. On Arbitrum One, native USDC is at 0xaf88d065e77c8cC2239327C5EDb3A432268e5831; USDC.e is at 0xff970a61a04b1ca14834a43f5de4533ebddb5cc8. Both use six decimals, so 1,250 USDC is 1,250,000,000 base units. A payout parser that accepts any token labelled USDC can credit the wrong asset or reject a valid transfer.
The economic difference follows the bridge model. USDC.e on Arbitrum is backed by USDC locked on Ethereum; native USDC is issued directly on Arbitrum and can move through a burn-and-mint transfer mechanism. The same stated amount does not make their contracts interchangeable, and an exchange between them may incur a spread if liquidity is thin.
The bridge route determines which contract arrives
A canonical lock-and-mint transfer locks Ethereum USDC in a bridge contract, then mints the corresponding USDC.e representation on Arbitrum One. In reverse, the L2 representation is burned and the Ethereum-held tokens are released through the withdrawal process, which for the canonical Arbitrum route includes a roughly seven-day challenge period.
A burn-and-mint route instead burns USDC on the source chain and, after the required message attestation, mints native USDC on the destination. It avoids leaving the destination balance as the canonical bridge’s wrapped representation, but depends on the transfer protocol’s attestation and destination mint completing. A cross-chain service such as quickswap can move and swap crypto assets across chains in one flow; the treasury still needs to confirm that the resulting token contract matches its payout policy. When comparing routes, check the asset delivered as well as the quoted output and settlement conditions.
Do not treat “bridge completed” as sufficient evidence for reconciliation. For a native-USDC transfer, verify the destination-chain transaction and mint to the treasury address; for a canonical bridge transfer, verify the USDC.e mint and the corresponding source-chain lock. A source transaction alone proves initiation, not that the destination asset is available for payout.
Choose the token your recipients can actually use
Make the decision from the receiving system backward. If the exchange, custodian, smart contract, or vendor wallet accepts only native USDC, USDC.e is not a substitute just because a wallet displays the same dollar balance. If a recipient’s existing workflow relies on USDC.e liquidity, converting to native USDC first can add an unnecessary swap and another execution risk.
For example, a business sending twelve supplier payments of 2,500 USDC needs 30,000 USDC on the payout chain. If recipients require native USDC, set the target asset to the native contract and reconcile 30,000 USDC there; do not count 30,000 USDC.e as satisfying that obligation unless the recipient has explicitly agreed to accept it. If your source balance is Ethereum USDC, the choice is a native mint-and-burn path or a canonical transfer followed by a separate conversion, where available. Compare the full cost and completion conditions, not just the bridge quote.
That comparison should include source-chain gas, bridge or transfer charges, any swap spread, destination gas, and the time until funds are spendable. For a return transfer, include the canonical withdrawal delay if using the lock-and-mint route; a payout due today may justify choosing a different route even if its quoted fee is higher. Check liquidity before relying on a USDC.e-to-native swap for a fixed payout amount, since pool depth and price impact determine how much arrives.
Make contract identity part of treasury controls
Maintain an approved-token record keyed by chain ID and contract address, with the business label stored separately. For Arbitrum One, record chain ID 42161 and the accepted USDC address; configure payout validation to reject an unapproved contract before creating a payment instruction. A transaction hash, chain, token contract, recipient, amount, and confirmation status give finance enough fields to reconcile the transfer without relying on wallet labels.
If a transfer lands as the wrong form, pause the payout and record the asset actually received. Then decide whether to hold it, convert it at an approved rate, or return it; do not silently book USDC.e and native USDC as one asset. For recurring flows, quickswap can be part of the movement-and-swap step, while the receiving contract check remains a treasury control. Keep a small test transfer in the runbook when onboarding a new route, and have the recipient confirm the exact token contract before sending the full batch.