Optional cookies require your permission.Privacy & cookies
In this essay6 sections
  1. Start with two businesses that need different things.
  2. Put every cost in the correct bucket.
  3. Build a cost comparison with explicit assumptions.
  4. Test break-even and the costs of exceptions.
  5. Request a quote that can be tested against the model.
  6. The Bitcoin Lawyer take

Start with two businesses that need different things.

A consultancy bills $1,000 for an engagement. A digital shop charges $20 for a download. If each adds Bitcoin at checkout, will the cost per completed order fall? The answer depends on the payment amount, how often customers choose Bitcoin, and who handles the work after the payment arrives.

Use two fictional businesses. Business A is a consultancy with twenty $1,000 orders a month from business customers in several countries. Business B is an online shop with two hundred $20 orders a month from individuals. All amounts in the comparison are in U.S. dollars. The order volumes and cost inputs are planning assumptions, and each business would need to test its own sales and obtain current prices.

For each business, identify the operating entity, customer locations, invoice currency, delivery process, refund pattern, and existing payment methods. Ask why customers would choose Bitcoin and whether they can use the proposed method. A technically available checkout option may have little commercial value if almost nobody in the actual customer base wants it.

List the services the existing arrangement supplies. It may include reporting, conversion, support, fraud tools, integrations, or other functions. Identify which the business uses and which it would need to replace. A lower processing charge is less useful if the owner must add substantial work that the old service performed adequately.

BitSettle’s pricing page describes a charge for setup and service with pricing quoted for the merchant’s requirements before onboarding. Find out which methods are available for your business, what the written quote covers, and who will operate the parts outside that scope. Use those details when you compare the quote with your current costs.

The choice depends on the orders, customers, and people available to operate the checkout. You might keep your current method, offer Bitcoin on a specified set of orders, or wait until demand justifies the work.

Put every cost in the correct bucket.

Separate initial work from recurring work. Initial costs can include requirements, implementation, testing, staff training, documentation, and migration. Recurring fixed costs can include hosting, service support, monitoring, and scheduled maintenance. Variable costs can include relevant network activity, exceptions, refunds, conversion and per-order administrative time.

Open-source software can be available without a license fee. Budget separately for infrastructure, implementation, and the people who maintain it. BTCPay Server’s integration guide and wallet documentation describe the capabilities you would be configuring. Estimate operating costs from the work your setup requires and any written quotes.

Identify who pays each fee and when. A customer generally pays their own outgoing network fee. The merchant may incur costs later when moving funds, processing refunds, or managing its infrastructure. Price those steps from the actual payment flow.

If you are considering Lightning, identify who manages liquidity, maintains backups, and handles recovery. BTCPay Server documents several setup options, including ways to manage liquidity. Confirm which configuration is available and has been tested with the merchant’s checkout before budgeting for it.

Keep conversion separate. A business that holds Bitcoin has a different operating process from one that needs another currency to pay expenses. If conversion is required, obtain current terms, availability, and costs for the actual route. Do not assume automatic conversion, a guaranteed rate, or a banking relationship that has not been established.

Include the accountant’s work and the merchant’s time. Estimate how many hours staff will spend preparing invoices, resolving exceptions, and reconciling sales. Show cash expenses and internal time separately so the owner can see the effect of both on the decision.

Tie those hours to an order milestone. If a digital shop delivers a download when payment is confirmed, it needs to match the order to the payment record and decide who handles a late or partial payment. A consultancy that reviews a few invoices by hand may budget for a different process. Ask which tasks the payment system can do and which remain with your team.

If a staff member handles three exceptions in one hour, allocate the time across the three orders and count it once in the monthly total. Apply the same labor rate to both payment methods. Track unusual refunds separately so a single incident does not distort the estimate for a typical order.

Build a cost comparison with explicit assumptions.

For this fictional model, assume the existing method costs 3 percent of sales plus $0.30 per order. Give the Bitcoin option a $1,200 initial implementation cost, a $120 monthly operating cost, and a $4 per-order allowance that combines administration and exception work. Replace those inputs with quotes or observations when you evaluate an actual setup.

Spread the initial $1,200 across twenty-four months to get a $50 monthly planning allowance. The modeled monthly cost becomes $170 plus $4 per order. In a separate cash budget, show the full $1,200 at the time the business expects to pay it.

For Business A at twenty $1,000 orders, the existing-method assumption produces a cost of $606 a month. The Bitcoin model produces $250 including the setup allowance, a difference of $356 under the model’s assumptions.

For Business B at two hundred $20 orders, the same existing-method assumption produces a cost of $180. The Bitcoin model produces $970. At that order value, the $4 per-order allowance alone exceeds the $0.90 cost of the existing method. A different checkout and support workflow could change the result.

