Re: [webpayments] Should we be publishing a specification for an HTTP API? (#17)

I'm not opposed to an HTTP API, but I agree with @adrianhopebailie that it's in a distant second place after the JS API.  I think that if we get the JS API right, payment providers will be able to implement a variety of HTTP APIs behind the scenes.  That doesn't mean that defining a standard one isn't useful, though.

Reply to this email directly or view it on GitHub:

Received on Wednesday, 27 January 2016 14:09:01 UTC