Bitcoin address vs Lightning invoice

An on-chain Bitcoin address tells a wallet how to construct a receiving output. The resulting transaction can be recorded in a Bitcoin block. A Lightning invoice is a payment request for the Lightning Network, which uses payment channels rather than recording each payment as a separate on-chain transaction.

This comparison focuses on common BOLT 11 invoices. Lightning also has other ways to request payment. The BOLT 11 specification defines the invoice format and expiry behavior.

A QR code can encode a bare address, a Bitcoin payment URI, a Lightning invoice or another kind of instruction. Scanning it tells the app what data is inside; the square pattern alone does not tell you which payment method it uses.

A Bitcoin payment URI can include an amount and label in addition to an address. Some payment requests offer multiple options. What matters is how your wallet decodes the request and what the confirmation screen proposes to send. BIP 321 defines the current Bitcoin URI format. It replaced the older BIP 21 and lets one payment request offer several methods at once, such as an on-chain address and a Lightning option.

Likewise, an email-like Lightning Address is not a bare on-chain address and is not itself the same object as a BOLT 11 invoice. Use wallet-supported flows rather than manually changing prefixes or guessing from the text’s appearance.

Imagine a recipient requests 20,000 sats. First they choose a receiving method their wallet supports. Your sending app must support that method too.

1. If the request is on-chain: the recipient supplies an address or a payment request containing one. Your wallet decodes it, lets you verify the amount and destination, and shows a fee estimate. The recipient may require a certain number of confirmations before accepting the payment.
2. If the request is Lightning: the recipient creates a compatible invoice. Your wallet reads its amount and expiry, then shows the proposed payment. Successful routing depends on the available route, liquidity and wallet conditions.
3. In either case: compare the recipient’s request with the decoded preview. The same 20,000 sats can have different fees and completion behavior under the two methods.

“I have enough sats” is necessary but does not establish that a particular Lightning route is available or that a provider supports the recipient’s request. Learn the related terms payment channel and confirmation.

1. Confirm the method with the recipient. Do both sides say Bitcoin on-chain, or do both say Lightning? Do not select another network simply because it also lists a BTC symbol.
2. Obtain current instructions. Use the recipient’s trusted receiving screen or request. For an expired invoice, ask for a fresh one.
3. Read the decoded preview. Check the amount, currency or unit, destination details and any description against the request. A valid format does not prove the recipient is trustworthy.
4. Review the full cost. Compare the amount the recipient should receive with the amount deducted and the displayed charges. See how Bitcoin fees work.
5. Check the result before retrying. Pending or ambiguous is not the same as failed. Confirm the wallet’s payment history and, when needed, the recipient’s status before authorizing another payment.

If the sending service rejects a request, stop and check compatibility. Editing a string to make a field accept it does not convert the payment method.

An on-chain address has no protocol expiry, but a receiving service may change its deposit instructions. Reusing addresses can also link activity. Obtain the current receiving instructions instead of treating an old saved destination as permanently appropriate.

For an ordinary Lightning invoice, request a fresh invoice for a new payment. Do not treat a previously paid or expired invoice as a permanent receiving address. Some wallets support reusable receiving mechanisms, but those are distinct flows with their own rules.

Payment compatibility also does not tell you who holds the keys. Both services and self-custody tools can offer Lightning or on-chain features. Read wallets, self-custody and recovery to understand what happens if you lose access to the app.