- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Mon, 26 Mar 2018 17:10:22 +0200
- To: Adrian Hope-Bailie <adrian@hopebailie.com>
- Cc: Web Payments <public-webpayments@w3.org>
Received on Monday, 26 March 2018 15:10:49 UTC
On 26 March 2018 at 16:31, Adrian Hope-Bailie <adrian@hopebailie.com> wrote: > Pity it only works on Lightning though... Would be nice to get some > collaboration on something that works across any payment network > > https://tools.ietf.org/html/draft-hope-bailie-http-payments-00 > https://interledger.org/rfcs/0014-http-ilp/ > https://medium.com/interledger-blog/http-ilp-paid-api-calls-with- > interledger-fda53643a2eb > Thanks for the pointers. I'm a fan of the work on lightning, however the 402 response itself doesnt seem to be lightning specific So it seems that the main difference is that this work uses X-Token vs the draft using Pay-Token And the body contains bolt11 payment request Both approaches seem reasonable? Perhaps the draft could look at a variety of implementations and use cases. > > On 26 March 2018 at 13:15, Melvin Carvalho <melvincarvalho@gmail.com> > wrote: > >> Very cool use of HTTP 402 -- Payment Required -- in the paypercall >> lightning network app >> >> https://github.com/ElementsProject/paypercall#paying-for-api-calls >> > >
Received on Monday, 26 March 2018 15:10:49 UTC