Skip to content
A global perspective on digital financeAbout The Token Press
CRYPTO. FINANCE. WHAT’S NEXT.The Token PressYour daily briefing ↗

Beginner · 6 min read

Bitcoin Lightning Payments: Invoices, Fees and Failed Transfers

Learn how a Lightning invoice differs from an on-chain address, what expiry and liquidity mean, and how to check a payment with an offline fee-and-status exercise.

The Token Press education desk · Updated

What is a Bitcoin Lightning payment?

Lightning is a payment network using channels anchored to Bitcoin's blockchain. Payments move through those channels rather than requiring a separate ordinary on-chain transfer for every purchase. The unit is still bitcoin; using Lightning does not require buying a separate 'Lightning coin'.

Lightning Labs describes routing a payment through connected nodes and channels. A usable route needs available participants and sufficient liquidity. This can make small payments practical, but neither a fast result nor a low fee is guaranteed for every payment or wallet service.

This guide focuses on checking a conventional BOLT 11 invoice payment. Other request formats and wallet features exist; follow your chosen wallet's documented support. You can complete the examples without installing a wallet, opening a channel or spending bitcoin.

If addresses, wallets and networks are new to you, start with the transfer and custody guides linked below. A Lightning-capable app may offer both on-chain and Lightning options, so the fact that both screens say BTC is not enough to select the right route.

How is an invoice different from an on-chain address?

A BOLT 11 invoice is a signed payment request with fields the wallet decodes. Its specification includes a network prefix, payment hash, description or description hash, and timing information. An amount can be specified or left open. Do not assume scanning a QR code has already checked the intended amount or recipient.

Use the recipient's trusted checkout or receiving screen to obtain the request. Let a compatible wallet decode it, then compare the network, requested amount, description and expiry with what you intended. A valid signature establishes a relationship to the signing node; it does not independently prove that the business or person behind a website is trustworthy.

Do not paste a Lightning invoice into an on-chain-only withdrawal field or treat an ordinary Bitcoin address as a BOLT 11 invoice. If a wallet offers conversion or another payment method, read that separate route's fees and instructions. Similar labels do not make the underlying destinations interchangeable.

An invoice may be displayed as text or a QR code. Neither presentation makes it an on-chain address. Avoid publishing live invoices or payment proofs in support screenshots; share only the information the legitimate provider needs through its official support channel.

Check expiry and status before asking for a new invoice

BOLT 11 defines expiry relative to the invoice's creation timestamp and says a payer should not attempt payment after that interval. Read the decoded expiry rather than assume every wallet uses the same default. If an unused invoice has expired, return to the trusted recipient to request a fresh one.

Expiry is not a cancellation or refund receipt for a payment already attempted. First inspect the original payment's status. If it is still in progress or its outcome is unclear, resolve that record before paying a replacement request. A second invoice could represent a second payment for the same order.

Lightning Labs' LND documentation describes invoices as one-use requests and provides invoice monitoring by payment hash, including settlement updates. A request being created is therefore a different event from it being settled. For an ordinary checkout, keep the order reference and the corresponding payment reference together.

These checks are especially useful when someone sends an old screenshot. The screenshot might show a request that has expired or already been paid. Ask for the current receiving workflow rather than relying on the appearance of the QR image.

Why can a payment fail when I have enough BTC?

A balance and the ability to route a payment are different things. Lightning Labs describes outgoing liquidity for sending and incoming capacity for receiving. A route can be unusable because of channel conditions or an unavailable participant even when the sender sees enough funds in an app.

For a deliberately simplified channel example, suppose 100,000 sats of total capacity is divided into 70,000 on your side and 30,000 on your peer's side. Ignoring reserves, pending payments, fees and all other limits, that channel gives you up to 70,000 sats of outgoing capacity and 30,000 of incoming capacity. It does not give you 100,000 in both directions.

Under those assumptions, receiving 40,000 sats through that channel cannot fit into its 30,000-sat incoming side. A real wallet can have multiple channels, split payments or use service-provider arrangements; this worksheet is not a prediction of its actual receive limit.

