Maximum Confirmation Wait

Overview

Maximum Confirmation Wait is an operational timeout around the confirmation process. It begins from a defined event such as first detection, block inclusion, or invoice expiry and ends when the system stops ordinary automated waiting.

The timeout should reflect network block intervals, typical Time to Finality, congestion, and provider-detection latency. One value should not be applied blindly across all networks.

Reaching the maximum wait does not reverse or cancel the transaction. The payment should enter a late-confirmation or manual-review state rather than being deleted.

Customer communication should explain whether the payment is still on-chain pending, under review, or no longer associated with the original quote or order. Creating a second payment without handling the first can cause duplication.

Monitoring must continue after timeout and reconcile any later Confirmed Transaction. The record should preserve the active confirmation rule, observed progress, timeout reason, and operator resolution.

Timeouts can be progressive rather than binary. A payment can first trigger a customer warning, then pause fulfillment, and finally move to manual review. Separate timers for transaction detection, first inclusion, and finality help identify whether delay comes from the payer, network fee, consensus, provider, or merchant processing.

The maximum should be reviewed using observed percentiles rather than averages. If a meaningful share of valid transactions regularly exceeds the timeout, the policy is creating support load rather than identifying exceptional delay.

A timeout policy should also state whether the original price, inventory reservation, and customer order remain valid during later manual investigation.

The timeout should identify whether a replacement payment session may be created and how the original transaction remains linked.