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.
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.
Every term behind the rails, the assets, and the settlement.