- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Sun, 27 Sep 2015 07:42:59 +0200
- To: Web Payments CG <public-webpayments@w3.org>
Maybe of interest. End-2-End-Secured in this case means that a by the user counter-signed and encrypted "paymentRequest" traverses [in a verifiable way] unmodified and [remains] confidential through a multitude of hops on its journey from the Wallet to the Bank. Other messages are also end-2-end-secured but these only simple request-response pairs. http://webpki.org/papers/payments/webpay-account-2-account-direct-debit-statediagram.pdf http://webpki.org/papers/payments/webpay-account-2-account-direct-debit-messages.html BTW, this particular scheme does exactly what some people have expressed concerns about. Marginalization of "Processors": https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Sep/0121.html AFAICT, "Processors" are strictly only needed when there is a mediating TTP involved in the actual payment scheme. Anders
Received on Sunday, 27 September 2015 05:43:33 UTC