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

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

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Thu, 5 May 2016 10:49:45 -0400
To: KUNTZ Vincent <Vincent.KUNTZ@swift.com>, Web Payments Working Group <public-payments-wg@w3.org>
Cc: KETELS Kris <Kris.KETELS@swift.com>
Message-ID: <572B5D89.5090205@digitalbazaar.com>
On 05/04/2016 06:12 AM, KUNTZ Vincent wrote:
> On top of the comments already provided by Kris, please find below a
>  couple of additional comments, related to the harmonisation with
> ISO 20022

Hi Kris, Vincent,

Thank you for the detailed input on both the Core Messages and HTTP API
specification.

In general, I agree with a large amount of your input and I think we can
make many of the editorial requests to the documents. As for how we
structure the document, I saw much that I agreed with and we'll either
make those changes or raise them as issues for further discussion if the
specifications are picked up by the group today.

There are a few things in there that had to do w/ naming and the
structure of messages that I think will be a difficult discussion (but
one we should have) with the browser vendors. My personal hope is that
we strive as much as possible for ISO20022 alignment while not making
the messages so foreign to Web developers that it causes confusion in
that ecosystem.

For example, I think making changes like PaymentRequest ->
PaymentInstruction, while logical in the larger payments ecosystem, may
be rejected by the browser vendors because they may feel that the
language might confuse web developers (I'm not saying they're going to
say that, but that is one possible response).

Personally, I'd like to see us move more toward something like a
PaymentInstruction as PaymentRequest doesn't really cover use cases like
refunds and pre-authorizations cleanly.

If the group adopts the work today, I'll go through each of your items
line by line and either make the changes to the spec (if the changes are
largely editorial) or raise them as issues for further discussion (so
all of your input will be considered and responded to).

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
JSON-LD Best Practice: Context Caching
https://manu.sporny.org/2016/json-ld-context-caching/
Received on Thursday, 5 May 2016 14:50:15 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 May 2016 14:50:16 UTC