Most explainers stop at "it's a dollar on a blockchain." That tells you nothing about where settlement risk lives, who holds the float, or why a stablecoin transfer behaves differently from a card swipe. To build on this rail, you need to separate four distinct events: mint, transfer, redemption, and the attestation that backs the whole thing. They do not happen on the same system, and conflating them is how teams misprice their counterparty exposure.
We will use USDC as the worked example because Circle publishes enough mechanical detail to be precise. The pattern generalizes to other fiat-backed tokens.
The four events, kept separate
A stablecoin is two systems bolted together. There is an off-chain reserve held by the issuer in real banks and money market funds, and there is an on-chain token whose supply is supposed to track that reserve one for one. Mint and redemption are the bridge between the two. Transfer happens entirely on-chain and never touches the reserve.
Keep that boundary in mind, because the off-chain leg carries banking-hours, counterparty, and redemption risk, while the on-chain leg carries settlement-finality and smart-contract risk. They are not the same risk and they do not clear on the same clock.
Mint: fiat in, token out
A Circle Mint client wires US dollars to a Circle bank account. Once the wire lands and clears, Circle credits the reserve and issues an equal amount of USDC to the client's on-chain wallet. The token did not exist a moment earlier; minting is the act of creating supply against a confirmed deposit.
The constraint here is that the front of this process runs on traditional banking rails. Your wire still settles on bank hours and bank cutoffs. The "instant" reputation of stablecoins applies to the transfer leg, not to getting newly minted tokens for the first time.
Transfer: the part that is actually fast
Once tokens exist, moving them is a single on-chain transaction. You sign a transfer, it lands in a block, and authorization and settlement are the same event. There is no separate clearing step, no batch window, and no acquirer or correspondent bank in the path.
This is the structural break from card and ACH. The token moves, the ledger updates, and the recipient holds value the moment the transaction reaches finality. Speed and finality depend entirely on the chain, which we will quantify below.
Redemption: token out, fiat in
Redemption reverses the mint. A client sends USDC back to Circle, Circle burns those tokens so they are permanently removed from circulation, and Circle wires dollars from the reserve to the client's external bank account. Burning is irreversible; the supply genuinely shrinks.
Note that redemption at par one for one with the issuer is generally a privilege of direct Circle Mint clients, such as exchanges, institutions, and banks. Everyone else exits through a secondary market or an exchange, which is why a token can trade slightly off a dollar even when the issuer stands ready to redeem at par. The peg you see on screen is a market price, not the redemption guarantee.
Attestation: why anyone trusts the number
The token supply is only as good as the reserve behind it. Circle holds the majority of USDC reserves in the Circle Reserve Fund, an SEC-registered 2a-7 government money market fund holding cash, short-dated US Treasuries, and overnight Treasury repurchase agreements. A Big Four firm, Deloitte, publishes a monthly third-party report attesting that reserve value meets or exceeds USDC in circulation, prepared under AICPA attestation standards.
Read the word "attestation" precisely. These are signed agreed-upon-procedures reports on a stated date, not full audits. They verify the reserve total, its composition, and the issuance figure at a point in time. We cover what that does and does not protect against in Module 4 on reserves, redemption, and depegs.
A worked example, side by side
Take a $100,000 payment from a US business to a supplier, settled three ways.
Card. The buyer authorizes in under two seconds. But authorization is not settlement. Clearing files move a few hours later, then net settlement runs the issuer-to-acquirer-to-merchant chain, and the merchant typically receives funds one to three business days afterward. The transaction is reversible for months through chargebacks, and interchange and scheme fees come out of the merchant's receipts.
ACH. The buyer originates a batch entry. ACH settles in one to three business days, processed in batches rather than in real time, and credit entries remain reversible within defined return windows.
USDC on-chain. The buyer signs one transfer of 100,000 USDC. On Ethereum, the transaction lands in a block in seconds and reaches full finality after roughly 12.8 minutes, two epochs, at which point reversal would require an attacker to destroy an enormous amount of staked ETH. On a faster chain like Solana the transfer confirms in seconds for well under a cent in fees. Once final, it is final; there is no chargeback mechanism baked into the rail.
The contrast is not merely "faster." Card and ACH split a payment across authorization, clearing, and net settlement on a batch clock, with reversibility designed in. The on-chain transfer collapses those into one irreversible event. That irreversibility is a feature for treasury operations and a liability for consumer disputes, which is the tradeoff Module 6 on regulatory wrappers picks up.
What this means for builders
The slow, risky parts of a stablecoin are the off-chain edges, mint and redemption, where you still depend on banks, banking hours, and the issuer's willingness and ability to honor par. The on-chain transfer in the middle is the genuinely improved primitive: fast, final, and cheap, with settlement and clearing fused.
So when someone tells you a stablecoin "settles instantly," ask which event they mean. Map your own flow to the four steps, locate where banking hours and counterparty risk actually bite, and you will price the rail correctly instead of buying the marketing.