Confirmation policy is a risk decision, not a protocol requirement. For a small in-person purchase, some merchants accept a transaction the moment it appears in the mempool (zero-confirmation), accepting a small risk of a rare double-spend attempt in exchange for speed; for larger amounts, waiting for one or more block confirmations reduces that risk substantially, at the cost of a short wait. Lightning payments settle near-instantly and sidestep this trade-off for smaller amounts entirely.
Because bitcoin's price relative to local currency can move meaningfully within hours, many merchants use a payment processor that quotes a price locked for a short window (commonly around ten to fifteen minutes) and settles the merchant's payout in local currency automatically, isolating the business from price movement between sale and settlement.
Businesses that choose to hold bitcoin received from sales are taking on the same price risk as any holder, and should treat that as a deliberate treasury decision rather than a side effect of accepting payments, it is not something this lesson recommends one way or the other.
In most jurisdictions, receiving bitcoin as payment for goods or services is treated as ordinary business income at its market value at the time of the transaction, and any later disposal (e.g. selling or spending it) may separately trigger capital gains or losses, similar to any other property. This varies significantly by country, so this is general information, not tax or accounting advice; a local accountant should be consulted for specifics.
Explain more simply
A business that accepts bitcoin needs to decide two practical things: how long to wait before treating a payment as final, and what to do about the price moving between the moment of sale and the moment they actually use or convert the funds.
Many businesses solve the price question simply by converting bitcoin to local currency immediately after each sale, so they never hold price risk at all, others choose to hold some or all of it.
Real-world analogy
Accepting bitcoin is similar to accepting a foreign currency at a shop: you can either hold onto it and bear the exchange-rate risk, or convert it to your home currency at the register and let a processor handle the exchange, just as many shops already do with foreign cash or cards.
Key facts
- Confirmation policy is a merchant risk decision, not fixed by the protocol.
- Payment processors can lock a short-window price and settle in local currency automatically.
- Bitcoin received for sales is generally treated as ordinary income at the time of the transaction; specifics vary by jurisdiction.
Common misconception
“A business that accepts bitcoin is automatically speculating on its price.”
Most merchant tools convert bitcoin to local currency within minutes of each sale, so accepting bitcoin as a payment method and choosing to hold it as an investment are two separate, independent decisions.[3]
Go deeper
Zero-confirmation acceptance is generally considered reasonable for low-value, in-person transactions where the merchant can visually confirm the customer did not immediately leave and where the payment was broadcast without RBF signalling, since both factors make a same-second double-spend attempt harder to execute unnoticed.
For accounting, tracking the local-currency value of every bitcoin transaction at the time it occurred, commonly called cost basis for later disposals, is essential and is exactly the kind of record-keeping ordinary point-of-sale and payment-processor software is built to automate.
Quick check
Answer every question correctly (100%) to complete this lesson.
1.How do many merchants avoid price risk on bitcoin payments?
2.Is deciding a confirmation policy a Bitcoin protocol rule or a business decision?
Counts towards your streak in this browser.
Extra exam questions
Every question here counts towards your accuracy, XP and rank. No guessing: every answer is explained.
Quick check
Answer every question correctly (100%) to complete this lesson.
1.What is zero-confirmation acceptance?
2.Why might a merchant wait for block confirmations on a large purchase?
3.How do Lightning payments compare to on-chain zero-confirmation payments for small purchases?
4.What does a payment processor typically do for a merchant accepting bitcoin?
5.Why does bitcoin's price volatility matter to a merchant even though a sale is complete the moment payment is received?
6.How is bitcoin received for goods or services generally treated for tax purposes?
7.What additional tax event can occur after a business holds bitcoin received from sales?
8.What is 'cost basis' in the context of accepting bitcoin payments?
Counts towards your streak in this browser.
Sources
- Bitcoin developer documentation, bitcoin.org / Bitcoin Optech glossary
- mempool.space REST API, mempool.space (open source)
Live block, mempool, fee, mining and Lightning figures shown on this site come from this API.