FAILURE_REASON_INCORRECT_PAYMENT_DETAILS

[premek]

Hi,
I'm often getting the following error when trying to pay an invoice using lncli and it's not clear to me what is wrong.

Payment status: FAILED, reason: FAILURE_REASON_INCORRECT_PAYMENT_DETAILS

I was able to pay one invoice using a newly opened channel but another one fails and I'm not able to send more payment anymore

I have a channel opened with the destination node

+------------------------------------------+--------------+--------------+--------------+-----+----------+--------------------+---------------------+
| HTLC_STATE                               | ATTEMPT_TIME | RESOLVE_TIME | RECEIVER_AMT | FEE | TIMELOCK | CHAN_OUT           | ROUTE               |
+------------------------------------------+--------------+--------------+--------------+-----+----------+--------------------+---------------------+
| INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS @ 1 |        0.061 |        0.645 | 20000        | 0   |   694965 | 764099008684228608 | WalletOfSatoshi.com |
+------------------------------------------+--------------+--------------+--------------+-----+----------+--------------------+---------------------+
Amount + fee:   0 + 0 sat
Payment hash:   08596fe98057b93f1d98b9833c26d8751ac8d3e96dfa52fde4893be29f2218c9
Payment status: FAILED, reason: FAILURE_REASON_INCORRECT_PAYMENT_DETAILS
[lncli] FAILED

2021-08-09 14:14:13.878 [DBG] HSWC: ChannelLink(694944:474:0): settle-fail-filter &{1 [0]}
2021-08-09 14:14:13.878 [DBG] HSWC: Closed completed FAIL circuit for 08596fe98057b93f1d98b9833c26d8751ac8d3e96dfa52fde4893be29f2218c9: (0:0:0, 6049) <-> (694944:474:0, 4)
2021-08-09 14:14:13.878 [DBG] HSWC: Storing result for paymentID=6049
2021-08-09 14:14:13.893 [DBG] HSWC: Received network result *lnwire.UpdateFailHTLC for attemptID=6049
2021-08-09 14:14:13.894 [WRN] CRTR: Attempt 6049 for payment 08596fe98057b93f1d98b9833c26d8751ac8d3e96dfa52fde4893be29f2218c9 failed: IncorrectOrUnknownPaymentDetails(amt=20000000 mSAT, height=694948)@1
2021-08-09 14:14:13.909 [DBG] HSWC: Tearing down open circuit with FAIL pkt, removing circuit=(Chan ID=0:0:0, HTLC ID=6049) with keystone=(Chan ID=694944:474:0, HTLC ID=4)
2021-08-09 14:14:13.913 [DBG] CRTR: Reporting pair success to Mission Control: pair=0205330720293b3bb0d9b126316c5ab7582f38d25e3c58615fc0c6613fa51e719d -> 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226, amt=20000000 mSAT
2021-08-09 14:14:13.913 [DBG] CRTR: Setting 0205330720293b3bb0d9b126316c5ab7582f38d25e3c58615fc0c6613fa51e719d->035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226 range to [20000000 mSAT-0 mSAT]
2021-08-09 14:14:13.913 [INF] CRTR: Payment 08596fe98057b93f1d98b9833c26d8751ac8d3e96dfa52fde4893be29f2218c9 failed: final_outcome=incorrect_payment_details, raw_err=IncorrectOrUnknownPaymentDetails(amt=20000000 mSAT, height=694948)@1
2021-08-09 14:14:13.924 [DBG] CRTR: Payment 08596fe98057b93f1d98b9833c26d8751ac8d3e96dfa52fde4893be29f2218c9 in state terminate=true, active_shards=0, rem_value=20000000 mSAT, fee_limit=10000 mSAT
2021-08-09 14:14:13.925 [ERR] CRTR: Payment 08596fe98057b93f1d98b9833c26d8751ac8d3e96dfa52fde4893be29f2218c9 failed: incorrect_payment_details
2021-08-09 14:14:13.924 [DBG] HSWC: Closed completed FAIL circuit for 08596fe98057b93f1d98b9833c26d8751ac8d3e96dfa52fde4893be29f2218c9: (0:0:0, 6049) <-> (694944:474:0, 4)

