Digital Currency for Businesses: Accepting and Managing Crypto Payments

Businesses across retail, e-commerce, professional services, and B2B supply chains are integrating cryptocurrency payment infrastructure into existing financial operations. This page covers how crypto payment acceptance works mechanically, the regulatory obligations that attach to merchant activity, the scenarios where digital currency payment rails offer measurable advantages or introduce risk, and the structural decision points that determine whether adoption is operationally appropriate for a given business model. The broader regulatory landscape governing these activities is documented at Regulatory Context for Digital Currency.

Definition and scope

For a business, accepting digital currency as payment means receiving a transfer of cryptographic value — most commonly Bitcoin (BTC), Ether (ETH), or a USD-pegged stablecoin such as USDC — in exchange for goods or services. This is categorically distinct from a business investing in digital currency as a treasury asset, though both activities can co-exist on the same balance sheet.

The IRS Virtual Currency FAQ classifies virtual currency received as payment for goods or services as ordinary gross income, measured at fair market value in US dollars on the date of receipt. This classification applies regardless of whether the business converts the received crypto to fiat immediately or retains it. Businesses that later dispose of retained crypto — by sale, exchange, or further payment — trigger a separate capital gain or loss event on any appreciation or depreciation from the original receipt value.

Beyond tax treatment, scope includes:

• Anti-money laundering (AML) obligations — Businesses that cross statutory thresholds into money transmission may fall under FinCEN's regulations at 31 CFR Part 1022, requiring Bank Secrecy Act compliance, Customer Identification Programs, and Suspicious Activity Report filing.
• State money transmitter licensing — 49 US states maintain money transmission licensing regimes; a business that holds customer crypto funds in transit may require licensure depending on jurisdiction. The Conference of State Bank Supervisors (CSBS) publishes multi-state MSB licensing resources.
• Consumer protection requirements — The Federal Trade Commission Act prohibits unfair or deceptive acts, including misleading representations about digital currency payment terms (FTC Act, 15 U.S.C. § 45).

The Digital Currency Authority homepage provides a structured entry point to the full topical reference framework covering these overlapping regulatory domains.

How it works

Merchant crypto payment acceptance follows a discrete process chain that diverges meaningfully from card or ACH flows.

1. Payment request generation — The merchant system (or a third-party payment processor) generates a unique receiving address or QR code tied to the transaction. Amount is typically quoted in fiat and auto-converted to the crypto equivalent at a spot rate locked for a defined window — commonly 15 minutes for Bitcoin and under 1 minute for stablecoins.

2. Customer broadcast — The customer's wallet signs and broadcasts the transaction to the relevant blockchain network. Bitcoin transactions require at least 1 confirmation (roughly 10 minutes average block time) before merchants consider payment final; Ethereum averages 12–15 seconds per block under proof-of-stake.

3. Settlement — The merchant either (a) auto-converts received crypto to USD via an integrated exchange service, receiving net fiat minus processor fees — typically 0.5% to 1% for major processors — or (b) retains the crypto in a business wallet.

4. Accounting entry — IRS Notice 2014-21 and subsequent Revenue Ruling 2023-14 govern recognition. The gross income amount is the fair market value at time of receipt; cost basis is that same value for any future disposition calculation.

5. Reporting — Businesses receiving crypto payments are not exempt from 1099-series reporting obligations. The Infrastructure Investment and Jobs Act (P.L. 117-58, enacted 2021) expanded broker reporting requirements under IRC § 6045 to include digital asset brokers, with phased implementation timelines set by Treasury rulemaking.

Stablecoins — covered in depth at Stablecoins Explained — materially simplify steps 1 through 4 by eliminating spot-rate volatility during settlement windows, but they do not eliminate tax recognition requirements.

Common scenarios

E-commerce and retail — Merchants integrate a payment processor API (such as those operated by licensed money services businesses) that handles address generation, confirmation monitoring, and fiat conversion. The merchant's accounting system receives a fiat-denominated invoice record. This model minimizes direct crypto exposure.

B2B cross-border payments — A US exporter invoicing a foreign counterparty in USDC or USDT can reduce wire transfer latency from 2–5 business days to under 1 hour and avoid correspondent banking fees that routinely exceed $25–45 per transaction on international wires. Cross-Border Payments with Digital Currency details the structural mechanics of this use case.

Treasury retention — Businesses that choose to hold a percentage of received crypto rather than converting immediately take on price exposure. Bitcoin's 30-day realized volatility has historically ranged from 30% to over 100% annualized (per CoinMetrics, a public blockchain analytics data provider), which creates non-trivial balance sheet risk absent a hedging strategy.

Payroll and contractor disbursements — Some businesses disburse contractor payments in crypto. These disbursements are still subject to W-9/1099 requirements for US persons. The IRS position under Notice 2014-21 treats crypto wages to employees as subject to federal income tax withholding and payroll taxes, measured at fair market value on the payment date.

Decision boundaries

Not every business context is appropriate for direct crypto payment acceptance. The following structural boundaries clarify the relevant distinctions.

Direct acceptance vs. processor-mediated acceptance
A business that accepts crypto directly into a self-custodied wallet retains full asset control but assumes custody risk, key management obligations, and direct AML exposure analysis. A business that routes through a licensed payment processor transfers settlement risk and conversion mechanics to the processor but incurs per-transaction fees and introduces a counterparty dependency. For businesses without dedicated financial operations staff, processor-mediated acceptance is the structurally lower-risk path — not because direct custody is prohibited, but because key management failures are irreversible. Private Key Management covers the technical parameters of self-custody.

Stablecoin vs. volatile-asset acceptance
Accepting USDC or USDT eliminates the exchange-rate window problem during transaction confirmation but introduces stablecoin-specific risks: the credit quality of the stablecoin issuer and reserve composition. USDC is issued by Circle and subject to monthly reserve attestations; USDT (Tether) reserve composition has been the subject of CFTC enforcement action resulting in a $41 million penalty in 2021. Businesses treating stablecoins as operationally equivalent to fiat should document that assumption against issuer risk.

Threshold triggers for MSB registration
A business that merely accepts crypto as payment for goods and services and promptly converts to fiat is generally not a money transmitter under FinCEN guidance. However, a business that holds customer funds, exchanges crypto on behalf of customers, or transmits value between third parties crosses into MSB territory. FinCEN's FIN-2019-G001 provides the definitive framework for these classifications.

Tax accounting method selection
Because each lot of crypto received has its own cost basis at receipt, businesses retaining crypto must select and consistently apply a lot-identification method (FIFO, LIFO, or specific identification) for capital gain/loss calculation on disposals. IRS Revenue Procedure 2024-28 addresses transitional rules for wallet-by-wallet basis tracking that took effect for transactions after January 1, 2025. Coordination with a qualified tax professional is essential before establishing an accounting method.

References

• IRS Virtual Currency FAQ — Frequently Asked Questions on Virtual Currency Transactions
• IRS Notice 2014-21 — Virtual Currency Guidance
• IRS Revenue Ruling 2023-14
• IRS Revenue Procedure 2024-28
• FinCEN — 31 CFR Part 1022 (Bank Secrecy Act Regulations for MSBs)
• FinCEN FIN-2019-G001 — Application of FinCEN's Regulations to Certain Business Models
• CFTC Press Release 8450-21 — Tether $41 Million Penalty

Read Next