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

Re: comments on web payment HTTP API and core message components

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 19 Jun 2016 21:16:18 -0400
To: public-payments-wg@w3.org
Message-ID: <576743E2.6040107@digitalbazaar.com>
Hi Vincent,

Response to your questions around the HTTP API below...

On 05/04/2016 06:12 AM, KUNTZ Vincent wrote:
> -          *Web Payment HTTP API:*
> o   On top of Krisí comments, I have also some doubts about the 
> consistency of the naming conventions,  but I have one specific 
> question: how does this integrate with the work performed already in 
> the flow task force.

I've gone through the flows and tried to ensure that the HTTP API can
(in theory) perform the things in many of the flows.

Some of the target flows /assume/ the Browser API, which is unfortunate.
For example PSP Mediated SEPA Credit Transfer assumes
PaymentRequest.show() - which doesn't exist in the HTTP API:


Other flows assume that there is a human in the loop. Again, unfortunate.

The HTTP API is largely focused on automated payments (regular payments
with variable price - loan payments, easily automatable payments - rent
payments, B2B payments, etc.). We don't have many (any?) flows for those
sorts of things.

> o   One very positive aspect brought up by this document is the fact
>  that the scope is not limited to cards transactions, but allows to 
> the extension of any payment instrument, including credit transfer, 
> but possibly also future payments instruments that could pop-up in 
> the future.

That aspect of the specification has been removed. It seems like the
group isn't focused on the future but largely focused on the present
customer shopping cart experience. I'd like to be focused on the latter
(as well as the former), but I'm not seeing a great deal of enthusiasm
and participation to make the future-looking use cases happen. :(

If you have any ideas on how we could change this, I'd be very
interested to hear them. :)

-- manu

Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
JSON-LD Best Practice: Context Caching
Received on Monday, 20 June 2016 01:16:48 UTC

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