OpenNode

Service Overview

OpenNode is a Bitcoin-only crypto payment processor. The operating entity is OpenNode, Inc., a Delaware corporation, with a team spread across 6 countries. Its about page states coverage of 120+ countries and 14,000+ registered users, with the product heavily weighted toward the Lightning Network.

Its product boundary is deliberately narrow: no Ethereum, no stablecoins, no fiat card acquiring. It handles collection, payouts and invoicing on a single chain and does that well. For merchants this means a small integration surface and simple mechanics, paid for by a locked-in asset set.

The part that matters most is the settlement model. Most crypto acquirers let coins land in the merchant wallet and leave conversion entirely to the merchant, which keeps price risk on the merchant side throughout. OpenNode does the opposite: at the moment of collection the Bitcoin can be converted to the merchant's chosen fiat at a locked rate, with no markup on the conversion, and the merchant receives the requested fiat amount minus the processing fee. The official pricing page spells this out with one concrete example — a 100 USD request, the customer pays the BTC equivalent, and the merchant receives 99.00 USD immediately. That 1% is the standard fee benchmark.

The fit is therefore clear: merchants who want to accept Bitcoin without holding Bitcoin. The misfit is equally clear: businesses whose customers live in stablecoins, or who need Ethereum and multi-chain assets.

Key Strengths

• One chain, the smallest possible mechanism surface: no multi-chain asset routing, no currency ambiguity, no cross-chain confirmation differences. A merchant only has to understand on-chain versus Lightning. A smaller surface means fewer failure modes to defend.
• Lightning is the primary rail, not an add-on: the official site places Lightning at the center of the product and treats on-chain as the fallback. The confirmation difference is directly visible in checkout — on-chain Bitcoin collection waits for block confirmations, which can mean many minutes, while Lightning settles in seconds, making scan-and-pay feel close to a QR wallet payment.
• Locked-rate conversion moves price risk off the merchant: conversion is stated as free and the settled fiat amount does not move with the market after locking. For an e-commerce team that does not manage crypto treasuries, this matters more than the fee — it means finance does not need a separate volatility gain or loss line.
• Four clearly defined withdrawal paths: scheduled BTC wallet withdrawals are free, instant Lightning withdrawals are free, instant on-chain withdrawals cost 1%, local bank withdrawals are available either on a schedule (next business day) or on demand (1-2 business days). That covers both ends of the speed-versus-cost trade-off.
• No chargebacks by construction: payer-initiated and final settlement means the card-network cycle of retrieval, representment and chargeback never needs to be built. For high-risk categories and digital goods, this is the most concrete saving in the cost of collection.
• Complete developer surface: the official sample creates a charge in roughly 10 lines, charges are the core object, and webhooks plus a hosted checkout cover both custom builds and no-code shops.

Product Ecosystem

Payments

A charge is the core object: the merchant creates a request with an amount and a fiat currency, the system converts to a BTC amount at the prevailing rate, and the customer pays through an on-chain address or a Lightning invoice. Charges support fixed and variable amounts, and a hosted checkout is available for merchants who prefer not to build a front end.

Currency Conversion

Per-charge conversion to the merchant's chosen fiat with a locked rate. Merchants can convert all, part, or none of each payment, which maps onto three financial postures: full volatility avoidance, partial Bitcoin exposure, or pure Bitcoin holding.

Payouts

Beyond collection, OpenNode offers Bitcoin payouts for suppliers, resellers, creators and staff. For businesses that collect and pay out in Bitcoin, both directions live in the same back office, which keeps reconciliation consistent.

Billing and Invoicing

Professional invoicing for service businesses, extending one-off collection into a reconcilable accounts-receivable workflow. For consulting, agencies and subscription billing, invoices fit the settlement process better than a checkout page.

Integrations and API

REST API plus webhooks, with official plugins for Shopify, WooCommerce, Magento, BigCommerce, Substack and Stripe Apps. Custom systems can use only the API and webhooks without adopting any front-end component.

Limitations

