Confirmation Override

Overview

Confirmation Override changes how the business interprets confirmation evidence without changing the transaction’s actual block depth or finalized status. The original evidence must remain visible.

An override can be used during provider outages, manual review, high-value risk escalation, or a known network incident. It can also require more confirmations rather than only reducing the threshold.

The action differs from Manual Confirmation Acceptance. Manual acceptance is a specific business decision to accept a payment, while an override changes the rule or threshold applied to that case.

Permissions should be separated from ordinary support access. The record needs actor, reason, prior rule, new rule, time limit, transaction evidence, and affected downstream actions.

Overrides should be rare and measurable. Repeated use indicates that the normal Confirmation Rule may be misconfigured or that the system lacks an appropriate exception state.

An override needs a defined scope. It can apply to one transaction, one network incident, a customer segment, or a limited time window. Broad permanent overrides should be converted into normal policy changes after review. Automatic expiry prevents a temporary emergency setting from silently becoming the long-term production rule.

Reports should distinguish override-created acceptance from normal confirmation acceptance. This lets finance quantify exposure and lets risk teams determine whether exceptional decisions produced higher loss or support rates.

High-value overrides can require dual approval and automatic notification to risk or finance teams before any balance or fulfillment action executes.

Every override should also identify which downstream actions were permitted, delayed, or blocked by the exception. This prevents one manual decision from being interpreted differently by balance, fulfillment, withdrawal, and accounting systems.