Across USDC Transfers: Deposit, Delivery & Recovery

Review a supported direct native-USDC route and verify its destination fill.

Configure and check the route

Choose Ethereum, Base or Arbitrum as distinct source and destination networks. This limited adapter requires server credentials and a compatible direct-USDC SpokePool quote with no destination message. A configured server can still receive an unsupported provider route; Bitpont blocks it instead of changing your intent.

Set input and minimum output

Enter native USDC to send and the minimum USDC you accept on the destination. Read the same-owner recipient, quoted output, fees and expiry. Keep ETH for source gas. A quote is not a promise of destination delivery.

Review approval and deposit

The finite token approval and the source deposit are separate transactions. Refresh the quote after approval, review the exact contracts and destination, then confirm the deposit. Keep its transaction hash.

Follow the fill

A finalized source transaction confirms a deposit, not a completed bridge. Bitpont checks the destination relay identity and native-USDC transfer against the source deposit. Reported or pending delivery remains unresolved until canonical proof is available.

Recover missing history

Reconnect the source wallet, choose the source network and import its transaction hash. Where available, provide the destination hash to check a fill. Refund reporting does not establish verified refund payment. Do not repeat the source deposit while its outcome remains uncertain.