Accepting Crypto Payments

02 September 2026

Accepting cryptocurrency as a business is not a single decision. It is a stack of decisions: which assets to accept, which blockchain to settle on, which payment processor to trust (or not to trust), how to detect and confirm a payment, how to reconcile it in your books, when to convert to fiat, and what compliance obligations you trigger at each step.

This page maps the entire territory. Each section below groups related topics and points to a dedicated spoke page that answers a specific question in full. If you know nothing about taking crypto payments, start here. If you hit a question that needs deeper treatment, follow the handoff.

Payment flow and settlement mechanisms

The core of any crypto payment system is the movement of value from a customer's wallet to a business's wallet, followed by the business's decision about what to do with that value.

For Bitcoin and other UTXO-based blockchains, the on-chain payment flow is straightforward: the customer constructs a transaction that spends one or more of their unspent outputs (UTXOs) and creates new outputs, one of which pays the merchant's address. The merchant detects the transaction by monitoring the mempool - the pool of unconfirmed transactions - and waits for a certain number of confirmations before treating the payment as final. The number of confirmations depends on the business's risk tolerance; a coffee shop might accept zero-conf for small amounts, while a high-value electronics retailer might wait for six Bitcoin confirmations. The dedicated page [How Bitcoin On-Chain Payments Work for Business] walks through this flow in detail, including address generation, UTXO selection, change output handling, and confirmation depth.

For faster, lower-fee payments, the Lightning Network offers a completely different settlement model. A Lightning invoice is a request for payment that encodes an amount, a destination node, and an expiry time. The customer's wallet finds a path of payment channels to the merchant's node, forwards the payment atomically, and the merchant learns the payment succeeded when the preimage - a secret that proves the payment was delivered - is revealed. The invoice expires, the channel balances update, and the merchant has received spendable bitcoin on Layer 2. [Lightning Network Invoice Lifecycle and Settlement for Merchants] covers invoice generation, payment hashes, preimage revelation, hold invoices for escrow-like holds, and the mechanics of settling those Lightning payments back to on-chain bitcoin.

For stablecoins - USDC, USDT, DAI, and others - settlement happens on EVM chains (Ethereum, Polygon, Arbitrum, Base, Optimism) or on Solana. Each chain has different confirmation finality, fee structures, and wallet compatibility. [Stablecoin Settlement on EVM Chains and Solana for Business] breaks down the trade-offs: Polygon offers sub-cent fees and two-second finality; Ethereum mainnet is slower and more expensive but has the deepest liquidity; Solana's high throughput comes with a different security model. The page also covers token approval mechanics, gas token management, and the use of Circle's Cross-Chain Transfer Protocol (CCTP) for moving USDC between chains.

A fundamental architectural decision underlies all of these flows: custodial vs. non-custodial payment acceptance. A custodial processor holds the private keys and settles to you in fiat or crypto after their internal ledger updates. A non-custodial setup means you control the keys - either through self-hosted software like BTCPay Server or through a hardware signing device. [Custodial vs Non-Custodial Crypto Payment Acceptance] compares the two models on security, counterparty risk, regulatory exposure, and operational complexity.

Payment processors and infrastructure tools

The tools a business uses to accept crypto payments range from full self-hosted solutions to turnkey third-party APIs. The choice depends on technical capability, compliance requirements, and whether the business wants to hold crypto or convert immediately.

BTCPay Server is the leading self-hosted, non-custodial option. It runs on your own server, connects to your own Bitcoin and Lightning nodes, generates invoices with single-use addresses, monitors the blockchain for payment, and supports multiple storefront plugins (WooCommerce, Shopify, Drupal, Magento, PrestaShop). It has a point-of-sale app, a crowdfunding app, pull payments for refunds, and full Greenfield API for custom integrations. [BTCPay Server Self-Hosted Payment Processor Setup Guide] walks through installation, node configuration, invoice generation, and plugin setup.

OpenNode takes the opposite approach: custodial, API-first, with automatic fiat conversion. It handles both Lightning and on-chain Bitcoin payments, sends settlement to your bank account, and integrates with WooCommerce and Shopify. [OpenNode Lightning and On-Chain Payment Gateway for Business] explains the fee structure, settlement timing, and how OpenNode's custodial model changes your risk profile.

Coinbase Commerce lets merchants accept Bitcoin, Ethereum, USDC, and several other assets on-chain. Unlike BTCPay Server, Coinbase Commerce holds the private keys unless you use the self-custody option (which requires a Coinbase Wallet). Settlement is in crypto or fiat via Coinbase exchange. [Coinbase Commerce On-Chain Crypto Payment Acceptance] covers the supported assets, the custody model, the dashboard experience, and the implications of using a US-based regulated entity.

BitPay is one of the oldest crypto payment processors. It offers on-chain Bitcoin, Bitcoin Cash, Ethereum, and stablecoin acceptance, with optional fiat settlement to a bank account. BitPay also provides a prepaid debit card and invoice management tools. [BitPay Merchant Crypto Payment Processing Service] details the merchant onboarding process, the verification requirements, and how BitPay handles refunds and disputes.

Strike is a Lightning-first payment processor that settles in fiat. It uses the Lightning Network for instant, near-zero-fee Bitcoin payments and converts to USD at settlement. The Strike API allows businesses to generate Lightning invoices and receive bank account settlement. [Strike API for Business Bitcoin and Lightning Payments] explains the API endpoints, the fiat conversion mechanics, and the geographic availability.

