First check the payment’s actual state in your wallet or node. A payment marked in flight (or pending) is not the same as a final failure, and sending the invoice again can create a duplicate charge attempt. Retry only after the original payment reaches a final failed state, and verify the invoice before trying again. A successful payment should not be sent again, even if a merchant has not yet updated your order.
What a stuck or failed Lightning payment means
Lightning payments are designed to be atomic: they either complete in full or fail in full. Lightning Labs states in its Builder’s Guide, “Each Lightning payment is atomic, meaning it is either completed or failed in full.” That does not mean every payment reaches a final status immediately. A payment can remain in flight while the network resolves the conditional transfers used along its route.
As an Amazon Associate I earn from qualifying purchases.
Your first task is therefore not to find a new route or press Pay again. It is to identify the current state recorded by the sending wallet or node. The correct next step depends on whether the payment succeeded, failed finally, or is still in flight.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →The word “stuck” is often used for two different situations. A wallet may simply be waiting for a response while the route is still active, or it may be displaying an unusually long unresolved HTLC. Neither situation should be treated as an ordinary failed payment until the wallet records a final result. A brief delay, a spinning progress indicator, or a merchant page that has not refreshed is not enough evidence to submit a second payment.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Check the payment state before doing anything else
Open the payment in your wallet and view its detail page. Wallet labels vary, but look for terms such as succeeded, settled, failed, pending, or in flight. If you operate an LND node, its TrackPaymentV2 payment-tracking function reports the same broad outcomes and can look up payments that have already reached a final state.
| Displayed state | What it means | Safe action |
|---|---|---|
| Succeeded or settled | The payment completed. The recipient should have the payment proof associated with it. | Do not pay the invoice again. If a merchant has not credited your account, contact it privately and provide the payment hash or wallet proof. |
| Failed (final) | This attempt will not be reattempted automatically. | Verify the invoice and the failure context, then make a new attempt only if the invoice is still valid or the recipient issues a fresh one. |
| In flight, pending, or unresolved | The attempt has not reached a final result. An HTLC may still be locked along the route. | Keep the original payment open, monitor it, and do not create a duplicate payment merely because it is taking longer than expected. |
Some wallets use “pending” for ordinary interface work as well as for an HTLC that has actually been locked in. Read the payment detail, not just the notification banner. If the wallet exposes a payment hash, keep it with the record; it lets support or the recipient distinguish this attempt from another attempt using a similar amount.
If the payment succeeded
Never send the same invoice again after a successful result. A missing order update can be a merchant-side synchronization problem rather than a failed payment. Use the merchant’s support channel, not a public chat or social-media post, and provide the payment hash, approximate time, amount, and the wallet’s successful status. Do not disclose seed words, private keys, or account credentials.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A recipient may need to search its invoice records by payment hash before it can credit an account manually. Give the merchant enough information to locate the transaction, but do not give anyone access to the wallet itself. Atomic settlement means the payment is not partly completed; it does not guarantee that a separate order database updates at the same instant.
If the payment failed finally
A final failure means that this particular attempt will not be tried again automatically. It does not by itself prove that the invoice is invalid. Lightning pathfinding uses observations from earlier successes and failures, and route conditions can change between attempts. Continue with the invoice checks below before deciding whether to retry.
Record the exact error before dismissing it. “No route,” “temporary channel failure,” and an invoice-details error point to different checks, even though a consumer wallet may show only a short summary. A final failure is a stopping point for that attempt, not a reason to keep pressing the same button without changing or verifying anything.
If the payment is still in flight
Do not treat a delay on the screen as proof of failure. When an HTLC has been locked in, the route must either settle when the receiver reveals the payment preimage or unwind after its timeout. Until that process finishes, a second payment can be a duplicate attempt against the same purchase. Leave the original payment visible in the wallet or node and check its status periodically.
Closing the app or restarting a device does not turn an in-flight payment into a final failure. Use the wallet’s normal recovery and synchronization process, then inspect the same payment record. If the application gives a stated pending window, use that window as your guide rather than an arbitrary time limit.
Verify the invoice before a new attempt
Lightning invoices encode the destination, amount, and validity information. Before retrying a final failure, inspect all three elements:
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
- Recipient: Confirm that the invoice came from the person or service you intended to pay. Do not trust an invoice copied from an unverified message, image, or website.
- Amount: Compare the encoded amount with the amount shown by the merchant or recipient. Stop if they differ.
- Validity: Check whether the invoice has expired. An expired request cannot be made valid by retrying it.
If the amount or recipient is wrong, the invoice is expired, or the receiving service says it cannot find the request, ask for a fresh invoice. Verify the new invoice independently before approving payment. On the recipient side, an invoice can be looked up by its payment hash, which helps support staff determine whether the request exists and what state it has reached.
Do not assume that a copied invoice is safe merely because it has the right amount. A malicious or mistaken sender can substitute a different destination while leaving the amount unchanged. Compare the invoice with the recipient’s trusted communication channel, and confirm the denomination shown by the wallet before authorizing it. If the service generates a new invoice, use that new request rather than editing or reusing an old string.
Free tools Windows power users keep installed
One-click scans. No signup required.
Decide whether retrying is safe
The key distinction is whether the previous attempt is final. LND documentation says failures that occur before an HTLC is locked in are safe to retry. Once an attempt is in flight with an HTLC locked along the route, it must resolve before you treat it as finished.
- Read the wallet’s payment detail and wait for a definitive result if it says pending or in flight.
- If it reports a final failure, check the invoice recipient, amount, and expiration.
- Ask the recipient for a fresh invoice when any invoice detail is wrong or the request has expired.
- Make one new attempt only after the previous one is final and the invoice is verified.
- If the new attempt also fails, stop repeating the same action and investigate route, liquidity, or service availability.
A single retry can succeed because path selection or network conditions changed. Repeatedly pressing the payment button without checking state does not improve those conditions and can make it harder to determine which attempt a merchant received. If the recipient has already confirmed one settled payment, do not make another attempt simply because an order page is slow.
Understand common route and “no route” errors
Lightning nodes advertise channel capacity and fees, but they do not publicly disclose the exact balance distribution inside every channel. A route can therefore look plausible while lacking enough balance in the required direction at the moment of payment. A channel may also be offline, disabled, or unable to forward the amount after fees are included.
Consequently, a generic no route or forwarding failure often indicates a liquidity or availability problem rather than an invalid invoice. After a final failure and invoice verification, a different route may work. If the recipient controls the service, it may be able to restore channel availability or provide a new invoice through a different receiving path.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFees matter at every forwarding hop. Even when the destination amount is affordable, the sender must have enough outbound liquidity for the amount plus the route’s forwarding fees. Public channel capacity is only a ceiling; it is not a promise that the needed directional balance is available right now. This is why a route can appear theoretically valid and still fail at dispatch.
What you can do as an ordinary wallet user
- Confirm the payment is final, not merely delayed.
- Verify the invoice and request a fresh one if it is expired or incorrect.
- Retry once when the wallet reports a final failure and the invoice is valid.
- Try again later if the service confirms a temporary availability problem, while keeping the failed attempt’s record for support.
- Contact wallet or merchant support with the timestamp, amount, invoice or payment hash, exact status, and displayed error.
You generally cannot inspect or repair the remote channel balances used by a custodial or hosted wallet. Avoid downloading “recovery” software, sharing a seed phrase, or paying someone who claims it can force a pending payment to settle. A person who asks for your seed phrase, private key, wallet password, or remote-access code is asking for control of your funds, not providing a route diagnosis.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
How to handle a genuinely stuck in-flight payment
An in-flight payment can become slow when a forwarding node or the receiver goes offline after an HTLC has been locked in. The receiver must reveal the preimage to settle it; if that does not happen, the conditional transfer can resolve only through its timeout path. The wallet may eventually change the status to failed or otherwise release the locked funds, but the exact wait depends on the route and implementation.
- Record the payment’s current status, amount, timestamp, invoice, and payment hash.
- Leave the original payment entry intact. Do not start a second payment for the same invoice while the first is unresolved.
- Check the wallet periodically for a final state rather than refreshing by repeatedly submitting the payment.
- Use the wallet’s stated support window as the escalation point. If that window passes without resolution, contact the wallet provider with the recorded details.
- Send those details through a private support channel. Never post an invoice, payment hash, account identifier, or other transaction information publicly when support does not require it.
Do not promise yourself an immediate refund simply because Lightning payments are atomic. Atomicity describes the final outcome; it does not guarantee that an HTLC already locked in will resolve instantly. A timeout is a protocol resolution, not a manual refund button, so support may need to wait for the wallet or node to observe the final state.
Node-operator diagnostics and remedies
Running your own Lightning node gives you more visibility than a normal wallet, but it also adds operational work. These checks are for node operators; they are not instructions to purchase a particular service or hardware product.
Inspect channel activity
Review whether the channels that could carry the payment are active and able to forward traffic. An inactive or disabled channel cannot provide a usable route even if its nominal capacity is large. Check the channels on the likely path rather than assuming that every open channel is available for every destination.
Check directional balances
Look at both local and remote balances for candidate channels. Sending requires outbound liquidity on the relevant direction. A channel can have substantial total capacity while offering too little balance on the side needed for your payment. Balances shift as other payments move, so an earlier observation can become stale quickly.
Account for fees and amount
Forwarding fees reduce the amount available along a route. A path that appears to fit the invoice amount may fail when fees or channel limits are applied. Compare the required amount with the available outbound balance on each hop, including the amount needed to cover fees.
Rebalance or obtain liquidity
If your node lacks outbound liquidity, consider an operational rebalancing strategy or obtaining additional liquidity through channels you control. The appropriate remedy depends on your topology, counterparty reliability, risk tolerance, and the amount you need to send; the documentation does not establish one universal provider or method. These are node-management decisions, not a reason for a consumer to install unfamiliar software or hand over wallet credentials.
Use path history carefully
LND’s Mission Control records previous payment successes and failures to influence pathfinding. Those observations are time-sensitive: balances and node availability change as other payments move through the network. A route that failed earlier may become usable later, while a route that worked yesterday may fail now. Treat path history as guidance rather than a permanent verdict on a channel or recipient.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Taproot Assets: errors with asset-specific causes
Taproot Assets payments can produce errors that require different handling from a standard Bitcoin-denominated Lightning payment. Apply the following guidance only when you are sending a Taproot Asset and your implementation reports the corresponding error.
FAILURE_REASON_NO_ROUTE
The Taproot Assets documentation associates this error with a disabled channel or insufficient liquidity. Check the node’s local channels and both asset capacity and satoshi capacity. A channel may have enough Bitcoin capacity for fees but not enough of the specific asset, or the reverse. Looking only at satoshi capacity can therefore miss the actual restriction.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →FAILURE_REASON_INCORRECT_PAYMENT_DETAILS
An asset invoice may require a hop hint identifying an asset-specific channel. If the sender routes through another channel, the receiver can reject the payment with this error. When the invoice supplies an applicable hop hint, ensure your sender honors it rather than forcing a different path. Confirm that the asset and amount in the request are the ones you intended to send.
Do not apply these implementation-specific checks to every consumer Lightning wallet. If you are not operating Taproot Assets infrastructure, follow the ordinary status, invoice, and retry workflow instead.
When to contact support
Escalate when the status remains unresolved beyond the wallet’s stated window, when a successful payment is not credited, or when repeated final failures continue after invoice verification. Include:
- Wallet or node name and software version, if relevant.
- Payment amount and currency denomination.
- UTC timestamp or the time zone used by the wallet.
- Invoice and payment hash, sent privately.
- Current state and the exact error text.
- Whether the recipient has confirmed receiving or locating the invoice.
Support should not need your seed phrase, private key, wallet password, or remote-access code. Anyone requesting those to “unstick” a payment is asking for control of your funds, not diagnosing a Lightning route. Keep screenshots or copied error text if they do not expose secrets, since the exact wording can help distinguish an invoice problem from a route problem.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsPrevent avoidable failures
- Pay invoices only from a trusted recipient and verify the displayed amount before approval.
- Keep the wallet software updated through its normal distribution channel.
- After tapping pay, wait for the wallet’s final result instead of submitting repeatedly.
- Save the payment detail when an error appears so support can distinguish a final failure from an in-flight attempt.
- If you operate a node, monitor channel activity and directional liquidity rather than relying on total advertised capacity.
The practical rule is simple: a final failed attempt can be retried after the invoice is checked; an in-flight attempt must be monitored until it settles or times out; and a successful attempt should never be duplicated.
Frequently Asked Questions
Can I retry a Lightning payment that says pending?
Not automatically. Pending or in-flight means the attempt may still contain a locked HTLC. Wait for a final succeeded or failed state, then act on that result. Sending the same invoice again can create a duplicate payment attempt.
Does a failed Lightning payment mean my money is gone?
A final failed attempt will not be reattempted automatically, and it is not the same as a settled payment. If the status is still in flight, funds may remain temporarily committed until the HTLC settles or times out. Check the wallet’s recorded state rather than assuming either outcome from a delay.
What should I do if the merchant says it did not receive a successful payment?
Do not pay again. Give the merchant the payment hash, amount, approximate time, and successful wallet status through a private support channel. The recipient can use the payment hash to locate its invoice and investigate an order-crediting or synchronization issue.
Why does Lightning show “no route”?
The route may lack directional liquidity, include an inactive or disabled channel, or fail after forwarding fees are considered. Public channel capacity does not reveal the exact balance distribution. After a final failure, verify the invoice and make one new attempt if appropriate; repeated submissions without a final state are unsafe.
Should I ask for a new invoice?
Yes, when the existing invoice is expired, has the wrong recipient or amount, or the receiving service cannot locate it. Verify the fresh invoice independently before paying. Do not edit an old invoice or rely on one copied from an untrusted source.
How long does a stuck Lightning payment take to resolve?
There is no universal time stated for every route or wallet. An HTLC can settle when the receiver reveals the preimage or resolve through its timeout path if that does not happen. Use the wallet’s stated support window and contact support if the payment remains unresolved beyond it.
What extra checks apply to Taproot Assets?
For a Taproot Assets payment reporting FAILURE_REASON_NO_ROUTE, inspect channel status plus both asset and satoshi capacity. For FAILURE_REASON_INCORRECT_PAYMENT_DETAILS, the invoice may require an asset-specific hop hint. These checks are implementation-specific and do not replace the ordinary workflow for standard Lightning payments.
Recommended Free Tools
What information is safe to send to support?
Provide the wallet or node version, amount and denomination, timestamp, payment hash or invoice through a private channel, current state, exact error, and whether the recipient can locate the invoice. Never send seed words, private keys, passwords, or remote-access codes.
The Bottom Line
Bottom line: Check the payment state first. Never duplicate a successful or unresolved in-flight payment. Retry only after a final failure, and verify the invoice’s recipient, amount, and validity before trying once more. If the payment remains locked, wait for settlement or timeout and use the wallet’s support process; node operators should then investigate channel status, directional liquidity, fees, and path history.
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.