[Roasbeef]

Are you trying to pay the very same invoice twice? Most nodes will reject payments to the same invoice twice, as it can actually result in loss of funds (someone in the middle just takes the payment since they remember the pre-image).

What arguments are you using when you use lncli (for the command itself)?

Also which version are you on?

[premek]

I'm on 0.13.0-beta and I'm using lnd with neutrino.

I believe it was not the same invoice two times.
I tried again today and after some successful payment I got the same error again. This time the route had 2 hops.

$ ./lncli payinvoice $I  -f --fee_limit 20 --amt 9000
+------------------------------------------+--------------+--------------+--------------+-------+----------+--------------------+-----------------------------------------------------------------------------------------+
| HTLC_STATE                               | ATTEMPT_TIME | RESOLVE_TIME | RECEIVER_AMT | FEE   | TIMELOCK | CHAN_OUT           | ROUTE                                                                                   |
+------------------------------------------+--------------+--------------+--------------+-------+----------+--------------------+---------------------------------------------------------------------------------+------------------------------------------+--------------+--------------+--------------+-------+----------+--------------------+-----------------------------------------------------------------------------------------+
| HTLC_STATE                               | ATTEMPT_TIME | RESOLVE_TIME | RECEIVER_AMT | FEE   | TIMELOCK | CHAN_OUT           | ROUTE                                                                                   |
+------------------------------------------+--------------+--------------+--------------+-------+----------+--------------------+-----------------------------------------------------------------------------------------+
| INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS @ 4 |        1.513 |        7.426 | 9000         | 1.018 |   695250 | 763297464789762048 | WalletOfSatoshi.com [2]->basaltmagnostempest->025aacb6dffa00232bb6->WalletOfSatoshi.com |
+------------------------------------------+--------------+--------------+--------------+-------+----------+--------------------+-----------------------------------------------------------------------------------------+
Amount + fee:   0 + 0 sat
Payment hash:   19bcd4e57b67bdd52e77de35292fe640d3a5587aae556366cf4de676f5f9117f
Payment status: FAILED, reason: FAILURE_REASON_INCORRECT_PAYMENT_DETAILS
[lncli] FAILED

Then I restarted the lnd and a payment of the same invoice went through this time:

$ ./lncli payinvoice $I  -f --fee_limit 20 --amt 9000
+------------+--------------+--------------+--------------+-------+----------+--------------------+-----------------------------------------------------------------------------------------+
| HTLC_STATE | ATTEMPT_TIME | RESOLVE_TIME | RECEIVER_AMT | FEE   | TIMELOCK | CHAN_OUT           | ROUTE                                                                                   |
+------------+--------------+--------------+--------------+-------+----------+--------------------+-----------------------------------------------------------------------------------------+
| SUCCEEDED  |        1.487 |        4.964 | 9000         | 1.018 |   695254 | 763297464789762048 | WalletOfSatoshi.com [2]->basaltmagnostempest->025aacb6dffa00232bb6->WalletOfSatoshi.com |
+------------+--------------+--------------+--------------+-------+----------+--------------------+-----------------------------------------------------------------------------------------+
Amount + fee:   9000 + 1.018 sat
Payment hash:   19bcd4e57b67bdd52e77de35292fe640d3a5587aae556366cf4de676f5f9117f
Payment status: SUCCEEDED, preimage: 2bdb93402f5e93022f4aa0dfc15276e020748887a45605eb18551947367a9c06

[Roasbeef]

Ah, ok makes sense, we had a regression in this area for 0.13, that's been fixed in 0.13.1: #5404

[Roasbeef]

This issue was resolved in 0.13.1: #5404

[premek]

great, thanks, I will update