Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A Lightning Bitcoin payment can be in flight without being failed. First open the original payment and identify its final state: in flight or pending, succeeded, or failed. Do not send a second payment while the first is unresolved. Then verify the invoice amount and validity, check your wallet’s connection, and follow the wallet’s retry or support process. Routing, fees, channel liquidity, offline nodes, and expired or incorrect payment requests can all prevent settlement. A pending Bitcoin on-chain transaction is a separate problem from a pending Lightning payment.
What “pending” and “failed” mean on Lightning
Lightning payments travel through a route of payment channels rather than directly from one wallet balance to another. The route must have usable channels, appropriate liquidity in the payment direction, reachable nodes, and fees and timing conditions that the sender’s wallet accepts.
In LND, the payment tracker distinguishes three outcomes:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors| Displayed state | What it means | What you should do |
|---|---|---|
| In flight or pending | The payment has not reached a final success or failure result. If part of the route has committed an HTLC (hashed time-lock contract), it must resolve rather than being treated as an ordinary failed attempt. | Monitor the original payment. Do not make a duplicate payment until the wallet or provider confirms the first attempt’s final state. |
| Succeeded | The payment settled and the recipient should have received it, subject to the wallet’s display refresh. | Save the payment details and ask the recipient to verify receipt if their balance does not yet show the credit. |
| Failed | The wallet has recorded a final unsuccessful result. In LND, a failure before HTLCs are locked in can generally be retried safely. | Correct any invoice or connectivity problem, then use the wallet’s own retry flow. Do not assume this LND behavior is a guarantee for every consumer wallet. |
The distinction between an early failure and an HTLC-locked payment is critical. The Lightning Labs LND Builder’s Guide, in its “Sending Payments” page, says: “If your payment fails in this first stage, perhaps because a node along the route was offline, or did not have sufficient balance to forward the payment, it is safe to retry.” The same guidance explains that after an HTLC is locked in, the payment must resolve. A wallet using another implementation or a hosted service may label and handle these stages differently.
#1 Best Overall
- BITCOIN EXCLUSIVE, PHONE VERIFICATION: Bitkey is designed from the ground up exclusively for bitcoin — a dedicated hardware wallet for secure bitcoin storage. Approve transactions with a tap using your phone and NFC. No device screen is required.
- SELF-CUSTODY, NO EXCHANGE OR CUSTODIAN REQUIRED: You hold two of the three keys in the Bitkey system – one on your phone and one on your Bitkey device. The third is stored on Bitkey’s server and cannot move your bitcoin on its own.
- NO SEED PHRASE: Set up and use Bitkey without creating or storing a seed phrase.
- 2-of-3 MULTISIG: Three keys are stored separately across your phone, Bitkey device, and Bitkey’s server. Any two keys are required to move your bitcoin.
- BUILT-IN RECOVERY: Encrypted backup and recovery tools can help you regain access if you lose your phone or Bitkey device. You can also designate a Recovery Contact.
Why a Lightning payment can fail even when your balance is sufficient
There is no usable route
Your wallet balance is only the amount you can spend. It does not prove that a path exists from your node or wallet service to the recipient. Pathfinding evaluates channels, advertised capacities, fees, and timeout requirements. An intermediary channel can be disabled, an involved node can be offline, or the route can lack enough capacity in the required direction.
Channel balances are not fully disclosed to the network. A wallet can therefore show enough spendable funds while the route-finding process cannot discover a path that can carry this particular payment. Retrying may succeed if a different route is found, but repeated attempts cannot create liquidity that is not available.
Liquidity is available in the wrong direction
Lightning channel capacity is divided between local and remote balances. For a payment you send, the route needs capacity to move value away from you and through each intermediary. For a payment you receive, the relevant property is inbound capacity: the ability of your node or wallet service to receive Lightning funds.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →As one side’s usable balance is depleted, finding a route in that direction becomes harder. A recipient may have an active channel and an apparently large total capacity yet lack enough inbound liquidity for your invoice. A payer usually cannot repair a remote channel or inspect every intermediary’s actual balance. Channel-management commands described in LND operator documentation are intended for node operators and are not universal controls in consumer wallets.
Rank #2
- Unparalleled Security: Protect your assets NDA-free EAL 6+ Secure Element, offering robust defense and complete transparency
- Simple & Secure Interface: Manage your digital assets easily with a clear OLED screen for secure on-device confirmations
- Supports 1000s of Coins & Tokens: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet
- Effortless Asset Management: Monitor and transact seamlessly with Trezor Suite, our intuitive desktop and mobile app
- Enhanced Backup Solution: Rest assured with Multi-share Backup, eliminating single points of failure for secure cold wallet recovery
Fees or route constraints reject the path
Channels advertise forwarding fees and timeout conditions. A wallet may reject a route whose cost exceeds its configured limit or whose timing properties do not meet its requirements. Check the fee shown by the wallet and any maximum-fee or routing setting it exposes. There is no single standard Lightning fee that applies to every payment or wallet.
A node went offline during settlement
An offline node can prevent an early route attempt from completing. More importantly, if an HTLC has already been committed, a node interruption or missing settlement information can leave the payment waiting for resolution until the applicable timeout. That is why a payment that is still in flight must not be treated as a routine failed payment.
The payment request is wrong, expired, or for a different amount
Lightning invoices contain payment-identifying data, an amount when one is specified, and an expiry value. A stale request, a copied invoice for a different amount, or a mismatch between the request and the intended recipient can stop payment or send it to the wrong transaction context. The expiry shown in an invoice example is not a universal expiry period; wallets and invoice creators can choose different values.
Recommended Free Tools
How to fix a pending or failed Lightning payment
1. Stop and inspect the original attempt
- Open the wallet’s transaction or payment history.
- Select the exact payment request that appears pending or failed.
- Record the displayed state, amount, recipient label, invoice or payment-request text, and any error message.
- Check whether the wallet offers a payment ID, payment hash, or support reference. Keep it private; do not publish credentials or recovery material.
If the state is still pending, in flight, or otherwise unresolved, leave the original attempt alone while you investigate. A second payment can create a duplicate charge if the first one later settles.
Rank #3
- Unparalleled Security: Protect your assets with EAL 6+ Secure Element, offering robust defense and complete transparency
- Simple & Secure Interface: Manage your digital assets easily with a clear OLED screen for secure on-device confirmations
- Supports 1000s of Coins & Tokens: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet
- Effortless Asset Management: Monitor and transact seamlessly with Trezor Suite, our intuitive desktop and mobile app
- Enhanced Backup Solution: Multi-share Backup eliminates single points of failure for secure cold wallet recovery
2. Verify the payment request before trying again
- Confirm that the amount is the amount you intended to pay. If the invoice is for a fixed amount, do not rely on a manually entered amount shown elsewhere.
- Confirm the recipient or merchant details using a trusted channel. A familiar name in your wallet history is not proof that the newly scanned request belongs to the same recipient.
- Check whether the wallet says the request is expired or no longer valid. Ask the recipient for a newly generated request instead of editing an old one.
- Make sure you copied or scanned the complete request. Truncation, altered characters, or an unsupported request format can produce an invoice error.
Invoice structure explains what data a wallet can validate, but it does not prescribe one universal error message. The exact wording and the way expiry is handled depend on the wallet and service provider.
3. Check the wallet’s connection and service status
Use the wallet’s built-in connection indicator, sync status, and service-status page if available. A wallet may connect directly to your own Lightning node or may depend on a provider that performs routing for you. Restarting an application can refresh a stale display, but it cannot settle an HTLC or restore a remote node’s liquidity.
- If the wallet reports that it is offline, reconnect to the network before initiating a new payment.
- If the wallet is hosted, check whether the provider reports an outage or degraded Lightning service.
- If you operate your own node, verify that the node process and its peer connections are healthy using the documentation for your installed software version.
LND operator commands are version- and configuration-specific. Do not paste node-management commands from an LND guide into a consumer wallet that does not expose an administrative interface.
4. Interpret a final failed result correctly
When the wallet explicitly marks the payment as failed, follow its retry option only after checking the invoice and connection. LND’s documented safe-retry statement applies to an initial-stage failure before HTLCs are locked in. It does not mean that every wallet’s “failed” label has identical semantics, nor that a payment marked pending can be safely replaced.
Rank #4
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
If the retry fails again, stop repeating it. Capture the error, payment reference, time, amount, and invoice details and ask the wallet provider or node operator which route or condition caused the failure.
5. Escalate an unresolved in-flight payment
There is no universal consumer timeout or guaranteed waiting period for every Lightning implementation. An in-flight payment may need to resolve through the protocol, and a provider may need to inspect its node logs or payment state. Contact support when:
- the wallet continues to show in flight or pending and provides no final result;
- the displayed state conflicts with the recipient’s claim that the payment settled;
- the amount is material and you cannot establish whether the first attempt succeeded;
- the wallet shows an HTLC, route, or settlement error that you cannot interpret; or
- the provider’s status page reports an outage.
Give support the payment reference and timestamp, not your seed phrase, private key, password, or backup file. Ask the provider to confirm the original payment’s final state before authorizing a replacement payment.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How to tell a Lightning problem from a pending Bitcoin transaction
Wallets often display Lightning activity and on-chain Bitcoin activity in the same history view. They require different remedies.
Best Value
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
| What you are seeing | Typical indicator | Correct troubleshooting path |
|---|---|---|
| Lightning payment | A payment request, route, invoice, payment hash, or in-flight status. | Check the Lightning state, invoice, connectivity, route, liquidity, and wallet support process. |
| On-chain channel funding | A Bitcoin transaction ID and a channel that is waiting for block confirmations. | Use on-chain transaction guidance and wait for the required confirmations. Fee-bumping tools, when available, are specific to the wallet, node software, and transaction state. |
| Ordinary on-chain Bitcoin payment | A Bitcoin transaction ID sent to a blockchain address rather than a Lightning invoice. | Check the transaction fee, mempool status, confirmations, and the recipient address using on-chain tools. |
An on-chain channel-opening transaction can remain unconfirmed while an ordinary Lightning payment is in flight, but those facts are not interchangeable. Do not apply an on-chain fee-bump command to a Lightning payment merely because both appear as “pending” in the interface.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Who can fix each type of problem?
| Problem | Most useful actor | Likely action |
|---|---|---|
| Wrong amount, stale invoice, or expired request | Payer and recipient | Cancel the old attempt if the wallet permits, obtain a fresh request, and verify its amount and recipient. |
| Wallet offline or provider outage | Payer or wallet provider | Restore connectivity or wait for the provider to restore service; do not duplicate an unresolved payment. |
| No route, disabled channel, or insufficient intermediary liquidity | Wallet routing service or node operators | Allow the wallet to find another route, adjust supported routing limits, or wait for network conditions to change. |
| Recipient lacks inbound capacity | Recipient or recipient’s node operator | Increase or rebalance inbound capacity through the recipient’s supported tools. The payer cannot directly repair the recipient’s remote channels. |
| HTLC-locked payment that remains in flight | Wallet provider or node operator | Track the protocol settlement and investigate the involved node; obtain confirmation before attempting a replacement. |
| Unconfirmed channel-funding transaction | Payer’s on-chain wallet or node operator | Follow the software’s on-chain confirmation and fee-management guidance. |
What not to do
- Do not pay the same invoice repeatedly while the first attempt is unresolved. A later settlement can turn a “safety” retry into a duplicate payment.
- Do not assume a sufficient wallet balance proves route availability. The missing resource may be directional channel liquidity or a reachable intermediary.
- Do not publish your seed phrase or private key to support. A legitimate provider should not need them to inspect a payment state.
- Do not treat an example invoice expiry as a universal rule. The invoice creator and wallet determine how validity is represented and enforced.
- Do not use operator-only liquidity commands in an app that does not run your node. Hosted wallets may conceal channel topology and provide only a support workflow.
- Do not use an on-chain fee-bump procedure for a Lightning payment. First identify whether the pending item has a Bitcoin transaction ID.
When a retry is reasonable—and when waiting is safer
| Situation | Safer choice | Reason |
|---|---|---|
| The wallet gives a final failed result before any settlement indicator and offers retry. | Correct the invoice or connection issue, then use the wallet’s retry flow. | LND documents early-stage failures as safe to retry, but wallet implementations differ. |
| The wallet says pending, in flight, or HTLC-locked. | Wait for a final result and contact support if it remains unresolved. | The payment may still settle or need protocol timeout resolution. |
| The recipient says nothing arrived, but your wallet says succeeded. | Share the payment reference with the recipient and provider; do not immediately pay again. | The sender and recipient displays may update at different times, and a second payment could duplicate the first. |
| The invoice is expired or clearly incorrect and the first attempt is final failed. | Request a new invoice and verify its amount before paying. | A new request removes ambiguity about validity and payment details. |
Information to collect before contacting support
A concise evidence bundle lets a provider distinguish an invoice issue from a route or settlement issue:
- Wallet and version, if the app displays it.
- Whether the wallet is self-custodied with your own node or hosted by a service.
- Exact displayed state: pending, in flight, succeeded, failed, or another label.
- Payment amount, currency denomination, date, and approximate time zone.
- Invoice or payment-request identifier and payment hash, while redacting secrets.
- Exact error text and whether the wallet reported a route, fee, liquidity, expiry, or connectivity problem.
- Whether the recipient received the payment and whether the recipient’s invoice was replaced.
- For an on-chain item, the Bitcoin transaction ID and current confirmation count.
Do not infer a cause from a generic “failed” label alone. The provider may be able to see route attempts, channel responses, and settlement status that a consumer interface omits.
Bottom line for a pending or failed Lightning payment
Identify the payment’s actual state before taking action. A final failed payment can often be retried through the wallet after you verify the request and connectivity; an in-flight or HTLC-locked payment should be monitored and escalated rather than blindly duplicated. Route availability, directional liquidity, fees, disabled or offline nodes, and invoice validity are the main Lightning-specific causes. If the pending item has a Bitcoin transaction ID, switch to on-chain confirmation guidance instead of Lightning troubleshooting.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
