Best Lightning Node for BTCPay Server: What to Run and Where

A shop owner packing a ceramic mug into a shipping box at a tidy home studio desk.

The best Lightning node for BTCPay Server is an LND node that you run yourself and connect to your store, with on-chain payments switched on first. LND has the widest BTCPay documentation and tooling. The software choice matters less than two questions: who holds the channel keys, and who supplies inbound liquidity? On a managed host, keep your Lightning keys on hardware you control.

TL;DR:

  • LND is the safest default implementation for BTCPay Server, with Core Lightning a reasonable choice if you already know it.
  • A Lightning node is a hot wallet, so an internal node on a shared host puts your channel funds on a machine you do not control.
  • A new channel can send but cannot receive. Most guides skip inbound liquidity, yet it is a required setup step.
  • Routing fees will not pay for a merchant node. Lightning earns its place by cutting fees on small orders.
  • Start with on-chain payments to your own wallet, then add Lightning when customers ask for it.

Table of Contents

What BTC Lightning Does for a Shop, and Why It Needs a Node

Lightning is a payment network built on top of Bitcoin. Two parties lock funds in a shared on-chain transaction, called a channel, then exchange signed balance updates off-chain. The design comes from the Lightning Network paper by Joseph Poon and Thaddeus Dryja, and the BOLT specifications are the interoperable rules that let different software talk to each other.

For a shop, the payoff is small payments that settle in seconds for a fraction of an on-chain fee. The cost is that you must run, or rent access to, a node that keeps channels open and stays online. BTCPay Server does not process Lightning payments by itself. It asks a node for an invoice and watches for the payment.

This article assumes your BTCPay Server itself is already sorted. If you are still deciding between a hosted store and your own machine, the BTCPay Server installation service guide covers that decision. What follows covers only the Lightning layer.

Lightning Setups for BTCPay Server, Compared

BTCPay Server's documentation lists LND, Core Lightning and Eclair as supported node software. You can run one inside BTCPay's Docker deployment (an internal node) or point BTCPay at a node you run elsewhere (an external node). Including the options with no node at all, that gives five practical setups.

Setup Who holds channel keys Inbound liquidity Best fit
On-chain only You, in your own wallet Not needed Stores starting out, high-value orders
Internal node on a host's shared server The server, which is a hot wallet You must arrange it Testing with small amounts
Internal node on your own server You, on hardware you control You must arrange it Merchants with steady Lightning demand
External node via connection string You, wherever the node runs You must arrange it Merchants who already run a node
Nodeless plugin using a liquidity provider The plugin's wallet, on the server Usually handled by the provider Low-volume stores that accept a trust trade-off

Every row that involves a node carries the same chore: someone has to fund channels and balance them. The rows differ in who can lose the money if the server is compromised.

LND or Core Lightning: Which Implementation to Pick

Pick LND. It is the node most BTCPay users run, so the answers you need at 2 a.m. already exist in forum threads and in the LND repository issue tracker. Its static channel backup feature and its channel management tooling are mature.

Core Lightning is a good choice if you already run it or prefer its plugin system and smaller footprint. I would not start there as a first-time merchant, because fewer people will have hit your exact problem.

Some defaults are worth knowing before you open anything:

  • Minimum channel size. LND's default minimum is 20,000 sats, which is too small to carry a meaningful order.
  • Maximum channel size. Without the large-channel option enabled, a single channel tops out at 16,777,215 sats.
  • Channel reserve. Each side must keep about 1% of the channel capacity unspendable, so a 1,000,000-sat channel can never be fully drained.
  • Routing fees. LND's default is a 1 sat base fee plus 1 part per million.

A freshly opened channel has 100% of its funds on your side, so it can send but cannot receive a single sat.

Why an Internal Node on a Shared Host Is the Wrong Default

A technician plugging a network cable into a server in a rack inside a data center.

A Lightning node signs transactions with keys that must stay online, which makes it a hot wallet. When that node lives on a server run by your host, the channel balance sits on a machine you cannot physically or administratively control. A custodial processor asks you to accept the same trade-off.

On-chain payments avoid this. BTCPay can generate addresses from a public key you supply, so customer payments go to your own wallet and the server never holds a spendable key. Hosted BTCPay Server for merchants walks through that custody split. Lightning breaks the pattern, because channel funds cannot sit in a cold wallet.

My position: on a managed host, run on-chain by default. Add Lightning through a node on your own server, or through an external node you already operate, and keep the amount in channels to what you would be comfortable carrying in a physical till.

Inbound Liquidity: The Cost Setup Guides Skip

To receive a payment, the other side of your channel needs funds. Opening a channel with 500,000 sats gives you 500,000 sats of outbound capacity and zero inbound capacity. A merchant needs the reverse.

You have three ways to get inbound liquidity:

  • Spend first. Pay out through the channel, for example by paying suppliers over Lightning, which shifts balance to the other side.
  • Buy a channel. Some node operators sell inbound channels for a fee. Compare the fee against your expected Lightning volume before you pay.
  • Ask a peer to open to you. This works if you have a relationship with an operator, and costs them an on-chain fee.

