OpenNode vs BitPay

One asset against fifteen#

OpenNode supports Bitcoin and Lightning. That is the entire list, and it disqualifies the provider immediately for any merchant whose customers hold stablecoins, which in most markets is most of them.

For a genuinely Bitcoin-denominated business the narrowness stops being a weakness. Conversion is free and stated as free, Lightning payouts settle on demand at no cost, and the economics of small-ticket Bitcoin acceptance work in a way they simply do not on the base chain through a general processor.

What does the cost comparison actually look like?#

BitPay's 2% plus a fixed amount is the highest entry rate in this index. OpenNode does not publish a processing rate at all, which means the headline comparison cannot be made from public pages.

What can be compared is everything around it. OpenNode publishes free conversion and free scheduled on-chain payouts; BitPay publishes neither figure. For a Bitcoin-only merchant the surrounding costs favour OpenNode strongly enough that the unpublished processing rate would have to be implausibly high to reverse it.

What happens when a customer wants to pay in USDT?#

At OpenNode, nothing happens. There is no path, and the sale either converts to another payment method or does not convert. For most merchants that single sentence ends the evaluation, which is why the coverage criterion carries the weight it does.

At BitPay the payment goes through, at a rate roughly double the market floor. The comparison is therefore between a provider that cannot serve part of your demand and one that serves all of it expensively, and the right answer depends entirely on how large that part is.

Who is each one wrong for?#

OpenNode is wrong for essentially any merchant whose customers hold stablecoins, which in most consumer markets is the majority. This is a hard disqualification rather than a scoring penalty.

BitPay is wrong for a small-ticket Bitcoin business, where 2% plus a fixed amount per transaction is punitive and Lightning support is the thing that would actually help.

The cost comparison that can actually be made#

Not the processing rate, since OpenNode does not publish one. What can be compared is everything around it: free conversion and free scheduled payouts against two unpublished components at BitPay.

For a Bitcoin-only merchant that surrounding structure favours OpenNode by enough that the missing headline rate would have to be implausibly high to reverse it. That is an unusual position and it follows from how much each provider chose to publish.

What breadth costs and buys#

BitPay supports fifteen assets and OpenNode one. For a business whose customers hold stablecoins, that is the entire comparison and nothing else needs weighing.

For a Bitcoin-denominated business it is close to irrelevant, and the fourteen extra assets are inventory nobody uses. Establish which description fits you before reading any further, because the two readings of this page reach opposite conclusions.

What to send both of them#

Ask OpenNode for the processing rate, which is the one figure missing from an otherwise unusually complete pricing page. Ask BitPay for the conversion spread and the payout cost, which are the two missing from its.

Then ask both how many confirmations they wait for before treating a Bitcoin payment as final. Neither publishes it, and it decides how long your customer waits at checkout, which for in-person acceptance decides whether the product works at all.

If Lightning matters to you, confirm support explicitly rather than inferring it from a network list.

Reading this pair by business type#

A Bitcoin-denominated business, especially one taking small payments in person, should take OpenNode and stop reading. Free conversion, free Lightning payouts and second-scale settlement are the product, and BitPay competes on none of them.

Any business whose customers hold stablecoins should take BitPay, or more sensibly should look at neither and read the wider catalogue, since both are narrow in different directions.

A charity taking Bitcoin donations sits in an unusual middle: OpenNode on economics, BitPay on the documentation a trustee may want. That is a governance preference rather than a payments one.

What would change this comparison#

OpenNode supporting a stablecoin. That single change would move it from a specialist product to a general candidate and would reshape its position across the whole index, not just this page.

Short of that, nothing either provider publishes changes the fact that they serve different businesses.

If you only do one thing#

Check whether any customer has ever asked to pay in something other than Bitcoin. If yes, this comparison is already settled against OpenNode regardless of its excellent fee structure.

What this comparison leaves open#

Unresolved on both sides is confirmation policy, which for in-person Bitcoin acceptance decides whether the product works at all. Neither publishes how many confirmations counts as final. Ask, and if the answer is more than one on the base chain, ask again about Lightning.

OpenNode publishing a processing rate would change this comparison more than anything else could. Both cards carry a checked date for the pages behind them.

Both document point of sale#

That is unusual on this site and it makes the pair genuinely comparable for a physical retailer, where most of the index simply does not compete.

Confirmation time is where they separate. Lightning settles in seconds at negligible cost; on-chain Bitcoin at BitPay does not, and a customer waiting at a counter notices the difference immediately.