OpenNode

• Name: OpenNode
• URL: https://opennode.com/
• Category: bitcoin payments operator / merchant settlement and payout company / hosted checkout and treasury workflow middleware
• Tags: bitcoin-ecosystem
• Summary: OpenNode belongs in companies/ because the practical control surface is not the Lightning rail itself but a named company that onboards merchants, issues API credentials, hosts checkout pages, decides which payout and settlement modes are available, and acts as the source of webhook and dashboard truth for payment state. The useful question is not just can this app accept bitcoin? but which company controls checkout creation, auto-conversion, merchant withdrawals, and the payout workflow businesses depend on?
• What it does:
  • Operates hosted Bitcoin checkout, API-based charge creation, and ecommerce integrations for businesses accepting on-chain and Lightning payments
  • Packages settlement options including optional fiat conversion and bank-wallet-linked auto-settlement rather than leaving merchants with a pure rail-only integration problem
  • Runs withdrawal and payout workflows across multiple transfer types, including Lightning, on-chain, wire, exchange, and internal transfer variants
  • Issues API-key-authenticated merchant access and controls callback / webhook-style payment-status delivery for integrated businesses
  • Sells one-company payment processing, treasury movement, and payout workflow rather than a neutral Lightning baseline
• Key claims:
  • The homepage describes OpenNode as Bitcoin payments at the speed of now and says businesses can get lightning-fast, low-cost bitcoin payments and payouts through APIs, ecommerce plugins, or hosted payment pages
  • The homepage also says merchants can automatically convert bitcoin to local currencies at the time of payment, which is a strong signal that the company boundary matters more than the underlying payment rail alone
  • OpenNode’s llms.txt frames the developer portal as a way to build your own Bitcoin payment infrastructure with OpenNode, which is analytically closer to operator middleware than to a protocol note
  • The create-charge API requires API-key authentication and exposes company-managed workflow fields such as callback_url, success_url, hosted_checkout_url, auto_settle, split_to_btc_bps, and charge TTL, showing that checkout creation and post-payment behavior sit inside one hosted control plane
  • The withdrawals API shows payout routing is also part of the same operator shell, with documented withdrawal types including ln, chain, wire, exchange, internal-fiat, internal-btc, and exchange-to-btc
• Whitepaper: No classic standalone company whitepaper is the important artifact here. The useful primary materials are the OpenNode homepage, docs index, charge-creation reference, and withdrawals reference, which together show a company-operated merchant-processing and payout stack rather than a neutral protocol primitive.
• Sources:
  • https://opennode.com/
  • https://developers.opennode.com/llms.txt
  • https://developers.opennode.com/reference/create-charge
  • https://developers.opennode.com/reference/list-withdrawals

Internal linkages

• Product-layer note: opennode.
• Best self-hosted merchant-stack contrast: btcpay-server.
• Useful adjacent company reads: bvnk, moonpay, and lightspark.

Protocol / company boundary

• opennode is the product-layer note for the checkout and API surface businesses integrate with.
• This company note is the operator boundary: merchant onboarding, API-key issuance, hosted checkout availability, webhook truth, payout-type exposure, fiat-conversion workflow, and settlement policy all sit with OpenNode as a named company.
• That split matters because the dependency businesses inherit is not simply Lightning support; it is a company-managed payment and treasury workflow graph.

Control surface

• Practical leverage sits in merchant admission, checkout lifecycle, charge expiry and redirect behavior, payout routing, fiat-conversion availability, bank-wallet setup for auto-settlement, and the API / webhook surfaces merchants trust as payment truth.

• The sticky dependency is operational rather than purely technical: once a business hardens around OpenNode-hosted checkout, callback delivery, settlement reporting, and payout rails, the real lock-in is to the company-run workflow shell.

• Read OpenNode as a merchant-payment operator first and a Lightning integration second.

• Last reviewed: 2026-08-06 UTC