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

Suggestions on API change

From: Anton Tveretin <tveretinas@yandex.ru>
Date: Wed, 4 May 2016 10:09:57 -0500
Message-Id: <7757711462357253@web18j.yandex.ru>
To: "public-payments-wg@w3.org" <public-payments-wg@w3.org>
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.

Received on Wednesday, 4 May 2016 15:10:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 4 May 2016 15:10:01 UTC