W3C home > Mailing lists > Public > public-payments-wg@w3.org > January 2016

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

From: bifurcation <notifications@github.com>
Date: Wed, 27 Jan 2016 06:08:19 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/17/175648282@github.com>
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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:13 UTC