Bitcoin Lightning

Why this rail

Lightning is what Bitcoin's payment layer would look like if it had been designed for monthly invoices rather than for store-of- value settlement. Payments are routed through HTLCs (hash time-locked contracts) along a path of cooperating channels, with onion-routed metadata that prevents intermediate nodes from seeing the sender, the recipient, or the full payment amount. Settlement is final at the protocol level in seconds rather than in tens of minutes, and routing fees are typically under a cent regardless of invoice size.

For a customer paying a recurring hosting bill from a self-custodial Lightning wallet, the privacy posture is structurally different from on-chain Bitcoin. There is no public ledger entry recording the payment. The payment hash is random. The sender is not directly observable to the recipient — the operator sees an invoice resolve, not a counterparty address. Channel topology and node aliases do leak some metadata, and custodial wallets (LSP-backed services that retain keys on the user's behalf) weaken the property substantially. Self-custodial wallets running on the customer's own hardware preserve it.

We run our own Lightning node behind BTCPay, with channels to several large public routing peers and a pair of private channels to liquidity providers that cover the inbound capacity an incoming payment requires. Invoices are short-lived — fifteen minutes from generation — to limit fee-rate exposure during volatile periods, and a fresh invoice scoped to the same order is one click away if an expiry is missed.

Acquisition is straightforward for customers who already hold on-chain BTC: open a self-custodial Lightning wallet (Phoenix, Mutiny, Zeus on a personally operated node) and fund a channel. RoboSats over Tor offers direct-to-Lightning P2P trades, which skips the on-chain step entirely; AgoraDesk and the P2P desks at Bisq cover the fiat-to-BTC step ahead of the channel opening.

How to pay

At checkout, choose Bitcoin Lightning as the payment rail. The order page generates a BOLT-11 invoice scoped to the order with a fifteen-minute expiry. The expiry is short by design — the fee rate that an LSP-backed wallet quotes against an invoice is stable for that interval, and a stale invoice is one click away from being regenerated.

From a self-custodial Lightning wallet — Phoenix on mobile, Mutiny in the browser, Zeus or RTL against a personally operated node — scan the QR or paste the BOLT-11 string and send. Settlement is final in the order of seconds, and the order page transitions to paid the moment the routing path resolves. Custodial wallets work but degrade the channel-level privacy property to that of any other custodian.

Provisioning fires immediately on settlement. The fifteen-minute invoice window does not constrain the order itself; it constrains the specific BOLT-11 string. If the wallet times out, regenerate the invoice from the order page and retry against the fresh string.

Closing notes

Lightning is the right rail for any monthly hosting cycle that could otherwise be paid on-chain. The settlement is faster, the fees are lower, and the privacy posture is meaningfully stronger than on-chain Bitcoin for the typical sender. The rail does not match Monero's default-private guarantee — channel topology and wallet custody both leak — but for a self-custodial sender the gap is narrower than the on-chain comparison would suggest.