- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Tue, 02 Jun 2015 15:14:49 +0200
- To: Adrian Hope-Bailie <adrian@hopebailie.com>
- CC: Web Payments IG <public-webpayments-ig@w3.org>
On 2015-06-02 15:00, Adrian Hope-Bailie wrote: > Hi Anders, Hi Adrian, > > Can you point out which use cases you believe need to be updated? Well, the use-cases are not very explicit in how things like authorization is achieved but there are a few concrete examples. 3.4 Delivery of Product/Receipt and Refunds ...encrypted line-item receipt 7.2 Tokenized Payments (ApplePay / Venmo / CyberSource) The mobile app creates an encrypted transaction Both of these examples are BTW somewhat strange, signed data looks like a more useful concept for transactions and receipts. Anders > > Adrian > > On 2 June 2015 at 08:32, Anders Rundgren <anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>> wrote: > > I believe use-cases dealing with Encryption and Signatures should specify which entities > are anticipated to be signing/encrypting and verifying/decrypting respectively, since this > has major implications on the key management architecture and enrollment. > > Anders > >
Received on Tuesday, 2 June 2015 13:15:24 UTC