For trivial amounts of money it's not a big deal if someone has to wait for everyone to figure out what is wrong, for larger amounts it is a big deal.
But.....
For trivial amounts it's not worth the time and effort to setup lightning for them. For larger amounts I could see it being a support nightmare.
How many posts here do you think we would see with people complaining that they were not getting 0.025BTC funds from exchange XYZ while the exchange is trying to explain the largest channel they have open is .0245BTC
-Dave
Businesses that accept LN today often advertise the maximum they can receive via LN. I don't see any reason why businesses wouldn't be able to advertise the max they can send via LN.
It's not what *they* can send it's what *the customer* can receive.
[img ]https://i.imgur.com/pZIR5jgl.jpg[/img]Look I have 0 that's zero, nothing, nada, zip inbound or outbound available. I just spun that node up.
But I can create a payment request and send it to an exchange, or anyone.
Not going to work however. So, yeah that's the issue.
Used RTL to make the point because it's easier to see, but can do the same from the CLI and get the same result.
-Dave
Ahh, I see your point. If a person has open channels with insufficient inbound capacity, the customer not understanding their inbound capacity limit may be an issue of insufficient/inadequate documentation that can be read/understood by the 'average' non-technical user, or error messages that are not specific enough.
If you were to send that invoice to a business, the business should (automatically) be able to tell you what is preventing them from paying the invoice, in your case insufficient inbound capacity.