Received an invoice for 1.5 sats, paid it, 4 were paid, now wallet no longer works. Error message below.
See original GitHub issueAs above:
Received an invoice for 1.5 sats, paid it, 4 sats were paid (no idea why) - now wallet no longer works.
Getting the error message:
Alert
API error: Payment failed. Does the receiver have enough inbound capacity? (Code 10)
Initially we thought the error was on the side of the person invoicing me.
Then they opened another hosted LN wallet, and I got the same error when trying to pay that.
Then they tested invoicing between their 2 hosted wallets and it worked.
So seems its just my Blue wallet. Has adequate sats in there.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Did you get an unexpected invoice from PayPal? It's a scam
Did you receive an unexpected invoice from PayPal? Don't send the money, it's a scam.
Read more >payment amount was below the minimum required by ... - GitHub
I wanted to send pay an invoice received from another Phonix user but the payment failed with the error "payment amount was below...
Read more >Ticket: # 1227953 - Spam advertisement emails Description
I have been receiving a number of advertisement emails from American Home ... prompts the user to have to opt out of text...
Read more >Invoice States | BitPay Documentation
An invoice is considered invalid when it was paid, but the corresponding cryptocurrency transaction was not confirmed within 1 hour on the corresponding ......
Read more >Shipstation Error Transferring Wallet Funds
I tried it your way and when I finally got to the part where I pay and print, this error message came up:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
10 more reports like this and I’ll fix the error message 😆