
Bitcoin Payment Gateway: How to Accept BTC in Your Online Store
How to accept Bitcoin in an online store: choose a plugin, hosted Checkout or the API, compare on-chain BTC with Lightning, and check minimums, fees and webhooks before a real test payment.
How to accept Bitcoin payments: the short answer
To accept Bitcoin in an online store with BlockBee, add a BTC receiving address in the dashboard, then choose a payment path: an e-commerce plugin, BlockBee's hosted Checkout page or your own payment screen built on the API. BlockBee generates the address the customer pays, notifies your server by webhook and forwards confirmed on-chain BTC to your address. Mark an order paid only after your server receives that verified notification.
Choose a setup: plugin, hosted Checkout or API
| Setup | What you do | What BlockBee handles | BTC options |
|---|---|---|---|
| E-commerce plugin | Install it, enter your API key, select Bitcoin, set your address | A no-code integration in your store | On-chain; check the plugin's guide for more |
| Hosted Checkout | Create a payment on your server and redirect the customer to it | The payment page and live status | On-chain; Lightning if enabled |
| Custom payment flow | Create a BTC address per order; build your own screen | The address, webhooks and forwarding | On-chain |
BlockBee has official plugins for WooCommerce, PrestaShop, OpenCart, Magento, Odoo and WHMCS. For other sites, BlockBee's docs estimate 5–10 minutes for a basic Checkout integration and 30–45 minutes for a custom flow, where you must display the amount, address, QR code and minimum yourself.
On-chain Bitcoin or Lightning?
| On-chain BTC | Bitcoin Lightning | |
|---|---|---|
| Available in | Plugins, hosted Checkout, custom payment flow | Checkout and PoS only |
| Minimum per payment (3 Nov 2026) | 0.00008 BTC (8,000 satoshis) | 0.000001 BTC |
| How funds reach you | Forwarded to your BTC address after the payment confirms | Daily at 00:00 UTC to your BTC address, once the balance exceeds 0.00008 BTC |
| How to turn it on | Add a BTC receiving address | Enable it in Payment Settings |
The Lightning payout rule comes from BlockBee's Lightning announcement, and the cryptocurrencies page lists the same daily settlement. Don't apply one rail's minimum to the other.
If a customer holds a different coin, Swap Everything can offer supported routes with a live quote on eligible Checkout flows, converting the payment into one of your configured receiving coins.
Set up BTC step by step
- Create an account and add your BTC address. Register for BlockBee, then set your Bitcoin receiving address on the Addresses page, and also in your plugin's settings if its guide asks for it. Use a wallet you control and back up its recovery phrase; Bitcoin.org warns that permanently lost self-custodied funds can't be recovered.
- Generate an API key and keep it on your server, never in client-side code or public repositories.
- Connect your payment path. Plugin: enter the key, select Bitcoin and save. Checkout: set your default fiat currency in Payment Settings (or pass
currency); your server requests a payment with the order value,notify_urlandredirect_url, then sends the customer to the returnedpayment_url. Custom flow: call the BTC create endpoint with yourcallbackURL and display the returned address. - Verify your domain. Once domain verification applies to your account, your
callback,notify_urlandredirect_urlmust use a domain verified for the profile. Accounts created on or after 20 October 2026 need this from the start; existing accounts from 1 February 2027. Add the domain under Profile settings → Domains and publish the TXT record shown, or use the HTTPS file option (see the domain verification guide). Plugin users verify the shop's domain. - Optional: enable Lightning in Payment Settings if you use Checkout or PoS.
Treat the webhook as proof of payment
A customer reaching your success page is not proof of payment; BlockBee's Checkout docs recommend validating with the notify_url rather than the redirect. So:
- Respond with HTTP
200and the body*ok*. BlockBee treats any other response as a failure and retries. - Verify the
x-ca-signatureheader with BlockBee's public key, following the signature guide. - Put your order ID and an unguessable per-payment value in the callback URL, store both, and reject notifications you don't recognise.
- Make the handler idempotent, because retries can deliver the same webhook more than once.
In a custom flow you can enable pending webhooks: one when the transaction is seen but unconfirmed, another once it reaches your requested confirmations. Reassure the customer on the first; fulfil on the second, once it shows BTC and the BTC amount you requested. Hosted Checkout sends a single webhook when the payment is complete and confirmed.
Bitcoin blocks arrive about every 10 minutes on average, but Bitcoin.org notes there is no guaranteed minimum or maximum delay, so don't promise a fixed confirmation time. Bitcoin transactions can't be reversed, only refunded by the recipient, so decide your refund process before launch.
BTC minimums and fees on 3 November 2026
- Minimum transaction: 0.00008000 BTC (8,000 satoshis), from BlockBee's API. Smaller payments are ignored and the funds lost, so every BTC order must convert to more than this.
- Minimum fee: the same API data lists 546 satoshis (0.00000546 BTC). It is a fee figure, not a payment minimum.
- Service fee: the fees page shows a 1.000% deposit fee for monthly volume of USD 0–9,999, with rates down to 0.25% based on your previous 30 days' volume and industry risk tier. Check the fee calculator for your rate.
- Network fees: separate from the service fee and, by default, deducted from the payment before it is forwarded to you. Blockchain fees pay to forward both BlockBee's fee and your payment, and the published estimates cover one output address, so they aren't an all-in cost. Optional Prepaid BlockBee Fees cover the service fee from credits, removing one transaction; unused credits can't be refunded.
Worked example: a 0.01 BTC payment at a 1% service rate carries a 0.0001 BTC service fee (0.01 × 1%), before network fees.
Test with a real payment, then reconcile
BlockBee has no sandbox or test mode. Its docs suggest a small real order above the coin's minimum, for example about $2 in Litecoin. To test BTC itself, place a small real BTC order comfortably above 0.00008 BTC, not one at the boundary.
Then check that:
- your order is linked to BlockBee's
payment_id(Checkout) oraddress_in(custom flow); - the webhook passed signature verification and got
*ok*back; - the order was marked paid once, on the confirmed webhook, not on the redirect;
- you stored the paid amount, coin and transaction hash;
- the BTC reached your wallet and matches the forwarded amount in the webhook.
FAQ
Can I build my own Bitcoin payment page?
Yes, with the custom payment flow on BlockBee's API. Lightning works only through Checkout and PoS, so a custom page takes on-chain BTC.
Which wallet receives my bitcoin?
The BTC address you set on BlockBee's Addresses page (also entered in your plugin, if its guide asks). BlockBee's Lightning announcement says Lightning payouts go to the same address.
What is the minimum Bitcoin payment?
On 3 November 2026: 0.00008 BTC on-chain and 0.000001 BTC on Lightning. Minimums change, so check the cryptocurrencies page before launch.
Should I enable Lightning?
Consider it if you use Checkout or PoS and want to accept smaller BTC amounts. Its funds arrive in a daily payout.
Can I test without real money?
No. BlockBee has no sandbox or test mode, so use a small real payment comfortably above the minimum.
Accept crypto payments in your online store
Use BlockBee plugins and checkout tools to accept 100+ cryptocurrencies on WooCommerce, Magento, OpenCart, PrestaShop, Odoo, and custom stores.
0% fees for 7 days!