# Circle Details CCTP Routes for Non-USDC ERC-20 Tokens

Published 2026-10-31 · Crypto.world Team · Crypto.world

> Circle's Oct. 30 guide explains how issuers can connect non-USDC ERC-20 tokens to its Cross-Chain Transfer Protocol. The routes use burn-and-mint for issuer-operated tokens, with a native deployment path on Arc Testnet and a custom setup for existing tokens.

[Circle](https://www.circle.com/blog/make-your-token-interoperable-with-cctp) says issuers can use its Cross-Chain Transfer Protocol (CCTP) for ERC-20 tokens beyond USDC, but the new routes are not a bridge for any token holder to use without preparation. The burn-and-mint options target tokens their issuers operate; assets outside that model need a separate ownerless configuration that does not use burn-and-mint.

A guide published Oct. 30 lays out two ways to connect issuer-operated tokens: deploy a new native cross-chain token or configure an existing ERC-20 on each chain in its route. Circle’s post focuses its end-to-end example on Arc Testnet, where developers can deploy the token and then create its counterpart on another chain.

## Two routes, both tied to the issuer

The native route is for a token designed for CCTP from the start. Circle’s CrossChainTokenService deploys the ERC-20 and its per-token manager; the issuer uses the same deployer address and salt to establish a shared token identity across chains. Each chain still has its own token contract and balances.

The custom route connects an existing ERC-20 that the issuer controls. The issuer configures it on every chain in the route, using the service’s registration and configuration process. Circle says the issuer sets the owner, operator, pause authority, rate limits and maximum transfer amount; the company does not take control of those settings.

> “You set the owner, operator, pauser, rate limits, and max transfer. Circle cannot assume control.”
>
> Hui Jing Chen, Developer Relations Manager, APAC at Circle

Both issuer-operated approaches use burn-and-mint: the source-chain token is burned, Circle’s Iris service attests to the message, and the destination chain mints against that attestation. For non-USDC tokens, Circle says the process runs through CrossChainTokenService and a manager assigned to each token, rather than USDC’s TokenMessengerV2 deposit flow.

## Arc Testnet is the guide’s proving ground

Circle’s walkthrough starts with a deployer address that the issuer reuses across supported blockchains, plus a token name, symbol, decimals and salt. The deployer and salt help define the shared token ID. Developers deploy on Arc Testnet, read the ID from the transaction receipt, then use Arc to deploy the remote token on a second chain.

Before transferring, developers approve the per-token manager. They then obtain an Iris fee quote and call `crossChainTransfer`. Circle’s optional forwarding service can submit the destination transaction without requiring the recipient to supply destination-chain gas, if the sender includes forwarding in the quote.

The testnet process has practical constraints: Circle says developers need USDC on Arc Testnet for gas and Iris fees, must check live quotes because fees vary by chain pair, and must keep token decimals consistent across chains. Circle also warns that zero transfer limits block transfers, so teams need to set limits during deployment or adjust them later.

## Cross-chain identity does not remove issuer risk

Circle’s post draws a boundary around the feature: the burn-and-mint routes described there assume the team issues or operates the token. Circle points to an ownerless configuration for tokens outside that relationship, but says it does not use burn-and-mint. That distinction matters for teams evaluating whether CCTP can carry an asset under its existing issuer controls.

The company also says it does not vet, endorse or back third-party assets, and that transfers are irreversible. Its testnet walkthrough is framed as a route to validate before production, where issuers should tighten permissions and transfer caps. The guide describes a new path for token teams, not a guarantee that every ERC-20 will be available across every chain.

## Sources

1. Original source · Blog post [Circle](https://www.circle.com/blog/make-your-token-interoperable-with-cctp) circle.com

## Companies in this story

- [Circle](https://crypto.world/companies/circle)

## Related stories

- [ERC-8475 Proposes Per-Transfer and Window Caps for ERC-20 Tokens](https://crypto.world/news/erc-8475-erc20-outgoing-window-limits)
- [Extended Schedules Oct. 22 Settlement Move From Starknet to Arc](https://crypto.world/news/extended-starknet-arc-settlement-migration-october-22)
- [Circle details Anduin payment-graph reputation test for AI agents](https://crypto.world/news/circle-anduin-payment-graph-agent-reputation-test)
- [Circle and ACI Plan USDC Settlement Pilot in Colombia](https://crypto.world/news/circle-aci-usdc-settlement-pilot-colombia)
- [Circle Match Runs Hourly Auctions That Pair USDC Minting With Redemptions](https://crypto.world/news/circle-match-hourly-usdc-mint-redeem-auctions)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/circle-cctp-non-usdc-erc20-token-routes
