W3C home > Mailing lists > Public > public-webpayments@w3.org > November 2015

Re: How would 402 Payment Required work? (was Re: wired - Coinbase Is Out to Build Payments Right Into Browsers)

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Wed, 18 Nov 2015 13:16:36 -0500
Message-ID: <564CC084.9000807@digitalbazaar.com>
To: Adrian Hope-Bailie <adrian@hopebailie.com>, Dave Longley <dlongley@digitalbazaar.com>
CC: Web Payments <public-webpayments@w3.org>, Melvin Carvalho <melvincarvalho@gmail.com>, Anders Rundgren <anders.rundgren.net@gmail.com>
On 11/18/2015 12:22 PM, Adrian Hope-Bailie wrote:
> My point was really that we could avoid another server roundtrip 
> potentially.

This is roughly what's in the spec right now:

http://web-payments.github.io/web-payments-http-api/#processing-a-payment-request

... and it does remove a round-trip, at the expense of wandering into a
REST gray area (resources that change wildly based on if you have access
or not to the resource). That may not be an issue for most people, and
it's certainly cleaner from a programmatic standpoint.

-- 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 Wednesday, 18 November 2015 18:17:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:43 UTC