Skip to content
Satnam SatoshiIn service of humanityFind your place ↗
Menu

Sikh Bitcoin · Beginner · Lesson 13 of 21

Reading a Lightning invoice

Understand amount, expiry and payment status.

About 10 minutes with practice. You only need something to take notes with. No real wallet details or payments are part of this lesson.

Course contents · Lesson 13 of 21
  1. Bitcoin without jargon
  2. Keys, custody and keeping control
  3. Payments for humans, including Lightning
  4. Money, prices and units
  5. Follow a payment from request to receipt
  6. Addresses, networks and QR codes
  7. Confirmations and patience
  8. Fees buy scarce block space
  9. Backups before dependence
  10. Scams, urgency and trusted routes
  11. Privacy is a practice
  12. Custody is a relationship
  13. Reading a Lightning invoice
  14. Exchanges and access to bitcoin
  15. Volatility and practical planning
  16. A fair invoice for creative work
  17. Donations with accountable purpose
  18. Proof of work and honest energy questions
  19. Bitcoin and Litecoin: related ideas, separate networks
  20. Read Bitcoin news with a source trail
  21. Capstone: welcome a newcomer safely

What you will learn

  • Locate the important parts of a request.
  • Explain why an expired invoice needs care.

The recipient makes a request

A Lightning invoice can encode an amount, payment hash, timestamp, expiry and descriptive information. BOLT 11 defines a widely used invoice format. Wallets present the encoded fields in a friendlier view. The text description is useful context, but it does not prove that the person sending the invoice is the artist or organizer you intended to pay.

Expiry is a condition, not a countdown game

A recipient may use an expiring invoice because its terms or receiving setup should not remain open indefinitely. Do not assume that an old screenshot remains payable. If a previous attempt has an uncertain status, resolve that attempt before obtaining and paying a new request. Otherwise two different requests might refer to one intended purchase.

The amount can be explicit or requested later

Some invoice workflows allow the payer to specify an amount; others already fix it. That difference changes what must be checked in the wallet. For a beginner, the safest classroom exercise is to annotate a mock request on paper. No real invoice or payment is needed. Distinguish invoice expiry, network routing and the status of an actual payment: they are separate pieces of information.

Practice on paper

An imaginary invoice for 8,000 sats expired before a learner opened it. No payment has been attempted. What information should a replacement preserve?

Reveal the worked answer

The intended recipient, order purpose and agreed amount should remain clear, while expiry and technical invoice fields can change. Verify the replacement through the known recipient rather than editing encoded payment data yourself.

Check your understanding

Choose an answer in your head or on paper, then reveal the explanation. Retry whenever you like. Answers are not submitted or scored; completion marks are your own learning notes.

1. Is the description cryptographic proof of a merchant’s identity?

  • Yes
  • No
Reveal answer 1

No. Check the recipient independently.

2. Should a pending attempt be ignored when asking for a new invoice?

  • Yes
  • No
Reveal answer 2

No. Resolve its result to avoid paying twice.

Take this with you

An invoice is a structured request; read its conditions.

Your learning, at your pace

Read every lesson freely. Optional progress tracking needs JavaScript and browser storage; it does not require an account or wallet.