In this article
Accepting bitcoin creates two separate questions for a business: how the customer pays, and what the business ultimately receives. OpenNode connects those steps through a hosted payment service that supports Bitcoin transactions, Lightning payments and conversion into supported local currencies. A merchant can accept BTC without deciding to keep every sale in BTC.
The convenience comes with a trade-off. OpenNode operates the processing infrastructure and account system, so a merchant depends on the company for access, transfers and service availability. It is a different arrangement from receiving every payment directly into a wallet controlled exclusively by the merchant.
What OpenNode is and who operates it
OpenNode is a business payments platform operated by OpenNode, Inc., identified in its published terms as a Delaware corporation. Its product range includes hosted checkout, payment buttons, invoicing, integrations and a payment API, an interface that lets business software request and track payments.
The company's own 2021 announcement dates its founding to 2018. That announcement described an integration allowing a selected group of Substack publications to receive Bitcoin payments, including through Lightning. It provides a concrete example of the platform's early focus: connecting an existing business application to Bitcoin payment infrastructure. It does not establish that every Substack publisher currently offers that option.
João Almeida was identified as a co-founder and chief technology officer in that announcement. His own professional website lists his OpenNode tenure as 2018 to 2023, so historical founder references should not be read as a current management roster. The service today is presented through OpenNode's corporate website, documentation and support channels.
How a payment moves through the service
With hosted checkout, a merchant creates a payment request and sends the customer to an OpenNode checkout page. OpenNode handles the payment interface, then redirects the customer back to the merchant's website after the payment flow. This reduces the amount of checkout infrastructure the business must build and maintain itself.
The distinction between a payment screen and a completed order still matters. A shop needs its order system to recognize the payment's actual status before releasing goods or providing access. A customer returning to the website is not, by itself, a sufficient accounting record. Businesses integrating any processor should test incomplete payments, abandoned checkouts and their own fulfillment rules.
OpenNode's API supports both on-chain Bitcoin and Lightning, along with incoming payments and outgoing payouts. On-chain payments are recorded on the Bitcoin blockchain. Lightning uses a network of payment channels and can complete payments without recording each individual transfer as a separate blockchain transaction. The two routes have different operational requirements, even though both transfer bitcoin.
Readers who need the underlying currency context can start with how Bitcoin works. For a merchant evaluating OpenNode, the more immediate question is whether customers can complete the offered payment route reliably with their own wallets.
Receiving bitcoin, local currency or a combination
OpenNode offers automatic conversion at payment time and conversion of settled account funds on demand. Its split-settlement feature allows a business to retain a chosen percentage in bitcoin and convert the remainder into a supported local currency. These are settlement preferences, not different currencies that the customer must necessarily purchase.
A merchant with expenses in dollars might prefer conversion for operational reasons, while another might choose to retain part of its receipts in BTC. Any retained bitcoin remains exposed to changes in its fiat value. Conversion can reduce that exposure for the amount converted, but it does not eliminate service, banking or account-access risk.
The currency used to price an invoice also needs to be distinguished from the currency available for withdrawal. OpenNode advertises a broad selection of source currencies for payment requests, but that does not mean every one is supported as a bank settlement currency. A business should confirm its actual bank transfer route before relying on a checkout denomination.
Nor does a fiat-denominated account balance necessarily mean the merchant has received a stablecoin. Stablecoins have their own issuers, redemption arrangements and network risks. OpenNode's Bitcoin-to-local-currency conversion is a payment service feature, not a promise that the merchant will receive an on-chain dollar token.
Published fees and the difference between payment and withdrawal
Checked on October 9, 2026, OpenNode's help center described typical payment and payout processing fees of 1%. It stated that there were no setup, minimum, monthly or annual fees, and no separate conversion fee. The word typical is relevant: merchants should confirm their applicable commercial terms rather than assume every business receives an identical offer.
Moving a balance out of the platform has a separate fee schedule. The same help article listed scheduled weekly Bitcoin transfers as free, on-demand Lightning transfers as free, and on-demand on-chain transfers at 1%. A processing fee and a withdrawal fee therefore answer different questions. A business comparing providers needs to consider both stages.
OpenNode's pricing page also invites custom quotes and indicates higher fees for high-risk businesses. Bank transfer availability, timing and charges depend on the supported route. A firm planning frequent withdrawals should confirm those details for its country and bank instead of applying the Bitcoin withdrawal schedule to a fiat transfer.
A useful comparison starts with the merchant's actual workflow: average payment size, expected volume, preferred settlement currency and withdrawal frequency. A percentage advertised for receiving payments does not capture every possible operational cost, including integration work and the business's own support time.
Security controls do not remove custody risk
OpenNode says its security measures include multisignature support, withdrawal limits, IP address whitelisting and monitoring for irregular activity. Multisignature arrangements require multiple signing approvals under the relevant configuration; IP whitelisting restricts access to approved internet addresses. These are company-described controls, not evidence that an individual merchant account is immune to compromise.
The company's pricing page explicitly acknowledges that users can hold bitcoin on the platform and recommends setting up an external wallet. Funds left in an OpenNode account depend on the provider's systems and ability to honor withdrawals. Transferring funds to a merchant-controlled wallet changes that relationship, while creating responsibility for protecting keys and recovery information.
The guide to wallet custody and recovery explains that distinction. A merchant should know who controls funds at each stage, who can authorize withdrawals and how access is recovered if an employee leaves or an account is compromised.
Bitcoin payments also lack the card network's ordinary chargeback mechanism. That does not make commercial fraud impossible or remove a seller's refund responsibilities. Incorrect orders, impersonation and disputes can still occur. Clear customer support and reconciliation procedures remain necessary.
Verification, availability and a realistic business fit
OpenNode's privacy policy says account activation involves identity verification and may require identification images, bank information and checks against third-party information. Businesses should therefore expect onboarding requirements. Paying with bitcoin does not make the merchant's account anonymous.
Its terms also reserve account approval to OpenNode, restrict use where prohibited and allow suspension in specified circumstances. Availability depends on the jurisdiction and the proposed business activity. Website accessibility alone does not establish that a particular merchant will be approved.
OpenNode's status page reported its payment, node, API and Bitcoin withdrawal components operational when checked on October 9, 2026. That is a dated service-status report, not an uptime promise. The published terms acknowledge that access can be interrupted, which makes a fallback payment route and a documented support process practical considerations.
The platform is relevant to a business that wants Bitcoin acceptance and supported currency settlement without running its own payment infrastructure. Its fit is weaker where exclusive control of payment keys, anonymous merchant access or unsupported settlement currencies are essential. The decision turns on the complete path from checkout to usable business funds, including approval, fees, custody and withdrawals.