- Why businesses accept crypto in 2026
- The six-step setup (with a processor)
Accepting crypto as a business means letting customers pay you in Bitcoin, Ethereum, or a stablecoin like USDC through a payment processor or directly to your own wallet. The setup takes about 30 minutes with a processor (BitPay, Coinbase Commerce, NOWPayments). The harder work is tax reporting, fraud prevention, and deciding whether to hold crypto or auto-convert to fiat.
How we verified this We cross-referenced the IRS digital asset filing pages, BitPay pricing and pricing disclosures, Coinbase Commerce fees page, Stripe's accept-crypto-payments guide, the U.S. Chamber of Commerce reporting on crypto acceptance pros and cons, BVNK's nine-step merchant guide, BitPay's Decrypted 2025 report, and Visa onchain analytics. Where a number is forecast rather than measured, we say so.
Key Takeaways
- Over 25 million global merchants accepted cryptocurrency as a payment method in 2025, up from about 18 million in 2023 (CoinLaw merchant adoption stats).
- BitPay's 2025 merchant count reached about 130,000 with payment volume growth of 12% year-over-year and an average transaction of about $800 (BitPay Decrypted 2025).
- Coinbase Commerce charges a 1% flat fee (Coinbase Help).
- BitPay charges 2% + $0.25 under $500K/month, 1.5% + $0.25 between $500K and $1M, and 1% + $0.25 above $1M (BitPay Pricing).
- Stablecoins accounted for 52% of total crypto transaction volume in 2025; Bitcoin held about 28%.
- The IRS introduced Form 1099-DA for the 2025 tax year to standardize broker reporting of digital asset gross proceeds.
Why businesses accept crypto in 2026
The reasons are concrete, not ideological. Three patterns show up across published merchant data and the U.S. Chamber of Commerce summary.
Lower fees on cross-border transactions. A stablecoin payment from a buyer in Singapore costs the merchant a 1% processor fee versus 2 to 4% on international card transactions plus FX spread. For B2B sellers with global customers, the savings are real.
Customer demand. Merchant surveys show roughly 73% of merchants planned to accept crypto within two years (CoinLaw 2025). The actual customer-side adoption is smaller than the merchant intent number suggests, but for some verticals (technology, travel, luxury goods, services with international clients) it is significant.
No chargebacks. Crypto transactions on a blockchain are final. A processor cannot reverse the payment under network rules. This is the single most underappreciated advantage for sellers exposed to friendly-fraud chargebacks on cards.
The flip side: crypto volatility, tax complexity, and limited consumer protection on the buyer side push most merchants to auto-convert received crypto to fiat at the moment of receipt.
The six-step setup (with a processor)
A merchant using a regulated processor is up and accepting payments in about 30 minutes. The BVNK nine-step guide at bvnk.com walks through a more detailed enterprise version; this is the SMB-friendly path.
- Pick a processor. BitPay, Coinbase Commerce, NOWPayments, and Crypto.com Pay are the most common for SMBs. Stripe also supports crypto via Bridge (its 2024 acquisition).
- Create the merchant account. Standard business KYB: formation docs, EIN, beneficial owners, business bank account for fiat settlement.
- Choose what you accept. At minimum, USDC and Bitcoin. Add USDT if you have buyers in Asia. Avoid niche tokens unless a specific customer asks.
- Choose settlement. Auto-convert to fiat (USD, EUR) for daily bank deposit (BitPay, Stripe via Bridge), or hold crypto in the processor's wallet and convert manually (Coinbase Commerce default).
- Integrate the checkout. Hosted payment page (5 minutes, just a link). Shopify or WooCommerce plugin (15 to 30 minutes). API integration if you need a custom flow.
- Configure tax reporting. Connect to your accounting software or a dedicated crypto tax tool (Bitwave, Cryptio, TaxBit). Set up the 1099-DA workflow with your processor.
The Stripe accept-crypto guide at stripe.com and the PayPal merchant guide at paypal.com both cover the same six-step pattern with platform-specific detail.
Processor comparison: fees, settlement, and integration
These are the four processors a U.S. SMB would realistically evaluate.
| Processor | Merchant fee | Settlement | Best for | Notable tradeoff |
|---|---|---|---|---|
| Coinbase Commerce | 1% flat | Crypto held in Coinbase wallet; manual fiat conversion required | Cheapest pure-stablecoin processor; Shopify integration via 2026 Commerce Payments Protocol | No auto-conversion to bank by default; manual treasury work |
| BitPay | 2% + $0.25 under $500K/month; 1.5% + $0.25 to $1M; 1% + $0.25 above | Bank-fiat in 1 to 2 business days (USD, EUR, GBP, CAD, AUD) or stablecoin | Mature enterprise B2B; broadest fiat settlement options | Higher fee at low volume |
| NOWPayments | 0.4 to 0.5% | Bank or crypto wallet | Lowest published fee; 250+ supported tokens | Smaller compliance footprint than BitPay; not suited to enterprise B2B |
| Crypto.com Pay | 0% to ~0.5% | Crypto held; conversion at withdrawal | Strong consumer-facing integration; cashback for buyers | Geographic limits in U.S.; not for B2B-heavy use |
| Stripe Crypto (via Bridge) | Quoted per merchant | Auto-convert to fiat at receipt | Existing Stripe merchants wanting one stack | Available only to qualified merchants |
Sources: Coinbase Commerce fees, BitPay Pricing, NOWPayments docs at nowpayments.io, Crypto.com Pay merchant docs, Stripe-Bridge press materials.
Practical advice. If you are Shopify-based and selling B2C, Coinbase Commerce via the Commerce Payments Protocol is the cheapest. If you are B2B with international buyers and want one-stop fiat settlement, BitPay handles it cleanly. If fee minimization is everything and you can absorb operational work, NOWPayments at 0.4 to 0.5% is the lowest published rate. If you already run Stripe for cards, Stripe Crypto is the simplest stack to add without changing tools.
What customers actually pay with
Mix matters because it determines your tax and conversion workflow. Across published 2025 data (BitPay Decrypted, Visa Onchain Analytics, CoinLaw crypto payment industry statistics):
| Asset | Approximate share of merchant payment volume | Notes |
|---|---|---|
| Stablecoins (USDC, USDT, PYUSD) | About 52% | Largest single category; fastest growing |
| Bitcoin (BTC) | About 28% | Largest single token by volume |
| Ethereum (ETH) | About 6% | Common for higher-ticket B2B |
| Litecoin (LTC) | About 4% | Loyal merchant base; small share |
| Other (Solana, Polygon, Dogecoin, etc.) | About 10% | Long tail |
BitPay reports that stablecoins reached 40% of its 2025 payment volume, up from 30% in 2024. That mirrors the broader category shift away from volatile assets toward stablecoins for commerce.
The practical takeaway: prioritize stablecoin acceptance first. Bitcoin still matters but accounts for less than a third of transactions.
Settlement: hold crypto, auto-convert, or split
This is the single most important policy decision for a merchant accepting crypto. The choice depends on your treasury function, accounting comfort, and risk tolerance.
Auto-convert to fiat at receipt (BitPay, Stripe-Bridge, Crypto.com Pay's bank settlement option). Lowest risk. The processor converts the customer's crypto to your local fiat the moment the on-chain transaction confirms, then deposits to your bank in 1 to 2 business days. The merchant never holds crypto on their balance sheet. Best for any merchant without a dedicated treasury function.
Hold crypto in the processor wallet (Coinbase Commerce default). The processor receives the customer's payment and holds it in a wallet you control. You decide when to convert. Risk: holding through a 10 to 20% drawdown without hedging can wipe out the margin on the original sale. Reward: if you have stablecoin-denominated obligations or you want exposure to BTC/ETH, holding is cheaper than buying it on a market.
Split settlement (BitPay, available on most processors). Receive some portion in fiat, hold some in crypto. Common pattern for B2B sellers building a small stablecoin treasury without taking volatile-asset risk: settle 90% to USD, hold 10% in USDC for vendor and contractor payments.
For most SMBs the right default is auto-convert all to fiat at receipt. Holding requires treasury tooling, hedging, and accounting policies that most small businesses are not equipped to run.
Tax and accounting: the 1099-DA era
Starting tax year 2025, U.S. brokers must report digital asset gross proceeds to the IRS and to taxpayers on Form 1099-DA. The CNN Business explainer at cnn.com and the IRS digital assets page cover the requirement.
For a merchant accepting crypto, the practical implications:
- Every crypto payment received is ordinary income at the fair market value at the moment of receipt. This matches the existing treatment but is now broker-reported.
- Selling, swapping, or converting crypto is a separate disposition. If you receive 0.05 BTC, hold for a week, then sell for USD, the gain or loss between receipt and sale is a capital event.
- Cost basis tracking matters more than ever. Auto-convert at receipt simplifies this because the receipt and disposition happen simultaneously at near-equal values. Holding requires lot tracking.
- Stablecoin de minimis rule: brokers may use a simplified reporting method for qualifying stablecoin sales under $10,000 in annual gross proceeds per customer, but the taxpayer still owes full reporting on the tax return.
For more on the treasury side of crypto income, see our guides to revenue recognition and accrual accounting. For tax filing fundamentals see guide to small business tax filing.
Fraud and chargeback risk
Crypto's biggest underappreciated benefit for a merchant is the absence of chargebacks. On a blockchain, a confirmed transaction cannot be reversed by the customer or their bank. There is no equivalent of a card-network dispute window.
That changes the fraud math in three ways.
Friendly fraud disappears. A customer who pays in crypto cannot later claim the charge was unauthorized to their bank. The most common SMB chargeback category (about 50% of all card disputes) effectively does not exist for crypto payments.
Cardholder fraud also disappears. Stolen cards cannot be used to pay you in crypto. The compromise vector moves to stolen wallets, which is a much less common attack on the customer side.
New risks appear. The biggest is customer-mistake risk, sending crypto to the wrong chain or wrong address. A buyer who sends USDC to your Ethereum address from a Solana wallet has lost the funds and will ask you for a refund. Most processors handle this by displaying the address and chain explicitly with QR codes, but mistakes still happen.
Other risks include price volatility between checkout and settlement (mitigated by auto-convert), regulatory risk for high-risk verticals (cannabis, adult content, gambling), and operational risk if you self-custody.
For comparison with card-network fraud rates and chargeback economics, see our payment fraud statistics and cryptocurrency payment statistics pages.
Original research: when crypto acceptance pays for itself
We modeled the breakeven point for a U.S. SMB adding crypto acceptance to an existing card-only checkout, across three vertical types. Inputs sourced from BitPay published merchant data, Coinbase Commerce fees, Visa and Mastercard merchant discount rates from Federal Reserve interchange data, and chargeback rate benchmarks from Visa Chargeback Insights.
| Vertical | Card fees baseline | Card chargeback cost | Crypto fee (Coinbase Commerce) | Crypto chargeback cost | Crypto pays off at... |
|---|---|---|---|---|---|
| Digital services (SaaS, design, consulting) | 2.9% + $0.30 | 0.4% of GMV | 1.0% | 0% | Any volume; pure savings |
| Cross-border B2B | 3.5 to 4.5% + FX spread | 0.2% of GMV | 1.0% | 0% | Any cross-border transaction |
| Domestic e-commerce | 2.5% + $0.30 | 0.6 to 1.2% of GMV | 1.0% | 0% | When 5%+ of customers want crypto |
| Travel and hospitality | 2.5 to 3.5% | 0.8% to 1.5% of GMV | 1.0% | 0% | Almost immediately; high chargeback category |
| Restaurants and quick-serve | 1.8 to 2.4% | 0.1% | 1.0% | 0% | Almost never; low chargeback, customer mix wrong |
For cross-border B2B and high-chargeback verticals (travel, digital services, certain ticketed events), crypto acceptance starts paying for itself with the first transaction. For low-chargeback, low-margin, high-volume domestic verticals (restaurants, retail), the value is much harder to find and most merchants in those categories should not add crypto.
When accepting crypto is the wrong call
There are five clear scenarios where the operational cost outweighs the value.
- Your customers do not ask for it. If you have not had a single customer ask for crypto acceptance in a year, do not add it. The setup is easy; the tax reporting and reconciliation work is not.
- Your average ticket is under $25. Per-transaction fees and tax-reporting overhead do not amortize.
- You operate in a strictly regulated industry (banking, securities, federal contracting). Crypto acceptance can trigger additional regulatory review. Confirm with counsel.
- You sell to customers who pay primarily by ACH. ACH at $0.25 per transaction is already cheaper than the best crypto processor. Crypto is not a free upgrade. See our ACH payment guide for comparison.
- You cannot dedicate any time to compliance. Crypto reporting will not go away on its own. If you do not have someone to handle 1099-DA reconciliation, do not add crypto until you do.
The Stripe guide at stripe.com and the BitPay business page at bitpay.com/business both gloss over these scenarios, they are written by sellers of the service.
Volatility, hedging, and the auto-convert default
Crypto's headline volatility is the reason most merchants choose to auto-convert. Even Bitcoin's typical monthly drawdown of 5 to 15% can wipe out the gross margin on a transaction received and held for a few days.
Three policy options, ranked by complexity:
- Auto-convert all crypto to USD at receipt. Removes volatility risk entirely. Pay the small spread the processor charges on the conversion (typically 0.5 to 1%). This is the right default for any merchant without dedicated treasury.
- Hold stablecoins, auto-convert volatile assets. A reasonable middle ground if you want a small stablecoin treasury for vendor payments. USDC and PYUSD at $1.00 do not carry the volatility risk of BTC or ETH, but they remain a taxable property for IRS purposes and require accounting work.
- Self-custody the full crypto balance, hedge separately. Only relevant for merchants with dedicated treasury or finance functions and an explicit strategic reason to hold crypto. Requires custody policy, hedging instruments (perpetual futures or options on CME), and audit-ready bookkeeping.
For SMBs, option 1 is the right answer 95% of the time.
Integration with your invoicing and accounting stack
If you already use an invoicing tool, the cleanest path is to add crypto as another payment method rather than replacing your flow.
Most modern invoicing platforms support crypto via a processor connection, Coinbase Commerce links can be embedded in an invoice's pay page, BitPay offers email-billing integration, and several stablecoin-native invoicing tools (Bitwave, Acctual, Mural Pay) build accounting integration in. See our best invoicing apps with online payments roundup for traditional platforms that now bundle crypto support.
On the accounting side, the workflow is:
- Map crypto receipts to your chart of accounts. Either a single "Crypto receipts" account that flows to revenue, or per-asset subaccounts. Our chart of accounts guide covers the structure.
- Sync transaction IDs and fair market values. Every payment needs a verifiable record. Crypto tax tools pull this from processors automatically.
- Reconcile monthly. Match processor reports to bank deposits and to invoices. The bank reconciliation guide covers the general pattern.
- Report at year-end. Match processor 1099-DAs to your books. Discrepancies almost always come from missing cost-basis records.
When this guide isn't for you
This is a U.S.-focused SMB guide. Merchants in the EU under MiCA, UK under FCA crypto regimes, and other jurisdictions face different licensing, KYC, and reporting requirements. The processor list and fee tiers are largely global, but compliance work differs by region.
It is also not a legal or tax opinion. Crypto regulation continues to change quickly. Verify current requirements with counsel and a CPA before relying on this guide for compliance.
Frequently Asked Questions
How do I receive a crypto payment?
Either share a wallet address and chain directly with the buyer (self-custody, lowest fee), or use a processor (BitPay, Coinbase Commerce, NOWPayments) that handles the wallet, KYC, and conversion. For most SMBs the processor route is the right starting point, setup takes about 30 minutes and the all-in fee is 1 to 2%.
Can someone pay me in crypto if I do not have a wallet?
Yes, through a processor. The processor holds the wallet on your behalf and converts the received crypto to fiat in your bank account. You never touch a wallet. BitPay, Coinbase Commerce, and Stripe Crypto all support this.
How much is $100 worth in crypto?
It depends on the asset and the moment. $100 in USDC or USDT is exactly $100 (each token is pegged to one U.S. dollar). $100 in Bitcoin or Ethereum varies with the spot price; a real-time conversion appears in your processor checkout. For invoicing purposes, you typically denominate the invoice in USD and let the processor calculate the crypto amount at the moment the buyer pays.
Does my business have to pay tax on crypto received?
Yes. The IRS treats crypto as property. When your business receives crypto as payment, it is ordinary income at the fair market value on the receipt date. Selling, swapping, or converting that crypto is a separate disposition event. Starting tax year 2025, your processor reports gross proceeds to you and to the IRS on Form 1099-DA. See the IRS digital assets page.
Can I get chargebacks on crypto payments?
No. Confirmed blockchain transactions are final and cannot be reversed by the customer or their bank. This is one of the strongest reasons high-chargeback verticals (travel, digital services, ticketed events) add crypto acceptance. The flipside is that the customer has no equivalent of a chargeback if they dispute the goods or services, handle disputes through your own customer service policies.
Should I hold crypto or convert to USD immediately?
For most SMBs, convert immediately. Auto-convert removes volatility risk and dramatically simplifies tax tracking. Hold only if you have a specific use for the crypto (vendor payments, payroll, treasury strategy) and you have the accounting tooling to track cost basis cleanly.
Which crypto should my business accept first?
USDC. It is a U.S.-regulated stablecoin pegged to $1.00, supports auto-conversion across all major processors, has the cleanest tax treatment of any crypto asset, and is what most institutional buyers prefer. Add Bitcoin second for retail consumers, USDT third if you have Asia-Pacific buyers.