• Bitcoin-only is a hard boundary: Ethereum, USDT and USDC are not supported at all. If the target audience holds stablecoins — the dominant pattern in cross-border trade and in several emerging markets — this solution does not apply and a second multi-asset acquirer becomes necessary, which means maintaining two sets of books.
• Fee structure is unfriendly to small tickets: a percentage fee applies equally to a few-dollar charge, while the fixed overhead of reconciliation, bookkeeping and reporting does not shrink. Digital goods, low-ticket subscriptions and tipping need the fee modeled before launch.
• Unavailable to mainland China entities: virtual-currency business activity is explicitly prohibited there, which is a prohibition rather than a difficulty. Overseas entities serving mainland customers still need a separate compliance assessment; technical feasibility is not business compliance.
• Uneven fiat currency coverage: local-currency withdrawal depends on licensed partner rails, so supported currencies and settlement times follow the current official list. Minor currencies often route through USD and incur an extra conversion layer.
• Compliance and accounting remain with the merchant: locked rates solve price risk but not revenue recognition or tax filing. Crypto collection still needs proper bookkeeping and tax treatment handled by the merchant or a professional adviser, and the platform issues no opinion.

Use Cases

• Bitcoin-native businesses (★★★★★): wallets, mining pools, Bitcoin hardware and Bitcoin-adjacent services whose customers already hold BTC. The collection path is as short as it gets.
• Digital goods and content subscriptions (★★★★☆): ebooks, memberships, courses and tipping with no physical logistics; seconds-level confirmation allows instant delivery and there is no chargeback risk at all. The smaller the ticket, the more the fee needs checking first.
• Cross-border services and freelancer settlement (★★★★☆): paying overseas suppliers or creators in Bitcoin avoids correspondent banks and wire delays, while locked-rate conversion fixes the fiat amount on the collection side.
• Adding a crypto option to an existing store or SaaS (★★★☆☆): a second payment method next to existing fiat acquiring, serving the subset of customers who prefer Bitcoin. Bitcoin as the only option limits reach.
• Mainland China operations (☆☆☆☆☆): virtual-currency business is prohibited domestically and the onboarding requirements on merchant jurisdiction cannot be met. Not worth evaluating.
• Stablecoin-centric businesses (★☆☆☆☆): if the treasury and customer base are USDT or USDC, a multi-asset or stablecoin-specialist acquirer is required; OpenNode does not cover it.
• Worst fit: finance teams that need instant fiat settlement and will not carry any price exposure (★☆☆☆☆): proceeds arrive as bitcoin, so the booked amount moves with the market and both month-end close and budgeting demand locked-rate conversion, forcing an accounting model built around fiat to be rebuilt.

Pricing

The table reflects the currently published OpenNode pricing page. High-volume, high-value, high-risk, ISO and reseller accounts can request a custom quote; actual rates and available currencies are governed by the contract and the current official support list.

FAQ

• I want to accept Bitcoin but not carry price risk. What now?
  Enable automatic conversion at collection and choose the conversion ratio — all, part, or a set share. The rate locks at the moment of payment, conversion is stated as free, and the merchant receives the requested fiat amount minus the processing fee. Finance then does not need a separate crypto volatility line.

• Lightning or on-chain — which should I use?
  Prefer Lightning: seconds-level confirmation and very low network fees suit almost every online scenario. Keep on-chain as the fallback for customer wallets without Lightning support, or for larger amounts where the main chain is preferred. Both rails reconcile in the same back office.

• What happens if a customer disputes a payment?
  There is no such process. Payments are payer-initiated and final on-chain, so card-network retrieval and chargeback workflows do not exist. The trade-off is that refunds must be initiated by the merchant as a reverse transfer, and disputes have to be settled directly with the customer.

• Can a mainland China company onboard?
  No. Virtual-currency business activity is explicitly prohibited there, and onboarding restricts merchant jurisdiction and business type. Overseas entities whose customers are mainly in mainland China still need a separate compliance review; running technically is not the same as operating compliantly.

• Does Bitcoin-only shrink the customer base too much?
  That is the cost of the design and it depends on the audience. For Bitcoin-native users, mining businesses or cross-border buyers willing to pay in BTC, coverage is sufficient. If customers are mainly on stablecoins or fiat, treat OpenNode as a supplementary rail and add a multi-asset or fiat acquirer alongside it.

Source: original 16IDC content. Product capabilities, supported countries and fee definitions follow OpenNode's official documentation and your contract.