Lightning Invoice

Overview

A Lightning invoice is a signed, encoded payment request used to receive Bitcoin through the Lightning Network. It normally specifies an amount or allows one to be chosen, includes a payment hash, destination and routing information, expiration, and optional description data. A Lightning invoice is generally single-use and time-limited, unlike a reusable Lightning Address or an on-chain Bitcoin address. For teams linking Lightning Invoice to Lightning Address, a reliable invoice workflow links the document to payment evidence while keeping document status, payment status, and accounting status separately auditable.

Important risks include expired invoices, duplicate payment attempts, routing failure, insufficient channel liquidity, incorrect network, privacy leakage, and treating an in-flight payment as settled. Systems should store the invoice string, payment hash, amount, creation and expiry, network, payment attempt, preimage or settlement proof, fees, and final result. Implementations should link Lightning Invoice to Lightning Address and Lightning Network through auditable references. Although the records can share a customer or transaction, Lightning Invoice retains its own authority, lifecycle, and recovery rules.

Operational controls for Lightning Invoice should reconcile the requested balance with every accepted payment, fee, conversion, refund, write-off, and credit. When Lightning Invoice interacts with Lightning Address, the system should distinguish document status from payment status, preserve who changed each field and why, and define how expired instructions, partial payments, excess payments, disputed items, and transactions received after cancellation are handled. For Lightning Invoice, the invoice and the payment used to settle it should remain separate records. When Lightning Invoice interacts with Lightning Address, the invoice defines the commercial obligation, parties, amount, denomination, tax, due date, and revision history; payment records hold quotes, addresses, transaction identifiers, confirmations, fees, refunds, and settlement. In the relationship between Lightning Invoice and Lightning Network, keeping these layers separate prevents a late payment, repricing event, or refund from silently changing the document originally issued to the customer.