Why Businesses Accept Bitcoin Payments
Bitcoin gives a business a payment rail that operates around the clock, settles with finality, and works identically for a customer across the street or across an ocean. Card networks and bank transfers route every payment through layers of intermediaries, each of which adds fees, delay, and the possibility of a reversal. A confirmed Bitcoin transaction has none of those properties: once it settles, the funds belong to the merchant.
The practical benefits come down to four things:
- Lower processing costs. Card processing commonly costs a business two to three percent per sale plus fixed fees. Bitcoin payment processing services commonly charge around one to two percent depending on the provider and monthly volume, generally at or below card processing rates, and self-hosted acceptance has no processing fee at all.
- No chargebacks. Bitcoin settlement is final. Chargeback fraud, a persistent cost for card-accepting merchants, is structurally impossible. The flip side is that refunds become a deliberate merchant action rather than a bank process, which is covered below.
- Global reach without cross-border friction. A payment from another country arrives the same way and at the same speed as a domestic one. The payment path contains no foreign exchange intermediary, card surcharge, or correspondent bank.
- Settlement speed. An on-chain payment settles in roughly an hour for high assurance, and a Lightning Network payment settles in seconds. Card settlements, by contrast, reach a merchant account in one to three business days.
For background on how Bitcoin compares with the rails businesses already use, see What Are Payment Rails?
The Three Ways to Accept Bitcoin
Every Bitcoin acceptance setup is a variation on one of three models. They differ in who runs the infrastructure, who custodies the funds, and whether the business ends up holding bitcoin or fiat.
| Model | Who Runs It | Who Holds the Funds | Best For |
|---|---|---|---|
| Self-hosted payment server | The business (or its IT provider) | The business, in its own wallet | Businesses that want zero processing fees and full control |
| Payment processor | A third-party service | Processor briefly, then fiat to the business bank account | Businesses that want fiat settlement and minimal setup |
| Direct wallet acceptance | Nobody; it is just a wallet | The business, in its own wallet | Small operations with low payment volume |
Model 1: Self-Hosted Payment Servers
A self-hosted payment server is software the business runs on its own hardware or a rented server. It generates a fresh invoice address for each sale, watches the blockchain for the payment, and marks orders paid automatically. The best-known option is BTCPay Server, a free and open-source project with integrations for major e-commerce platforms, a point-of-sale app for in-person sales, and support for both on-chain and Lightning payments. Its source code is public and maintained by an open contributor community.
Self-hosting carries no processing fee, and no third party can freeze settlement or hold funds at any point: payments go straight to keys the business controls. In exchange, the business takes on operational work. Someone has to deploy the server, keep it updated, back up the wallet, and manage the funds that accumulate. For a business with any in-house technical capacity, that work is modest. For one without it, a processor may be the more realistic starting point.
Model 2: Payment Processors
Bitcoin payment processors are hosted services that handle the entire flow: invoice generation, payment detection, compliance screening, and settlement. The defining feature of the category is automatic conversion. The customer pays in bitcoin, the processor converts the payment at the moment of sale, and the business receives its local currency in a bank account on a normal settlement schedule. The business never touches bitcoin and carries no price exposure.
Processors in this category typically:
- Charge a service fee of around one to two percent per transaction, depending on the provider and monthly volume, generally at or below typical card processing rates.
- Settle in fiat, in bitcoin, or in a configurable split between the two.
- Handle regulatory obligations connected to the conversion, since the processor, not the merchant, is the party touching the asset.
- Plug into existing checkout flows through plugins, APIs, and hosted payment pages.
The trade-off is the mirror image of self-hosting. Setup takes minutes and no Bitcoin expertise is required, but the business depends on the processor's terms, pays its fee on every sale, and gives up the option of receiving funds with no intermediary involved. Because the processor briefly controls the funds, the business is also trusting its solvency and uptime for the duration of each settlement cycle.
Model 3: Direct Wallet Acceptance
The simplest model needs no server and no service: the business displays a payment request from its own wallet, the customer pays it, and the funds arrive directly. A self-custodial wallet such as the Blockstream app can generate payment requests with the amount embedded, and the cashier confirms the payment on screen before completing the sale.
Direct wallet acceptance suits a market stall, a freelancer invoicing a handful of clients, or a small shop testing demand before committing to infrastructure. It scales poorly past that. There is no automatic order matching, so each payment has to be checked by a person, and reusing addresses degrades the privacy of the business and its customers. Once payment volume justifies it, a self-hosted server adds the automation while keeping the self-custody.
On-Chain or Lightning at the Point of Sale
Whichever model a business picks, it will face a second decision: which Bitcoin layer to accept at checkout.
On-chain payments settle on the Bitcoin base layer. They suit larger invoices where the customer and merchant can tolerate waiting for confirmations, and they carry a network fee that varies with demand for block space. For an explanation of how that fee market works, see Why Does Bitcoin Have Fees?
Lightning payments settle in seconds for fees that are usually a fraction of a cent, which makes them the natural fit for retail checkout, where a customer is standing at a counter and a coffee cannot wait ten minutes. Lightning is a layer-2 protocol anchored to Bitcoin: channels are secured by on-chain Bitcoin transactions, and funds can always be settled back to the base layer, though Lightning carries its own operational requirements, such as staying online and managing channel liquidity. Most modern payment servers and processors present both options on a single invoice and let the customer choose.
The full comparison lives in Lightning vs. On-Chain, and the merchant-specific details, including liquidity management and integration paths, are covered in Lightning Network for Merchants.
Handling Price Volatility
The bitcoin exchange rate moves, and a business has to decide who carries that movement between the sale and the books. There are three working policies:
- Convert everything instantly. The processor converts each sale to fiat at the moment of payment. Revenue is predictable, margins are protected, and accounting looks like any other sale. This is the default for businesses that accept bitcoin as a payment option rather than as a treasury position.
- Hold everything. The business keeps the bitcoin it receives, taking on price exposure in exchange for a position in the asset. This converts a payments decision into a treasury decision, which deserves its own analysis; see What Is a Bitcoin Treasury Strategy?
- Split the flow. Many processors and payment servers support keeping a configured percentage in bitcoin and converting the rest. A business can cover costs in fiat while accumulating a small bitcoin position from organic sales.
Pricing works the same way under all three policies: goods stay priced in local currency, and the invoice quotes the equivalent amount in bitcoin or sats at the current exchange rate, locked for a short window (commonly 10 to 15 minutes) while the customer pays.
Taxes and Bookkeeping
Accepting bitcoin creates two bookkeeping events instead of one. In the United States, the IRS treats digital assets as property: a sale paid in bitcoin is generally recorded as ordinary income at the fair market value at the time of receipt, and if the business later sells or spends that bitcoin, the difference between the receipt value and the disposal value is a capital gain or loss. A business that converts instantly through a processor mostly avoids the second event, since there is little or no holding period.
Record-keeping is the practical burden. Each payment needs a timestamp, a fair market value at receipt, and a cost basis if held. Payment servers and processors export this data, and accounting integrations can post it automatically. Treatment differs by jurisdiction, so a business should involve a qualified tax professional before going live. This article is general information rather than tax advice. For the fuller accounting picture, including how holdings are measured on the balance sheet, see How Do Companies Account for Bitcoin?
Choosing a Model: A Checklist
The right setup falls out of a handful of honest answers about the business, worth working through before evaluating any specific tool:
- Does the business want to end up holding bitcoin, fiat, or a mix? If the answer is pure fiat, a processor is the shortest path. If the answer includes holding, self-custody belongs in the design from day one.
- Is there technical capacity to run and maintain a server? A self-hosted server is straightforward for a team that already manages infrastructure and a burden for one that does not.
- What is the expected payment volume? A handful of payments per month can be handled by direct wallet acceptance. Hundreds per day need automation, either self-hosted or through a processor.
- Are payments in person, online, or both? In-person checkout makes Lightning support close to mandatory. Online invoicing tolerates on-chain confirmation times more easily.
- Can the business tolerate a third party in the payment path? Some businesses adopt Bitcoin precisely to remove intermediaries; others are happy to trade an intermediary for convenience.
- Who reconciles the books, and do they have a data feed? Whichever model wins, confirm it exports payment records the accounting workflow can consume.
Getting Started
A sensible rollout starts small and keeps options open. A business can pilot with a processor or a direct wallet to test customer demand, then graduate to a self-hosted server once volume and confidence grow. Nothing about the models is exclusive: plenty of merchants run a self-hosted server for online sales while a processor handles a retail location, and a business can change models without changing anything customers see at checkout.
Frequently Asked Questions
Does a business have to convert bitcoin to dollars immediately?
No. Conversion is a policy choice. Payment processors can convert each sale to fiat at the moment of payment, which removes price exposure. A business may also hold some or all of the bitcoin it receives, which adds volatility risk and additional accounting work but keeps the asset on the balance sheet.
Are Bitcoin payments taxable for a business?
In the United States, the IRS treats digital assets as property. A sale paid in bitcoin is generally recorded as income at the fair market value at the time of receipt, and a later sale of that bitcoin can create a capital gain or loss. Rules vary by jurisdiction, so businesses should consult a qualified tax professional.
What fees do businesses pay to accept bitcoin?
Self-hosted acceptance has no processing fee; the customer pays the network fee. Payment processors charge a service fee, typically around one to two percent depending on the provider and volume, which is generally at or below most card processing rates. Lightning payments carry network fees that are usually a fraction of a cent.
Can customers reverse a Bitcoin payment?
No. A confirmed Bitcoin transaction is final and cannot be reversed by the customer, a bank, or a card network. This removes chargeback fraud for the merchant. It also means refunds become a deliberate merchant action, so businesses should publish a clear refund policy before accepting bitcoin.
Does a business need to hold bitcoin to accept it?
No. With a payment processor, the customer pays in bitcoin and the business receives fiat in its bank account, so no bitcoin ever sits on the company's books. Holding is only necessary if the business chooses self-hosted or direct wallet acceptance and decides to keep what it receives.