How to Choose CCTP Fast vs Standard Transfer (2026)

Circle's Cross-Chain Transfer Protocol (CCTP) gives you two attestation speeds for native USDC burns — and picking the wrong one costs either minutes or basis points.

Choose CCTP Fast Transfer when seconds matter and you can pay the source-chain Fast fee (0–13 bps as of September 2026) plus a buffered maxFee. Choose CCTP Standard Transfer when cost and hard finality win: 0 bps protocol fee on published chains, no Fast Transfer allowance burn, and attestations after finalized blocks.

Key Takeaways

• Fast uses confirmed finality (minFinalityThreshold ≤ 1000); Standard uses finalized (≥ 2000).
• Fast protocol fees run 0–13 bps by source chain; Standard is 0 bps on published chains.
• Fetch live fees with GET /v2/burn/USDC/fees — never hardcode.
• If maxFee is too low, the burn reverts or Fast can degrade to Standard.
• Fast consumes Circle's global Fast Transfer allowance; Standard does not.
• Some source chains have no Fast mode because Standard is already seconds.
• Native gas on burn and mint is separate from the USDC protocol fee.
• Date-stamp every fee quote; Circle can change rates at any time.

What the Fast vs Standard switch actually is

CCTP burns native USDC on the source chain and mints native USDC on the destination. The switch is not a different bridge — it is the finality threshold you pass into depositForBurn.

CCTP Fast Transfer asks Circle to attest after the burn is confirmed (minFinalityThreshold ≤ 1000). Circle's docs put most Fast routes at about 8–20 seconds (Ethereum and Starknet Fast closer to ~20s; many L2s ~8s).

CCTP Standard Transfer waits for hard finality (minFinalityThreshold ≥ 2000). On Ethereum and many OP-stack L2s that often means ~15–19 minutes; Linea Standard can run 6–32 hours; Starknet Standard often 2–4 hours. See Circle's finality and block confirmations.

For the burn/mint flow itself, use how to transfer USDC between chains without a bridge. This guide only decides which mode to pick.

Named downside: Fast is not free speed. You pay a protocol fee, you consume Fast Transfer allowance, and a too-low maxFee can silently slow you back to Standard.

Fast vs Standard at a glance

Fee table: what Fast actually costs

Circle charges fees on Fast Transfers only. Standard Transfers are free at the protocol layer on the published chain list. Always pull live numbers from CCTP fees or GET /v2/burn/USDC/fees — Circle says do not hardcode.

Illustrative Fast rates from Circle's September 2026 fee table (bps on source):

So a $1,000 Fast burn from Ethereum is about $0.10 in protocol fee; the same notional Linea → Base is about $1.30–$1.40 before gas. Standard on those routes is 0 bps protocol fee.

By default the Fast fee is deducted when USDC is minted on the destination. An upfront-fee path exists so the recipient can receive the full amount — budget that in the product UX.

Gas on the source burn and destination mint is paid in the chain's native gas token, not in USDC. That is the same "second token" problem covered in why you need a second token to send stablecoins.

When Fast wins

Use Fast when the product promise is measured in seconds, not minutes.

• Checkout or game UX that cannot show a 15-minute spinner on Ethereum → Base.
• Treasury rebalances that unblock a same-session trade or liquidation.
• Routes where Standard finality is extreme (Linea 6–32h, Starknet 2–4h) and the Fast fee (13 bps / 12 bps) is cheaper than operational delay.
• You have confirmed Fast Transfer allowance headroom for the ticket size.

Pick the source chain the same way you pick a settlement network in how to choose a USDC network — fee bps and finality both move with the source.

When Standard wins

Use Standard when dollars matter more than clocks.

• Large tickets where 1–13 bps is real money (e.g. $1M × 13 bps = $1,300 on Linea Fast).
• Overnight or batch treasury moves where 15–19 minutes (or longer) is fine.
• High-volume apps that must preserve Fast Transfer allowance for customer-facing Fast paths.
• Source chains where Fast is not offered because Standard is already fast enough (Circle lists these on supported blockchains — use Standard there).

Stablecoin Insider's take: default treasury wires to Standard; reserve Fast for user-facing SLAs and named exception routes.

maxFee and Fast Transfer allowance checklist

maxFee is the maximum Fast protocol fee (in USDC subunits) you pass to depositForBurn. If the live fee exceeds maxFee, Circle documents that the source burn reverts and no USDC is burned. Separately, if maxFee sits below the Fast threshold, Fast may degrade to Standard instead of failing — which is how a "fast" button becomes a 15-minute wait.

Do this every burn:

1. Call GET /v2/burn/USDC/fees for the source/destination pair (see get the transfer fee).
2. Add a 10–20% buffer on the protocol fee when setting maxFee (Circle's own example pattern).
3. Confirm Fast Transfer allowance for the notional if you are on Fast.
4. Set minFinalityThreshold to ≤1000 (Fast) or ≥2000 (Standard) on purpose — do not leave a leftover constant.
5. Confirm you are burning native Circle USDC, not a bridged wrapper (see how to tell native USDC from bridged USDC).

Named downside: hardcoding last week's fee table is how you ship silent Standard degradation or revert storms after Circle updates rates.

Stablecoin Insider's take

Stablecoin Insider's take: treat Fast as a priced SLA, not a free upgrade. Quote the live bps and the attestation window in the product copy so operators know they are buying seconds. Keep Standard as the default for batch treasury and anything that can wait for hard finality.

What to do on Monday

Wire one config flag: cctpMode: "fast" | "standard". For Fast paths, fetch fees at least weekly (Circle's guidance), buffer maxFee 10–20%, and alert when Fast Transfer allowance drops below your peak-hour notional. For Standard paths, surface the route's average attestation time so finance is not surprised by Linea hours or Starknet multi-hour waits.

FAQ

What is CCTP Fast Transfer vs Standard Transfer?
Fast attests after confirmed blocks (minFinalityThreshold ≤ 1000, typically ~8–20s). Standard waits for finalized blocks (≥ 2000), often ~15–19 minutes on Ethereum and many L2s.

How much does CCTP Fast cost?
As of September 2026 Circle docs, Fast protocol fees are 0–13 bps by source (e.g. Ethereum 1 bps, Base 1.3, Arbitrum 1.4, Linea 13, Starknet 12). Standard is 0 bps on published chains. Always refetch live fees.

What happens if maxFee is too low?
The burn can revert with no USDC burned, or Fast can degrade to Standard when maxFee is below the Fast threshold. Buffer 10–20% above the live fee.

Does Standard use Fast Transfer allowance?
No. Only Fast consumes Circle's global Fast Transfer allowance. Standard does not.

Are gas fees included in the bps?
No. Source burn gas and destination mint gas are paid in the native gas token, separate from the USDC protocol fee.

Do all chains support Fast?
No. Some sources omit Fast because Standard attestation is already fast enough. Use Standard on those sources.

This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.