
Voltage vs. OpenNode: choosing a Bitcoin payment API for checkout and reconciliation

Updated
Compare Voltage and OpenNode for Bitcoin checkout, payment confirmation, refunds, reconciliation, and settlement.
A customer pays for an order with Bitcoin. Your checkout shows a confirmation, your application releases the order, and finance records the money. When those steps agree, nobody needs to think much about the payment provider.
The harder questions come when they don't agree. What if the customer closes the tab after paying? What if an on-chain payment is still waiting for confirmation? And what happens when a paid order needs a refund?
Both OpenNode and Voltage Payments give developers APIs for Bitcoin and Lightning payments. OpenNode also offers hosted payment pages and ecommerce integrations. Voltage supports embedded payment workflows and offers a hosted payment page through Voltage Checkout. You don't have to choose between “a checkout” and “an API.” You need to decide which provider fits the way your team accepts, confirms, and accounts for payments. OpenNode API overview, Voltage Checkout documentation
OpenNode is worth considering if its checkout, integrations, conversion, and payout services cover your requirements. Voltage is worth evaluating if you're building payment operations into your product and want its payment controls, developer tooling, and eligible credit-backed funding options. If your existing OpenNode integration works well, a switch should solve a specific problem your team can measure.
Walk through an order before comparing features
Consider a $100 purchase. Your customer sees a dollar price and chooses to pay over Lightning. Your application needs to connect the order to the provider's payment reference and confirm that the expected payment arrived before releasing the purchase.
With OpenNode, the integration revolves around a charge. Its documentation separates a settled Lightning payment from an on-chain transaction that has merely been detected. A charge becomes paid when the Lightning payment settles, or when the on-chain payment reaches the documented confirmation requirement. OpenNode charge lifecycle
With Voltage Checkout, your server creates a session and receives a checkout URL, session ID, and payment ID. You can open the hosted page through a redirect, an iframe, or the JavaScript SDK. Your server then verifies the payment before fulfilling the order. Voltage Checkout
In either implementation, keep the order reference and provider reference together. Your customer might never return to the success page, even though the payment completed. Order fulfillment needs to follow the payment record rather than depend on that browser visit.
If you're building your own Lightning payment screen, Voltage's wallet deep-linking guide explains how to open an invoice in a compatible wallet. That can reduce copying and pasting on a phone. Opening a wallet still leaves the customer with a payment to authorize; your application must confirm the result.
Plan for the orders that need attention
An on-chain payment can arrive below the requested amount. OpenNode documents an underpaid state, with options to complete the amount or return the funds. Its refunded lifecycle state describes that underpayment flow. It shouldn't be read as proof that every completed purchase has the same automated refund process. Charge lifecycle
For customer refunds more generally, OpenNode's help article directs businesses to its support team. Before choosing a workflow, ask how full and partial refunds are handled for your account, who authorizes them, and how they appear in your records. OpenNode refunds
Work through the same questions with Voltage. A payment API's ability to send Bitcoin doesn't, by itself, specify your refund policy, approval process, or accounting treatment. Decide whether you're returning a fixed dollar value or the original Bitcoin amount, how you'll obtain the customer's destination, and how the outgoing payment will link to the original order.
Lightning settlement has no card-network chargeback mechanism. Your business still needs to handle refunds, compromised accounts, and disagreements about the purchase. Payment finality helps with one part of the job; customer service and fraud controls remain part of operating it.
Give support a way to recover a missing update
Suppose the payment completed while your application was being deployed and your webhook endpoint missed the notification. The customer has paid, but the order still looks unpaid.
OpenNode documents charge and withdrawal notifications, along with a webhook simulator for testing event handling. Its charge webhook guide distinguishes Lightning settlement from on-chain processing and failure events. Use those states to decide what your application should do next. OpenNode webhooks, charge events
Voltage's documentation covers signed webhook verification, delivery inspection, retrying individual deliveries, and a reconciliation loop that retrieves payment updates your webhook handler may have missed. Those tools give your team a documented way to investigate an order that hasn't caught up with its payment. Voltage webhooks
For either provider, test repeated notifications and delayed updates. Processing the same event twice should not release two orders or credit a customer twice. A support agent should be able to find the payment from the order number, see its latest status, and explain what happens next.
Agree on where the money ends up
OpenNode advertises automatic conversion and local-currency settlement alongside Bitcoin acceptance. Its pricing documentation also describes USD bank transfers. Confirm the supported currency, jurisdiction, transfer method, and timing for your business. OpenNode payment services, transfer terms
Voltage documents a USD credit-backed receiving flow: the customer pays in Bitcoin, while an eligible USD wallet is credited in dollars through the conversion workflow. The Lightning payment and a subsequent bank movement are separate steps. A USD-denominated wallet balance also doesn't mean that the customer paid with USDC or another stablecoin. Voltage USD receiving
If outgoing payments are part of your product, include their funding in the evaluation. OpenNode documents on-chain and Lightning withdrawals. Voltage's credit-backed setup uses a Voltage-provided line of credit; eligibility, limits, and repayment terms need to be agreed for your business. OpenNode withdrawals API, Voltage credit-backed setup
Put the commercial proposal next to the integration plan
OpenNode's published guide describes typical processing fees of 1% for payments and payouts, with no setup, minimum, monthly, or annual fees. It separately lists instant Lightning transfers from an OpenNode account as free. These are different fee categories: don't assume the free-transfer statement makes every payout service free. OpenNode pricing and fees
For an illustrative month with 2,000 purchases averaging $100, a 1% processing rate on $200,000 would be $2,000. That's a processing-fee example, not an all-in quote. The same guide says bank-transfer fees and minimums depend on the transfer method and banking partner.
Give both providers that same order volume, plus your actual refund frequency, outgoing payments, conversion needs, and bank-transfer requirements. Ask Voltage for a proposal covering the applicable processing charges, commitments, and funding terms. Include the engineering work needed to support the workflow you want. There isn't enough public pricing here to declare an all-in winner for your business.
| Before choosing | What your team should establish |
|---|---|
| Customer interface | OpenNode's hosted pages and integrations versus your chosen Voltage API or Checkout implementation. |
| Confirmation and recovery | The payment states that trigger fulfillment, event verification, and recovery after a missed notification. |
| Funds and access | Who holds funds and controls credentials in the selected deployment; who can view activity or send payments. |
| Settlement and eligibility | Supported assets, countries, conversion terms, bank availability, and any funding limits. |
| Finance and support | Required reporting fields or exports, refund records, agreed service coverage, and escalation ownership. |
Replace one order flow, then decide whether to expand
If you're considering an OpenNode alternative, start with a limited test of new orders. Existing invoices and payment references remain with the provider that created them. Preserve that history and continue processing its outstanding events and refunds.
Build a mapping between your order records and the new provider's identifiers. Test a successful Lightning payment, an expired unpaid request, a repeated event, a missed notification, and a refund your team has approved. If your product also accepts on-chain payments, test those confirmation and exception paths separately.
The Voltage CLI and Agent Skill Pack can help developers work through payment requests and status checks in a development environment. Use that first integration to show finance and support how they will find and reconcile an order.
Before moving production traffic, agree how balances will be transferred and how new orders can return to the previous provider if needed. Keep tracking payments already submitted. Switching the route for new orders doesn't cancel those obligations.
If OpenNode already handles this comfortably, keeping it may be the right decision. If you're spending too much time recovering payment state, building around a funding constraint, or maintaining an experience that no longer fits your product, bring that workflow to our team. We can walk through where Voltage would help and what your team would need to change.