Retail Payments

Cross-Chain CCTP Transfer

USDC transfer across chains via Circle's Cross-Chain Transfer Protocol — burn on source, mint on destination.

Vendors

Circle · CCTP

Compliance center

Burn-mint bridge compliance at Transport

retailusdccctpcross-chainbridge
Filter by shape:
|
R2 · RETAILCross-chain CCTP transfer·5 stations(1 compliance, 4 infra)·circle
S1INTENTS2S3DISCOVERYS4NEGOTIATIONS5S6AUTHORIZATIONS7S8FINALITY01Smart Wallet02Sanctions03CCTP Bridge04CCTP Bridge05Smart Wallet
3+5 shape system
GatePre-condition — blocks if it failsMonitorConcurrent — observes without haltingObligationPost-settlement — reports after the factsolid = codedashed = policy
How to read this diagram
Each station on the rail represents a compliance or infrastructure event in the Cross-chain CCTP transfer path. Hover any station to inspect it. The shape tells you what kind of event it is. The ring tells you how it's enforced.
Gate Monitor Obligation| Ingress Crossing Transform Settlement Venue
This path at a glance
5 stations across 5 of 8 segments. 1 are compliance checkpoints, 4 are infrastructure.
3 code-enforced2 policy-enforced
R2 · CROSS-CHAIN CCTP TRANSFER · BASE · ETHEREUM
00
Mandate
01
Intent
02
Identity
03
Discovery
04
Negotiation
05
Transport
06
Authorization
07
Facilitation
08
Finality
09
Disposition
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKBASE
L5 APPLICATIONWALLET
L4 ACCOUNTWALLET

Step 1 · Payer Wallet (Base)Policy-Enforced

"The payer's bank app — identity verified, balance confirmed, cross-border payment instruction ready."

Self-custody wallet on Base. The payer initiates a cross-chain USDC transfer to an Ethereum address. L4 Account and L5 Application lit — same starting silhouette as R1 (single-chain), but the destination is on another chain.

Counterparty
Self (payer holds keys)
Latency
Instant · no on-chain tx yet
Finality
N/A — payment not yet submitted
Vendors
Coinbase Wallet · Coinbase Smart Wallet (ERC-4337 account abstraction — passkey-based onboarding) · EOA + ERC-4337 Smart Account (Coinbase Smart Wallet is the canonical Coinbase-operated AA surface) · Coinbase Custody Trust Company, LLC (New York limited-purpose trust company under NYDFS) · Coinbase Prime brokerage (institutional custody + execution surface) · third-party qualified custodians per integrator (Anchorage · BitGo · Fireblocks) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow; transfer-agent function is off-chain, identical on Base and Ethereum) · Coinbase Paymaster (gas-sponsorship primitive for Coinbase Smart Wallet flows · ERC-4337 paymaster contract) · Coinbase Verifications (Ethereum Attestation Service-backed attestation product binding Coinbase-verified identity attributes — country of residence, accredited-investor status, etc. — to addresses) · Securitize Markets ATS (SEC-registered ATS) · BlackRock BUIDL · other Securitize-issued RWAs (Base deployments via multichain expansion — ACRED was Ethereum-mainnet and Base availability is NOT independently confirmed)
Chain
Base (Coinbase (sole sequencer operator at launch; decentralization on roadmap))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKBASE
L3 EXECUTIONOFAC screening
◆ Enforcement Line — code-enforced at this layer

Step 2 · Sanctions ScreeningCode-EnforcedINGESTDETECTALERT

"The sanctions-screening leg before a cross-border wire — the payment halts until the list check returns."

OFAC oracle fires at L3 Execution on Base. Both source and destination addresses are screened. The path halts until the oracle returns pass. Cross-chain transfers get extra scrutiny because the destination chain may have different compliance tooling.

Counterparty
Chainalysis OFAC oracle (on-chain read)
Latency
<1s · atomic with burn tx
Finality
Pre-condition gate — blocks the burn
Vendors
Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Uniswap v4 · Aerodrome (Base-native AMM derived from Velodrome) · BaseSwap · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport between Base and Ethereum / other CCTP-supported chains) · Base Bridge (OP Stack canonical L1 ↔ L2 bridge with 7-day challenge window · L1-escape-hatch via force-inclusion) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting — ACRED is Ethereum-only; BUIDL multi-chain expansion to Base reported in public reporting but primary-source confirmation pending)
Chain
Base (Coinbase (sole sequencer operator at launch; decentralization on roadmap))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKBASE
L3 EXECUTIONCCTP (NATIVE)
L2 CONSENSUSCCTP (NATIVE)
L1 NETWORKCCTP (NATIVE)
◆ Enforcement Line — code-enforced at this layer

