Accepting Bitcoin Payments: A Guide for Online Businesses
January 06, 2025
Rodrigo Fernández
Director of Infrastructure
Accepting Bitcoin online requires more than displaying a wallet address. You need to connect each payment to an order, decide when to deliver and handle expired invoices, refunds and recovery.
Begin with the payment flow your business can operate. On-chain Bitcoin and Lightning have different confirmation, liquidity and recovery considerations.
Choose custody and administration first
A hosted processor may operate the payment infrastructure for you. Check who holds funds, which countries and businesses it supports, withdrawal conditions and how records can be exported.
With a self-hosted system, your team maintains the application and its supporting infrastructure. You also need a deliberate custody design.
BTCPay Server is an open-source option for Bitcoin invoicing. It does not charge a software processing fee, but that does not make hosting, network transactions or operating the system free.
Budget beyond the advertised fee
| Cost area | What to check |
|---|---|
| Processing service | Current charges, withdrawal rules and optional services. |
| Infrastructure | Server resources, storage, backups and maintenance. |
| Network activity | On-chain transactions and Lightning-related costs. |
| Conversion | Availability, exchange rate, spread and settlement conditions. |
| Staff time | Reconciliation, support, updates and recovery tests. |
Use current terms for the provider and country involved. Do not treat an illustrative fee comparison as a quotation or assume that conversion into local currency is included.
Integrate payment status with orders
Select an integration supported by the current versions of your store and payment software. Follow the BTCPay deployment documentation if using that system.
The server should confirm payment status through the processor's supported mechanism. A browser redirect or customer screenshot is not sufficient.
Handle:
- Unpaid and expired invoices.
- Partial, excessive or late payments.
- Duplicate notifications.
- Temporary failures between the payment system and store.
- The difference between a detected payment and your accepted settlement state.
Make order updates idempotent: receiving the same event twice must not deliver or credit twice.
Secure keys and recovery
Separate administration from spending permissions where possible. Keep recovery material protected and independent of the production server.
For on-chain receiving, consider a design that does not place spending keys on the website host. Lightning requires additional attention to the online node, liquidity and implementation-specific recovery. Review the BTCPay Lightning documentation.
Do not assume a generic server snapshot can safely restore a Lightning node. Test the supported recovery process before relying on it.
Define refunds and accounting
Record the order amount, payment amount, time and relevant exchange-rate information for your accounting process. Agree on how you will handle price movement between invoicing and refunding.
Bitcoin does not provide a card-network chargeback process, but customers may still require refunds. Verify refund instructions and approvals before sending funds.
If conversion is needed to cover operating expenses, confirm the service and costs rather than assuming automatic conversion is available.
Test before launch
Run a small pilot covering successful payments, invoice expiry, notification failures and refunds. Verify that accounting records reconcile and that another authorized operator can follow the recovery instructions.
Frequently asked questions
Does self-hosting mean zero cost?
No. Software fees and total operating cost are different.
Is Lightning guaranteed to complete every payment immediately?
No. Routing, liquidity and service availability can affect completion.
Does Bitcoin eliminate fraud?
No. Account compromise, false payment evidence and refund scams still require controls.
Choose infrastructure for the tested deployment
If self-hosting fits your operating model, review CR Servers VPS options against the payment software's current requirements. Include storage growth and recovery resources before choosing a plan.