How bitcoin on-chain payments work for business
A customer clicks "pay with Bitcoin." What happens next is a sequence of technical steps, but for a merchant the sequence is a set of operational decisions. The protocol does the heavy lifting. The merchant chooses how to handle each stage.
Address Generation
The merchant's checkout system generates a fresh Bitcoin address for each transaction. This is not the merchant's long-term cold storage address. It is a derived address, typically from a Hierarchical Deterministic (HD) wallet. The merchant's software derives a unique address per invoice using a master seed and an index. This avoids address reuse, which harms privacy and makes reconciliation harder. The merchant must ensure address generation happens offline or on a machine that never exposes the master seed.
Customer Broadcast
The customer's wallet constructs a transaction sending the required amount to that address. The customer broadcasts the transaction to the Bitcoin peer-to-peer network. The merchant's node, or a third-party block explorer API, sees the transaction appear in the mempool. The merchant does not control broadcast timing. The customer does. The merchant's software must detect mempool presence quickly, because the customer expects feedback within seconds.
Mempool Monitoring
The merchant's system watches the mempool for any transaction spending to the generated address. This is the first confirmation that the customer has initiated payment. The merchant sees the transaction ID, the amount, and the fee rate. The merchant's decision at this stage: acknowledge the payment as "pending" or wait for on-chain confirmation. Some merchants show a "payment detected" state immediately. Others wait. The difference is trust in the mempool versus trust in a block.
Confirmation Depth Thresholds
A Bitcoin transaction is not final when it appears in the mempool. It is final only when included in a block. One confirmation means one block has been mined on top of the block containing the transaction. Merchants choose a confirmation depth threshold. For small-value items, one confirmation is common; for high-value items, three to six confirmations are typical. The threshold is a business risk decision, not a protocol requirement. The merchant's software must track the block height and count confirmations. It should also watch for chain reorganizations that could orphan the transaction block.
Settlement to cold storage
Once the confirmation threshold is met, the merchant considers the payment settled. The Bitcoin sits at the derived address, which is part of the merchant's HD wallet. This is not cold storage yet. The merchant must sweep the funds to a cold storage address. A sweep transaction moves all UTXOs (unspent transaction outputs) from the hot wallet addresses to a cold wallet address. The merchant's operational choice: sweep after each transaction, or batch sweeps. Batching reduces fees but increases the time funds stay in a hot environment.
Wallet Sweeping Consolidation
The merchant's cold storage wallet should not have many small UTXOs. Each UTXO is a separate input in future transactions. Many small inputs mean high fees when the merchant eventually spends. The merchant consolidates UTXOs by sweeping multiple payments into a single cold storage transaction. This consolidation happens on a schedule. Weekly or monthly. The merchant chooses the timing. Consolidation is a fee management strategy, not a security requirement.
Fees and Timing
The merchant pays transaction fees for each sweep and consolidation. The customer pays fees for the original payment. The merchant's fee cost depends on Bitcoin network congestion. The merchant can choose to sweep during low-fee periods. This requires monitoring the mempool fee market. Some merchants automate this by setting a maximum fee rate threshold: below that threshold, sweep; above it, wait.
The merchant's operational checklist
Each stage requires a decision. Address generation: online or offline. Mempool detection: immediate or block-based. Confirmation depth: one or six. Sweep timing: per transaction or batched. Consolidation: weekly or monthly. Fee strategy: fixed or dynamic. None of these is built into Bitcoin. They are the merchant's responsibility.
The protocol handles verification and settlement. The merchant handles the operational architecture around it. That architecture determines cost, security, and customer experience. A merchant who understands each decision point can run Bitcoin payments without unnecessary risk or expense. A merchant who ignores them might accept payments but lose money to fees or fail to secure funds.
Not financial advice. unidexai.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.