Open pirapira opened 5 years ago
I think Raiden should only be focus on off chain payments and not specific scenario like merchant payment request and then response...etc, because:
@jeemud Yes, that sounds like disciplined engineering. I'll add "Invoicing might not be a part of Raiden. If Raiden provides enough functionality for others to build invoicing, that's also fine." in the description of this issue.
@pirapira I agree. I think we can have independent implementations on top of Raiden for merchant usecase. That will be good demo of Raiden also. Are there any set of requirements?
I don't know. Figuring that out is part of this issue.
Maybe this is a starting point? Raiden Invoice Repo https://github.com/ChaeByunghoon/raiden-invoice) made by @chaebyunghoon
oh that repo is just made for my demo scenario. That repo just apply concept of bolt11
Here is a short description of how the Lightning Invoicing works: https://medium.com/suredbits/lightning-101-what-is-a-lightning-invoice-d527db1a77e6
Unlike the original transaction, for the invoice payment the transaction should be initiated by receiver and the confirmation should be asked from payer by asking the secret.
Abstract
In many cases merchants send bills and then customers pay. This issue keeps track of supporting this use case in Raiden.
Invoicing might not be a part of Raiden. If Raiden provides enough functionality for others to build invoicing, that's also fine.
Motivation
@LefterisJP wondered whether this is kept track of.