18.04.2025
TRC20, ERC20 and other USDT formats: overview and comparison
Read article
Accepting Bitcoin payments can help an online business reach crypto-native customers, support international buyers, reduce dependence on card-only checkout, and add another payment rail for digital products, deposits, subscriptions, invoices and cross-border transactions.
But accepting Bitcoin is not the same as posting a wallet address on your website.
A business needs to decide how payments are created, how invoices are matched to orders, how long to wait for confirmations, who handles network fees, what happens if the customer sends the wrong amount, and whether the company wants to hold BTC or convert it into a stablecoin or fiat currency.
The right setup depends on your business model. A small online store, SaaS platform, iGaming product, VPN service, marketplace, Telegram bot and mobile app will not need the same Bitcoin payment flow.
This guide explains how Bitcoin payments work for businesses, which integration methods are available, what risks to plan for, and where a crypto payment gateway can simplify the process.
To accept Bitcoin payments, your business gives customers a way to pay for goods, services, subscriptions, deposits, invoices or account balance using BTC.
In practice, a Bitcoin payment flow usually includes:
For a simple one-time sale, this may look straightforward. For a real online business, every step matters.
If the amount is wrong, the order may not match. If the invoice expires, the customer may still send funds late. If the transaction fee is too low, confirmation may take longer. If the business holds BTC, accounting and volatility become part of finance operations. If the website grants access before verifying payment, fraud and support problems can appear.
This is why many businesses use a crypto payment gateway instead of building the entire process from scratch.
Bitcoin remains the most recognized cryptocurrency. For many customers, “pay with crypto” still starts with BTC. That brand recognition matters, especially for international digital services, privacy-conscious buyers, high-trust purchases and audiences that already hold Bitcoin.
But Bitcoin is not ideal for every payment scenario.
On-chain Bitcoin transactions are strong for security, liquidity and global reach, but they can be slower and more expensive than transactions on some other networks. Bitcoin’s average block interval is designed around roughly 10 minutes, and real confirmation time can vary depending on network conditions and fee level. That means on-chain BTC is not always the best option for low-value, high-frequency or instant-access purchases.
For small payments, balance top-ups, gaming deposits or frequent repeat purchases, businesses may need a wider crypto payment mix:
The practical answer is not “Bitcoin or nothing”. It is usually “Bitcoin as part of a wider crypto payment mix”.
For a broader comparison of payment assets, see the guide on top cryptocurrencies for accepting payments.
Bitcoin and stablecoins solve different payment problems.
Bitcoin is useful when customers want to pay with the most recognized crypto asset, when the purchase value is meaningful, when the audience already holds BTC, or when the business wants to support crypto users without relying only on stablecoins.
Stablecoins are useful when the business wants price predictability. A payment in USDT or USDC is easier to connect to a USD-denominated invoice, subscription, balance or internal accounting process. For many businesses, stablecoins are more operationally convenient than holding volatile assets.
That does not mean Bitcoin is less important. It means the checkout should match the use case.
For example:
If your finance team wants to reduce exposure to price movement after accepting crypto, read the guide on protecting crypto payments from volatility.
There are three main ways to accept Bitcoin payments online: direct wallet payments, self-hosted payment tools, and crypto payment gateways.
The simplest method is to create a Bitcoin wallet and show your address to customers.
This can work for very small businesses, donations, manual invoices or early testing. It gives you direct control over funds and does not require a payment provider.
But direct wallet payments create operational problems quickly:
Direct wallet payments are usually not enough for a serious checkout flow. They may be acceptable for manual sales, but they do not scale well for e-commerce, SaaS, marketplaces, deposits, subscriptions or automated access.
A self-hosted payment processor gives more automation while keeping control over funds.
The best-known example is BTCPay Server. It can create invoices, track payment status and connect with e-commerce platforms. This model is attractive for businesses that want self-custody, no processing fees and technical control.
The trade-off is responsibility.
You need to manage hosting, updates, backups, wallet security, checkout reliability, invoice logic, integrations and support. For technical teams that understand Bitcoin infrastructure, this can be a strong choice. For companies that want fast launch, business reporting, AML tools, multi-asset support and guided integration, it may add more complexity than expected.
Self-hosted tools are best when control is more important than convenience.
A Bitcoin payment gateway is usually the most practical option for online businesses.
A gateway can generate payment invoices, show QR codes, detect transactions, update payment status, connect to your website or app, support several cryptocurrencies, provide reporting and help with settlement rules.
For the customer, the flow is simple: choose crypto at checkout, select BTC, scan a QR code or open a wallet, send payment and receive confirmation.
For the business, the gateway reduces manual work:
This is the model most companies should evaluate first when they want Bitcoin payments as part of a commercial checkout.
The exact setup depends on your provider and product, but the business process is similar.
Start with the use case.
Are customers asking for BTC? Are you selling to international users? Do you have card declines? Are you serving crypto-native customers? Is Bitcoin part of a broader payment strategy? Do you need deposits, subscriptions, top-ups, invoices or one-time purchases?
The answer affects the payment flow.
For example, a one-time e-commerce order may need a simple hosted checkout. A SaaS subscription may need renewal logic. An iGaming deposit needs fast balance crediting and clear status. A marketplace needs reconciliation between buyer, seller, fee and payout records.
Bitcoin should solve a specific payment problem, not just add a new logo to checkout.
Choose the model based on operational maturity.
Use a direct wallet only for manual or very early testing.
Use a self-hosted setup if your team wants custody, technical control and is ready to maintain the infrastructure.
Use a gateway if you want to connect Bitcoin payments to checkout, orders, accounts, reporting and support without building every part internally.
Most commercial teams should start by evaluating gateway functionality before deciding to self-host.
Before integration, define the post-payment logic.
Will the order be confirmed after one confirmation, several confirmations, or after the gateway marks it paid? Will the customer get instant access or wait? What happens if the payment is underpaid? What if it arrives after invoice expiration? What if the customer overpays? How do refunds work?
For Bitcoin, confirmation policy matters because payment finality is not the same as clicking “Pay” with a card. A transaction can be broadcast before it is deeply confirmed. The business should choose a policy that fits transaction value and risk.
High-value orders may require more confirmation confidence. Low-value digital access may tolerate a faster but more risk-aware flow.
A good Bitcoin checkout should not feel like a technical instruction page.
The customer should see:
Avoid asking customers to copy long addresses when a QR or wallet-open flow is available. Avoid generic errors like “payment failed” without explaining whether the issue is expiration, wrong amount, slow confirmation or unsupported transaction.
The broader principles are similar to any payment method: fewer manual steps, more clarity, better status visibility. The guide on why multiple payment methods matter explains how payment choice affects checkout conversion.
A hosted page or HTML widget can be enough when payment is simple: one-time orders, digital products, manual invoices, early-stage MVPs or landing pages.
An API is better when payment must trigger product logic automatically:
For technical teams, the main integration question is not “Can we show a Bitcoin address?” It is “Can our system trust payment status and update the product correctly?”
The crypto payment API checklist covers invoices, statuses, webhooks, idempotency, test mode and backend verification. For lighter setups, see when an HTML widget for crypto payments is enough.
After receiving Bitcoin, the business has to decide what to do with it.
There are three common options:
Holding BTC creates upside and downside exposure. It may be acceptable for companies with a treasury strategy, but it can complicate accounting and cash flow.
Converting into a stablecoin can make operations more predictable, especially when invoices, salaries, suppliers or reporting are denominated in USD or another fiat currency.
Converting into fiat can be useful when the company does not want to hold crypto at all, but availability depends on provider, jurisdiction, banking access and compliance requirements.
CryptumPay can support automatic conversion into USDT, which is useful for businesses that want to accept Bitcoin but avoid holding a volatile asset after checkout.
Bitcoin payment acceptance is not finished when the button appears on the website.
Finance needs records:
Support needs context:
Without this, Bitcoin payments can create manual work even if the checkout looks simple.
Bitcoin payment cost depends on network conditions and transaction structure. When the network is busy, users may need to pay a higher fee for faster confirmation. When the fee is too low, the transaction can take longer to confirm.
For merchants, this affects checkout in several ways.
First, the customer may abandon payment if the fee feels too high for the order value. This is especially important for low-ticket purchases.
Second, the order may stay pending longer than expected. If the business sells instant-access products, this can create support tickets.
Third, the customer may misunderstand who pays the network fee. If the amount received is lower than expected, the invoice may be underpaid.
Fourth, the business needs a policy for late payments. If a BTC transaction arrives after the invoice expires, the system should know whether to credit it, refund it or send it to manual review.
For a deeper explanation, see the article on how crypto payment fees work.
Bitcoin payments fail or create support tickets for predictable reasons.
The most common issues are:
These are not only technical problems. They are checkout design problems.
A good Bitcoin payment flow should explain the exact amount, status, expiration and next step. It should also give the business enough data to handle edge cases without asking the customer for screenshots.
The same logic applies across crypto checkout. The guide on failed crypto payments explains how wrong amounts, expired invoices, network confusion and poor status handling reduce payment conversion.
Usually no.
Bitcoin is important, but many customers who use crypto for payments prefer stablecoins because the amount is easier to understand. If the order is priced in USD, EUR or another fiat currency, a customer may find 100 USDT more predictable than a changing BTC amount.
A strong crypto checkout often includes Bitcoin plus stablecoins and selected networks.
This gives users choice:
The business should not add every token blindly. It should choose assets based on customer demand, liquidity, fees, wallet support, compliance needs and support complexity.
If you are deciding between stablecoins, start with the guide on USDT, USDC and other stablecoins. If USDT is a key option, review the differences between TRC20, ERC20, BEP20 and other USDT formats.
For e-commerce, Bitcoin can help with international buyers, high-value goods, privacy-conscious customers and customers who already hold crypto.
The payment flow should connect BTC invoices to orders automatically. The store should not rely on manual address checks. Refund rules should be clear before launch.
For a wider store setup, see the guide on accepting crypto payments in an online store.
For SaaS, Bitcoin may work for annual plans, invoices, account credits or customers in markets where card payments are unreliable. For monthly subscriptions, stablecoins or saved payment flows may be easier to operate.
The key is renewal logic. If every renewal requires a manual BTC transfer, the payment method may create churn instead of solving it.
VPN, hosting, VPS, proxy, cybersecurity tools and other digital products often have customers who value global access and flexible payment options. Bitcoin can be a strong method here, especially when traditional card rails create friction.
The product should grant access only after verified payment status, not just after the user claims to have paid.
For iGaming, gaming, ad networks, creator platforms and balance-based products, Bitcoin can be one option, but speed matters. If users need frequent deposits or top-ups, stablecoins and lower-fee networks may be more practical for daily usage.
Bitcoin can still be offered for users who prefer BTC, but it should not be the only crypto option if instant balance crediting is central to the product.
For B2B, Bitcoin can work for larger invoices, cross-border services and clients that hold crypto treasury. The business should define exchange-rate timing, payment window, accounting records and settlement asset before accepting the first invoice.
Bitcoin transactions are irreversible. That reduces some payment risks, but it does not remove operational or compliance risk.
A business still needs to think about:
Requirements differ by country, business model, customer type, transaction size and provider setup. This article is not legal, tax or financial advice. Before accepting Bitcoin at scale, businesses should confirm requirements in their own jurisdictions.
In CryptumPay, Bitcoin can be accepted as part of a broader crypto payment setup with tools such as API or widget integration, dashboard visibility, AML checks, 2FA, withdrawals and optional conversion to USDT.
Before choosing a provider, ask practical questions.
Does it support BTC and the other assets your customers use? Can customers pay from common wallets? Does the provider generate invoices and QR codes? Can it detect payments automatically? How are underpayments, overpayments, late payments and refunds handled?
Check the integration model. Does the provider offer API, widget, hosted checkout, payment links, plugins or White Label? Can your backend receive reliable webhooks? Is there a test environment? Can you map payment statuses to orders, subscriptions, deposits and user accounts?
Check finance controls. Can you see transaction history, fees, settlement asset, withdrawals and balances? Can you export records for reconciliation? Can you convert BTC into USDT or another asset?
Check risk controls. Does the provider offer AML screening, account protection, 2FA and review workflows? What are the merchant responsibilities?
Check support and edge cases. If a customer sends too little, pays late or asks for a refund, can your team resolve it without manual chaos?
Use this checklist before going live.
Define the business use case: one-time orders, subscriptions, deposits, invoices, top-ups or marketplace payments.
Choose the payment architecture: direct wallet, self-hosted processor or crypto payment gateway.
Decide whether to accept only BTC or BTC plus stablecoins and other major assets.
Set confirmation rules based on order value and risk.
Define what happens with underpayments, overpayments, expired invoices and late payments.
Choose settlement logic: hold BTC, convert to USDT, or convert to fiat where available.
Prepare accounting fields: transaction hash, order ID, amount, exchange rate, status, fee and settlement asset.
Build status logic into the product: pending, detected, confirmed, paid, expired, failed, review, refunded.
Test the checkout on desktop and mobile.
Give support access to payment context.
Review AML, security, tax and regulatory requirements for your jurisdiction.
Monitor payment conversion, success rate, support tickets, confirmation delays and reconciliation workload after launch.
You can accept Bitcoin payments directly to a wallet, through a self-hosted tool or through a Bitcoin payment gateway. For most businesses, a gateway is the most practical option because it can create invoices, show QR codes, detect payments, update statuses and connect payments to orders or accounts.
If you accept BTC directly, yes. If you use a payment gateway, the setup depends on the provider. Some gateways let you avoid managing customer-facing wallet addresses manually and may support conversion into stablecoins or fiat settlement where available.
On-chain Bitcoin can be less convenient for small payments because confirmation time and network fees may be high relative to the order value. For frequent low-value payments, stablecoins, lower-fee networks or Lightning-based flows may be more practical.
That depends on your treasury policy and risk tolerance. Holding BTC exposes the business to price movement. Some companies prefer to convert BTC into USDT or fiat to make accounting and cash flow more predictable.
Bitcoin transactions are generally not reversible like card payments. That can reduce chargeback-style risk, but it also means businesses need clear refund rules, payment verification, AML controls and support processes.
For most online businesses, the easiest path is a crypto payment gateway with an API, widget, hosted checkout or payment link. The right option depends on how deeply payment status needs to connect with your product.
Accepting Bitcoin payments can be valuable, but the business setup matters more than the logo on the checkout page.
A weak implementation creates manual wallet checks, unclear payment status, support tickets, accounting gaps and volatility exposure. A strong implementation connects BTC invoices to orders, shows clear payment instructions, handles confirmations, records settlement data and gives customers a predictable checkout experience.
Bitcoin works best when it is part of a thoughtful payment strategy: BTC for recognition and crypto-native demand, stablecoins for price predictability, and a payment gateway for automation, reporting and operational control.
Create an account and connect the checkout yourself, or talk to sales and we will plan the integration with you.
