- Pricing
- For USDC, read on https://developers.circle.com/cctp/concepts/fees (HTTP 200, fetched 28 September 2026): "CCTP charges fees on Fast Transfers only. Standard Transfers are free." and "Fee range : 0-13 basis points depending on source blockchain, for example $0-$1.30 per $1,000 transferred". Fast Transfer fee by source chain, same page: "Arbitrum 1.4 bps (0.014%)", "Base 1.3 bps (0.013%)", "Codex 1.5 bps (0.015%)", "EDGE 1.5 bps (0.015%)", "Ethereum 1 bps (0.01%)", "Ink 2 bps (0.02%)", "Linea 13 bps (0.13%)", "Morph 4 bps (0.04%)", "OP Mainnet 1.3 bps (0.013%)", "Plume 2 bps (0.02%)", "Solana 1 bps (0.01%)", "Starknet 12 bps (0.12%)", "Unichain 2 bps (0.02%)", "World Chain 1.3 bps (0.013%)", "X Layer 1.3 bps (0.013%)". The Standard Transfer table lists 28 source chains, each at "0 bps (0%)". The page warns "Do not hardcode fee values. Fees can change at any time." and adds that "Some deployments of the TokenMessengerV2 contract include a fee switch that enforces a minimum onchain fee." (Sei is the only chain listed with it). For a token issuer's own asset, the relevant schedule is CCTP for non-USDC, launched 2026-09-16: https://developers.circle.com/cctp/expanded-assets (HTTP 200, fetched 28 September 2026) says transfer fees are "Fee paid in native gas on the source blockchain", quoted per transfer by Circle's Iris API, and the custom-token quickstart (https://developers.circle.com/cctp/expanded-assets/quickstarts/configure-custom-token) says of the registration call only "If you are configuring on mainnet, verify whether a fee applies before submitting." No registration fee, licence fee or per-transfer rate for non-USDC tokens is published.Circle Cross-Chain Transfer Protocol (CCTP) — official pricing page ↗ · 28 September 2026
- Licences held
- Not published
- Compliance level
- partial
- Regulatory note
- Not published
- Supported chains
- Ethereum, Arbitrum, Base, OP Mainnet, Polygon PoS, Avalanche, Solana, Unichain, Linea, Codex, Sonic, World Chain, Monad, Sei, BNB Smart Chain (USYC only), XDC, HyperEVM, Ink, Plume, Starknet, Stellar, EDGE, Injective, Morph, Pharos, Cronos, X Layer, Aptos, Plasma, Arc
- Markets served
- global
- Primary markets
- Not published
- Restricted markets
- Not published
- Operating limits
- Not published
- Availability note
- STANDARD OFAC/SANCTIONS REPRESENTATION, NOT A REGIONAL FOOTPRINT. The Circle Developer Terms (https://console.circle.com/legal/developer-terms, HTTP 200, read 17 August 2026) define the restriction purely by sanctions: '“Restricted Territory” means a region, territory or country subject to Sanctions', with 'Sanctions' defined by reference to 'the U.S. Department of Treasury’s Office of Foreign Assets Control, the U.S. Department of Commerce, or the U.S. Department of State ... the United Nations Security Council, and all other relevant international sanctions authority'. The developer obligation is likewise generic: 'You will ensure that your Circle Developer Account, any Developer Tools and Services, and Your Service, cannot be used or accessed by any person or entity in a Restricted Territory or any Sanction Target, including by implementing commercially reasonable procedures, such as sanctions screening and geo-lo[cation]'. No market-by-market availability list, no country whitelist and no per-jurisdiction gating for CCTP itself was found on any CCTP docs page. One separate and genuinely regional fact, from Circle's own site chrome rather than the protocol docs: circle.com labels USYC — the second CCTP-enrollable asset — 'Not available in the US' (www.circle.com/blog/cctp-version-updates navigation, read 17 August 2026). That constrains an asset, not the protocol. Tagged global.