Free tools Windows power users keep installed
One-click scans. No signup required.
A Lightning Bitcoin payment marked pending is not automatically lost or failed. It may still be in flight while one or more payment channels resolve an HTLC (hashed time-lock contract). A failed result is a final outcome in the wallet, but the safe retry procedure depends on whether the payment failed before or after an HTLC was locked in.
Start by opening the original payment, identifying its exact state, and checking the invoice details. Do not send a second payment while the first is unresolved. Route availability, channel liquidity, node connectivity, fees, invoice expiry and on-chain confirmation are separate issues, so the right fix depends on which one your wallet is actually reporting.
As an Amazon Associate I earn from qualifying purchases.
What “pending” and “failed” mean on Lightning
Lightning payments are not single transactions broadcast directly to the Bitcoin blockchain. Your wallet attempts to send the amount through a route made of payment channels. Each hop conditionally forwards the payment with an HTLC. The payment can therefore be waiting at an intermediate stage even when your wallet has already deducted or reserved funds.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Wallet state | What it indicates | What you should do |
|---|---|---|
| In flight or pending | The payment has not reached a final success or failure state. An HTLC may still be attempting to settle or unwind. | Do not create a duplicate payment. Monitor the original record and contact the wallet provider if it remains unresolved. |
| Succeeded or paid | The recipient’s payment was completed and the payment secret was returned through the route. | Keep the receipt or payment identifier. If the merchant has not credited you, give the merchant that identifier rather than paying again. |
| Failed | The wallet has reached a final failure result. The reason may be routing, liquidity, fees, connectivity or invoice data. | Read the failure reason and use the wallet’s retry flow only when it confirms the original attempt is final. |
Wallet applications use different labels. Some display “pending” for a short pathfinding attempt; others use it for an HTLC that has already been committed. The label alone is not enough to decide whether another payment is safe.
#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 you must not pay again immediately
Open the original payment details before taking any action. Record the amount, destination, invoice or payment request, timestamp, displayed status and any error text. A second payment can create a duplicate charge if the first attempt later succeeds.
The Lightning Labs LND Builder’s Guide describes two important stages. Before HTLCs are locked in, a failed attempt can generally be abandoned and retried. After an HTLC is locked in, the payment must resolve—either by presenting the payment secret and settling or by reaching its timeout and returning funds. It is not equivalent to an ordinary failed send that can simply be started again.
There is no universal consumer timeout or guaranteed waiting period that applies to every wallet. The length of an unresolved payment depends on the route, node software, channel policy and the service operating your wallet. If your provider cannot show a final state, ask it to confirm the original payment’s status before authorizing a replacement.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsFirst check which kind of transaction is pending
Many wallets display both Lightning activity and Bitcoin on-chain activity in the same history. A pending channel-opening transaction is not the same thing as a pending Lightning payment.
Lightning payment in flight
This is an attempted payment routed through channels. It is identified in the wallet’s Lightning payment history and normally has an invoice, payment hash or equivalent payment identifier. Its resolution depends on the route and HTLC settlement.
On-chain funding or confirmation
A channel-opening transaction is a Bitcoin transaction that must receive blockchain confirmations before the channel is usable at the required level. It may remain unconfirmed because of network fees, mempool conditions or the transaction’s confirmation policy. Follow the wallet’s on-chain guidance for that case; do not apply Lightning-payment retry advice to it.
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
Some node software documents fee-bumping tools for unconfirmed Bitcoin transactions. Those tools are version-sensitive and apply to an on-chain transaction, not to an ordinary Lightning payment that is merely shown as in flight.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Inspect the payment request before troubleshooting the route
A Lightning invoice (also called a payment request) carries the information the sender needs to make the payment. The exact display varies, but the data can include the requested amount, a destination or payee identity, an expiry and a payment hash used to identify the payment.
- Compare the amount. Confirm that the amount shown in the invoice matches what you intended to send. If the invoice is for a fixed amount, do not assume your wallet can safely alter it.
- Confirm the recipient. Check the merchant, person or service name shown by your wallet against the place where you obtained the invoice. A copied request can belong to a different payment.
- Check validity and expiry. Use the wallet’s own invoice-details or validation view. An expired request may be rejected even though the text still looks intact. An example expiry shown in technical documentation is not a universal expiry period for every invoice.
- Use the original payment record. If you already attempted the invoice, inspect that attempt rather than pasting the request into a second send screen. The payment hash or wallet identifier lets support distinguish the two attempts.
- Obtain a fresh request when appropriate. If the invoice is expired, the amount is wrong or the recipient says it was cancelled, ask for a new invoice. Do not assume a fresh invoice makes an unresolved old payment disappear; verify the old status first.
Invoice formatting does not by itself reveal whether a route exists. A syntactically valid, unexpired request can still fail because no usable path is available.
How Lightning routing can fail even when your balance is sufficient
Pathfinding looks for a sequence of channels from your wallet to the recipient. It considers advertised channel information, fees, time-lock requirements and the amounts that each hop can forward. The network does not disclose the exact balance split inside every channel, so a wallet can show enough total funds while no route has the required directional liquidity.
Unavailable or disabled channels
An intermediary node may be offline, a channel may be disabled, or its advertised information may be stale. A route that existed minutes ago can become unusable when a node disconnects or changes channel policy. Your wallet may then report “no route,” “route not found” or a similar message.
Insufficient directional liquidity
Channel capacity is divided between a local side and a remote side. Funds can move only in the direction supported by the current distribution. A channel with large total capacity may have little capacity available in the direction your payment needs.
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
Fees and route constraints
Each forwarding channel can advertise a base fee, a proportional fee or other forwarding requirements. The pathfinder must find a route whose total fee and time-lock settings fit the wallet’s limits. A failure caused by a fee ceiling or route policy is different from an expired invoice, even though both stop the payment.
Recipient or intermediary outage
If the destination node or a forwarding node is offline, the route may fail before settlement. If the outage happens after an HTLC has been committed, the payment can remain in flight until the protocol resolves it. That is why an in-flight record needs different handling from a final failed result.
Liquidity: local balance, remote balance and inbound capacity
Liquidity is directional. For a node operator, local balance is the amount on that operator’s side of a channel, while remote balance is on the peer’s side. The useful direction depends on whether the node is sending or receiving.
| Situation | What the capacity means | Who can change it |
|---|---|---|
| You are sending | You need enough usable outbound liquidity along every hop, not merely a large wallet balance. | Your wallet and its connected node can choose another route; only channel operators can change channel distribution. |
| You are receiving | You need inbound capacity: the ability of your node to accept additional Lightning funds. | The receiving node operator can add or rebalance channels. A payer cannot repair a remote channel from the send screen. |
| A forwarding channel is depleted | The channel may still be open, but it cannot forward the requested amount in the needed direction. | The channel peers or routing service must restore liquidity; changing the invoice does not create capacity. |
Operator documentation can show channel balances and liquidity reports, but those controls are not exposed in the same way by consumer wallets. Do not run node-operator commands against a hosted wallet unless its provider explicitly documents them. A consumer usually cannot inspect or repair the remote channels that caused a route failure.
A safe step-by-step fix sequence
- Pause the payment. Do not press “send” again and do not create a replacement invoice until the original record has a final state or the provider tells you it is safe.
- Open the original details. Identify whether the wallet says in flight, succeeded or failed. Save the payment hash, invoice and error text if the interface provides them.
- Separate Lightning from on-chain activity. Check whether the pending item is a routed payment or a channel-funding transaction awaiting Bitcoin confirmation.
- Validate the request. Check recipient, amount, expiry and payment details. If any are wrong, obtain a corrected invoice from the recipient, but keep the old payment record available for status verification.
- Check connectivity. Confirm that the wallet is online and synchronized with the service or node it uses. If it is a hosted wallet, the provider may be experiencing an outage even when your phone or computer has internet access.
- Read the final error. A no-route, insufficient-liquidity, fee-limit or offline-node message points to routing. An invalid or expired-invoice message points to the payment request. An on-chain confirmation message belongs to a different workflow.
- Retry only after a final failure. If the wallet clearly marks the original attempt as failed and offers a retry action, follow that flow. Change only the detail the wallet or recipient says is wrong; do not assume repeated retries will solve a liquidity shortage.
- Escalate an unresolved attempt. Give the provider the payment identifier, amount, invoice, time and displayed state. Ask it to confirm whether an HTLC is still in flight and whether a replacement payment could duplicate the original.
- Confirm the recipient’s result. After a success, provide the payment identifier to the recipient if its service has not credited you. Do not send another payment solely because a merchant’s internal balance is delayed.
What to do for common failure messages
“No route,” “route not found” or “unable to find a path”
This usually means the pathfinder could not find a route that met its channel, liquidity, fee and policy constraints at that moment. Wait briefly if the wallet recommends it, then retry only after the original attempt is final. If the same invoice repeatedly fails, ask the recipient for another payment method or a newly generated invoice and report the route error to your provider.
In Taproot Assets-specific operator guidance, disabled channels and lack of liquidity are examples of causes for a no-route error. That example is not a universal error taxonomy for every Lightning wallet, so use your own wallet’s diagnostic text as the authority.
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.
“Insufficient liquidity” or “amount too large”
The problem can be directional capacity on one or more channels, not the amount in your wallet. Try the wallet’s supported route or amount options only after the first attempt is final. Splitting a payment is not universally supported and can introduce separate invoices or payment semantics; use it only when your wallet and recipient explicitly support it.
“Fee limit exceeded” or a fee warning
Forwarding fees vary by route. Review the fee shown by the wallet and its maximum-fee setting. A lower amount may fit a route, but reducing the amount changes what the recipient receives unless the invoice is designed for variable amounts. Do not override a fee warning without understanding the total you will pay.
“Invoice expired,” “invalid invoice” or incorrect amount
Stop using that request and obtain a corrected one from the recipient. Verify the old attempt’s final state before paying the new invoice. Keep the exact error text for support because wallets can use different wording for expiry, malformed data and amount mismatches.
The recipient or a node is offline
A temporary outage can prevent a new route or delay an already committed HTLC. The payer cannot force an unavailable intermediary to settle. If the payment is final-failed, retry later with the wallet’s normal flow. If it is still in flight, contact the wallet provider rather than repeatedly submitting the invoice.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why an in-flight HTLC can take longer than a normal failure
During an early attempt, a node can reject the payment before the HTLC is locked in. That kind of failure is the case for which the LND Builder’s Guide says a retry is safe: “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 statement applies to that first, pre-lock-in stage.
Once the HTLC is committed, the protocol must protect both sides while the route resolves. The recipient can settle by supplying the payment secret; otherwise the contract eventually times out and the funds return according to the channel rules. A node outage or a missing settlement message can therefore leave the wallet showing an in-flight state for an extended period. The documentation does not establish one universal timeout for all consumer wallets.
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.
Do not try to “clear” an in-flight payment by restoring a backup, deleting the wallet application or making a second payment. Those actions can obscure the original state and complicate provider recovery. Preserve the wallet’s payment record and use its support channel.
What the payer, recipient and provider can each do
| Participant | Useful actions | Actions they cannot reliably perform |
|---|---|---|
| Payer | Check status, validate the invoice, confirm connectivity, follow a final-failure retry flow and provide the payment identifier to support. | Repair an intermediary’s channel liquidity or force an offline node to settle. |
| Recipient | Confirm whether its system generated the invoice, whether it is still valid and whether a successful payment was credited. | Declare a payer’s in-flight HTLC failed merely because its own screen has no credit yet. |
| Wallet or service provider | Inspect backend payment state, identify an HTLC, explain provider-specific labels and guide recovery. | Guarantee a route when the network has no usable liquidity or an intermediary is unavailable. |
| Node operator | Monitor channels, maintain connectivity and manage local liquidity using operator tools. | Change the balance of a channel controlled by another node. |
Consumer-wallet limits versus LND operator guidance
LND documentation is written for people running or integrating an LND node. It can describe payment states, channel balances, liquidity reports and node-level diagnostics in more detail than a hosted consumer wallet exposes.
If your wallet connects to a provider’s node, you may not have access to channel lists, local and remote balances, routing policies or command-line payment tracking. The absence of those controls does not prove that funds are missing. It means the provider must inspect the underlying node and report the final state.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Use a command or setting only when your wallet’s own documentation names it for your version and deployment. A command intended for a self-hosted LND node is not a general instruction for mobile, browser or exchange wallets.
When to contact support and what to include
Contact the wallet or service provider when an in-flight payment does not resolve, when the wallet shows contradictory states, or when a final failure is followed by a balance discrepancy. Send information through the provider’s official support channel, not in a public chat.
- Wallet name and version, if the provider requests it.
- Payment date and approximate time, including time zone when relevant.
- Amount and currency unit.
- Invoice or payment request, shared only through the provider’s secure channel.
- Payment hash or transaction identifier.
- Exact status label and error text.
- Whether the recipient saw a success, failure or no payment.
- Whether the wallet is self-hosted, connected to your own node or operated by a service.
Never send a seed phrase, private key, wallet password or recovery code to support. A legitimate provider can investigate a payment without asking for control of your funds.
Checklist before you try again
- The original payment is marked failed, not pending or in flight.
- The invoice has the correct recipient and amount.
- The request is still valid or a new invoice has been issued.
- Your wallet is online and its provider reports no outage.
- You understand any displayed fee and route-limit warning.
- The recipient is ready to confirm the new payment.
- You have saved the original payment identifier in case the first attempt later settles.
If any item is uncertain, pause and ask the provider to confirm the original state. A short delay is safer than paying twice.
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.
