How to Accept Bitcoin Payments for Your Business

What do you need before accepting Bitcoin?

You need a way to receive the money, a clear payment request and someone who decides when an order counts as paid. A wallet address alone doesn't handle delivery, customer service or your books.

Start with how your customers buy. On a web shop, payment has to attach to the right basket. At a counter, staff need to recognise an accepted payment while the buyer is still standing there. For a one-off bill, give both sides a reference they can find later. When you pick a processor with our processor selection guide, start from those same jobs.

This guide covers Bitcoin for your own lawful retail sales. Bitcoin on its main network and Lightning are two different ways to pay. Bitcoin Cash, wrapped Bitcoin tokens and stablecoins are different assets, and a service that lets you hold BTC may not offer checkout for them.

For the running example, picture a hypothetical stationery company, a Delaware LLC based and operating in Delaware. Its owners, directors and controllers are US citizens living there, and its buyers are in the US. It runs its own BTCPay for mainnet invoices into its company wallet, with the spending keys kept off the payment server, and we assume no bank conversion or deposit. It's a teaching case, not a real account or an installed shop.

1. 
   01

   Pick a product and a receiving plan

   Check that you qualify, then decide whether money lands in your company wallet or an approved account. Getting paid into a bank takes its own setup.

2. 
   02

   Decide who does what

   Name who handles invoices, who checks receipts and who may spend from the wallet, and settle backups and absence cover.

3. 
   03

   Decide when an order counts as paid

   Set your confirmation rules, and name someone to sort out short, late, excess or invalid payments.

4. 
   04

   Ship, then keep the records

   Release the parcel once, then keep delivery, returns and records tied to the order, including if you shut checkout down.

Should you run checkout or use a managed service?

Run it yourself if receiving Bitcoin directly is worth the upkeep. Consider managed acceptance if you'd rather pay a company to carry more of the work. A managed service also has to approve your business, and you still need to add up the full cost.

BTCPay creates invoices linked to a connected wallet and can generate receiving addresses without needing the spending keys.^[5] The trade-off, covered in our BTCPay review, is that more control over the software makes you responsible for keeping it working for the shop.

BitPay Acceptance is the merchant product to look at, not Send or a consumer wallet. As we read them on 11 October, its Acceptance Terms describe BitPay acting as a payment agent with conditions on your account, and they don't hand you control of the spending keys for incoming payments.^[20] Our BitPay review and BTCPay versus BitPay comparison go further.

OpenNode's guide for registered businesses lists the company and ownership checks it runs.^[12] Read its incoming-payment contract against your own sales (owners, business purpose, activity, region, Bitcoin network, what you're allowed to receive) before you pay, so you don't buy a connection your account can't use. Marketing aimed at resellers or high-risk businesses isn't approval to collect for third parties. Our OpenNode review covers the remaining account and control questions.

Can your company and customers use the chosen product?

Check that your company and its owners qualify before you pay for an integration. BitPay's merchant-country guidance covers US and Canadian applications and pauses new EEA, UK and Australian onboarding. Product and US state limits still apply, and its lists aren't exhaustive.^[17]

BitPay's compliance guide asks about your business, owners, operating address, website, industry and receiving details. For bank settlement the account must belong to the applying business, and customers and refund recipients can face verification conditions too, which can change what you promise at checkout and on a return.^[18] Alongside merchant approval, check that your customers' countries and the coin and network you want are enabled.

OpenNode's guide asks registered businesses for proof that the company exists, who owns or controls it, and its business address. The ownership wording covers significant owners or a control person, so don't read a percentage cut-off as an exemption from checks. The document gives no full list of merchant countries and no guaranteed approval time.^[12]

The hypothetical shop's direct company-wallet setup is a different case. It assumes no BitPay or OpenNode approval, no managed USD credit and no US bank service, and running the software yourself doesn't get you approved by a host, platform, conversion partner or bank. This is general information, not legal advice.

What should the buyer send?

The buyer should follow the current invoice's amount, Bitcoin network, destination and payment window, not an old email or a generic wallet address.

BTCPay's Stores FAQ describes configurable invoice expiry, rate selection and confirmation handling. An invoice fixes its crypto amount for a set window, and a reusable payment request is a different thing.^[9] Don't promise a permanent exchange rate, and look again before reusing an expired quote.

Put the instructions where the buyer sees them before opening their wallet: which order they're paying, which method to select, and where to get help if their usual wallet can't do the network you offer.

When is it safe to release the order?

Ship when the matching payment has the confirmations you've configured and meets your delivery conditions, and you've checked the reference, full amount, network and any exceptions, not just the status on screen. Don't rush the parcel.

For BTCPay mainnet payments, the Stores FAQ separates a transaction being seen from settlement after the configured confirmations. Its older terminology varies within the page, so ask your developer or host how your installed version reports status and handles exceptions.^[9] A Paid label someone changed by hand isn't evidence of a confirmed receipt.

Other products use their own words. At BitPay, a paid state can mean only that a transaction was broadcast, with no payment guarantee to the merchant, and your configured fulfilment policy and the account-credit state are different things.^[15] OpenNode calls a mainnet payment processing once the transaction is seen and paid once it's confirmed, and a Lightning payment is paid when it settles.^[13] Neither says anything about money reaching your bank.

Bitcoin.org explains that confirmation timing varies, so an average interval isn't a shipment deadline.^[3] Decide in advance who makes the call when the warehouse is ready but the payment is still pending.

Who handles a short, late or mistaken payment?

Give payment problems a named owner who can find the evidence and agree the next step with the buyer. Otherwise customer service, the warehouse and whoever does the books each assume somebody else is following up. An order with an open problem isn't paid until someone has deliberately resolved it.