The lower-volume rows compare what each method would cost on the same subset of orders. If you keep the existing method and add Bitcoin, budget for both. For example, if two of the consultancy’s twenty orders switch to Bitcoin and eighteen stay with the original method, the modeled combined cost is $723.40. That is $545.40 for eighteen existing-method orders plus $178 for Bitcoin, compared with $606 if all twenty stay on the existing method.

The model excludes taxes, actual conversion costs, unusual incidents, and some services supplied by the existing method. Add items that apply to the setup you are considering. Keep assumptions about staff time visible so you can replace them after a pilot.

Illustrative monthly costs in U.S. dollars using fictional inputs
Business and volumeSalesExisting model: 3% + $0.30/orderBitcoin model: $170 + $4/orderModel result
A: 20 orders at $1,000$20,000$606$250Bitcoin model lower by $356
A: 2 orders at $1,000$2,000$60.60$178Existing model lower by $117.40
B: 200 orders at $20$4,000$180$970Existing model lower by $790
B: 20 orders at $20$400$18$250Existing model lower by $232

Test break-even and the costs of exceptions.

Using the fictional model, the proposed arrangement costs less on the orders that switch once the savings per order cover the $170 monthly fixed and setup allowance. For a $1,000 order, the assumed existing cost is $30.30, compared with a variable cost of $4 in the Bitcoin model. The difference is $26.30 per order, so seven orders must switch to reach the first whole-order volume with modeled savings.

For a $20 order, the assumed existing cost is $0.90, below the Bitcoin option’s $4 variable allowance. Under those inputs, each additional order increases the cost gap. The shop would need a less expensive way to handle those orders or a customer benefit that justifies the added cost.

Use the threshold as a decision aid, not a sales target. If customers prefer another method, the merchant cannot assume seven Bitcoin orders merely because that number makes the worksheet attractive. Demand needs its own evidence.

Change the exception workload next. Estimate how often staff handle late, short, excess, or mismatched payments, how long each case takes, and who can decide it. Use actual pilot observations when available. One difficult case can consume more time than many ordinary payments, particularly when records are incomplete or responsibility is unclear.

Include refunds as a separate workflow. The business may need to review the calculation, confirm receiving instructions, authorize the payout, and reconcile the result. In BTCPay Server’s documented workflow, the customer submits a refund address and the merchant approves and sends the payout. Estimate the time and any costs for the steps your team will handle.

Test downtime and recovery assumptions without inventing a failure rate. Ask what happens to already-created orders, who investigates uncertain payments, and what support is included in the quote. A provider promise should be read from the actual contract. Do not assign a financial benefit for round-the-clock support or guaranteed recovery when neither has been agreed.

Consider customer experience. A method that reduces stated fees can still cost more if more shoppers abandon purchases or need help. It can also be worth offering at a higher cost if it serves an important group of customers. Record those benefits separately from the costs in the worksheet.

Request a quote that can be tested against the model.

Give potential providers or implementation teams the same factual brief: entity and operating location, customer markets, order sizes and volumes, supported currencies, delivery integration, accounting needs, and expected support. Ask them to identify availability and dependencies before pricing. A quote for a different workflow is not a comparable alternative.

Require scope boundaries. What is included in implementation, maintenance, monitoring, updates, and incident handling? Which asset and network are enabled and tested? Who controls funds and infrastructure? What remains the merchant’s responsibility? Avoid treating a short price email as an agreement covering every operating task in the worksheet.

Ask how costs change with lower volume, more transactions, another method, or an additional integration. Identify minimum charges, third-party costs, and work billed separately. Keep official or provider terms dated. A quote can be accurate when issued and cease to apply after the business changes the scope or waits beyond its validity period.

Run a bounded pilot to replace the weakest assumptions. Measure the time required to reconcile an order and handle a controlled exception. Verify that the customer and bookkeeper can use the workflow. Do not extrapolate a single successful payment into a guaranteed support workload, but use the evidence to improve the model before wider use.

Make one view for cash commitments and another for total operating effort. Show initial spending, recurring costs, and per-order assumptions. If a Bitcoin checkout would serve a specific customer need, state which orders it would cover and what you can spend to serve them.

Use the completed worksheet when you request implementation prices. Explain what the business needs to buy, what it will operate in-house, and which assumptions could change the decision. Ask BitSettle or another provider to quote against the same sales and payment scenarios.

The whole picture

The Bitcoin Lawyer take

Model the first month of orders you expect to process, including how many customers will keep using the existing method. Count the ongoing cost of both methods if you offer both. In the consultancy’s example, seven $1,000 orders need to switch each month before the fictional Bitcoin setup begins to save money.

Use the same order values and volumes when requesting quotes. Then run a small pilot to replace guesses about reconciliation and exception work with observations. Ask who owns each task and what a change in volume would do to the bill.

Cite this essay

Adam Juchniewicz, CEO, Bitcoin Lawyer. “What it costs a business to accept Bitcoin.” https://www.bitcoinlawyer.com/journal/what-does-accepting-bitcoin-actually-cost-your-business