About these signals: Optaimaze currently measures historical candidate rankings, not payment success probability or independent node reliability. Read methodology and coverage →

← Why Lightning payments fail

Lightning error guide

"Invoice expired" and "incorrect or unknown payment details": recipient-side Lightning failures

Last updated:

Not every Lightning failure is a routing problem. Sometimes the route works fine and the payment is refused by the invoice itself or by the recipient's node. Two errors account for most of these: "invoice expired", which your own wallet usually reports before sending anything, and incorrect_or_unknown_payment_details, which the recipient's node returns after the payment arrives.

The good news is that both are usually easy to fix, and neither means funds were lost. A rejected payment is failed back along the route.

Live data

Live Lightning routing signal

Reliability signal100/100
SignalStrong historical signal
Risk levelLow
Top-ranked nodeACINQ
Last snapshotNov 22, 2026 20:56 UTC

This is a historical ranking proxy built from observed route candidates over the last 24 hours. It is not a payment success probability and does not measure directional liquidity for your specific path.

Check current routing reliability on the dashboard →

How Lightning invoices expire

A BOLT 11 invoice carries an expiry, the x field, measured in seconds from the invoice's creation timestamp. If the field is missing, the specification's default is 3,600 seconds (one hour). Node software sets its own defaults when creating invoices. LND's addinvoice defaults to 24 hours and Core Lightning's invoice to one week. Exchanges, merchants, and swap services often use much shorter windows, frequently 10 to 15 minutes, because the invoice locks in an exchange rate or an order.

Once the expiry passes, the sender's wallet will normally refuse to pay. The recipient's node will also reject late payments, because it no longer considers the invoice valid.

Common causes of "invoice expired"

What incorrect_or_unknown_payment_details means

BOLT 4 defines this as a permanent failure returned by the final node. The recipient is deliberately vague here for privacy reasons, so the same code covers several situations:

Probing tools deliberately send payments with a fake hash and use this error to confirm a route reaches the destination. Seeing it in probe results is expected.

Fixes for wallet users

  1. Request a fresh invoice and pay it promptly. This fixes most cases.
  2. Never reuse an invoice, even for the same amount to the same person.
  3. Check your device clock and turn on automatic time sync.
  4. Before asking for a new invoice after a timeout, confirm the earlier payment is not still pending. Otherwise you risk paying twice. See payment timed out.
  5. Prefer reusable payment methods for repeat payments, such as Lightning Addresses, LNURL-pay, or BOLT 12 offers. They fetch a fresh invoice each time.

Fixes for developers and merchants

Separating invoice problems from routing problems

If a payment fails with an invoice error, the route reached the recipient, so liquidity and pathfinding were not the problem. If it fails with "no route" or repeated temporary channel failures, look at routing. See no route found and insufficient liquidity. For background on routing conditions, the Optaimaze insights dashboard shows historical ranking signals for observed route candidates.

Error guides

Lightning payment error guides

FAQ

Invoice expired FAQ

Why does my Lightning invoice say expired?

Every BOLT 11 invoice has an expiry time set by the recipient, one hour by default if none is specified, and often 10 to 15 minutes at exchanges and merchants. After it passes, wallets refuse to pay and the recipient rejects late payments. Ask for a fresh invoice. Also check that your device clock is correct.

What does incorrect_or_unknown_payment_details mean?

It is a permanent failure from the recipient's node. It covers an unknown payment hash, an invoice that is expired, canceled, or already paid, a wrong amount, a mismatched payment secret, or a final time-lock that is too short. The payment reached the recipient, so routing was not the problem.

Can I pay the same Lightning invoice twice?

No. BOLT 11 invoices are single-use. Once paid, the recipient rejects further payments to that invoice. For repeat payments, use a Lightning Address, LNURL-pay, or a BOLT 12 offer, which provide a fresh invoice each time.

Do I lose money if a Lightning payment fails because the invoice expired?

No. A wallet usually refuses to send to an expired invoice at all. If the recipient rejects a payment, the HTLC is failed back along the route and the funds return to your channel.

How long should a Lightning invoice be valid?

It depends on the flow. Price-locked checkouts often use 10 to 15 minutes with a refresh option. Donations and manual payments can use hours or a day. Use the shortest window that still leaves the payer comfortable time.

Live reliability signal

Check current routing reliability.

See current top-ranked route candidates, leadership changes, volatility, and risk level from recent snapshots.

Open Insights