What does the invoice contain?
A BOLT 11 invoice encodes a payment request that a compatible wallet can interpret. It can carry an amount, timestamp, expiry information and other fields. Its signature does not establish that the recipient is the person or merchant you intended.
A Lightning Address, a BOLT 12 offer and a native on-chain address are different identifiers or request mechanisms. Do not copy one into a field that expects another and assume that matching the word “Bitcoin” is sufficient. The on-chain versus Lightning guide explains the route choice.
Read an intentionally incomplete example
The fragment lnbc10u… is incomplete and cannot be used to pay. In BOLT 11 amount notation, 10 microbitcoin means 0.00001000 BTC, or 1,000 satoshis. This fragment is useful for explaining units; it is not a validated invoice or a request from Fiat2Bitcoin.
The actual wallet’s complete decoded amount is what you review before authorizing. Do not infer the amount from a fragment in a message. An amountless invoice may require the payer to specify an amount, while a particular platform may insist on a fixed amount. Follow the real receiver’s requirements.
A receiving and paying worksheet
Scroll across the table to see all columns.
| What you see | What it means | Next check |
|---|---|---|
| Recipient and purpose | Does this match the invoice you expected? | A signature alone does not identify a trusted merchant |
| Network and request type | Does your wallet support this request? | On-chain and Lightning fields are not interchangeable |
| Amount and unit | Compare satoshis, BTC and any displayed fiat estimate | 1,000 sat is 0.00001000 BTC, not 0.001 BTC |
| Expiry and status | Is this invoice still usable and unpaid? | Request a fresh invoice through the intended recipient if necessary |
What if a Lightning payment fails or remains pending?
Start with the sending wallet’s actual status. A routing attempt can fail for reasons such as route availability or liquidity; a pending result needs investigation before a second attempt. A failed attempt and a completed payment require different next steps.
Record the platform’s reference, amount, time and status. Contact the sending wallet or service through its official channel for an unresolved status. A recipient’s request to pay another invoice does not prove the first attempt failed. Share only the relevant support evidence; do not post invoice histories or payment secrets publicly.
Does the invoice tell you the complete cost?
The requested payment amount is separate from a sending wallet’s routing or service charges. Funding or opening a channel can involve other costs in some wallet designs. Read the actual preview and the wallet’s custody and recovery model rather than treating “Lightning” as a universal free-payment promise.
Fiat2Bitcoin’s educational coverage does not establish Lightning delivery availability in a provider purchase. Check the actual returned offer and supported receiving route. The provider handles its purchase, verification, payment and delivery process. For a QR that embeds more than one request, read the Bitcoin QR-code guide.
Sources & further reading
These sources explain the payment systems and rules discussed in this guide. For your purchase, check the provider’s current offer and terms.
- Lightning BOLT 11: Payment request encoding
- BIP 321: Current Bitcoin payment URI specification
- Bitcoin developer guide: Payment processing
Published by Fiat2Bitcoin. Worked examples use fictional figures and records; they are not current prices or customer transactions. How we prepare our guides.




