---
title: "Inbound Liquidity — Nuri Glossary"
description: "How much room a channel has to receive, which is the usual reason a Lightning payment fails."
lang: "en"
type: "glossary-term"
canonical: "https://preview.nuri.com/glossary/inbound-liquidity"
---

# Inbound Liquidity

How much room a channel has to receive, which is the usual reason a Lightning payment fails.

## Basically

Room for you to receive. A brand-new Lightning wallet often cannot get paid until someone gives it that room.

## Key Takeaways

- Inbound liquidity is how much room your channels have to receive right now.
- It is the number one reason first-time Lightning users cannot get paid.
- You buy it, rent it, or someone sends it to you first.

## Why a fresh wallet cannot receive

A new Lightning wallet has no channels, and with no channels there is nowhere for a payment to land. Even after opening one, if all the funds sit on your side, you can send but not receive — your inbound capacity is zero. On a network where payments move pre-existing balances, receiving requires capacity positioned on your side.

## How people get it

An LSP opens a channel to you or sells you inbound capacity. A friend sends you a payment, leaving balance on your side. Just-in-time channels open the moment a payment arrives, with the provider briefly trusting the new connection. All of these trade money, fees or trust for the same thing: room to receive.

## Managing it

For routing nodes, inbound and outbound are inventory that must be balanced or you earn nothing. For a user, the practical takeaway is simpler: if someone cannot pay you, it is usually capacity, not a bug — and the fix is a channel with the right split, not a support ticket.
Part of the [Nuri glossary](https://preview.nuri.com/glossary), which defines 1774 Bitcoin, Lightning, wallet, stablecoin and payment terms.
