The right processor is one that can serve your business, support the assets your customers use, and settle funds the way your finance team needs. A payment processor can manage checkout and blockchain monitoring, but you still decide which funds to accept and how to handle them. Settlement means the movement of collected payment funds into your chosen fiat currency or crypto balance.
Your choice affects checkout, custody, fees, and exposure to volatility. A business that needs steady cash flow may prefer fiat currency, while another may want to hold crypto. Neither approach suits every company. Use clear requirements to compare what each provider can support and what your team can manage.
Set a written acceptance and conversion policy before you compare provider features.
Key Takeaways
- Confirm that a provider can serve your business and its customer markets.
- Check each asset-network pair, not just the token name.
- Compare settlement options and the full cost of receiving funds.
- Choose between custodial processing and self-custody based on your controls.
- Test checkout, accounting, refunds, and exceptions before launch.
How to Evaluate Crypto Payment Processors for Your Business

Score each candidate against six essentials: legal reach, asset and network coverage, settlement, total cost, security, and technical fit. Start with must-haves, such as the states you serve, your required assets, and the way finance needs funds delivered.
A processor can generate a payment address or QR code, monitor a blockchain transaction, confirm payment, and settle proceeds in fiat or crypto. That workflow covers more than a wallet-only setup, but it does not take over every merchant obligation. You still need clear operating rules and records.
Compare candidates with the same business scenario. Score each criterion against your actual checkout volume, customer needs, and accounting workflow. A long asset list matters little if the provider cannot support your state or the network your customers use.
Remove any candidate that fails a must-have requirement before comparing nice-to-have features.
Before contacting providers, write down the answers to these five questions:
- Which customer markets matter most to your business?
- Do you want funds in fiat currency, crypto, or both?
- Which assets do customers request most often?
- What does your checkout and accounting stack require?
- Who will manage payment exceptions and customer questions?
Keep the answers specific. For example, “USDC on a supported network” is more useful than “stablecoins.” A payment processor should explain the payment states, timing, and records its workflow provides. A demo should use your likely order types, not a generic sample checkout.
Use the scorecard to keep sales conversations focused. Ask each provider to show how its process works from the customer’s payment screen through your finance records.
Can the provider serve your U.S. business legally?
Before reviewing features, confirm that the provider can onboard your legal entity and support the states where you operate. State reach matters because federal registration alone does not establish permission to serve every U.S. jurisdiction.
FinCEN registration is federal and does not itself authorize money transmission in any state. Money transmitters may need state licenses in 49 states and Washington, D.C.; Montana is an exception for most crypto businesses. State money transmitter licenses can take 6-18 months per state.
Check state reach and provider registrations
Ask how the provider’s access varies by state and which services your business can use. CoinPayments supports U.S. businesses, though some features may vary by state. It requires additional approval for transactions of $350,000 or more.
Coinbase Business is available to businesses with a legal entity in the United States or Singapore. It requires a registered business entity and a business bank account. BitPay uses verification-based processing limits, and merchants can request higher limits by providing additional information.
Use four checks to screen each provider:
- Business eligibility in every state where you operate.
- Applicable federal registrations and state licenses.
- Required onboarding documents and review time.
- Transaction limits and escalation requirements.
Separate provider controls from your obligations
Provider screening can help flag activity, but your business retains its own regulatory obligations. CoinPayments screens transactions for AML, KYC/KYB, and sanctions controls. Its business verification can take up to a week before a business can accept crypto payments.
Match the provider’s screening process to your own business model, customer markets, and transaction types. Get advice on the exact model and states you serve, especially if you have more than one legal entity or sales channel.
Treat license coverage as a state-by-state check, not a single national yes-or-no answer.
Which cryptocurrencies and networks should you accept?
Start with the assets your customers are most likely to use, then verify the exact network each checkout option accepts. Demand and liquidity help narrow the list, while network support determines whether a payment can reach the right destination.
BTC, ETH, and stablecoins are common assets to assess for a merchant checkout. CoinPayments supports more than 40 digital assets, including BTC, ETH, USDT, USDC, LTC, BNB, TRX, XRP, SOL, and DOGE. A token name alone does not identify the asset-network pair your checkout accepts.
Choose assets around customer demand
Use customer requests, order size, and your ability to manage each asset to shape your list. Stablecoins such as USDC and USDT are designed to track a fiat currency’s value, which can reduce price swings compared with BTC or ETH.
Stablecoins are not risk-free. Their value can change, and the risks depend on the token and the systems behind it. More volatile assets can move in value between payment and conversion, so consider whether your business can absorb that change.
Keep the first launch focused. Supporting an asset creates customer-service and reconciliation work, even when the processor handles much of the transaction flow. Add another asset only when it serves a clear customer need.
Verify the exact network at checkout
USDT and USDC can be used on networks including Tron, Polygon, and Ethereum. A provider may support a token on one network but not another. A payment sent on an unsupported network may not arrive as expected.
Test the checkout instructions with the exact asset and network you plan to enable. Confirm that the payment screen identifies both before the customer copies an address or scans a QR code. This detail is especially important when the same token operates across several blockchains.
Display the asset and network together wherever the customer receives payment instructions.
How will payments convert and reach your account?
Decide first whether the business needs predictable fiat deposits or wants to hold crypto after checkout. Your cash needs should drive that choice, since a crypto balance can change in value before you use it.
Some providers convert automatically into local currency; others let you keep crypto or split settlement between currencies. BitPay supports local-currency settlement, cryptocurrency settlement, or a mix, with one fiat currency and up to five cryptocurrencies at a time. Compare each payout rail, minimum balance, and withdrawal fee.
Choose between fiat and crypto settlement
Fiat settlement can make day-to-day budgeting simpler because funds arrive in a bank account in a selected currency. Holding crypto keeps the business exposed to its price changes, but may suit a company that already uses digital assets.
Approved CoinPayments businesses can receive bank payouts through ACH, SWIFT, SEPA, or Faster Payments. Transfers between CoinPayments wallets have no network fees, while transfers to external wallets incur standard network fees. The destination and payment method affect the total you receive.
Check payout timing and rate windows
Separate the customer’s blockchain confirmation from the processor’s payout schedule. A processor’s settlement-speed clock starts after the transaction is confirmed. Confirmation time depends on the network and the fee the customer pays.
CoinPayments locks rates for 60 minutes at checkout. BitPay issues merchant settlements every business day for payments processed since the prior business day’s settlement. Its USD ACH settlement has a $20 minimum, and funds generally appear two business days after settlement is issued.
BitPay says cryptocurrency settlements are sent daily and usually reach the merchant’s wallet within one hour, with applicable miner fees covered by BitPay. Square standard Bitcoin withdrawals are free and take about 24 hours. Rush withdrawals cost $2 plus a pro rata share of network fees and take about one hour. Priority withdrawals cost $3 plus a pro rata share and take about 20 minutes.
Compare the time from customer confirmation to bank or wallet availability, not just the advertised payout schedule.
What will processing actually cost?
Compare the amount the business ultimately keeps, not just the percentage shown beside “processing fee.” The fee basis matters: a percentage of a payment, a per-transaction charge, and a conversion fee affect your proceeds differently.
Published rates offer a starting point, but the terms may use different fee bases. Include network, conversion, withdrawal, and payout charges when calculating total cost. Use the same transaction amount and settlement choice for every provider comparison.
| Provider | Stated rate or fee | Condition or fee basis |
|---|---|---|
| BitPay | 2% plus $0.25 | Monthly volume under $500,000 |
| BitPay | 1% plus $0.25 | Monthly volume of $1 million or more |
| CoinGate | 1% | Published processing fee |
| NOWPayments | 1% | Published processing fee |
| Coinremitter | 0.23% | Published processing fee |
BitPay’s listed tiers show why you should use your expected monthly volume when comparing rates. A quote at one volume level may not match your business’s actual price. The percentage also does not tell you whether other charges apply to the same transaction.
Coinbase Business lists a 1% transaction fee for migrating merchants, and Coinbase Commerce charged a 1% transaction fee. Square lists 0% processing fees for Bitcoin payments through December 31, 2026, then 1%. Square also charges 1% on daily sales converted to Bitcoin and 1% for buying or selling Bitcoin, with a possible spread on buys or sales.
CoinGate and NOWPayments list processing fees of 1%, while Coinremitter lists 0.23%. CoinsPaid, Triple-A, and BVNK require a written quote because they do not publish a processing rate. Treat these as distinct pricing examples, not proof that the lowest listed percentage costs least.
Ask each finalist to itemize processing, conversion, network, and withdrawal costs for the same transaction scenario.
How does the provider protect funds and transactions?

