Head to head · checked 2026-08-31
BitPay vs Coinbase Commerce
Two US processors with the clearest counterparty risk in the category. Coinbase Commerce charges a flat 1% against BitPay's 2% + $0.25 entry tier. BitPay publishes fiat settlement terms; Coinbase Commerce settles on-chain into USDC and publishes less about payouts.
How do BitPay and Coinbase Commerce differ?
Weights| Gateway | Score | From | Assets | Verification | Settles fiat | Discloses |
|---|---|---|---|---|---|---|
| | 5.6 | 2% | 15 | KYB and KYC | Yes | 79% |
| | 6.2 | 1% | 10 | KYB and KYC | 58% |
Scoring BitPay against Coinbase Commerce
| Criterion | Weight | BitPay | Coinbase Commerce |
|---|---|---|---|
| Assets, networks and geography How many assets and chains are live for merchants, and in which markets settlement actually works. | 25 | 6 | 6 |
| All-in cost Processing percentage, conversion spread and payout cost taken together, not the headline number alone. | 25 | 4 | 7 |
| Onboarding and verification What a merchant must submit before going live, how long it takes, and which verticals are refused outright. | 20 | 4 | 5 |
| Integrations and API Maintained plugins, API surface, webhook reliability and whether a developer can reach a test transaction from public docs alone. | 18 | 8 | 7 |
| Support and operations Reachable channels, published response commitments, and documented handling of underpayment and wrong-network sends. | 12 | 7 | 6 |
| Weighted total | 5.6 | 6.2 |
Where the two diverge
Scored 0–10 · checked 2026-08-31
BitPay Coinbase Commerce
On this page
Two American processors, two different products#
Both answer the counterparty question better than anyone else in this index, which is why merchants who care about that question end up comparing exactly these two. Coinbase Commerce sits inside a listed company whose finances are public. BitPay has fourteen years of operating history and a settlement product built around bank payouts.
The pricing gap is wide and one-directional. Coinbase Commerce charges a flat 1%. BitPay charges 2% plus a fixed amount until half a million monthly. For a merchant below that threshold the annual difference runs to five figures on modest volume.
Where does each one's settlement design push you?#
Coinbase Commerce converts on chain into USDC. That removes volatility without a treasury process and leaves you holding a dollar-denominated token rather than dollars, which is a distinction your accountant may care about more than you do.
BitPay settles daily into a bank account in one of seven named fiat currencies. That is the more conventional shape and the reason finance teams tend to prefer it. If your requirement is money in a bank rather than value on a chain, the premium is buying something specific and Coinbase Commerce does not offer it in the same form.
Which onboarding is more likely to refuse you?#
Both run US compliance processes and both decline a wider range of verticals than European or offshore providers. If your business sits anywhere near the edge of what a US processor underwrites, that risk applies to this whole comparison rather than to one side of it.
BitPay at least signals the issue by stating that high-risk industries pay more, without naming the rate. Coinbase Commerce routes onboarding through Coinbase compliance and publishes less about the outcome. For a business expecting friction, asking before integrating is worth more than either provider's feature list.
Who is each one wrong for?#
BitPay is wrong for anyone below its volume tiers who does not specifically need daily bank settlement. The 2% entry rate is difficult to justify against a flat 1% from a counterparty of comparable standing.
Coinbase Commerce is wrong for a business that needs money in a bank rather than USDC on a chain, and for one whose vertical is likely to fail Coinbase compliance. Both are worth establishing before any integration work, and the verification guide covers what to ask.
Disclosure, where they diverge#
BitPay publishes 79% of the fields tracked here and Coinbase Commerce 58%, which is a wider gap than the rate difference suggests. Volume tiers, verification requirements and settlement currencies are all public on one side and largely absent on the other.
Neither is opaque by the standards of this category. The point is that a merchant choosing between two US providers of comparable standing can price one of them from public pages and cannot price the other.
What you end up holding#
BitPay settles into a bank account in one of seven named fiat currencies. Coinbase Commerce settles into USDC on one of four chains. Both remove volatility; only one removes the asset.
For a business whose accounts are kept in fiat, that difference is a step somebody has to own. It is small and it is not nothing, and it decides this comparison more often than the fee gap does.
What to send both of them#
Ask both, in writing, whether your vertical is accepted, before any integration work. These are the two US-domiciled providers in the index and both decline a wider range of businesses than their European or offshore counterparts.
Ask BitPay for the high-risk rate if that applies to you, and ask Coinbase Commerce what happens between USDC on a chain and money in your bank account, since that step is yours and neither pricing page covers it.
A vague answer to the vertical question is a negative one. Treat it that way and save the engineering.
Reading this pair by business type#
Below half a million monthly, Coinbase Commerce is the straightforward choice on price alone, at a flat 1% against 2% plus a fixed amount. The counterparty question is answered comparably well by both.
Above the BitPay volume tiers the price gap narrows and the settlement design decides instead. A business wanting bank currency daily takes BitPay; one comfortable holding USDC takes Coinbase Commerce and saves the step.
Neither suits a business near the edge of US underwriting, and that is the check to run before any of the above matters.
What would change this comparison#
Coinbase Commerce publishing payout and settlement terms. At 58% disclosure it is the quieter of two providers whose counterparty quality is otherwise comparable, and closing that would make the price advantage decisive.
BitPay reaching its lower volume tiers changes it from the other side, and that is something you can trigger yourself by growing.
If you only do one thing#
Ask both whether your vertical is accepted, in writing, before writing any code. Both are US-domiciled and both decline more businesses than their European counterparts, and a rejection after integration is the most expensive outcome available here.
What this comparison leaves open#
Neither card resolves what happens to a balance if the relationship ends. Both are large enough that insolvency is not the concern; account closure and offboarding are, and neither publishes terms for it. Ask both how long funds remain accessible after an account closes and how they are returned.
Both providers are large enough that terms change through policy rather than negotiation, so re-check the published pages periodically rather than assuming what you agreed still describes the offer.
Read next
Questions merchants ask
Which has lower counterparty risk?
Both are unusually legible for this category. Coinbase Commerce sits inside a listed company with public financials. BitPay has the longer operating history. Neither answer substitutes for asking where funds are held and whether they are segregated.
Which is cheaper?
Coinbase Commerce, clearly, at a flat 1% against 2% plus a fixed amount below half a million monthly volume. On modest volume the annual difference reaches five figures.
Is BitPay or Coinbase Commerce cheaper?
Coinbase Commerce publishes the lower processing rate, 1% against 2%. The published rate is not the whole cost. Neither publishes a conversion spread, so the headline gap is a starting point rather than an answer.
Can you run BitPay and Coinbase Commerce at once?
Yes, and it is the sensible way to switch. Keeping the incumbent live while the new one takes real traffic turns a migration into a comparison you can reverse. Expect uneven effort in this pair: one side publishes no platform integrations, so running both means building one of them against the API.