- From: Adrian Hope-Bailie <adrian@hopebailie.com>
- Date: Tue, 5 Jul 2016 23:13:59 +0100
- To: Adam Roach <abr@mozilla.com>
- Cc: Web Payments Working Group <public-payments-wg@w3.org>
Received on Tuesday, 5 July 2016 22:14:29 UTC
Hey Adam, I like it and think it's useful to frame how this MAY work when talking about the generic case of web-based payment apps. Happy to discuss briefly this week. Adrian On 5 July 2016 at 22:54, Adam Roach <abr@mozilla.com> wrote: > Ahead of seeing some of you face-to-face this week, I wanted to send out > some thoughts about how native payment apps can be incorporated into our > existing work by leveraging work already underway in the web browser space. > To be clear, I'm not expecting to discuss this during our formally > scheduled meetings, but would love informal feedback either via email or > after hours. > > > https://docs.google.com/document/d/1eljnrb4pT9ggRi7E_1T_jjv2CDt0i4sIxrrGfWgibvI/edit?usp=sharing > At this point, I'm not sure this even needs any particular specification, > as it functionally describes how to use existing technologies to bridge > from the work we're currently engaging in to native applications. However, > keeping this approach in mind as we move forward with the payment app spec > -- to ensure we don't cut off this otherwise straightforward avenue as we > develop that API -- would probably be quite helpful. > > -- > Adam Roach > Principal Platform Engineer > Office of the CTO >
Received on Tuesday, 5 July 2016 22:14:29 UTC