How Bitcoin Works
Bitcoin operates on a decentralized peer-to-peer network maintained by thousands of independent nodes worldwide, with no single entity capable of controlling or censoring it. Transactions are grouped into blocks and appended to a shared public ledger called the blockchain, secured through a competitive process called Proof of Work mining. Understanding this architecture helps merchants and payment developers make informed decisions about accepting, routing, and settling Bitcoin payments.
A transaction is broadcast
When a user sends Bitcoin, the transaction is broadcast to the peer-to-peer network. It contains the sender's address, the recipient's address, and the amount being transferred. The transaction is cryptographically signed with the sender's private key, proving ownership without revealing the key itself.
Nodes validate the transaction
Full nodes across the network independently verify the transaction against Bitcoin's protocol rules — confirming the sender has sufficient unspent outputs and that the signature is mathematically valid. No central authority approves or rejects the payment; consensus emerges from thousands of independent validators.
Miners compete to add the block
Valid transactions enter a mempool, where miners select them and compete to solve a cryptographic puzzle. The first miner to find a valid solution broadcasts the new block and earns the block reward plus transaction fees. This energy-intensive competition is what makes the chain tamper-resistant: rewriting history requires outpacing the entire network's hash rate.
The block is confirmed
Once a block is added to the chain, it receives one confirmation. Each subsequent block added on top adds another confirmation, making earlier transactions exponentially harder to reverse. Most payment processors require 1–6 confirmations before releasing goods, representing 10–60 minutes of settlement time under normal network conditions.
Settlement is final
Unlike card payments, confirmed Bitcoin transactions cannot be reversed, recalled, or charged back. The recipient has permanent, censorship-resistant ownership of the funds, which they can hold as BTC or convert to fiat through an exchange or payment processor that offers instant conversion at settlement.
Why Bitcoin Matters
Bitcoin introduced a fundamentally new model for value transfer — one that requires no bank account, no intermediary approval, and no geographic restriction. For global commerce, this has material implications around settlement finality, cross-border fees, and access to financial infrastructure in underbanked regions.
- Market scale: Bitcoin's market capitalization exceeded $1.3 trillion in 2024, surpassing the total equity value of most national stock exchanges and cementing it as a mainstream institutional asset class (CoinMarketCap, 2024).
- Global holders: Approximately 106 million people worldwide held Bitcoin as of Q4 2024 — adoption growing fastest in markets with weak local currencies, high remittance costs, and limited banking access (Statista, 2024).
- Merchant acceptance: Over 15,000 businesses globally accept Bitcoin directly, with hundreds of thousands more enabled through payment processors that auto-convert to fiat at checkout, removing volatility risk entirely (BitPay, 2024).
For merchants, Bitcoin acceptance opens a customer segment that actively prefers cryptocurrency payments and frequently demonstrates higher average order values than card users. For payment professionals, Bitcoin remains the reference asset against which all digital currency infrastructure — custody, routing, settlement, and compliance — is designed and benchmarked.
Bitcoin vs. Stablecoin
Bitcoin and stablecoins are both digital currencies that settle on blockchain rails without chargebacks, but they serve distinct roles in a payment stack. The table below covers the dimensions that matter most for merchants and payment integrators evaluating which asset to accept.
| Dimension | Bitcoin (BTC) | Stablecoin (e.g. USDC) |
|---|---|---|
| Price stability | Volatile — daily moves of 2–10%+ | Pegged 1:1 to fiat (e.g. USD) |
| Settlement speed | 10–60 min on-chain / instant via Lightning | Near-instant (varies by chain) |
| Chargeback risk | None — irreversible by design | None — irreversible by design |
| Regulatory clarity | Established asset class in most jurisdictions | Evolving — reserve requirements vary |
| Liquidity | Highest of any digital asset | High, but issuer-dependent |
| Inflation resistance | Yes — fixed 21M supply | No — tracks underlying fiat inflation |
| Merchant use case fit | High-value orders, store-of-value treasury | High-frequency, margin-sensitive transactions |
| Acceptance breadth | Widest processor and wallet support | Rapidly growing, chain-dependent |
Merchants with infrequent, high-value orders often prefer Bitcoin, while those with thin margins and large transaction volumes lean toward stablecoins to avoid FX exposure. Leading payment orchestration platforms support both, letting merchants configure settlement currency and asset preference per payment method or order threshold.
Types of Bitcoin
Bitcoin has several representations and Layer 2 implementations, each carrying distinct trade-offs for payment acceptance and developer integration.
Native BTC (Layer 1) is the original asset on the Bitcoin mainchain. It provides maximum security and decentralization with the longest track record, but requires confirmation time and fees that fluctuate with network demand — potentially high during congestion events.
Lightning Network BTC routes Bitcoin through a Layer 2 payment channel network sitting on top of the mainchain. Transactions settle in milliseconds at sub-cent fees, making Lightning practical for retail checkout, micropayments, content monetization, and streaming money use cases. Adoption has accelerated significantly since 2022, with digital wallet providers like Cash App, Strike, and Wallet of Satoshi enabling Lightning by default.
Wrapped Bitcoin (WBTC) is an ERC-20 token on Ethereum representing Bitcoin at a 1:1 ratio, with the underlying BTC held by a third-party custodian. It enables BTC to participate in Ethereum-compatible DeFi protocols and smart contracts, but introduces custodial counterparty risk absent in native BTC.
Liquid Bitcoin (L-BTC) is Bitcoin on the Liquid Network sidechain, offering faster settlement and confidential transactions — used primarily by exchanges and OTC desks for inter-institutional settlement rather than consumer-facing payments.
Best Practices
Accepting Bitcoin at scale requires deliberate decisions about settlement, confirmation thresholds, and customer experience. Best practices differ meaningfully between merchant operations and technical integrations.
For Merchants
- Auto-convert to fiat at settlement. Unless you have a deliberate treasury strategy for holding BTC, configure your payment processor to convert to local currency immediately upon receipt. Most processors offer this with no additional steps and absorb the spread into their fee.
- Set confirmation thresholds by order value. For orders under $50, zero or one confirmation is operationally acceptable. For high-value orders, require 3–6 confirmations to reduce the negligible but non-zero risk of a chain reorganization.
- Display prices in fiat, calculate BTC dynamically. Show customers the fiat price at checkout and compute the BTC equivalent in real time using a live feed. This avoids confusion and reduces cart abandonment from unexpected amount changes.
- Offer Lightning alongside on-chain. Enabling Lightning Network payments dramatically improves the checkout experience for smaller purchases, reduces confirmation wait times to near-zero, and lowers per-transaction fees.
- Record fiat-equivalent values at time of receipt. In most jurisdictions, accepting Bitcoin is a taxable event. Log the fiat market value at the moment of transaction for accurate profit/loss and VAT reporting.
For Developers
- Use a battle-tested payment library or server. BTCPay Server, BitcoinJS, and equivalent libraries abstract address generation, transaction construction, and webhook handling — reducing the risk of cryptographic implementation errors that can cause permanent fund loss.
- Never reuse addresses. Generate a fresh receiving address per invoice. Address reuse degrades customer privacy and complicates accounting reconciliation across concurrent orders.
- Implement webhook idempotency. Payment confirmation webhooks can fire multiple times due to network retries. Use the transaction ID as an idempotency key to prevent duplicate order fulfillment.
- Support BIP-21 payment URIs. Encoding payment requests as
bitcoin:address?amount=X&label=OrderIDallows wallets to pre-fill all payment details, reducing user error and failed transactions. - Monitor mempool fee rates dynamically. Fee rates fluctuate by orders of magnitude. Integrate a mempool fee estimation API to surface appropriate fee tier recommendations to users at the moment of sending.
Common Mistakes
Even experienced payment teams make avoidable errors when adding Bitcoin to their stack.
Treating Bitcoin like a bank transfer. Bitcoin has no account number, IBAN, or sort code. A transaction sent to a wrong address is permanently lost with no recourse. Build explicit address confirmation UX — such as displaying the first and last six characters of the address — into every payment flow before funds are committed.
Holding BTC without a defined treasury policy. Merchants who accumulate Bitcoin without auto-conversion face mark-to-market losses if the price falls between receipt and settlement. Define a clear policy — convert immediately, convert weekly, or hedge with options — before accepting Bitcoin at any meaningful volume.
Overlooking the central-bank-digital-currency regulatory context. As CBDCs roll out globally and jurisdictions tighten frameworks for private digital assets, compliance obligations for Bitcoin acceptance are evolving. Merchants operating across borders should track AML, KYC, and tax reporting requirements in each jurisdiction rather than assuming a single policy applies everywhere.
Accepting zero-confirmation transactions for instant-release products. Unconfirmed transactions can be replaced using Replace-by-Fee (RBF), meaning a sender can double-spend before confirmation. For digital goods, software licenses, or any product released instantly, require at least one confirmation or use Lightning Network which has its own finality model.
Conflating Bitcoin with other digital assets in customer-facing messaging. Customers who read "we accept crypto" may attempt to pay with any token on any chain. State explicitly which assets and networks you support — Bitcoin mainnet, Lightning, or both — to prevent failed transactions, misdirected funds, and avoidable support volume.
Bitcoin and Tagada
Bitcoin acceptance does not have to live outside your main payment stack. Tagada's orchestration layer routes Bitcoin through supported processors alongside card, bank transfer, and alternative payment methods — with unified reporting, settlement, and risk controls across all rails.
Tagada lets merchants enable Bitcoin acceptance through connected processors — with auto-conversion to fiat at settlement, per-method confirmation thresholds, and fallback routing if a processor is unavailable — all configured from the same orchestration dashboard as your card and bank transfer rules.
For payment operations teams, this means Bitcoin transactions flow into the same reconciliation pipeline, chargeback-rate dashboards (spoiler: zero chargebacks), and financial reporting as every other payment method. No separate Bitcoin integration, no siloed reporting, and no manual conversion workflow — Bitcoin becomes one more configurable rail in an orchestrated payment stack.