@@ -1669,15 +1669,28 @@ message Invoice {
16691669 */
16701670 uint64 settle_index = 17 [json_name = "settle_index" ];
16711671
1672+ /// Deprecated, use amt_paid_sat or amt_paid_msat.
1673+ int64 amt_paid = 18 [json_name = "amt_paid" , deprecated = true ];
1674+
1675+ /**
1676+ The amount that was accepted for this invoice, in satoshis. This will ONLY
1677+ be set if this invoice has been settled. We provide this field as if the
1678+ invoice was created with a zero value, then we need to record what amount
1679+ was ultimately accepted. Additionally, it's possible that the sender paid
1680+ MORE that was specified in the original invoice. So we'll record that here
1681+ as well.
1682+ */
1683+ int64 amt_paid_sat = 19 [json_name = "amt_paid_sat" ];
1684+
16721685 /**
1673- The amount that was accepted for this invoice. This will ONLY be set if
1674- this invoice has been settled. We provide this field as if the invoice was
1675- created with a zero value, then we need to record what amount was
1676- ultimately accepted. Additionally, it's possible that the sender paid MORE
1677- that was specified in the original invoice. So we'll record that here as
1678- well.
1686+ The amount that was accepted for this invoice, in millisatoshis . This will
1687+ ONLY be set if this invoice has been settled. We provide this field as if
1688+ the invoice was created with a zero value, then we need to record what
1689+ amount was ultimately accepted. Additionally, it's possible that the sender
1690+ paid MORE that was specified in the original invoice. So we'll record that
1691+ here as well.
16791692 */
1680- int64 amt_paid = 18 [json_name = "amt_paid " ];
1693+ int64 amt_paid_msat = 20 [json_name = "amt_paid_msat " ];
16811694}
16821695message AddInvoiceResponse {
16831696 bytes r_hash = 1 [json_name = "r_hash" ];
0 commit comments