OpenNode

• Name: OpenNode
• URL: https://opennode.com/
• Category: hosted Bitcoin merchant processor / checkout and payout control plane
• Tags: bitcoin-ecosystem
• Summary: OpenNode at the project layer is the hosted Bitcoin checkout, settlement, and payout surface inside a broader OpenNode company shell. The useful product cut is the merchant-facing API and hosted-checkout integration surface; the broader operator boundary now lives in opennode, which is the cleaner place to reason about merchant onboarding, payout-type exposure, API-key issuance, webhook truth, fiat-conversion workflow, and settlement policy.
• What it does:
  • Lets businesses accept bitcoin payments through APIs, ecommerce plugins, and hosted payment pages
  • Supports both on-chain Bitcoin and Lightning Network payment collection, with instant-settlement positioning on Lightning
  • Exposes API primitives for creating charges, receiving payment-status callbacks, redirecting users after payment, and configuring settlement behavior
  • Documents withdrawal and payout surfaces, including multiple withdrawal types such as Lightning, on-chain, wire, exchange, and internal transfer variants
  • Offers auto-settlement and fiat-conversion features in official materials for businesses that want Bitcoin acceptance without full BTC price exposure
• Key claims:
  • The official site describes OpenNode as “Bitcoin payments at the speed of now” and emphasizes low-cost Bitcoin payments and payouts for businesses
  • OpenNode claims businesses can protect themselves from BTC price volatility by automatically converting bitcoin to local currencies at the time of payment
  • The docs portal positions OpenNode as infrastructure for building Bitcoin payment systems rather than just using a hosted merchant page
  • The create-charge API reference shows a fairly complete merchant checkout surface including fiat-denominated charge creation, callback URLs, success redirects, auto-settlement, and split-to-BTC controls
  • The withdrawals API material indicates OpenNode’s product surface extends beyond inbound checkout into treasury and payout operations
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were OpenNode’s official site, docs portal, charge-creation API reference, and withdrawals reference pages; see ../whitepapers/opennode-primary-sources-2026-04-25.md.
• Sources:
  • https://opennode.com/
  • https://developers.opennode.com/
  • https://developers.opennode.com/reference/create-charge
  • https://developers.opennode.com/reference/list-withdrawals

Internal linkages

• Company boundary for the broader operator shell: opennode.
• Best self-hosted merchant-stack contrast: btcpay-server.
• Closest hosted-processor peer once the question is merchant operations rather than broader banking software: coingate.

Protocol / company boundary

• Keep this note on the product shell: hosted checkout behavior, charge creation, callback and redirect wiring, settlement settings, withdrawal objects, and the merchant-facing API surfaces integrators actually build around.
• Use opennode for the named-operator layer around merchant admission, API-key issuance, payout-type exposure, fiat-conversion policy, settlement workflow, and the support/legal shell around the processor.
• That split matters because how does the OpenNode integration surface behave? and which company controls merchant access, settlement policy, and production trust assumptions? are related but not identical questions.

Control surface

• At the product layer, practical authority sits in checkout creation, hosted checkout URLs, callback delivery, charge expiry, settlement behavior, and the merchant-facing payout objects the integration exposes.

• For the wider operator shell around merchant admission, API-key issuance, payout-type exposure, fiat conversion, and settlement policy, read opennode.

• Read it as a managed processor product surface, not as a Lightning infrastructure baseline.

• Last reviewed: 2026-08-06 UTC