How to Accept Bitcoin Payments as a Small Business

You can accept bitcoin payments as a small business in about an afternoon: price the sale in your own currency, hand the buyer an invoice, let them pay the Bitcoin equivalent, wait for confirmations, ship. No merchant account application, no underwriting, no chargeback window hanging over you for three months. The honest catch is that Bitcoin is not the right rail for every sale — a $5 order gets eaten alive by network fees — and you want a plan for volatility and bookkeeping before you switch it on, not after.

Why a small business would accept bitcoin payments

The reasons that actually hold up are boring and financial, not ideological.

• No chargebacks. A confirmed on-chain payment is final. Nobody calls their bank ninety days after delivery and claws the money back. If you sell digital goods, remote services, or anything an acquirer files under "high risk", that finality is often worth more than the fee saving.
• Customers who cannot pay you any other way. A client in Argentina, Nigeria or Turkey may hold a card your acquirer silently declines. A crypto payment does not care which country the buyer sits in, and it clears on a Sunday night just as fast as on a Tuesday morning.
• No merchant account, no gatekeeping. Nobody underwrites you, asks for six months of bank statements, or parks a rolling reserve because your dispute rate ticked up half a point.
• Genuinely lower fees. The 2.9% + $0.30 on a card is a floor, not a ceiling. Cross-border surcharges, currency conversion and dispute fees stack on top of it.

Notice what is missing from that list: "the price might go up". That is speculation, not a business reason, and it is the fastest way to talk yourself into a bad decision.

And the honest reasons you might not

Every guide that skips this part is selling you something.

• Volatility, but only if you hold. If you convert to your local currency on arrival, your exposure is measured in minutes. If you decide to sit on BTC, you have quietly turned your shop into a fund, and a bad quarter can wipe out a year of margin. Decide which business you are in before the first invoice, not after.
• Bookkeeping overhead is real. Every payment needs a fiat value recorded at the moment it landed, and disposals may be reportable events where you operate. This is not tax advice — it is a nudge to ask your accountant one question before you switch it on, not in March.
• Bitcoin's own network fee makes tiny sales silly. When the mempool is busy, moving BTC can cost a few dollars. On a $5 order that is a rounding error you cannot round. Bitcoin is a poor fit for micro-transactions and there is no clever way around it.
• Most customers will still reach for a card. Crypto is an additional rail that unlocks specific buyers. It is not a replacement, and treating it like one leads to disappointment.

What it actually costs

Here is a realistic comparison for a small business. Network fees fluctuate with congestion, so treat these as typical ranges rather than quotes.

Run the numbers on a $2,000 invoice. A card takes about $58 before any cross-border surcharge. The same invoice paid in BTC costs you nothing to accept — the buyer covers a couple of dollars of miner fee. On a $5 sale the arithmetic inverts completely, which is exactly why the buyer should be offered a cheaper chain. With Payora it is 0% to accept; fees apply only when you move money out — 1.5% on payouts, transfers and withdrawals on the Free plan (0.75% on Pro, 0.5% on Business), plus the coin’s network fee (minimum withdrawal $50). On-chain fees always apply and are always paid by the sender.

The setup that works: price in dollars, get paid in bitcoin

The mistake small businesses make is thinking in BTC. Do not. Think in your own currency and let the gateway do the conversion arithmetic at payment time.

1. Create a fiat-priced invoice. Your order is $2,000 with an order id from your own system. Your books, your pricing page and your head all stay in dollars.
2. Send the buyer to a hosted checkout. The invoice is quoted in BTC at the current rate, with a countdown so the quote cannot drift forever.
3. Let the buyer choose the rail. Bitcoin for a $2,000 invoice is fine. For a $19 one, USDT on Tron or TON is the sane answer, and the buyer picking it saves you both money. Stablecoins on cheap chains also sidestep volatility entirely.
4. Wait for confirmations, then ship. Not before.
5. Take the signed webhook and mark the order paid. Your server verifies an HMAC-SHA256 signature and flips the order state. No polling, no manual checking.

Confirmations before you fulfil

A payment that has been broadcast is not a payment that has settled. Bitcoin's practical rule is one confirmation for small amounts and more as the sum climbs; each block is roughly ten minutes. For a $30 download, one confirmation is plenty. For a $20,000 order, wait longer — the cost of waiting an hour is nothing next to the cost of being wrong. We go through the thresholds properly in how many confirmations are safe. The key point for a small business is that the gateway should wait for you, automatically, and only then tell your system the order is paid.

Where the money actually lands

This is the part worth being picky about. Ask any provider one question: do you ever hold my money? If the answer involves an account balance you have to withdraw from, they do, and you have swapped bank gatekeeping for a smaller company's gatekeeping.

The alternative is non-custodial. Receive addresses are derived from public key material only — an xPub or an offline-generated address pool — so the server can hand out an address for every invoice without ever being able to spend from one. Private keys stay offline and payouts are signed offline. A compromised server leaks data, not funds. That mechanism is explained in the xPub walkthrough, and it is the difference between money that is yours and money that is merely owed to you.

Wiring it into what you already run

Two paths, depending on your shop.

If you run a CMS store, install a module and fill in an API key. There are free drop-in modules for 22 platforms — WooCommerce, PrestaShop, OpenCart, Magento 2, WHMCS, Easy Digital Downloads and more — on the modules page. Nobody needs to touch PHP.

If you run a custom site or a SaaS, it is one API call to create the invoice and one endpoint to receive the webhook. There is a one-file, dependency-free PHP SDK (7.4+) and a plain-JSON REST API in the documentation. Realistically it is an afternoon, most of which is testing the webhook. The invoice, hosted checkout and payment-link pieces are covered on accept payments.

So should you turn it on?

Yes, if you sell anything above roughly $50, you have international customers, or chargebacks have hurt you. Yes if a card processor has ever refused or dropped you. No, or at least not with BTC specifically, if your average order is a few dollars — offer a cheap chain instead, or skip it. And no if you plan to hold the coin and hope, because that is a different business with a different risk profile.

The setup cost is genuinely small, and it is reversible: switch it on, watch what share of orders use it for a quarter, keep it if the number justifies the bookkeeping. Create a free account to get API keys and see how the checkout behaves with a real invoice.