OpenNode vs Apa: Bitcoin-Only Processor vs Multi-Chain Non-Custodial Checkout

OpenNode is a Bitcoin payment processor. A customer pays in Bitcoin — either on-chain or, more commonly for speed, over the Lightning Network — and OpenNode processes that payment, optionally converting it to fiat, and settles to the merchant. Its Lightning focus is the headline strength: Lightning payments confirm effectively instantly, which is a materially better experience than waiting on Bitcoin block confirmations. OpenNode positions itself squarely at Bitcoin-only businesses that want fast, cheap acceptance of BTC.

Apa works across many chains. A customer pays in any of nine assets on any of roughly ten networks, and the payment settles on-chain directly to a wallet you control. There is no platform balance in the middle — Apa is the rail between customer and wallet, not a place funds accumulate.

The core contrast is scope and custody. OpenNode is a specialized Bitcoin/Lightning processor that touches funds in transit; Apa is a multi-chain, non-custodial checkout that settles straight to your wallet. Neither is 'more correct' — they suit different businesses.

OpenNode operates a semi-custodial model. Payments transit through OpenNode-managed Bitcoin addresses before being forwarded or settled to the merchant, which is what allows OpenNode to offer instant conversion and scheduled fiat settlement. OpenNode itself recommends that merchants set up and withdraw to their own Bitcoin wallet rather than leaving funds on the platform — a sensible practice precisely because funds pass through OpenNode's control on the way.

That custody-in-transit is the trade-off for OpenNode's conveniences: auto-conversion, exchange-rate locks, and bank settlement all require the processor to hold the coins briefly. It is a reasonable design, but it is not non-custodial.

Apa is non-custodial by design. Funds settle directly to your own wallet and Apa never holds a balance, not even in transit for conversion. If eliminating any custodial hop is a priority — for compliance, treasury policy, or simply principle — that is a structural difference between the two products rather than a matter of degree.

OpenNode's asset support is deliberately singular: Bitcoin only. It supports BTC on-chain and over the Lightning Network. There are no altcoins and no stablecoins — if a customer wants to pay in USDC or ETH, OpenNode is not the tool. For a Bitcoin-maximalist merchant that is exactly the point; for a business that wants stablecoin revenue it is a hard limit.

Settlement is flexible within that Bitcoin scope. OpenNode can keep you in BTC (on-chain or Lightning) or automatically convert Bitcoin to fiat at the time of payment and settle to your bank. Fiat settlement is available in eight currencies — USD, EUR, GBP, BRL, MXN, AUD, HKD, and CAD — with bank transfers typically arriving in one to two business days, per OpenNode's product pages as of early 2026.

Apa spans nine assets — BTC, ETH, SOL, USDC, USDT, POL, BNB, AVAX, and TRX — across roughly ten chains including Bitcoin, Ethereum, Solana, Base, Polygon, BNB Chain, Avalanche, and Tron. Settlement is on-chain, directly to your wallet, in the asset and chain you chose. Apa does not offramp to a bank; it delivers crypto to your wallet, and you can nominate a stablecoin if you want stability without leaving the chain.

OpenNode publishes a clean, flat headline: 1% on payments and payouts, with no setup costs, minimums, or monthly commitments, per its pricing page as of early 2026. The detail underneath is favorable for Lightning-first businesses: Lightning withdrawals are free, scheduled transfers are free, instant on-chain settlement carries the 1% fee, and bank transfers in local currency carry a 0.2% fee. OpenNode also states it does not charge conversion fees, so moving BTC to fiat does not add a separate percentage on top.

That 1% flat rate is one of the more competitive headline numbers in crypto payments, and it comfortably undercuts the roughly 2.9%-plus-fixed fee of card networks.

Apa charges a flat 1.5% that is final and all-in, falling to 0% for direct same-asset settlements. The important distinction is what all-in means. OpenNode's 1% is a genuinely low and honest headline, but because OpenNode is semi-custodial, payments first transit its managed addresses; consolidating your Bitcoin to your own on-chain wallet then carries a network (miner) fee on top of that 1% — only the free Lightning withdrawal path avoids it. Apa settles in a single on-chain step directly to the wallet you control, so its 1.5% is the complete cost with no separate withdrawal or platform-balance step. On pure headline Bitcoin economics OpenNode can be cheaper, especially over Lightning; the fair framing is that Apa's number is all-in and non-custodial across nine assets and ten chains, while OpenNode's 1% is Bitcoin-and-Lightning only and, for on-chain self-custody, sits before the withdrawal network fee.

