Confirmation Rule

Overview

Meaning and scope

A confirmation rule is the explicit condition a payment system uses to decide when an observed blockchain transaction has enough network evidence to advance to a later payment state. It can require a specific block count, finalized checkpoint, conflict-free interval, transaction status, or network-specific combination. The rule should be separate from amount matching and business fulfillment so each decision remains explainable.

Mechanism and operation

A Confirmation Rule translates blockchain evidence into a state-transition condition. For a proof-of-work asset, the rule can require a defined number of blocks after inclusion. For a deterministic-finality network, it can require authenticated finalized status. Provider configuration can expose Required Block Confirmations for each supported network. The transaction must also pay the correct asset, amount, destination, and reference and must have succeeded under the chain’s execution model. A rule should define behavior for replacement, reorganization, provider disagreement, and Maximum Confirmation Wait. Without exception states, a delayed transaction can remain stuck indefinitely or be accepted inconsistently.

Practical payment example

A business applies its own network-specific confirmation rule instead of treating every visible block inclusion as settlement.

Operational checks

The active rule and evidence should be stored with the payment. Rules should be expressed as machine-readable configuration with test cases, not only prose. A rule can include minimum depth, finalized state, successful execution, conflict absence, maximum wait, and amount tier. Simulations using reorganized blocks, delayed providers, and duplicate callbacks help prove that the implementation follows the documented policy.

Distinctions and limits

One confirmation on Bitcoin, Ethereum, TON, or Solana does not represent the same security model or elapsed time. Changing policy later should not make historical acceptance decisions impossible to reconstruct.

Related reading

Related definitions: Required Block Confirmations, Maximum Confirmation Wait.