WORLD CRYPTOCURRENCY GUIDE
Practical analysis

Lightning: channels, liquidity and payments

Understand channel capacity, invoices, routing costs and recovery limits before making a first Lightning payment.

Phone and payment equipment on a café table
AI-generated illustrative photograph: Phone and payment equipment on a café table
Short answer

Lightning enables off-chain payments backed by Bitcoin. Total channel capacity is not enough: available direction, routing and custody determine what you can actually send or receive.

Separate workstations in a shared space — AI-generated photograph
Separate balance from capacity

Two directions

Read the invoice

Amount and expiry

Account for the whole cost

Routing and on-chain fees

01

Separate balance from capacity

In a hypothetical 100,000-satoshi channel, 80,000 sit on your side and 20,000 on the remote side. Before reserves and other constraints, this chiefly provides sending capacity; it does not let you receive an arbitrary 100,000. Payments shift balances without increasing total capacity. An interface may aggregate channels, so a global balance does not describe available routes.

02

Read the invoice

A Lightning invoice can include amount, expiry and routing information. Check those details in your application. A conventional Bitcoin address is not a Lightning invoice; unified wallets should make the actual payment method clear. Do not pay a fresh invoice merely because the previous attempt seems slow: first check its outcome to avoid making two separate purchases.

03

Account for the whole cost

Intermediate nodes can charge base and proportional routing fees. Your wallet may set a fee limit. Opening and closing channels also require Bitcoin transactions, while services may charge for liquidity access. Compare total cost against your actual usage, particularly infrequent payments. Lightning has no universal tariff or guaranteed payment delay.

04

Choose custody deliberately

A custodial wallet usually manages availability and liquidity for you, but creates dependence on the service and its ability to return funds. Self-custody makes you responsible for keys, backups and the monitoring required by your implementation. A node or watchtower does not replace a documented recovery procedure. Inspect any additional liquidity-provider dependencies.

05

Prepare recovery

A Bitcoin seed does not automatically recreate every channel state. Static channel backups and restoration differ across implementations; they may help request channel closure rather than resume channels unchanged. Restoring an outdated channel database can be dangerous. Follow your software documentation, practise with a small amount and retain funds for on-chain operations.

06

Diagnose failure

An expired invoice, unavailable route, fee limit or inadequate directional capacity can prevent payment. Record the status and error without publishing private node information. When the outcome is uncertain, inspect payment history before retrying. Receiving regularly requires incoming capacity and attention to its cost; depositing bitcoin alone does not solve every receiving constraint.

07

A concrete verification

Test sending and receiving separately: sending capacity does not prove sufficient incoming liquidity.

08

Hypothetical case: enough balance, insufficient inbound capacity

A hypothetical 100,000-satoshi channel holds 90,000 locally and 10,000 remotely before reserves and restrictions. It cannot automatically receive a 30,000-satoshi invoice. Total balance and liquidity direction differ. Multiple channels and routing can change the outcome, but an aggregated balance alone does not guarantee payment.

  • Separate sending capacity, receiving capacity, channel restrictions and a usable route.
  • Record invoice amount and expiry; another attempt must account for its state.
  • Check implementation-specific backup requirements: restoring an outdated channel state may be dangerous.
09

Total capacity does not guarantee a usable path

Lightning channel liquidity is directional. Adding several channels’ capacities does not guarantee that a particular payment can find a route. Local balances, transfer limits, fees and intermediate channels affect the result.

  • Receiving capacity differs from sending capacity.
  • A multipart payment may help when supported features and available routes allow it.
10

Worked example: 90,000 sats of inbound capacity

Two channels provide 50,000 and 40,000 sats of inbound capacity. Their combined 90,000 sats does not guarantee a single path for receiving 80,000 sats.

  • A multipart payment may succeed under suitable conditions, without a general guarantee.
  • If payment status is uncertain, check it before initiating another payment.
11

What a static channel backup restores in LND

With LND, the recovery seed can recover the onchain Bitcoin wallet. For an open channel, a static channel backup (SCB) lets the node ask its peer to close with its latest state. The expected result is recovery of onchain bitcoin after closure and any applicable waiting periods. An unavailable peer can delay recovery. Identify your software’s backup format in advance and keep old copies of the channel database out of the routine recovery procedure.

Compare

Scenarios and model limits

Scenarios and model limits
SituationInterpretation
100,000 sat: 80,000 / 20,000Directional capacity before reserves; total ≠ receivable amount.
Expired invoiceRequest a fresh invoice after checking previous status.
Channel closureOn-chain cost and timing depend on mechanism and state.
FAQ

Frequently asked questions

Why can I send but not receive?

Channel balances are directional. Incoming liquidity and a usable route must support the receipt; total capacity alone is insufficient.

Does Lightning remove Bitcoin fees?

Channel payments avoid an on-chain transaction for every payment, but opening, closing and some recovery operations use Bitcoin.

Is a seed phrase sufficient?

Not necessarily for channels. Check your implementation’s backups and recovery procedures before funding them.

Verifiable sources

Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Updated November 15, 2026

Related terms

Inbound capacity
Amount a Lightning channel can receive given remote balance and applicable constraints.
Lightning invoice
Payment request carrying Lightning-specific data such as optional amount and expiry.
Static channel backup
Implementation-specific backup that may assist recovery through channel closure.

Prepare and continue reading

Useful background

  • Bitcoin: UTXOs, change and transaction fees

    A Bitcoin balance sums unspent transaction outputs, or UTXOs. Spending consumes whole outputs and creates new ones for the recipient and often your change. Fees are the difference between input and output amounts.

  • How to choose a crypto wallet

    A crypto wallet manages the keys that authorize operations; it does not physically hold the assets. The right choice depends on use, value at risk and your ability to protect a recovery phrase without sharing it.

Continue to the next step