Step 3 · CCTP Burn (Base)Code-Enforced

"The debit leg of a correspondent banking hop — value leaves the source ledger and a burn receipt is produced for the destination to honor."

Native USDC is burned on Base. The CCTP contract destroys tokens and emits a burn event. L1+L2+L3 lit — the full stack below the enforcement line processes the destruction. Circle's attestation service observes the burn and prepares a signed attestation for the destination chain.

Counterparty
Circle CCTP burn contract (Base)
Latency
~2s · single Base block
Finality
Burn final on Base; attestation pending
Vendors
Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport between Base and Ethereum / other CCTP-supported chains) · Base Bridge (OP Stack canonical L1 ↔ L2 bridge with 7-day challenge window · L1-escape-hatch via force-inclusion) · Ethereum (via OP Stack) — Base posts batch data to Ethereum via EIP-4844 blob DA for ordering anchor; state-transition security inherits from Ethereum L1 subject to OP Stack fault-proof activation status · Coinbase Sequencer (Coinbase-operated at launch · decentralization stated as roadmap commitment · OP Stack-derived sequencing semantics) · Uniswap v4 · Aerodrome (Base-native AMM derived from Velodrome) · BaseSwap · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting — ACRED is Ethereum-only; BUIDL multi-chain expansion to Base reported in public reporting but primary-source confirmation pending)
Chain
Base (Coinbase (sole sequencer operator at launch; decentralization on roadmap))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONCCTP (NATIVE)
L2 CONSENSUSCCTP (NATIVE)
L1 NETWORKCCTP (NATIVE)
◆ Enforcement Line — code-enforced at this layer

Step 4 · CCTP Mint (Ethereum)Code-Enforced

"The credit leg of the correspondent hop — value is reconstituted on the destination ledger against the burn attestation."

Against Circle's signed attestation, native USDC is minted on Ethereum. Same three-layer silhouette as Step 3 but on a different chain. The CCTP bridge is native — no wrapped tokens, no liquidity pools, no third-party risk. Circle is the sole trust assumption.

Counterparty
Circle CCTP mint contract + attestation service
Latency
~8-15 min (Base finality + attestation)
Finality
Final on Ethereum block confirmation
Vendors
Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Ethereum devp2p / libp2p transport · EIP-4844 blob-data DA layer (canonical DA for OP Stack and other rollup-based L2s — Base, Arc, Tempo, Arbitrum, Optimism, etc.) · Ethereum Proof-of-Stake (Beacon Chain — Casper FFG finality + LMD-GHOST fork choice) — permissionless 32-ETH stake threshold; effective validator economics concentrated via Lido / Coinbase / Binance / Kraken / Figment staking pools · MEV-Boost relays (Proposer-Builder Separation — out-of-protocol; OFAC-compliant relays Flashbots / BloXroute Regulated have periodically dominated relay share) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWALLET
L4 ACCOUNTWALLET

Step 5 · Payee Wallet (Ethereum)Policy-Enforced

"The beneficiary's credit-to-account — funds arrive on the destination chain and the cross-chain payment is complete."

USDC arrives at the payee's wallet on Ethereum. L4 Account and L5 Application lit on the destination chain — same silhouette as the origin in Step 1, but on Ethereum instead of Base. The cross-chain transfer is complete. Recordkeeping obligations attach.

Counterparty
Payee wallet on Ethereum
Latency
Instant on mint confirmation
Finality
Final · irrevocable on Ethereum
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))

Resolved 5 steps across 2 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.

Coverage notes: 5 disclosed gap(s).

Other Retail Payments Paths

R1 Single-Chain USDC Transfer Circle · Wallet Providers
R3 Visa+Stablecoin Card Payment Visa · Coinbase Card
R4 P2P Wallet Transfer Self-Custodial Wallets
R5 Cross-Border Remittance Stellar · MoneyGram
R6 Merchant POS Stablecoin Accept Coinbase Commerce · BitPay
SETTLEMENT CHAINS
BaseEthereum
← All Retail Payments Paths
Resolve Your Own Path →