Merchant Confirmation Policy

Overview

Merchant confirmation policy is the documented framework a merchant uses to decide how much blockchain confirmation or finality is required before accepting payment or fulfilling an order. In an operational payment system, this field or policy should have one authoritative meaning across the API, checkout, webhook, ledger, and support tools.

The policy can vary by network, asset, amount, customer risk, product type, transaction replaceability, and operational reversibility. It may include low-value exceptions, high-value holds, and finality-based rules for proof-of-stake networks. In practice, the system should preserve the original request, the observed blockchain or checkout evidence, and every status change that affects this value. This makes support investigations and financial reconciliation possible without reconstructing the payment from screenshots or mutable client data.

The merchant should configure thresholds centrally, version changes, monitor reorganizations, cap provisional exposure, and ensure customer-facing status messages match the backend policy. Exceptions should require authorized review and leave an audit trail. The implementation should use exact asset precision, authenticated server-side updates, and idempotent processing wherever repeated API calls, blockchain observations, or webhook deliveries can occur.

It is broader than an invoice confirmation threshold, which is the concrete requirement applied to one invoice, and broader than a network-based threshold, which focuses on differences between chains. It should be interpreted alongside Invoice Confirmation Threshold, Low-Value Confirmation Policy, Network-Based Confirmation Threshold. These concepts belong to the same workflow, but each answers a different operational question and should not be collapsed into one ambiguous field.

A policy may permit one confirmation for small digital goods, three for ordinary orders, and explicit finality plus review for high-value settlement. The practical test is whether a merchant can explain how the value was produced, verify it independently, and apply the same rule consistently when the payment is delayed, duplicated, partially paid, refunded, or reviewed manually.