Security depends both on the provider’s controls and on who can authorize a transfer from the business account. Control of the keys determines who can move funds and who must protect access credentials.
With custodial processing, the provider controls the keys and funds. With self-custody, the business controls the keys and funds, including key security and backups. Neither model removes the need for clear access rules and recovery plans.
Understand who controls the keys
Custodial processing can reduce the technical work your team handles, while leaving operational dependence on the provider. Ask how the provider limits account access and what happens if service is disrupted. Consider who can initiate a transfer and who can approve it.
Self-custody gives your business direct control, but your team must secure keys and maintain backups. Decide how many people need access and how the business would restore access after a lost device or credential.
Verify security and transfer controls
Ask about account roles, approval workflows, key protection, incident response, and recovery. Get a clear explanation of how the provider detects and handles unauthorized access, and how your team will be notified if action is needed.
CoinPayments is SOC 2 Type 1 compliant and ISO 27001 certified. It requires two-factor authentication for all outbound transfers. Certifications and controls are useful evidence to examine, but they do not guarantee that funds cannot be lost.
Review the actual steps required to add a user, approve a payout, and change account access. A policy that only one employee understands can fail when that employee is unavailable. Write the handoff into your normal finance procedures.
Confirm who can approve outbound transfers and what recovery steps apply if an authorized device or credential is lost.
Will the processor fit your checkout and accounting stack?
A good integration should carry payment status from checkout through order fulfillment and into finance records. Test the full path, because a payment marked complete in one system may not automatically update the others.
An API can connect a custom storefront directly to the processor, while an e-commerce plugin may fit an existing platform with less development. Choose the path your team can maintain, not just the one that launches fastest.
Match the integration to your platform
A processor API can create a payment intent and return a payment address, crypto amount, QR code, and rate expiry. Shopify and WooCommerce are examples of e-commerce platforms with processor integrations.
| Integration path | Named example or function | What it connects |
|---|---|---|
| API checkout | Payment intent, address, QR code, rate expiry | Storefront to processor |
| E-commerce plugin | Shopify or WooCommerce | Store checkout to payment flow |
| Accounting connection | Coinbase Business with QuickBooks and Xero | Transaction records to accounting software |
Test payment events and reconciliation
Blockchain monitoring can produce pending and confirmed events. Your storefront needs to handle both states clearly, so an order is not fulfilled before the processor marks its payment confirmed.
Coinbase Business offers QuickBooks and Xero accounting integrations. Coinbase Commerce did not offer accounting integrations. Confirm that the records your finance team receives include the fields needed to match payments to orders.
Before launch, test these five cases:
- A successful payment reaches the correct order.
- An expired rate produces the expected customer message.
- A pending payment changes to a confirmed event.
- An order reconciles with the processor transaction record.
- An accounting export includes the transaction details.
Run the full payment-event flow in a test environment before accepting a live customer payment.
What tax records and reports will your business need?
Build a recordkeeping process that captures both the crypto received and its U.S. dollar value at the time of receipt. Record the receipt first, then track what happens if the business later sells, exchanges, or spends the asset.
Cryptocurrency income is generally measured at fair market value when received. Selling cryptocurrency, trading it for another cryptocurrency, or using it to buy goods or services can trigger a U.S. capital gain or loss. The receipt value and a later transaction are separate tax events to track.
Keep records that connect the original payment to any later movement of funds. Save transaction IDs, timestamps, asset and network, fair market value at receipt, conversion details, and settlement records. These details help your finance team explain the recorded value and reconcile activity.
In the United States, brokers must report gross proceeds from digital-asset sales and exchanges on Form 1099-DA beginning January 1, 2025. Cost-basis reporting begins January 1, 2026. The IRS receives a copy of Form 1099-DA reporting gross proceeds.
U.S. taxpayers may be subject to backup withholding on crypto sales or exchanges beginning January 1, 2027, if they do not submit required tax certification information. The date and condition matter: this is not automatic withholding for every crypto payment.
Keep processor reports with your business’s own transaction records, rather than treating a payout statement as a full tax ledger. Ask a qualified U.S. tax professional how your business’s facts affect income, gains, and reporting.
Reconcile processor statements against the business’s own transaction records before closing each reporting period.
How will you handle refunds and payment errors?

