What is Liquidity on the Lightning Network?
On Lightning, liquidity is the bitcoin in a channel that is available to move in a given direction. A channel has a fixed capacity, but that capacity is split between two sides. The part on your side is outbound liquidity: what you can send. The part on the other side is inbound liquidity: what you can receive.
Inbound and outbound
If you open a channel and fund it yourself, all of the bitcoin starts on your side. You can pay out, but you cannot receive until some of it moves across. A new business therefore starts with no inbound liquidity. The split changes with every payment, so the same channel can accept a large payment in the morning and be full by the afternoon. Moving balance back to a useful split is channel rebalancing.
The total size of a public channel is visible to the network. The split is not. Senders have to estimate it, which is why liquidity problems often look like routing problems.
Why payments fail without liquidity
A payment succeeds only if every channel on the path has enough balance on the sending side. The most common failure is a timeout while searching for a route with enough liquidity along the whole path. A second cause is a recipient with no inbound liquidity or one that is offline. Amboss makes the same point in its post on why Lightning payments fail: failures come from where liquidity sits, not from the protocol. A failed payment returns to the sender.
Ways to get inbound liquidity
- Swap Lightning balance out to on-chain bitcoin with a submarine swap. This moves balance to the remote side.
- Ask peers to open channels to you.
- Buy a channel. Many node operators do this through a liquidity marketplace.
- Lease it on a recurring basis. See liquidity leases.
How Amboss handles liquidity
Never worry about your liquidity. With Amboss Payments, you create invoices and send payments through one API. Amboss provides the channel management and liquidity services for your payments node, so your team does not source inbound liquidity or rebalance channels. See Lightning network liquidity management.
See how payment providers use Amboss Payments
For businesses that run their own node, Amboss offers the options below.
Magma is the Amboss marketplace for inbound liquidity. A buyer pastes a node pubkey, pays a Lightning invoice and receives channels from peers chosen by matching software. No account is needed. Channels arrive after 6 on-chain confirmations. Details are in the Magma v2 post.
For businesses that run their own node, Liquidity Subscriptions keep inbound capacity in place. The buyer chooses a monthly budget and Amboss uses it to acquire and maintain channels. The budget can be raised or lowered at any time. See Liquidity Subscriptions.
On the supply side, Rails liquidity providers commit bitcoin to Magma and earn leasing fees while keeping custody. Amboss research decides where to place it. MPFlow, an Amboss agent, has made 4,640 channel-open decisions in production, allocating 267.3 BTC across 30 managed nodes. See machine learning.
Amboss also reports how much inbound liquidity the market buys. Node operators bought 17.38 BTC on Magma in October 2026, against 10.48 BTC in October 2025. Learn more on the Magma page.
Liquidity management and payment liquidity
"Liquidity management" means keeping bitcoin on the right side of the right channels. It covers opening channels, sizing them, rebalancing and closing the ones that no longer earn. "Payment liquidity" means the same thing seen from the payer or business: whether a payment of a given size will go through. In practice the work is the same. See channel management.