Zaprite is not a payment processor - it is an invoicing and reconciliation platform that connects to multiple processors and wallets. A business can create an invoice in Zaprite, let the customer pay via BTCPay Server, OpenNode, Strike, or a direct wallet, and then reconcile the payment against the invoice in the same interface. [Zaprite Invoice and Crypto Payment Management Platform] covers invoice creation, payment gateway connections, and the accounting export features.

IBEX Pay provides Lightning Network payment infrastructure targeted at businesses in Latin America and other regions. It offers a simple API, a hosted checkout page, and fiat settlement options. [IBEX Pay Lightning Payment Infrastructure for Business] describes the integration flow and the regional focus.

NOWPayments accepts over 70 cryptocurrencies and can auto-convert them to a single coin or to fiat via partner exchanges. It supports on-chain and Lightning payments, but the conversion rates and fees vary by asset. [NOWPayments Multi-Coin Crypto Payment Gateway] explains the asset list, the conversion options, and the payout schedules.

CoinGate is a European payment gateway that settles to a business bank account in euros or dollars. It supports Bitcoin, Ethereum, USDC, USDT, and several other coins, with automatic conversion at the point of sale. [CoinGate Payment Gateway With Fiat Settlement for Business] covers the supported settlement currencies, the KYC requirements, and the integration plugins.

Accounting, reconciliation, and tax treatment

Taking crypto payments creates an accounting problem that fiat payments do not: every incoming transaction has a hash, a block timestamp, a confirmation count, and a market price at the moment of receipt. Matching that transaction to an invoice and recording it correctly in your books requires a reconciliation process.

[Crypto Payment Reconciliation by Transaction Hash and Amount] explains how a business maps an incoming on-chain or Lightning transaction to a specific invoice. For on-chain payments, the merchant generates a unique address per invoice (or uses a payment URI with an embedded invoice ID). For Lightning payments, the payment hash ties directly to the invoice. The page covers reconciliation tools like Cryptoworth, Cryptio, and CoinTracking, as well as manual methods using block explorers and spreadsheets.

The accounting treatment of crypto payments depends on when you recognize revenue and when you assign a cost basis. If you hold the crypto after receipt, you have a new asset on your books that changes value. If you convert to fiat immediately, you recognize revenue at the conversion price. [Fiat Conversion at Point of Sale vs Post-Settlement for Crypto Payments] compares instant conversion (using a processor like OpenNode or CoinGate) with batch conversion (sweeping to an exchange and selling periodically) and discusses the impact on revenue recognition timing and taxable events.

Getting the crypto from your wallet to your bank account involves exchange settlement rails. Most payment processors offer direct fiat settlement. If you hold the crypto yourself, you need to move it to an exchange, sell it, and withdraw fiat. [Exchange Settlement Rails to Bank Account for Crypto Revenue] walks through the Kraken, Coinbase, Binance, and Bitstamp withdrawal flows, the settlement timeframes, and the fees involved.

Compliance, risk, and security

Accepting crypto payments does not exempt a business from anti-money laundering (AML) and know-your-customer (KYC) obligations. The threshold at which those obligations trigger varies by jurisdiction and by the nature of the business.

[KYC and AML Triggers at Crypto Payment Acceptance Thresholds] explains when a business must collect customer identity information, when Travel Rule data must be transmitted between virtual asset service providers, and how sanctions screening applies to blockchain addresses. The page covers tools like Chainalysis, Elliptic, and TRM Labs for blockchain analytics and address screening, and discusses the difference between a payment processor that handles compliance (like BitPay or Coinbase Commerce) and a self-hosted setup where the merchant bears the full compliance burden.

Security for a self-custody setup means managing private keys, using multi-signature approval workflows for treasury movements, and monitoring for address reuse and UTXO correlation risks. The spoke pages on custodial vs. non-custodial acceptance and on BTCPay Server setup both address key management in depth.

Refunds, errors, and operational edge cases

Crypto payments introduce failure modes that do not exist in card payments. Transactions can be stuck with low fees, invoices can expire, customers can overpay or underpay, and refunds require the merchant to construct a new transaction on the same blockchain.

[Crypto Refund Mechanics On-Chain and via Lightning Network] covers the operational steps for returning funds. On-chain refunds require the merchant to know the customer's address (which they may not have, depending on how the payment was made) and to pay a transaction fee. Lightning refunds can use a new invoice generated by the customer, or - if the merchant supports it - a pull payment that the customer claims. The page also covers partial refunds, the dust limit problem, and the use of BTCPay Server's pull payment feature.

Common errors that businesses encounter include "Transaction not found" in a block explorer after broadcast (usually a propagation delay or a rejected transaction), "Unconfirmed transaction" stuck with a low fee (requiring Replace-By-Fee or Child-Pays-For-Parent acceleration), and "Insufficient funds" despite a visible wallet balance (caused by unconfirmed UTXOs or reserved funds). The spoke pages on on-chain payments and Lightning settlement both include troubleshooting for these errors.

Choosing Your Path

A business accepting crypto payments for the first time should start with one asset (Bitcoin or USDC), one settlement chain (Lightning for Bitcoin, Polygon for USDC), and one processor that handles the complexity of invoice generation, payment detection, and fiat conversion. Over time, as the team understands the operational and compliance requirements, they can add assets, chains, and self-custody infrastructure.

The spoke pages listed below each answer one question in full. Read the ones that match your current stage, and come back to this pillar page when you need to see how the pieces fit together.