# Accept Bitcoin Payments: Pricing the Volatility Out > How a business takes Bitcoin without taking the price risk, what confirmation policy to use, and where Bitcoin still makes sense against a stablecoin. - Source: https://cryptounderthehood.com/accept-bitcoin-payments-business/ - Published: 2026-08-01 - Author: Ivan Kruse - Publication: Crypto Under the Hood — How crypto payment infrastructure actually works - Topic: bitcoin payments - Tags: bitcoin, payments, risk --- The objection to accepting Bitcoin payments has always been the same: the price moves. The answer has also been the same for years and it is well understood, which is that you do not have to hold it. The version of this that operates in production is [a Bitcoin payment gateway with guaranteed fiat settlement](https://collectnexchange.cy/services/accept-bitcoin), and their documentation fills most of the gaps below. ## The mechanism that removes the risk A payment processor quotes the customer an amount of Bitcoin equivalent to your fiat price, guarantees that fiat amount to you, and converts on receipt. You invoice a hundred euros, you receive a hundred euros minus the fee, regardless of what Bitcoin did in between. The processor carries the risk of the movement between quote and confirmation. It prices that risk into the fee and hedges it. This is the same arrangement as any other merchant acquiring product. If a provider does not guarantee the fiat amount, you are carrying that risk yourself, and for a business with normal margins that is an unnecessary position. Check which model applies before integrating. ## The confirmation problem, specific to Bitcoin Bitcoin blocks arrive roughly every ten minutes, and the interval is highly variable. A payment might confirm in two minutes or in forty. This creates a customer experience problem that other chains do not have. A customer who has paid is waiting, and the wait has no reliable estimate. Three approaches are in use. **Zero-confirmation with risk scoring.** Accept at broadcast for small amounts, using replace-by-fee signalling and mempool analysis to assess double-spend risk. Fast, appropriate below a threshold, carries a small residual risk that the processor usually absorbs. **One confirmation.** Typically ten minutes. Reasonable for most e-commerce amounts. **Six confirmations.** An hour. Appropriate for large amounts, poor for anything retail. A tiered policy is correct. A flat six-confirmation policy on a thirty euro order is a checkout that customers abandon. ## The fee deduction problem Bitcoin wallets frequently deduct the network fee from the sent amount when the user selects "send max" or when the wallet is configured that way. The result is a payment short by the fee. Property transactions surface the same constraint more sharply, and [a crypto acquiring provider with fiat settlement](https://collectnexchange.cy/business-solutions/crypto-acquiring) exists for it. During a busy period that fee can be several euros. Configure a tolerance band, and state on the payment page that the fee is payable in addition to the amount. ## Lightning, and whether to bother Lightning settles in seconds at negligible cost and removes both the confirmation wait and the fee deduction issue. The constraint is customer adoption. In most business contexts, the proportion of customers who can pay over Lightning is small. For consumer-facing businesses in markets where it has traction, it is worth supporting. For B2B invoicing it is usually not yet. If your processor offers it at no additional integration cost, enable it. If it requires meaningful work, defer until you see demand. ## Bitcoin against stablecoin for business payments For invoicing, a stablecoin is simpler: no volatility between quote and payment, no confirmation variance, lower fees on the common networks. Bitcoin remains relevant where the customer holds Bitcoin and does not want to convert, which in practice is a meaningful share of individual customers and a small share of businesses. The correct answer for most merchants is to support both and let the customer choose. The incremental cost of supporting a second asset through a processor is close to zero. ## What to configure before launch Confirmation tiers by amount. Underpayment tolerance. Payment window, which for Bitcoin should be longer than for fast chains, twenty to thirty minutes rather than ten. Clear customer-facing copy about the wait. And a refund policy, since refunding Bitcoin at a later price is a decision rather than a default. A provider set up to [accept Bitcoin payments with guaranteed fiat settlement](https://collectnexchange.cy/services/accept-bitcoin) handles the hedging, and your job reduces to setting the policies above sensibly. ## The honest summary Accepting Bitcoin is a solved operational problem. The reasons to do it are customer demand and the absence of chargebacks, not the asset. Anyone accepting it as a treasury position has made a different decision, and that one should be explicit. --- This article explains how something works. It is not financial advice. Canonical HTML version: https://cryptounderthehood.com/accept-bitcoin-payments-business/