A deduction by the buyer's exchange isn't automatically a processor fee or a discount you agreed to absorb. BTCPay describes underpayment caused by custodial sending deductions; you and your customer still have to sort out the amount.^[5] Before you ask the buyer to send again, check what arrived.

Would Lightning help at the counter?

Lightning is worth a look when waiting for a mainnet confirmation doesn't suit a counter, but it adds things to run. Staff need an invoice the customer's wallet can pay, and the system's own evidence that the payment settled.

BTCPay describes a browser point of sale tied to a store, with cart and keypad views.^[8] A device showing the payment request is no guarantee, by itself, of payment, wallet compatibility or finished setup.

Someone has to look after capacity for incoming payments, connectivity, and service or routing costs. BTCPay warns that a host's shared internal Lightning wallet receives into the host's wallet before redistributing it; an external node or wallet is a different setup.^[7] The mainnet example's keys-off-the-server model doesn't describe every Lightning balance. Give staff another way to take payment when Lightning isn't available.

What will accepting Bitcoin cost your business?

Budget for the whole job of running and receiving before you compare headline rates. The hypothetical shop has no complete quote. Start with the acceptance fee, then add application or account charges, platform and plugin costs, hosting, staff time, and upkeep and support. After that come the customer's sending costs, your own network fees for moving money, and any Lightning service or capacity costs. Bitcoin.org explains that mainnet fees depend on transaction data, not just the value sent, so they don't price every other service around a sale.^[1]

BitPay's pricing, as we read it on 11 October, has standard bands based on cumulative volume and an unquoted rate for higher-risk businesses. Its terms also require an application charge it doesn't price.^[19][20] A headline rate may not cover every account or activity, so find out which schedule applies to you. Our BitPay fee guide breaks those costs out.

OpenNode charges for acceptance and for moving an account balance to an external wallet as two different things. Its typical fee wording isn't a quote for your account, and bank-method and partner fees or minimums come on top. A no-conversion-fee label says nothing about the spread you'd get when the trade runs.^[11] Count a transfer you choose to make once per transfer, not against every sale.

Then add the costs that hide in the gaps: conversion and spread, bank and intermediary deductions, partner charges and later transfers, plus the minimums and fee floors on payments or withdrawals. Returns, unused credits, recovery, holds and closing the account cost money too, even when the usual sale is straightforward. An unknown cost isn't a free one. The fee calculator guide explains how a subtotal of fees differs from your total savings and the cash you'll end up with.

Does receiving Bitcoin put money in your bank?

No. Receiving Bitcoin isn't the same as getting managed account credit or usable bank funds. Even if you price your goods in dollars and show that value throughout the order, the invoice can still ask for Bitcoin.

OpenNode's currency help treats the currencies you can request payment in as different from USD conversion, settlement and bank transfers for US-based businesses.^[14] That description says nothing about this Delaware company, its account or its bank, so check the agreement, the enabled network, the minimums and the receiving bank's conditions before you rely on it.

If you run BTCPay yourself, any later conversion service and any way of getting the money into the company's bank need their own approval, terms and pricing. Put the money you need for supplier bills where you can reach it through a setup you already understand. This guide doesn't recommend holding or selling Bitcoin.

How do you complete a return and choose its value?

Work out what the customer is owed, and what that's worth, before you promise a coin amount. Then follow the product's return process, which needs funds behind it. An incoming Bitcoin payment can't be reversed, but that doesn't decide your return policy or your duties to customers.

Returning the same number of bitcoin and returning the sale's original dollar value can mean different amounts. BitPay's guide for fully paid invoices uses the original fiat value converted at the rate when the refund is claimed, and requires enough funds in the merchant's ledger.^[16] That's BitPay's guidance, not a rule for every Bitcoin sale. What counts depends on your contract, who pays the fee and what the customer receives.

BTCPay's illustrated on-chain return has distinct steps: a customer claim, approval, signing, broadcast and confirmation.^[10] In OpenNode's charge documentation, the refunded label describes an underpayment being cancelled with a refund request, and the page says nothing about returning an ordinary fully paid sale or the customer receiving the money.^[13] Don't promise automatic fee deductions, recovery of the original fee, or guaranteed recovery.

Who maintains checkout and keeps the records?

Someone has to run checkout and someone has to keep the records, including during absences and if you shut checkout down. Limit access by job: checking receipts, changing future payment instructions and spending the company's money are three different powers, and whoever answers buyers' payment questions needn't be able to move funds.

A watch-only mainnet connection isn't the same as a hot wallet. A third-party host controls its own server and any hot wallet it holds, and if your receiving instructions are compromised, future payments can be diverted even though the spending keys stay elsewhere.^[6]

Bitcoin.org describes keeping online monitoring apart from spending approval, and planning for backups.^[2] You shouldn't promise anonymity on a public transaction network.^[3]

For the Delaware example, the IRS guidance we read on 18 October 2026 supports one narrow US federal point: keep records of when you receive Bitcoin and when you later dispose of it, including the amount of bitcoin, the time and the USD value. Tie each record to the order, the reference and the Bitcoin network, and record a later return on its own.^[4] This isn't a filing guide or a ruling on how the LLC is taxed.

If you already have a store, see how the connection works in our WooCommerce guide or Shopify guide; a published how-to is no guarantee it will work on your install. Repeated requests, recurring invoices, prepaid balances and settlement schedules still don't let you debit a customer's external wallet.

BTCPay's General FAQ points users to community help and possibly paid specialists, which isn't the same as a support contract.^[5] A host or managed service gives you whatever support its agreement includes. Our ecommerce guide ties these jobs to delivery, and the methodology explains how we use documents as evidence.

Bitcoin payments FAQ