XPayr on ARC

Bridge USDC to and from ARC

ARC App Kit Bridge abstracts the CCTP burn, attestation and mint sequence for supported USDC routes. It is designed to let users move native USDC between ARC, EVM networks and supported non-EVM environments without wrapped-liquidity accounting.

Verified on ARC Testnet Technical status last verified July 2026
ARC
Direct answer

ARC App Kit Bridge abstracts the CCTP burn, attestation and mint sequence for supported USDC routes. It is designed to let users move native USDC between ARC, EVM networks and supported non-EVM environments without wrapped-liquidity accounting.

How XPayr applies it

XPayr exposes bridge planning, a locked operation fee and wallet-signed execution through the Merchant ARC Hub. Mainnet routing stays disabled until the production CCTP contracts and supported capability matrix are confirmed.

Verified on ARC Testnet

XPayr keeps ARC Mainnet payment execution review-gated until canonical production contracts, explorer support and low-value wallet-signed pilots are verified. Public tools and Testnet flows remain available for evaluation.

From question to a controlled ARC transaction

1

Understand the primitive

Start with the exact ARC capability, supported asset and network boundary instead of a generic blockchain promise.

2

Plan the route

Choose checkout, send, bridge, swap, Unified Balance, memo, batch or agent settlement and review its fee model.

3

Sign from the wallet

The merchant or payer wallet signs the operation. XPayr does not treat a browser response as settlement proof.

4

Verify and reconcile

XPayr checks chain, token, amount, recipient and transaction evidence before updating payment and fee ledgers.

Free ARC planning tools

ARC USDC Bridge Planner

Plan a USDC route into or out of ARC, separate the bridge amount from the XPayr operation fee and continue to wallet-signed execution.

Open the free ARC tool

Execution boundary

XPayr exposes bridge planning, a locked operation fee and wallet-signed execution through the Merchant ARC Hub. Mainnet routing stays disabled until the production CCTP contracts and supported capability matrix are confirmed.

ARC questions answered clearly

Bridge USDC to and from ARC: How XPayr applies it

XPayr exposes bridge planning, a locked operation fee and wallet-signed execution through the Merchant ARC Hub. Mainnet routing stays disabled until the production CCTP contracts and supported capability matrix are confirmed.

Is this available on ARC Mainnet through XPayr?

XPayr keeps ARC Mainnet payment execution review-gated until canonical production contracts, explorer support and low-value wallet-signed pilots are verified. Public tools and Testnet flows remain available for evaluation.

Does XPayr custody funds or hide the network fee?

No. Wallets sign transactions, chain fees remain visible and XPayr records its operation fee separately. Standard successful checkout uses the configured XPayr gateway fee; advanced ARC operations use their published fee quote.

Continue through the ARC stack

Primary references

Move from ARC research to a working test flow.

Open the public planner, then create a free merchant account to test checkout and wallet-signed operations without enabling Mainnet.