How Stablecoins Actually Settle

Most explanations of stablecoins stop at "it's a dollar on a blockchain." You send USDC, the recipient gets USDC, one token equals one dollar. Simple.

But when you send USDC from your wallet to someone else's, no dollars move. Not one cent leaves any bank account. The reserves sitting in BlackRock's money market fund don't shift. The only thing that changes is which blockchain address holds a claim on those reserves.

Dollars move only twice in a stablecoin's life: when it's born, and when it dies. Everything in between is just updating a ledger entry that says who's next in line to redeem.

Minting and burning are the only real settlement

When a business deposits $10 million into a Circle Account, Circle credits the deposit, then calls a permissioned smart contract function to mint 10 million USDC. The tokens appear on-chain. The dollars go into the Circle Reserve Fund, a money market fund managed by BlackRock, held primarily in short-dated US Treasury bills and overnight repo agreements at BNY Mellon.

That mint is the settlement event. Dollars entered the traditional banking system, tokens entered the blockchain. Two separate ledgers now agree that $10 million changed form.

Redemption runs the same flow in reverse. A Circle Account holder submits a redemption request, Circle burns the tokens on-chain, then initiates a bank wire. Target settlement: one business day for USD. International or cross-currency redemptions take two to three days.

But most stablecoin holders never touch this process. Circle requires KYC-verified accounts for direct redemption, with a $100 minimum for individuals. Tether's minimum is $100,000, which effectively locks retail users out entirely.

If you hold USDT on Coinbase and want dollars, you're selling on a secondary market, not redeeming from Tether. The exchange batches its own redemptions with the issuer at institutional scale.

So the vast majority of stablecoin "settlement" is secondary market trading between parties who all hold claims on the same reserve pool. The actual dollars don't move until someone exits to fiat.

Moving tokens across chains without a bridge

A harder settlement problem: you hold USDC on Ethereum and need it on Solana.

Third-party bridges solve this by locking tokens on the source chain and minting wrapped versions on the destination. The problem is that wrapped USDC on Solana isn't USDC. It's a claim on tokens locked in a bridge contract, and bridge contracts have lost billions to exploits. The Wormhole hack alone was $320 million.

Circle's Cross-Chain Transfer Protocol (CCTP) takes a different approach. USDC is burned on Ethereum. Circle's attestation service, running off-chain, validates the burn event and produces a signed attestation. A relayer submits that attestation to Solana, where Circle's contract mints fresh, native USDC. The transfer doesn't rely on wrapped tokens, liquidity pools, or bridge contracts holding funds.

The architectural tradeoff is trust. Third-party bridges are permissionless but introduce smart contract risk. CCTP is safer from an exploit standpoint, but Circle is a trusted intermediary in every cross-chain transfer. If Circle's attestation service goes down, cross-chain USDC movement stops.

For payment processors integrating stablecoins, CCTP is the cleaner primitive. One token, native on each chain, backed by the same reserve. But it means every cross-chain payment depends on Circle's infrastructure availability.

The finality gap

On-chain confirmation and settlement finality are different things, and the difference creates real credit risk.

A USDC transfer on Ethereum gets included in a block within about 15 seconds. At that point, most wallets show the transaction as confirmed. But Ethereum's proof-of-stake consensus requires two epochs, roughly 12 to 15 minutes, before a transaction reaches finality. Before finality, a chain reorganization could theoretically reverse the transaction.

Solana is faster. Slot time is about 400 milliseconds, and the chain reaches "optimistic confirmation" quickly. But exchanges typically wait for 31 confirmations, around 12 to 15 seconds, before crediting a deposit.

Compare this to traditional payment rails. An ACH transfer settles in one to two business days but can be reversed for 60 days. A wire transfer settles same-day with no reversal. A card authorization holds funds instantly but doesn't settle for one to two days.

Stablecoins sit in an unusual position: fast confirmation, moderate finality, and no reversal mechanism. Once a transaction is final on-chain, there's no chargeback and no dispute process. If you sent USDC to the wrong address, the money is gone.

Visa's stablecoin settlement pilot uses USDC on Solana and Ethereum for merchant payouts. They wait for chain-specific finality thresholds before considering settlement complete. The operational question for any payment processor is the same: how many confirmations do you require before you treat the funds as settled? Too few and you absorb reorganization risk. Too many and you slow down a system that's supposed to be faster than wires.

Two ledgers, one reserve

The simplest way to understand stablecoin settlement is that it operates on two ledgers simultaneously.

The blockchain ledger tracks who holds tokens. Transfers are fast, global, and permissionless. Anyone can send USDC to anyone with a wallet address, at any time, on any supported chain.

The banking ledger tracks who holds dollars. The reserve pool sits in regulated accounts. Dollars enter through minting, leave through redemption, and don't move in between.

Between those two ledgers sits the issuer. Circle or Tether. They are the bridge between on-chain token ownership and off-chain dollar claims. When you hold USDC, you don't hold dollars. You hold a token that Circle promises to redeem for dollars, subject to their terms of service, KYC requirements, and operational capacity.

The GENIUS Act, signed in July 2025, now requires stablecoin issuers to maintain 1:1 reserves in cash, Treasury bills, or agency debt, with monthly public attestations and federal or state licensing. Algorithmic stablecoins, the kind that maintain their peg through software rather than reserves, are explicitly barred.

That regulatory framework makes the issuer's bridge more trustworthy. It doesn't eliminate the fundamental architecture: two ledgers, one reserve, and an issuer who promises to keep them in sync.