Choose an Arc funding route

About this guide

We checked the sources for this guide on 24 Sept 2026. Use the linked sources for current availability, terms and network details. See subsequent updates

Choose a funding route from the asset and location you already have. A bank balance, USDC on another chain and a deposited Gateway balance are three different starting points.

Match the route to the starting point

You start withInvestigateVerify before signing
Fiat in a bank or card accountA supported onramp in Portal or an applicationCountry, payment rail, identity checks, total cost and destination network
A supported asset on another chainCCTP or a product that uses itExact source/destination route, fees, recipient and recovery steps
An existing Gateway depositA supported Gateway spendSpendable balance, signer permissions, destination and removal rules
Testnet tokensA testnet application or faucetTestnet on both sides of the flow

Portal’s introduction describes its funding entry points. Circle CCTP and Gateway document the protocol-specific flows.

Read the quote as an end-to-end amount

Compare how much leaves the source with how much arrives at the destination. Identify the network fee, route or service fee and any conversion spread. Check whether the destination receives enough USDC to cover the next action or whether that action has a sponsor.

If the provider cannot quote the exact route, do not assume a similar ticker or another supported chain will work. A supported provider can have unavailable assets, corridors or account types.

Keep a record of every stage

Crosschain transfers have more states than a single-chain payment. In a CCTP flow, a source burn can complete before an attestation is retrieved or the destination mint succeeds. Save the result and both chain identifiers when the transfer starts.

For an application, model at least submitted, source confirmed, destination pending, completed and needs attention. Keep those labels tied to evidence from the operation. A progress bar should not imply that a transfer completed because a timer elapsed.

The App Kit recovery guide explains its per-step results and retry path. Inspect which step succeeded before asking a user to sign again. Repeating the original transfer after a successful burn can create a second transfer rather than finish the first.

Check asset coverage per product

The September 23 Interop announcement distinguishes CCTP asset movement from Gateway’s unified balance. It describes USDC Gateway support while marking EURC and cirBTC Gateway support as forthcoming. Multi-asset CCTP support should not be read as identical support in Gateway.

Finish a funding test by locating the destination receipt and verifying the recipient’s balance. Save the source hash, destination hash and quoted-versus-received amount together. Those records are more useful to support than a screenshot saying “processing.”

Sources & references

Documents cited in this guide.

  1. blog/arc portal the easiest place to get started on arcarc.io
  2. Cross-Chain Transfer Protocol - Circle Docsdevelopers.circle.com
  3. Circle Gateway - Circle Docsdevelopers.circle.com
  4. App Kit recovery guidedocs.arc.io
  5. Interop announcementarc.io