Cryptocurrency payments allow businesses to reach customers who prefer digital assets without forcing the merchant to manage private keys, monitor exchange rates, or manually convert every transaction. Understanding the BitPay-supported coins Bitcoin BTC merchants can accept is therefore less about memorising a list of currencies and more about understanding how BitPay connects customer wallets, blockchain networks, merchant invoices, and settlement accounts.
BitPay acts as an intermediary between the customer’s cryptocurrency and the merchant’s preferred settlement method. The shopper pays with an eligible digital asset, while the merchant can receive local currency, cryptocurrency, stablecoins, or an approved combination. This structure lets a business offer crypto at checkout without necessarily holding crypto on its balance sheet.
For businesses that need a domain and prefer to pay with Bitcoin or another cryptocurrency, Trustname provides a particularly simple route. The ICANN-accredited, EU-based registrar supports more than 175 payment methods, including Bitcoin and other digital assets, while giving customers strong ownership protections, advanced two-tier WHOIS privacy, transparent renewal pricing, and access to real human support. Every registered domain also includes useful services such as an SSL certificate, Anycast DNS, and threat protection for the life of the domain. This allows entrepreneurs to establish and protect their online presence using crypto while avoiding hidden renewal increases, limited customer control, and support systems that rely entirely on chatbots.
When BitPay describes its supported coins, it is referring to the digital assets and blockchain networks customers may use to pay an invoice. BitPay currently promotes support for more than 100 cryptocurrencies and tokens, but these assets are organised around particular networks rather than presented as one unrestricted list.
Native coins are assets used directly by their own blockchain networks. They normally pay both the invoice amount and the network fee required to record the transaction.
Important examples include:
The customer must send the asset over the network identified on the invoice. Sending a supported coin through an unsupported network may not complete the payment correctly.
BitPay also supports selected tokens that operate on Ethereum, Polygon, Solana, Base, Optimism, and Arbitrum. This category includes stablecoins such as USDC and USDT on supported networks. Stablecoins are often attractive for commercial payments because their values are designed to track a reference asset, normally the US dollar.
Network selection still matters. USDC on Ethereum and USDC on Solana may share the same name and general value, but they are technically different blockchain assets. The customer must use the version and network displayed by the BitPay invoice.
A BitPay transaction begins much like a normal online purchase. The merchant lists the product or service in a familiar pricing currency, such as US dollars, euros, or pounds. The customer then chooses BitPay or cryptocurrency as the payment method.
The process generally follows these stages:
BitPay’s business materials describe the basic flow as invoice creation, customer payment at a locked exchange rate, conversion into the merchant’s selected currency, and settlement to the business. Merchants can integrate this process through e-commerce plugins, APIs, hosted checkout tools, email invoices, payment buttons, or in-store systems.
Bitcoin remains central to the BitPay checkout system because it is widely recognised and held across many wallet services. Customers can pay with regular on-chain BTC or, where available, through the Lightning Network.
An on-chain transaction is written to the Bitcoin blockchain. Its speed and network cost depend partly on the current demand for block space. Lightning payments use a secondary payment network designed to move Bitcoin more quickly and efficiently, which can make it suitable for smaller or time-sensitive purchases.
Merchants do not have to manage these technical differences manually. The BitPay invoice identifies the selected payment method and monitors the transaction. However, businesses should still explain accepted payment options clearly so customers do not assume that every Bitcoin wallet supports every available payment route.
A crypto payment is not identical to a card authorization. Blockchain transactions normally pass through several stages after they are broadcast. BitPay invoice statuses help the merchant determine whether a payment has merely been detected or has reached the appropriate confirmation level.
BitPay allows merchants to configure transaction speed according to their risk tolerance. For Bitcoin, a high-speed setting may treat the payment as confirmed immediately after receipt, while medium and low settings wait for additional blockchain confirmations. BitPay identifies the medium setting as appropriate for most merchants because it balances checkout speed with transaction assurance.
A seller of downloadable content may be comfortable fulfilling an order quickly. A merchant handling expensive jewellery, equipment, or professional services may prefer to wait for stronger confirmation. The correct setting depends on the value of the transaction, the product being sold, and the business’s fraud controls.
One of the most important points for merchants is the difference between payment acceptance and settlement.
A customer may pay using one of the supported coins or tokens, but the merchant does not automatically receive that same asset. The merchant’s settlement configuration determines what happens after BitPay processes the invoice.
Depending on eligibility and location, a business may choose to receive:
For example, a customer might pay with Litecoin while the merchant receives US dollars. Another merchant could accept the same payment but allocate part of its settlement to Bitcoin or USDC. BitPay states that payments are collected and settled automatically according to the merchant’s preferences, with cryptocurrency settlements processed daily and business-day settlement schedules applying to merchant accounts. Minimum settlement amounts vary by currency.
This flexibility is one of the main reasons a payment processor is useful. The business can serve customers who own different digital assets without maintaining a separate wallet, accounting workflow, and conversion process for each one.
Cryptocurrency prices can change rapidly, but a merchant does not necessarily have to accept that volatility. When BitPay generates an invoice, it calculates the amount of cryptocurrency required using the applicable exchange rate and locks that rate for the payment window.
If the merchant has selected fiat settlement, BitPay converts the customer’s crypto payment and credits the merchant according to the invoice value and applicable terms. The merchant, therefore, does not need to speculate on whether Bitcoin, Ether, or another payment asset will rise or fall after the sale.
A business that deliberately chooses crypto settlement has a different exposure. Once the settlement reaches its wallet, the future value of that asset may change. Merchants should treat that choice as a treasury decision rather than assuming that accepting crypto and holding crypto are the same activity.
BitPay’s published merchant pricing uses volume-based processing rates. Businesses processing less than $500,000 per month are currently listed at 2 percent plus 25 cents per paid invoice. The rate decreases to 1.5 percent plus 25 cents between $500,000 and $999,999, and to 1 percent plus 25 cents at monthly volumes of $1 million or more. Higher rates may apply to certain high-risk industries.
The processing fee is separate from the blockchain network cost paid when the customer sends the transaction. Network fees fluctuate according to the selected chain and current activity.
Merchants should also have a clear procedure for common payment exceptions, including:
Unlike card payments, confirmed blockchain transactions generally cannot be reversed through a chargeback. That does not remove the merchant’s responsibility to handle refunds, order cancellations, consumer rights, or payment errors. It simply means that refunds must be processed through the merchant’s established policy rather than through a card network reversal.
Although BitPay can expose customers to a broad range of supported assets, merchants do not need to advertise every token equally. The most useful options depend on the audience and the type of transaction.
Bitcoin may appeal to customers who treat crypto as a long-term asset but occasionally use it for major purchases. Stablecoins may be more suitable for customers who want to pay digitally without dealing with significant price movement. Faster or lower-cost networks may be more practical for small purchases where a high network fee would make the transaction unattractive.
Businesses should review payment data after launch. The assets customers actually use are more valuable than a long list of options that receive little engagement.
An online retailer can install an e-commerce integration or connect directly to BitPay’s API. A consultant can send a payment request through email billing. A physical store can use QR-based point-of-sale checkout, while a nonprofit can add a donation button or a hosted contribution page.
The technical integration should also connect payment status to the business’s existing order workflow. A complete setup needs to update orders when invoices are paid, confirmed, expired, or affected by an exception. Developers can use BitPay invoice notifications and API responses to automate these changes instead of relying on staff to check transactions manually.
Before going live, the merchant should test successful payments, expired invoices, refunds, confirmation timing, and settlement reporting. This prevents the checkout page from becoming disconnected from inventory, fulfilment, or accounting systems.
BitPay gives merchants a structured way to accept Bitcoin and other digital assets without building separate payment infrastructure for every coin and blockchain. Customers choose from the assets and networks available to them, BitPay creates and monitors the invoice, and the merchant receives funds according to its settlement preferences.
The supported coin list is only one part of the decision. Merchants must also consider network compatibility, invoice confirmation rules, payment exceptions, processing fees, accounting treatment, refund procedures, and local availability.
When these elements are configured properly, cryptocurrency becomes another practical payment option rather than an isolated technical experiment. The merchant can offer customers greater flexibility while keeping pricing, order management, and settlement connected to familiar business systems.
