BTCPay Server vs OpenNode
BTCPay Server
btcpayserver.orgOpenNode
opennode.comSide by side
| Figure | BTCPay Server | OpenNode |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | Yes | — |
| Web | Yes | Yes |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 2 | 1 |
| Spec score · Crypto Payment Processors | 8.8 (#2) | 6.7 (#20) |
| Integrations | The project lists integrations including WooCommerce, Shopify, Drupal, Magento, and PrestaShop. | Official ecommerce plugins are listed for Shopify, BigCommerce, WooCommerce, Magento, PrestaShop, and OpenCart. |
| Security | Using an existing wallet for on-chain transactions requires public wallet information rather than the master private key. | OpenNode lists multisig, withdrawal limits, IP address whitelisting, and regular monitoring for potentially irregular activity as security measures. |
| Support | The project directs users to its documentation, GitHub, and community channels for help. | OpenNode lists guides, API documentation, developer and test environments, and technical support for developers. |
Plans
In their own words
BTCPay Server
BTCPay Server is self-hosted, open-source software for processing cryptocurrency payments. It describes its service as free, with no subscriptions or transaction fees; payments go directly to merchant-controlled wallets rather than being held by a payment intermediary. Merchants can create invoices, receive payment notifications and export invoices for bookkeeping. Built-in tools include point of sale, tipping buttons, payment links and crowdfunding campaigns, alongside wallet management with hardware wallet support. The Greenfield REST API can connect commerce applications and automate BTCPay instances. Listed checkout options include hosted invoice checkout, payment requests, HTML buttons, e-commerce plugins, point of sale and custom API integrations. Integrations include platforms such as WooCommerce, Shopify, Drupal, Magento and PrestaShop. For on-chain transactions using an existing wallet, public wallet information is used rather than the master private key. Third-party hosted accounts may lack Lightning by default, wallet rescanning and server settings access. It supports web, Linux, self-hosting and API use.