What are network confirmations and finality
A confirmation is each block added to the chain after the block containing a transaction; more confirmations mean a lower risk of reversal.
When a transaction is included in a block, it has one confirmation. Each subsequent block adds another. On networks with probabilistic consensus, such as Bitcoin, a recent block can occasionally be replaced by a competing chain (a reorganisation, or reorg), and transactions in it may disappear. Every new block on top makes this less likely.
Bitcoin produces a block roughly every ten minutes on average, and waiting for six confirmations is a long-standing convention for large amounts. Many services credit smaller payments after fewer. Ethereum after the move to proof of stake has explicit finality: blocks become finalised after two epochs, on the order of 13 minutes, and after that reverting them would require a massive, provable attack.
Other networks have their own terms. Solana exposes commitment levels: processed, confirmed and finalized. TON reaches finality within seconds. TRON uses delegated proof of stake with a set of super representatives, and blocks become irreversible once enough of them have built on top. The common idea is the same: a merchant should credit a payment only once the risk of it being undone is acceptable for the amount.
The typical mistakes are crediting an order the moment a transaction appears in the mempool (it can be replaced or never confirmed), relying on a single node that may be out of sync or lying, and showing customers “payment failed” while the transaction is simply waiting for confirmations. A good checkout explains that the payment is seen and is being confirmed.
Moonvex credits a payment only after two independent node providers confirm it, and then notifies the merchant via a webhook and in the Telegram bot.