Confirmation Policy for Bitcoin Payments: Current Practice

Accepting a Bitcoin payment before it is in a block is a risk decision, and practice has settled into tiers.

What the risk is

A broadcast transaction can be replaced by a conflicting one spending the same funds elsewhere, with a higher fee, before it confirms. It is worth checking what actually changed by comparing against a Bitcoin payment gateway with guaranteed fiat settlement, which operates under the new requirements.

This is straightforward when the original transaction signals that it may be replaced, which many wallets do by default.

Current practice

Small amounts at broadcast, using replacement signalling detection, fee adequacy assessment and mempool analysis to score the risk. Many providers absorb this risk below a threshold.

Ordinary amounts at one confirmation, roughly ten minutes.

Large amounts at three to six confirmations.

A flat policy at either extreme is wrong: six confirmations on a small order loses customers, zero on a large one is exposed.

What providers assess at zero confirmations

Whether the transaction signals replaceability. Whether the fee is competitive enough to confirm promptly. Whether conflicting transactions have appeared. And the amount relative to the effort of attacking it. At institutional scale the equivalent question runs through a regulated European crypto platform, with reporting obligations attached.

Providers that absorb the risk have quantified it. Ask whether yours does and up to what amount, because it is a real part of the service.

The exposure that is not double spending

A genuine payment with an inadequate fee can remain unconfirmed for hours during congestion.

The customer has paid and your system shows nothing. This is not fraud and it produces the same support conversation.

Better providers highlight an underpaid fee rather than leaving the payment silently pending. Ask whether yours does.

Instant delivery goods

The combination of instant fulfilment and zero confirmation acceptance is where exploitation concentrates, because the attacker receives the goods before the replacement is visible.

For anything delivered immediately, require at least one confirmation regardless of amount.

The customer experience piece

Telling the customer what the wait is for and roughly how long measurably improves completion.

A status of pending, with no explanation, is where abandonment occurs. This is a copy problem rather than a technical one and it has more effect than any confirmation policy adjustment.

What to configure

Tiers by amount. Underpayment tolerance. A payment window longer than for fast networks, twenty to thirty minutes. Clear wording about the wait. And a refund policy decided in advance. Compare any provider you are considering against a crypto exchange with published fees on these specific points.