A confirmation policy is the rule for when a blockchain payment counts as paid: how many block confirmations, on which chain, before the invoice flips to settled. One confirmation on Bitcoin is nearly forever; one on a busy chain can be reorganized minutes later.
The policy is a dial between speed and certainty. Tighten it and buyers wait less; loosen it and double-spend attacks cost less. The right setting depends on ticket size: a coffee can clear at first confirmation, a car should wait for finality.
A confirmation policy is the rule for when a transaction counts as settled: how many blocks deep a transaction must sit before a system treats it as final and acts. One confirmation means the block containing it; six means five more blocks built atop it. Each additional block makes reversal exponentially harder, so depth is confidence purchased with time.
The right number depends on the chain's economics and the value at stake. Exchanges historically waited six blocks on Bitcoin because rewriting that much proof-of-work is expensive. Fast-finality chains quantify differently: some blocks are final the moment the network commits them, and reorgs beyond the finality checkpoint are not accidents but consensus failures.
For payments the policy is a business dial: accept at first confirmation for small tickets where a double-spend attempt costs more than the goods, wait for finality on large ones. Serious checkout systems state the policy per asset, and the buyer sees the same state the merchant acts on, which removes the disagreeing-statuses class of support ticket.
A tokenized stock settles on an L2 with fast finality, so checkout acts within seconds. The same platform's Bitcoin payments show a confirmation counter to the buyer, with the policy's threshold visible, so both sides watch the same finish line.
Merchants set the confirmation policy per store and per asset on U.CASH, with sensible defaults per chain; buyers see exactly what counts as paid before they send.
Merchants feel the policy as the speed-vs-safety dial on every crypto checkout: digital goods can ship at first confirmation, physical goods comfortably wait, and large tickets wait for finality. U.CASH states each asset's policy on its page, so the dial is a fact rather than a setting you discover in production. On communicating it: state the policy where the buyer waits rather than in a doc they never open. A line that says settling, typically seconds on this asset turns the confirmation pause from a doubt into a countdown, and support volume follows that distinction almost mechanically.
Every term behind the rails, the assets, and the settlement.