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

Re: [Suggestions on API change

From: Ian Jacobs <ij@w3.org>
Date: Wed, 4 May 2016 10:45:30 -0500
Cc: "public-payments-wg@w3.org" <public-payments-wg@w3.org>
Message-Id: <F954C170-D0DA-444A-B7A7-041C8CD25CA1@w3.org>
To: Anton Tveretin <tveretinas@yandex.ru>

> On May 4, 2016, at 8:37 AM, Anton Tveretin <tveretinas@yandex.ru> wrote:
> 
> Hello,
> Maybe this have been written several times already...
> Using a bank card for a Web payment is inherently insecure and quickly becoming obsolete. The fastest way - as I posted to mathplus.borda.ru - is a payment order, especially if generated automatically. However:
> 1. A format for a bill is needed. My proposed "CoABoS" is in progress (not prepared, nor published). A bill could be downloaded from merchant's site, received by e-mail, or generated locally. In this case, no special "payment" API is needed; file transfer and generation (DOM-like) APIs work.
> 2. An API for banking (financial) software (including web sites and web apps) to pick an outstanding bill is needed. I assume that bill is handled (e.g. converted into a payment order) by banking software.
> Let me tell here about specs I publish.

Hello Anton,

The Web Payments Working Group Charter [1] does mention work on a “web payment request” which
may correspond to your notion of a “payment order.”

Ian


[1] https://www.w3.org/Payments/WG/charter-201510.html
--
Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
Tel:                       +1 718 260 9447




Received on Wednesday, 4 May 2016 15:47:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 4 May 2016 15:47:38 UTC