NOWPayments vs OpenNode

Three hundred and fifty against one#

No pair in this index has a wider coverage gap. NOWPayments publishes the longest asset list here; OpenNode publishes a count of one.

That is a difference in product category rather than in quality. One is a general processor and the other is a Bitcoin specialist that supports Lightning properly, which almost no general processor does.

The question is not which number is larger. It is whether your customers hold anything other than bitcoin, and if they do, whether you want their money.

Lightning is the specialist's whole argument#

On-chain Bitcoin confirms in roughly ten minutes and costs a fee that does not shrink with the payment. At small ticket sizes both properties are wrong and no provider quality compensates.

Lightning fixes both, settling in seconds at negligible cost. The specialist supports it as a first-class rail; the generalist lists Bitcoin among seven networks without it.

For a business taking many small payments, that single line reverses the coverage argument completely. Three hundred and fifty assets is worthless if the one your customer holds settles too slowly to sell a coffee.

One publishes the rate, the other the payouts#

The generalist publishes a flat 1% on processing and nothing about conversion or payout. The specialist publishes zero conversion and a full payout structure — on-chain scheduled and Lightning on-demand free, on-chain on-demand at 1% — and no processing rate at all.

Between them they publish most of a fee table, and neither publishes all of one. That is a neat illustration of why this index reports disclosure separately from cost.

Both sit at sixty-eight percent disclosure, which is mid-table. Different fields, same total.

Custody splits them cleanly#

The generalist is non-custodial: settlement reaches a wallet the merchant controls and no provider balance exists. The specialist holds funds, which is what makes its scheduled withdrawals and fiat settlement possible.

That trade is entirely coherent on both sides. You cannot deliver dollars to a bank account on a schedule without holding something first.

It is also the decision to take before the rate. The custody guide covers what each side costs when a provider has a bad quarter.

Fiat settlement exists on one card#

The specialist documents settlement into bank currency. The generalist records it as unpublished, which for a non-custodial provider is close to structural: a system that never holds a balance is not the shape that pushes bank transfers.

For a coffee shop or a small business pricing in dollars, that one line settles the pair regardless of everything above it.

For a business content to hold what it receives, it is a feature that will never be switched on.

Neither names a plugin#

Both cards enumerate no first-party ecommerce integrations. Two of the better-known providers in this category, and both leave the storefront path undocumented.

That puts an API integration in front of a shop owner either way, and it is a genuine mark against both. The WooCommerce list covers the providers that have done this work.

Point of sale is documented on both, which softens it for a physical business considerably more than for an online one.

Product surface beyond the checkout#

The generalist documents mass payouts, recurring billing, point of sale and invoicing. The specialist documents point of sale and invoicing, and records mass payouts, recurring billing and white label as unpublished.

For a platform paying out to users, only one of these has a documented answer. For a shop taking payments and nothing else, the surfaces are equivalent.

Neither publishes a white-label tier, which is the category norm rather than a differentiator.

How the totals land#

Coverage is worth twenty-five in the method and it decides this pair on paper: nine against three. The specialist's total is respectable despite that, carried by cost and support.

That gap flatters the generalist for any Bitcoin-only business, which is a real limitation of scoring a specialist on a general scale. Reweighting coverage downward is the honest way to read this page.

Support scores higher on the specialist, which is unusual and reflects a narrower product with better-documented operational behaviour.

What to ask each of them#

To the specialist: the processing rate, which is the one number missing from an otherwise unusually complete card, and how Lightning channel liquidity is handled at your payment volumes.

To the generalist: the conversion spread and the payout cost, and whether Lightning is supported at all, since it is absent from the published network list.

To both: verification requirements, recorded as undisclosed on each card after checking.

Where this pair actually lands#

A business taking small, frequent bitcoin payments and banking in dollars takes the specialist and never notices the asset count.

A marketplace or an international store meeting customers with unpredictable holdings takes the generalist, keeps its own keys, and arranges fiat conversion separately.

Anyone weighing this pair on the numbers alone will pick the generalist and may pick wrongly. The right question is what your customers hold, not how long the catalogue is.

Confirmation policy is worth asking about#

How many confirmations a provider waits for before treating a payment as settled is a commercial setting rather than a technical constant, and neither card publishes its number.

On the specialist that question mostly disappears over Lightning, where settlement is effectively immediate. It returns for on-chain payments, where one confirmation averages ten minutes and three averages half an hour on a pending screen.

On the generalist it applies across seven networks with different finality characteristics, so the answer is probably a table rather than a number. Ask for the table.