Bitcoin confirmations measure the transaction’s inclusion relative to the chain tip. Coinvay’s current Bitcoin policy requires six confirmations before its invoice verifier accepts the payment. A merchant should communicate the waiting state clearly without converting that count into a guaranteed time estimate.
Why broadcast is not completion
A transaction can be visible to a wallet or mempool service before it is included in a block. The customer may call that sent, but the invoice still lacks the required chain evidence. Inclusion and subsequent confirmations are additional steps.
For a high-value equipment order, the merchant can reserve stock while the payment is pending and release shipment after verified settlement. This separates a useful customer-service action from an irreversible fulfillment decision. A screenshot is not a substitute for confirming the transaction’s actual state.
Match the correct output and block
Bitcoin transactions can contain several outputs. Coinvay checks for an output to the quoted recipient with the exact expected amount, then checks the canonical block information and confirmation count. A transaction’s total value is therefore not necessarily the amount that paid a particular merchant.
A customer’s transaction might include change returning to their own wallet. Staff should not interpret that change output as an additional invoice payment. Use the receiving output and order reference when reconciling a receipt, rather than adding every amount shown in an explorer view.
Support delays without weakening the rule
Inclusion timing depends on network conditions and the transaction’s fee policy. If the invoice is waiting, collect the hash, confirm the receiving output and inspect the current chain state. Do not promise that six confirmations always means exactly sixty minutes.
A quote’s price window is a separate question from later confirmation accumulation. If a transfer was mined outside the permitted window or for a different amount, a support review may be needed. Increasing the displayed confirmation count cannot correct an incorrect asset, recipient or quote match.
Practical checklist
- Tell buyers that broadcast, inclusion and confirmation are distinct.
- Reconcile the merchant’s output rather than the transaction total.
- Use a pending state while the confirmation policy is unmet.
Common questions
Can Bitcoin blocks arrive at perfectly regular intervals?+
No. Block production is not a precise customer-service timer. Avoid fixed completion promises and let the actual chain evidence determine payment state.
Does a confirmed transaction automatically pay any invoice with that hash?+
No. The verifier must match the relevant output, recipient, exact amount and payment window. Reusing evidence must not create a second successful sale.
Sources and further reading
Primary references and Coinvay product documentation. Check the linked pages for current details.
AI-assisted drafting, published by Coinvay. Examples are illustrative. Read our editorial approach.