Record the wallet's failure reason and check its official instructions. Do not respond to every failure by raising fees, funding a new channel or paying a recovery service. If the wallet uses a custodian, its account limits and service status also matter. Review who controls the funds and what the wallet's recovery process actually restores.

Worked example: invoice amount, fees and total debit

Consider a fictional request for 25,000 sats. One bitcoin contains 100,000,000 sats, so the requested amount is 0.00025 BTC. No dollar conversion is needed to check that unit conversion.

Suppose a fictional wallet preview separately lists a maximum routing fee of 60 sats and a fixed service charge of 20 sats. If those are the only charges and both are additional to the invoice amount, the maximum debit under this preview is 25,080 sats. This is an arithmetic assumption, not a statement about any wallet's pricing.

The final record in our exercise shows a routing fee of 18 sats, the same 20-sat service charge and a successful 25,000-sat payment. The debit is 25,038 sats, or 0.00025038 BTC. The 38-sat total fee is 0.152% of the invoice amount. The unused portion of a maximum fee is not another charge in this example.

Compare the actual preview and receipt field by field. Some services may quote a combined fee or impose different charges for funding, receiving or moving funds on-chain. Do not subtract a fee twice or assume a routing-fee limit caps every charge in the wallet.

For a second scenario, add a separately disclosed 1,000-sat setup cost. The exercise's total becomes 26,038 sats. A small per-payment routing fee does not make that additional cost disappear. Decide which costs belong to this payment and which serve later use before making a comparison.

Visual explainerReconcile the actual payment, not just its preview
Invoice25,000 satsThe amount requested by the fictional recipient.
Actual fees38 sats18 routing plus 20 service; both additional in this example.
Total debit25,038 sats0.00025038 BTC; no market-price assumption.
A 60-sat maximum routing fee is different from the 18-sat routing fee actually charged.Original hypothetical worksheet, not a live wallet quote or transaction. Other charges are excluded unless stated.

What counts as evidence that the recipient was paid?

Inspect the sender's final payment record and the recipient's invoice or order status. LND's documentation distinguishes newly created invoices from settled invoices and supports monitoring the latter. A screenshot of a request, a spinner or an attempted send is not the same evidence as settlement.

BOLT 11 describes cryptographic payment evidence tied to the signed request. A payment hash is a Lightning reference, not automatically a Bitcoin transaction ID that will appear in an on-chain explorer. Keep the wallet's appropriate receipt and reference; do not conclude that a payment failed solely because an explorer cannot find that reference.

For an exchange deposit or a merchant order, also check the receiving service's credit or fulfilment record. Those are application steps in addition to the payment. If the sender reports success but the order remains unpaid, reconcile the original request and references through official support before paying again.

For ordinary pending on-chain transactions, use the separate RBF and CPFP guide. Its fee-bumping techniques are not general instructions for retrying a Lightning invoice.

Five-minute practice: choose the next check

Case A: a request was created at 10:00 UTC with an explicit 15-minute validity period. At 10:20 UTC, no payment has been attempted. It expired at 10:15; obtain a new request from the trusted recipient. Do not infer expiry from a default or from the time you first opened the screenshot.

Case B: the same request was attempted at 10:14 and the wallet still reports an unresolved payment at 10:16. The correct next step is to inspect and resolve that original attempt, not assume the clock crossing 10:15 reversed it.

Case C: the fictional receipt shows 25,000 sats paid and fees of 18 plus 20 sats, but the merchant order is still pending. Reconcile 25,038 sats of debit and the original payment reference with the order. This is a receiving-service investigation, not evidence that another payment is required.

Change Case C's service charge to 30 sats. The expected debit becomes 25,048 sats. If the receipt still says 25,038, one of the recorded fields or assumptions needs correction. Keep the discrepancy visible rather than invent an explanation to make the numbers agree.

  • The receiving method and wallet support match.
  • The invoice amount, units, expiry and intended recipient have been checked.
  • The fee limit and any additional service costs are understood.
  • An unresolved attempt is investigated before a replacement payment.
  • Payment settlement and the recipient service's account or order credit are checked separately.

Sources & further reading

Educational content. Examples are illustrative. Protocols, products and rules can change; consult the linked documentation for current details.

Explore the newsroom

Connect what you have learned with the latest reporting.