How Do “Zero-Confirmation” Transactions Pose a Risk to Merchants?

A zero-confirmation transaction is one that has been broadcast to the network and received by a merchant but has not yet been included in a confirmed block. The risk to the merchant is that the sender could attempt a "double-spend" attack.

By broadcasting a conflicting transaction with a higher fee, the sender could incentivize a miner to include the new transaction instead, effectively reversing the original payment and leaving the merchant with an unconfirmed, invalid transaction.

Why Is Full RBF Controversial among Some Cryptocurrency Users and Merchants?
How Does a Double-Spend Transaction Work in the Context of a 51% Attack?
Why Might a Miner Prioritize a Zero-Fee Transaction over a Low-Fee One?
What Is a “Race Attack” and How Does It Differ from a Standard Double-Spend?
How Does Network Congestion Affect Confirmation Time and Double-Spend Risk?
How Can a User Replace a Zero-Fee Transaction with a Higher-Fee One?
How Does Transaction Confirmation Time Impact the Risk of a Double-Spend?
How Do Zero-Confirmation Transactions Increase the Risk of a Double-Spend?

Glossar