Lightning Payment Stuck or Overpriced? Fix It

If a Lightning payment is stuck or costs more than expected, the fix is usually to cancel it, review the fee settings, and retry with a more realistic fee or a different route. Stuck payments happen when the fee you set is too low for the current network conditions, and overpriced payments usually come from choosing a high fee or using a wallet that overestimates the required amount. Below is a practical guide to diagnosing and resolving both problems.

Formula

The calculator estimates the total cost of a Lightning payment when you know the amount and the fee limit. The fee per hop is the fee limit divided by the number of hops in the route:

Fee per hop = Fee limit ÷ Route length

Total cost = Amount + Fee limit

Variables:

• Amount (sat) – the amount you want to send, in satoshis.
• Fee limit (sat) – the maximum fee you are willing to pay for the whole payment.
• Route length (hops) – the number of channels the payment passes through (typically 2–5).
• Fee per hop (sat) – the average fee paid to each intermediary node.
• Total cost (sat) – the amount plus the fee limit.

Worked Example

Using the default values: amount = 1000 sat, fee limit = 10 sat, route length = 3 hops.

1. Fee per hop = 10 ÷ 3 = 3.33 sat (rounded to 3 sat).
2. Total cost = 1000 + 10 = 1010 sat.

The calculator shows a fee per hop of 3 sat and a total cost of 1010 sat.

Why Lightning Payments Get Stuck

Lightning payments are not broadcast to a blockchain like Bitcoin transactions; they are routed through a network of payment channels. A payment gets stuck when the sender’s wallet cannot find a path to the recipient that meets the fee and time-lock constraints. The most common reasons are:

• Fee too low – each node along the path charges a routing fee. If your fee limit is below what the nodes demand, the payment cannot proceed.
• Insufficient liquidity – the recipient’s channel may not have enough incoming capacity to receive the payment.
• Route not found – the network graph in your wallet may be outdated, so it cannot see a viable path.
• Time-lock too tight – some wallets set a maximum time-lock (CLTV) that is too short for the route.

How to Fix a Stuck Payment

If a payment has been pending for more than a few minutes, do this:

1. Cancel the payment – in most wallets, you can abandon a stuck payment. It will be removed from the pending list.
2. Increase the fee limit – set a fee that is at least the median fee currently seen on the Lightning network (you can check a fee estimator or your wallet’s suggested fee).
3. Retry with a different amount – if you are sending a large amount, try splitting it into smaller payments. Large payments are harder to route.
4. Update your node’s channel graph – if you run your own node, run a graph sync. If you use a mobile wallet, close and reopen the app to refresh the network view.
5. Use a different wallet or node – some wallets have better routing algorithms. If one fails repeatedly, try another.

Why a Lightning Payment Might Cost More Than Expected

The fee you pay on Lightning is the sum of the fees charged by each node in the route. The total can be higher than you expected for several reasons:

• You chose a high fee limit – your wallet may have used the entire limit even if a cheaper route existed.
• Long route – more hops mean more fees. A route through 5 nodes costs more than one through 2.
• High base fees – some nodes charge a fixed base fee (e.g., 1 sat) plus a proportional fee. Even a small payment can incur several base fees.
• Currency conversion – if you are sending from a wallet that shows fiat amounts, the displayed fee may not include the conversion spread.

How to Choose the Right Fee

Most wallets offer three fee options: low, medium, or high. The “low” option is often too low for the current network state, leading to stuck payments. Here is a practical approach:

1. Start with the wallet’s recommended fee – it is usually based on recent network activity.
2. If the payment fails, increase the fee by 50–100% and retry.
3. For time-sensitive payments, choose the highest fee – it gives the payment the best chance of routing quickly.
4. For large amounts, consider splitting – a 1,000,000 sat payment may be easier to route as two 500,000 sat payments.

Common Mistakes and Misconceptions

• “Lightning fees are always near zero.” – They are usually low, but they are not zero. During congestion, fees can rise significantly.
• “A stuck payment will eventually go through.” – Not always. If the route is impossible, the payment will fail after a timeout. You can cancel it earlier.
• “The fee shown before sending is the final fee.” – Some wallets show an estimated fee, not the exact one. The actual fee may be slightly higher if the route changes.
• “You can force a payment through a specific node.” – Most wallets do not let you choose the route; they pick it automatically.

Alternatives to Lightning

If Lightning is giving you trouble, consider these alternatives:

• On-chain Bitcoin transaction – slower and often more expensive, but never gets “stuck” in the Lightning sense; it just waits for confirmation.
• Liquid Network – a sidechain with fast, low-cost transfers, but not as widely supported.
• Other payment channels – some services use custom channels, but they are not interoperable with Lightning.

Frequently Asked Questions

Why is my Lightning payment stuck at “pending”?

It means your wallet is still trying to find a route. If it stays pending for more than 10 minutes, cancel it and retry with a higher fee or a smaller amount.

Can I get my money back if a payment is stuck?

Yes, the funds are never sent until the payment is completed. If you cancel a stuck payment, the amount is returned to your balance immediately.

How do I know what fee to set?

Use your wallet’s recommended fee. If you want to be safe, add 20–30% to that. You can also check a fee estimator like bitcoinvisuals.com for current median fees.

Why did my payment cost 50 sat when I expected 5 sat?

Because the route had multiple hops, each charging a base fee. A 5-hop route with 1 sat base fee per node plus a small percentage easily reaches 50 sat.

Is Lightning safe to use for large amounts?

It is safe, but not ideal. Large payments are more likely to fail due to liquidity constraints. For amounts above a few hundred dollars, consider an on-chain transaction.

What is the difference between a stuck payment and a failed payment?

A stuck payment is still being attempted; a failed payment has been rejected by the network. You can cancel a stuck payment, but a failed one is already returned.

Related

• How Robotaxi Sensors Collect Data: Cameras, Mics & More
• Two-Tailed Test Z-Score Calculator & Guide
• Type Test Score Calculator: How It Works

in t | Amount (sat) | sat | 1000 | 0
in f | Fee limit (sat) | sat | 10 | 0
in r | Route length (hops) | - | 3 | 1
out fee_per_hop | Fee per hop (sat) | sat | f / r | 0
out total_cost | Total cost (sat) | sat | t + f | 0