Confirmation Risk

Overview

Meaning and scope

Confirmation risk is the possibility that a payment considered sufficiently confirmed is later reversed, reorganized, delayed, or never becomes final. Confirmation Risk must specify the objective or asset exposed, causal scenario, threat or dependency, likelihood basis, impact dimensions, time horizon, existing controls, and accountable owner.

Mechanism and operation

Competing blocks, consensus attacks, network congestion, invalid replacement transactions, or protocol-specific finality delays can change the expected outcome. A fixed confirmation count can be inappropriate when security, hash power, validator behavior, or finality rules differ across assets. Payment systems should use asset-specific policies, monitor reorganizations and conflicts, delay irreversible fulfillment when necessary, and define responses for exceptional network conditions. Confirmations reduce probability of reversal but do not always equal deterministic finality. Confirmation policies should reflect network-specific finality and transaction exposure, because one fixed count cannot represent equal risk everywhere. For Confirmation Risk, the assessment should evaluate the possibility that a payment considered sufficiently confirmed is later reversed, reorganized, delayed, or never becomes final.

Practical payment example

An exchange credits a deposit before the blockchain reaches its chosen finality threshold. Risk management measures exposure to reorganizations and conflicting transactions under that early-credit decision.

Operational checks

The assessment record should separate observed evidence supporting the possibility that a payment considered sufficiently confirmed is later reversed, reorganized, delayed, or never becomes final from assumptions, state the time horizon and existing controls, and identify who owns any remaining exposure. Monitoring should test whether the conditions described in the possibility that a payment considered sufficiently confirmed is later reversed, reorganized, delayed, or never becomes final have changed enough to require a new rating, treatment, or approval.

Distinctions and limits

Confirmation risk arises when a recipient acts before a blockchain transaction has reached an appropriate level of settlement confidence. Risk varies by network, transaction value, fee, block position, consensus design, recipient exposure, and current network conditions.

Related reading

Related definitions: Confirmation, consensus attacks.