Invoices & Payments
To execute a payment in bitcoin a receiver needs to provide the sender with the destination which is usually an address. On the lightning network the destination is encoded in what is called an invoice.
Aside from the standard lightning invoice, there are a number of different variations of invoices that a user can potentially send to coerce different types of transactions. These work by playing with the different primitives of an invoice to tease out certain unique types of behaviors.
We will first go over the core parts of a standard invoice, and then cover the different variations, how they are constructed and what new capabilities it adds.
We go into the default properties and behaviour of a lightning invoice.
An invoice that is held by the recipient but not settled right away.
Payments made using the recipient node’s public key instead of an invoice.
Splitting a payment across multiple routes in order to handle various routing limitations.
Work in progress…