OpenNode gives Bitcoin merchants real volatility tooling. You can take payout in BTC (on-chain or Lightning) if you want to stay in Bitcoin, or you can auto-convert to fiat at the moment of payment with an instant exchange-rate lock that protects you against price movement between payment and settlement. Fiat then settles to your bank in one of eight supported currencies, typically within one to two business days. The one thing OpenNode cannot do is settle you into a stablecoin — its world is BTC or fiat.

Apa approaches volatility by decoupling pay-in from payout. A customer can pay in BTC while you receive USDC on the chain you choose, so you get stablecoin settlement without an offramp and without waiting on a bank. You pick your payout asset and chain once, and every payment lands that way.

So both remove volatility risk, but via different destinations. OpenNode converts Bitcoin to fiat in your bank; Apa converts pay-in to your nominated on-chain asset — including a stablecoin — instantly and without leaving the chain.

Both products deliver the finality that makes crypto attractive versus cards. OpenNode states that once transactions are complete you do not have to worry about impacts to revenue — Bitcoin settlement is final, there are no chargebacks, and there is no fraud-protection overhead of the kind card networks impose. That immutability is inherent to Bitcoin, and it is one of OpenNode's core selling points.

Apa is the same in substance: confirmed on-chain payments are final and there are no chargebacks, across every chain it supports.

The nuance is again about scope. OpenNode's finality is Bitcoin finality, backed by the most battle-tested settlement network in crypto. Apa's finality spans multiple chains, so you get the same no-chargeback guarantee whether the customer paid in BTC, ETH, SOL, or a stablecoin. For a Bitcoin-only merchant the difference is immaterial; for a multi-asset merchant Apa extends the same protection across the board.

OpenNode offers a solid, focused integration set: a hosted checkout, a payment button, a Bitcoin API with documentation and webhooks, and e-commerce plugins. For a developer building Bitcoin or Lightning acceptance, OpenNode's API is well regarded and the Lightning support is first-class. Everything is oriented around Bitcoin, which keeps the surface area small and the docs coherent.

Apa's integration set covers the same core jobs across many chains: a hosted checkout, shareable payment links, and a developer API with webhooks. The payment-links path is worth noting — it makes ad-hoc and social selling straightforward without any storefront integration, which OpenNode does not emphasize in the same way.

The defining developer-experience difference is self-hosting. OpenNode is a hosted, managed processor — it is not self-hostable or open source. Apa is self-hostable, so a team that wants to run the checkout inside its own infrastructure, for control or data residency, can do so. If self-hosting is a requirement, OpenNode cannot meet it and Apa can.

OpenNode is an excellent fit for Bitcoin-first businesses. If you want to accept BTC and Lightning specifically, value instant Lightning settlement, and are happy with a flat 1% (with free Lightning withdrawals) and optional fiat settlement to your bank in eight currencies, OpenNode is arguably the strongest specialized choice on the market. Its Bitcoin-only focus is a strength for merchants who share that focus.

Apa is the better fit for businesses that want more than Bitcoin: acceptance of nine assets across roughly ten chains, non-custodial settlement straight to their wallet, stablecoin payout without an offramp, and the ability to decouple what the customer pays from what the merchant receives. It also wins for anyone who needs to self-host, which OpenNode cannot do.

Put simply: choose OpenNode if your world is Bitcoin and Lightning; choose Apa if you want multi-chain acceptance, non-custodial settlement, and self-hosting.

Starting with Apa takes only a few steps because there is no custody to configure and no balance to fund. You connect the wallet you want to receive into and choose your default payout asset and chain — for instance USDC on Base for stable, on-chain settlement, or BTC on Bitcoin if you want to stay in Bitcoin like an OpenNode merchant would.

Then you pick how to collect: a hosted checkout for your storefront, shareable payment links for one-off or social sales, or the API with webhooks for a custom flow. Because pay-in is decoupled from payout, customers can pay in any of Apa's nine assets — including BTC and Lightning-adjacent Bitcoin flows — while you consistently receive the one asset you nominated.

And because Apa is self-hostable, teams that want full control can run it in their own infrastructure. Whether hosted or self-hosted, every payment settles on-chain, directly to your wallet, with no chargebacks and no platform holding your funds in transit.