Write the refund and error policy before enabling crypto checkout, because a confirmed blockchain payment cannot simply be reversed. A refund is a new transfer from the business to a wallet address, not a reversal of the original transaction.
Processor workflows distinguish pending from confirmed payments. Do not treat a pending payment as confirmed or send a refund before reviewing its status. Clear rules help customer support explain delays without promising that a blockchain transfer can be undone.
Use these five checks before approving a refund:
- Verify the asset and network used for the payment.
- Compare the received amount with the invoice.
- Confirm the transaction’s current status.
- Verify the refund address with the customer.
- Record the approval and refund transaction ID.
Underpayments and overpayments need a consistent response. Keep the order on hold while you compare the amount received with the invoice. Then follow a written policy for a top-up, partial fulfillment, or refund.
For a wrong-network payment, do not assume the funds arrived in a usable wallet. Check the processor’s payment record and the exact network involved before deciding how to respond. Delayed confirmations also call for a status check, not a second payment request that could create a duplicate.
Decide whether refunds go out in crypto or fiat, and explain how the refund amount is calculated. A refund in crypto may differ in fiat value from the original payment if the asset’s price changed. Keep the decision consistent with your stated policy.
Require a second person to review the destination address for high-value refunds.
Which providers match your operating needs?
Shortlist providers by the operating model you want, not by how many coins appear on a feature page. Fit the workflow to your team’s capacity, customer markets, and required settlement method.
Coinbase Commerce is no longer a live option for U.S. merchants: its transition deadline passed on March 31, 2026, and the Commerce portal became inaccessible afterward. U.S. merchants should assess Coinbase Business instead of relying on the former Commerce service.
Coinbase Business is custodial and supports USDC today; it describes USDT as coming soon. It has no self-custody option. This can suit a business seeking a managed, USDC-centered workflow, provided the required asset and network are supported.
BitPay may suit merchants weighing broad crypto-settlement reach. It supports cryptocurrency settlements in over 200 countries and direct bank deposits in 37 countries. Check how those options align with the markets where your business actually operates.
| Acceptance approach | Who controls the funds and infrastructure | When it may fit |
|---|---|---|
| Hosted payment processor | Provider handles checkout and blockchain monitoring | Businesses prioritizing a managed workflow |
| Direct wallet acceptance | Business controls wallet and payment matching | Teams with crypto expertise and security processes |
| Self-hosted solution such as BTCPay Server | Business runs payment infrastructure and controls wallet | Technically capable teams prioritizing control |
Eliminate any option that cannot meet a required customer-market, asset, or settlement need.
Coinbase Commerce once supported hundreds of assets, but it did not provide custody or fiat offramps. That history does not make it a current U.S. option. Compare active products on their present operating model, not a legacy feature list.
Check current eligibility and exact asset-network support for each finalist. A provider’s country reach does not guarantee that every feature, currency, or asset is available to your specific business.
Conclusion
A sound choice is the processor that meets your nonnegotiable requirements without adding controls your team cannot maintain. Fit depends on your legal footprint, desired settlement, customer assets, and capacity to manage custody and exceptions.
Create a short scorecard for your leading candidates. Request written confirmation of eligibility, fee components, and settlement terms before signing. Put the finalists through the same documented checks, then choose the one your business can operate confidently.











-white.png)
-white.png)

