The unspent transaction output is Bitcoin's accounting atom: coins exist as discrete outputs waiting to be spent, and a payment consumes whole outputs, returning change as new ones. There is no balance anywhere, only a set of unspent tickets whose sum is what you hold.
The practical consequence is change and consolidation: every spend leaves dust change at new addresses, wallets manage the shuffle invisibly, and a wallet fragmented into many small outputs can make a large payment slower and costlier to assemble.
The unspent transaction output model is Bitcoin's accounting system: a wallet's balance is not a number in a database but the set of outputs from prior transactions that have not been spent. A new transaction consumes some of those outputs as inputs and creates new outputs, including change back to the spender. Coins are literally chains of custody, not ledger rows.
The consequences are distinctive. Spending requires selecting which outputs to consume, so a wallet holding many small outputs builds bigger transactions to pay the same amount, paying more fee for the weight. Change addresses emerge naturally: each spend can route the remainder to a fresh output, which is where Bitcoin's privacy patterns come from.
Account-model chains, by contrast, keep a global balance per address and treat a transfer as a simple decrement and increment. Neither model is strictly simpler; the UTXO one parallelizes validation cleanly and forces explicit coin management, which batch senders and payout systems feel directly.
A wallet holding four outputs of 0.4 BTC that sends 1.0 BTC consumes all four, delivers 1.0 to the recipient, and returns the change minus fees as a new output. The next payment starts from that fresh output rather than the original four.
Bitcoin checkouts on U.CASH settle to addresses derived per invoice or to an xpub the merchant controls, and the confirmation policy reads the UTXO's confirmations the way the chain actually counts.
Merchants feel UTXOs through batching and fees: a payout run to many recipients consolidates inputs efficiently, and platforms that manage output selection keep per-payment costs predictable. On the receiving side, nothing changes: the balance arrives and spends. The merchant-facing summary: on Bitcoin-family rails, balances arrive as outputs and leave as inputs, and the software manages the bookkeeping invisibly. Where it becomes visible is fee behavior on wallets with long payment histories, which is one reason platform-managed receiving with proper consolidation beats a hand-run wallet at any volume.
Every term behind the rails, the assets, and the settlement.