The case against BitPay in 2026 is not the fees. The fees are bad, but they are not the worst part. BitPay's 1.2 out of 5 Trustpilot rating is the receipt. The structural problem is what produces that rating.
BitPay is the oldest crypto payment processor (founded 2011). The product is built around a custodial model that worked when crypto payments meant Bitcoin payments and "compliance" meant collecting an email address. The model in 2026 produces predictable failure modes: verification delays of weeks, "network cost" line items that obscure actual fees, support that operates on a Monday-to-Friday email queue, and a custodial settlement structure that creates exactly the platform risk crypto was supposed to eliminate.
This is a case against BitPay built on the company's own published documentation. Read it before you sign the merchant agreement.
The 1.2 Trustpilot rating
Customer-side reviews aggregated on Trustpilot and BBB describe a consistent pattern. According to Paybis's BitPay review: "BitPay currently holds a 1.2 out of 5 rating on Trustpilot with consistent complaints around verification delays, unclear fees, and unresponsive support."
A 1.2 rating is not a "some users have bad experiences" rating. It is "the median user is unhappy enough to write a public complaint" territory. For a B2B payment processor handling merchant operations, that is structurally damaging.
The same Paybis review documents the verification issue: "BitPay's official documentation states that if verification is pending longer than 24 or 48 hours, users should contact support, but in practice, multiple verified users report waits extending days to weeks."
Verification delays are not annoyance. They are revenue loss. A merchant cannot accept payments while waiting for BitPay to approve the account. Each week of delay is a week of lost revenue.
The fee opacity issue
BitPay's public pricing page advertises 1 to 2 percent plus 25 cents per transaction. Clear enough. But the actual fee a merchant pays includes a "network cost" line item that BitPay calculates separately.
According to BitPay's own support docs, the network cost is "the miner fee needed to confirm a transaction within approximately 20 minutes" using Bitcoin Core's "conservative 2-block fee estimate."
Two problems with this:
- 1.The "network cost" is added on top of the percentage fee. The merchant's actual cost is percentage + flat 25 cents + network cost. The total can be 3 percent or more once network conditions spike.
- 1.The "conservative 2-block fee estimate" is intentionally high. BitPay calculates the fee to confirm fast, charges the merchant, then pockets any spread between what was charged and what the chain actually consumed. The merchant has no way to audit the spread.
Paybis flagged the same issue: "BitPay bundles service charges into 'network cost' line items that obscure actual transaction fees." The pricing page advertises 1 percent. The invoice charges 1.4 percent. The difference is in the line item nobody reads.
The Monday-Friday support window
BitPay's support page lists customer support hours as Monday through Friday, 10 AM to 8 PM ET, with weekend hours of 10 AM to 2 PM ET, and expected response times of 24 hours.
In e-commerce, the highest-traffic times are evenings and weekends. A failed checkout on a Friday at 7 PM sits in BitPay's email queue until Monday morning. The merchant's customers see a broken payment flow for 60+ hours.
The structural problem is that BitPay's support model is enterprise-style for an SMB-style customer base. The merchants paying 2 percent are not enterprise. They need same-day support. They get next-week support.
The custodial settlement structure
This is the structural problem the fee discussion obscures. BitPay is custodial. The merchant's payment lands at BitPay, BitPay holds the funds while it converts to the merchant's chosen settlement currency, BitPay then forwards to the merchant's bank or wallet on BitPay's schedule.
BitPay's terms of use state the standard custodial language: BitPay holds merchant balances and forwards according to the agreed schedule. A merchant cannot directly request a payout outside that schedule. A merchant cannot move funds before BitPay has processed them.
In the FTX-and-Celsius era, this should make every merchant nervous. $15 billion has been lost to custodial failures since 2014, including FTX ($8B) and Celsius ($4.7B frozen). The court ruling in the Celsius bankruptcy made the structural point explicit: customer deposits into a custodial platform become the platform's property at the time of deposit. BitPay's terms operate on the same legal structure.
Is BitPay going to go bankrupt? Probably not. BitPay is profitable and well-capitalized. But "probably not" is not a feature. It is the absence of a problem. The merchant pays a 1-to-2 percent fee for a settlement structure that introduces counterparty risk the underlying rail (Bitcoin, Ethereum) does not require.
The merchant-side KYC requirement
BitPay requires merchant-side KYC at all volume tiers. BitPay's complaints page and supporting docs describe the standard enhanced-due-diligence process for new merchants: business registration, beneficial owner ID, bank statement history, and a "high-risk industry assessment" for verticals BitPay flags.
For low-risk merchants, the KYC process is annoying but completes. For high-risk verticals (gambling, adult, forex), the rejection rate is high enough that BitPay is not a reliable option. According to BitPay's pricing page: "High-risk industries may face elevated fees disclosed during account setup." The unwritten part is that many applications never get an "elevated fee" offer. They get a rejection.
What BitPay does well
This is a one-sided case, but BitPay does have real strengths worth naming.
Brand recognition at checkout. "Pay with BitPay" carries weight with consumers who associate the brand with crypto payments. A merchant who values brand equity at checkout pays a premium for it.
Mature plugins. BitPay's Shopify, WooCommerce, Magento, and other e-commerce integrations are battle-tested and well-documented. A merchant integrating from scratch will find BitPay easier than newer alternatives.
Compliance posture. BitPay's regulatory posture is the strongest in the industry. For merchants who specifically need a US-registered money services business as their payment processor, BitPay is one of the few options.
These advantages are real. They are not worth a 2 percent fee, a 1.2 Trustpilot rating, and a Monday-Friday support window for most merchants.
The alternative without the trade-offs
A non-custodial flat-fee rail eliminates the structural problems at the cost of the brand-recognition feature. Plaitr is one example: $99 to $999 monthly subscription based on volume tier, no per-transaction fee, no merchant-side KYC, no custodial holding, same-day settlement direct to the merchant's wallet, every L1 and leading L2 supported, 24/7 operation because the chain is the support team.
The trade-off is brand equity at checkout. A "pay with Plaitr" button does not carry the same recognition as "pay with BitPay." For most merchants this is a fixable problem (white-label the checkout, brand it however you want). For some, the BitPay brand is the asset.
What to do this week
Pull your last 12 months of BitPay invoices. Compute: 1. Average effective rate (total fees ÷ total volume) 2. Cumulative support response time on incidents 3. Number of "verification" or "review" delays that cost you revenue
Compare against the flat-fee alternative at your volume tier. If the effective rate is above 1.5 percent or your support incidents add up to more than 48 hours of delay across the year, the math favors switching.
The case against BitPay in 2026 is not that fees are too high. It is that BitPay's product is built for a customer base that no longer exists. The crypto payment merchant in 2026 wants a non-custodial rail with same-day support and a flat predictable cost. BitPay does not offer any of those three.