What Is a Confirmation Threshold for Business Crypto Payments, and How Do You Set One?

14 October 2026

A confirmation threshold is the number of block confirmations you require before treating a crypto payment as final. For a business, setting the right threshold balances the risk of accepting a double-spend attempt against the inconvenience of making customers wait. In practice, most merchants choose between 1 and 6 confirmations depending on the payment value, the blockchain used, and whether they can reverse a mistake.

Why Confirmations Matter

When a customer sends a crypto transaction, it first appears in the mempool as unconfirmed. Miners then include it in a block. The first confirmation comes when that block is mined. Each subsequent block built on top of it adds another confirmation. With each confirmation, the work required to reverse the transaction grows exponentially, because an attacker would need to re-mine that block and all blocks after it.

For a low-value coffee purchase, waiting for one confirmation might be acceptable. For a high-value equipment sale, you might wait for six confirmations on Bitcoin or a lower number on a faster chain. The risk is that a customer sends a transaction that appears valid, you release the goods, and then the transaction is replaced or orphaned before it gains enough confirmations.

Factors that affect your threshold

Transaction Value

The higher the payment amount, the more attractive it is to an attacker with enough hashing power to attempt a double-spend. A common rule of thumb is to require more confirmations for larger values. Many payment processors let you set different thresholds for different invoice amounts.

Blockchain speed and finality

Different blockchains produce blocks at different rates and have different security assumptions.

• Bitcoin (on-chain): Blocks arrive roughly every 10 minutes. Six confirmations takes about an hour. This is the traditional standard for irreversible settlement, but many businesses accept lower numbers for small amounts.
• Ethereum and EVM chains: Blocks arrive every 12 - 15 seconds. Finality is usually reached after 12 - 30 confirmations on Ethereum, but many merchants accept 1 - 2 for low-value payments. On faster chains like Polygon or BNB Smart Chain, a few confirmations can be enough.
• Lightning Network: Payments are settled instantly and do not use block confirmations in the same way. A Lightning payment is considered final once the invoice is settled. This is covered in the page on Lightning invoices.

Your ability to reverse

If you sell digital goods that can be revoked (like API access or streaming subscriptions), you can afford a lower threshold because you can cut off access if the payment fails. If you sell physical goods or services that cannot be taken back, you should wait for more confirmations.

How to Set a Confirmation Threshold in Practice

If you use a self-hosted solution like BTCPay Server, you can configure thresholds per store or per invoice. The general procedure is:

1. Decide on a risk profile for your business. List the typical value ranges you expect. For example: under $50, $50 - $500, $500 - $5000, above $5000.

2. Choose a minimum confirmation count for each range. A common starting point is:

3. Under $50: 0 confirmations (show as paid but wait for 1 before delivering high-value digital goods)
4. $50 - $500: 1 confirmation
5. $500 - $5000: 3 confirmations
6. Above $5000: 6 confirmations

These are not rules. You should adjust based on your own tolerance and the blockchain you accept.

1. Configure the threshold in your payment processor. In BTCPay Server, you set the "minimum number of confirmations" in the store settings. You can also override it per invoice. Some hosted processors let you set a default and then manually review large payments.

2. Test with a small payment. Send a test transaction from a wallet you control. Check that the invoice status changes from "unconfirmed" to "paid" only after the required number of confirmations. Make sure your order fulfillment system does not trigger before that point.

3. Monitor for stuck or dropped transactions. A transaction that remains unconfirmed for hours may never confirm. Your payment processor should have a timeout setting. After a certain period, you should cancel the invoice and ask the customer to resend. The page on stuck unconfirmed payments covers what to check.

What about zero-confirmation payments?

Some merchants accept unconfirmed transactions, called "zero-conf" payments. This is common for very small amounts or for trusted customers. The risk is that the transaction can be replaced with a different one that spends the same inputs (a double-spend attempt). For on-chain Bitcoin payments, zero-conf is not recommended for anything above pocket change. For Ethereum and similar chains, the risk is lower because the mempool rules differ, but it still exists.

If you accept zero-conf, you should at least verify that the transaction has a sufficient fee to be mined quickly and that it is not signaling replace-by-fee (RBF) on Bitcoin. Even then, you are trusting that no one will try to double-spend.

A Note on Accounting and Reconciliation

Your accounting system should record the invoice as "pending" until the confirmation threshold is met. Once the payment reaches the required confirmations, the invoice becomes "settled" and you can recognize revenue. The page on crypto payment reconciliation covers how to match transactions by hash and amount. Do not mark a payment as received until your threshold is satisfied.

Summary

Set your confirmation threshold based on the payment amount, the blockchain's speed and security, and your ability to reverse the transaction if something goes wrong. Start conservative and lower the threshold only after you understand the risks. For most small to medium businesses accepting Bitcoin on-chain, one confirmation is reasonable for amounts under a few hundred dollars, and three to six confirmations for larger sums. For faster chains or Lightning, you can accept lower numbers or instant settlement.

Back to crypto payments