Size matters. A channel of 1,000,000 sats with the 1% reserve gives you at most about 990,000 sats of receivable capacity, and a single invoice can never exceed what one route can carry. If you sell higher-priced items, plan for several smaller channels instead of one large one.

Is Running a Lightning Node Profitable?

Not from routing fees. At LND's defaults, forwarding a 1,000,000-sat payment earns about 2 sats: 1 sat base fee plus 1 sat from the proportional rate. Raising fees helps a little, but a merchant node at the edge of the network sees little forwarding traffic anyway.

The profit case for a store is cost avoidance. Take a $50 order and assume a 3% card rate: that is $1.50 lost to the processor. A Lightning payment into your own channel costs you nothing per order, and the sender pays a routing fee that is usually a fraction of a cent. Against that, you pay on-chain fees to open and close channels, plus your time and the cost of the server.

The break-even depends on your order count and current on-chain fees, which move with demand for block space. If you take a handful of Lightning orders a month, the on-chain payment path is probably cheaper to run. Refunds are also less tidy on Lightning, since BTCPay handles them through pull payments that the customer must claim.

At LND's default fee of 1 sat base plus 1 ppm, routing a 1,000,000-sat payment earns you 2 sats.

Best Lightning Wallet and Coinbase: Two Questions Merchants Keep Asking

What is the best Lightning Network wallet? It depends on which side of the sale you are on. Your customers can pay from any wallet that can scan a BOLT11 invoice, and you cannot choose that for them. For you, the best wallet is a self-custodial one where you hold the seed phrase, used to receive withdrawals from your node or on-chain sweeps from your store. Avoid any wallet where an account login controls the funds, because that returns you to trusting a third party.

Does BTCPay work with Coinbase? Not as a payment backend. BTCPay needs either an on-chain wallet you control or a Lightning node, and an exchange account is neither. You can still move funds between them: withdraw from an exchange to your BTCPay wallet's on-chain address, or to a Lightning invoice if the exchange supports Lightning withdrawals. That is a one-time transfer, and the exchange never sees your customers' payments.

What Reddit and GitHub Threads Get Right About This Setup

Search for this topic and you will find many Reddit threads and GitHub issues. They are useful for specific errors, such as connection string formats or macaroon permissions, and the BTCPay Server repository is the place to check whether a bug is known.

Two patterns recur. Advice written for hobbyists running a home node often assumes you want to route payments, which a merchant does not. And many threads recommend an internal node because it is the quickest to set up, without mentioning that it concentrates keys on one server. Setup speed and safety are separate scores.

Pro Tip: After every channel open or close, save a fresh static channel backup file off the server, and never restore an old copy of the full channel database. Restoring stale channel state can broadcast an outdated balance, which your peer is entitled to punish by taking the channel funds. The static backup only helps you request a force close, and that is what you want in a recovery. Before you enable Lightning at checkout, also pay a test invoice from a different wallet and confirm the full amount arrives.

For tax records, Lightning receipts still count as sales. Reporting bitcoin sales for taxes covers how to export them at year end.

Get a Managed BTCPay Store Without Running Channels Yourself

Myntli hosts and maintains your BTCPay Server for $29 a month, with monitoring, updates and sync handled for you. On-chain payments go straight to your own wallet with no percentage taken and no custody. If you do not yet have a self-custody wallet, Myntli will help you set one up before you take your first payment. It supports WooCommerce, Shopify, Ghost, Magento, PrestaShop, Drupal Commerce, Invoice Ninja and ReplaPay, and API access is available for custom builds.

If you want Lightning with keys you control, the $449 option installs a full BTCPay node on your own server, so any channel funds stay on your hardware. One caveat: Lightning is not a checkbox. Opening channels and obtaining inbound liquidity remain your job, and what is included on each plan can change, so check the current spec sheet before you order.

Frequently Asked Questions

What is the best Lightning node for BTCPay Server?

LND is the best default for most merchants, because BTCPay supports it well and it has the largest pool of documentation and community answers. Run it on hardware you control, either alongside BTCPay on your own server or as an external node that you connect to your store.

What is BTC Lightning?

Lightning is a payment layer built on top of Bitcoin. Two parties open a channel with one on-chain transaction, then trade signed balance updates off-chain, which makes small payments fast and cheap. The channel settles back to the blockchain when it closes.

Is running a Bitcoin node profitable?

Not directly. At LND's default fees of 1 sat base plus 1 part per million, forwarding 1,000,000 sats earns about 2 sats. A merchant node pays off by avoiding processor fees on small orders, and only if your Lightning order volume covers channel costs and server upkeep.

Does BTCPay work with Coinbase?

BTCPay does not use an exchange account as its payment backend, since it needs a wallet or node you control. You can withdraw from an exchange to your BTCPay wallet address, and to a Lightning invoice if the exchange supports that.

Do I need Lightning to accept bitcoin with BTCPay Server?

No. On-chain payments work on their own and go to your wallet without any channel management. Add Lightning later if customers ask for faster or smaller payments.

Sources