- From: Matt Saxon <matt.saxon@gmail.com>
- Date: Mon, 15 Feb 2016 19:49:45 +0000
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: Adrian Hope-Bailie <adrian@hopebailie.com>, public-payments-wg@w3.org
Manu, No problem, I'll add it back to the list. This has been my misunderstanding, not an attempt to descope. Adrian, will you be able to refactor to align as far as possible with the rest of the flows, in particular adding a payee site? Regards, Matt Sent from my iPhone > On 15 Feb 2016, at 03:21, Manu Sporny <msporny@digitalbazaar.com> wrote: > >> On 02/14/2016 05:47 PM, Matt Saxon wrote: >> I dropped it based on my understanding that he basic flow just >> covered a peer to peer payment and the other flow covered an >> interaction closer to a web browser payment. If I've misunderstood, >> please can someone clarify, Adrian? > > Please don't drop that flow as it's the most fundamental demonstration > that the Web Payments API can handle "off-Web" cryptocurrency payments. > > BIP70 is also interesting, but for different reasons. > > -- manu > > -- > Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) > Founder/CEO - Digital Bazaar, Inc. > blog: Web Payments: The Architect, the Sage, and the Moral Voice > https://manu.sporny.org/2015/payments-collaboration/ >
Received on Monday, 15 February 2016 19:50:16 UTC