A structured payment request used by Lightning wallets.
Lightning invoice meaning
A Lightning invoice carries the information a payer needs to attempt a Lightning payment. Depending on the invoice type, it can include an amount, payment hash, expiry, destination information, and routing hints. It is often shown as text and a QR code.
How it works in Bitcoin
The payer's wallet parses the invoice, finds a route through payment channels, and uses conditional transfers so the hops settle together. Traditional BOLT 11 invoices normally expire and are intended for one completed payment.
A simple example
A café creates an invoice for 25,000 sats. The customer's wallet scans it, checks the amount and description, finds a route, and completes the payment after the recipient reveals the required secret.
Why Lightning invoice matters
Lightning terms describe a payment layer built with Bitcoin transactions and off-chain channel updates. Custody, liquidity and backup design still matter even when payments feel immediate.
What people often get wrong
An invoice is not an on-chain address. Confirm the amount, description, network, and expiry, and do not send it through a wallet that does not support the requested payment type.
Quick checks before using the term
- Is the wallet custodial or self-custodial?
- Where does inbound liquidity come from?
- What happens when a channel or service is unavailable?
Apply these questions to the concrete example above. A precise answer is more useful than repeating the definition without naming the actor, rule or failure path.
Check the primary reference
This entry is written in plain English, but the technical source is available when you need exact protocol detail.
Lightning Network Specifications ↗