Re: [webpayments] Is there an HTTP API based message flow? (#17)

I may have been mistaken, but I heard that an HTTP API is "not in scope" during our last call. I vaguely remember @adrianhopebailie saying that personally he feels that it's really important, but our charter doesn't call it out as a deliverable. Looks like we have preliminary consensus to propose an HTTP API as a WG deliverable (citing that a browser-only API wouldn't meet our broader 'user agent' API requirement).

@adrianhopebailie @mountainhippo can we get this on the agenda for the next call and do a straw poll to see if we have approval to create and publish an HTTP API as a FPWD in March?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/17#issuecomment-164992668