- From: Evan Schwartz <evan@ripple.com>
- Date: Wed, 21 May 2014 10:58:48 -0700
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: Web Payments CG <public-webpayments@w3.org>
- Message-ID: <CAONA2jU9baLs2ZnZEvp02VUodmHLqsVynw7L5z6KWkaE0fCiQQ@mail.gmail.com>
+1 to all of the use cases listed. I'm sorry I haven't been able to be more active in this set of discussions about identity credentials use cases. Was there any talk of a discovery use case? If I want to pay Manu, how do I find which digital entity I should initiate a transaction with? I'd like to find not only what payment methods he accepts but also some evidence that, for example, msporny@digitalbazaar.com is owned by the Manu Sporny I know as opposed to, say, manu.sporny@gmail.com. On Wed, May 21, 2014 at 7:37 AM, Manu Sporny <msporny@digitalbazaar.com>wrote: > On 05/19/2014 01:11 AM, Timothy Holborn wrote: > > Use Case: Execute a transaction without revealing secrets (i.e. > > identity, passwords, PINs) whose primary purpose is orthogonal to the > > actual transaction. > > > > - I'm not sure i understand the Use Case... > > The use case requirement is basically: "Don't ask customers to type in > their credit card numbers, they're unnecessary and insecure." > > The same thing applies to CVV2 numbers on the back of the credit card. > > In other cases, it should be unnecessary for you to transmit your > identity in order to, for example, pay for a pack of gum. The > description for this use case would elaborate on these points. > > > Use Case: Enable anonymous transactions such that the identity of the > > customer is not discoverable by merchants or payment processors. > > > > - I think this means completely anonymous - meaning untraceable? if > > so, -1. > > > > I can see the validity of a use-case that states customer's identity > > is not discoverable by the merchant and/or recipient; however i > > interpret the 'payment processor' to include KYC/AML related > > requirements. If Fiduciary responsibilities are supported (IE: for > > law-enforcement purposes) then +1. > > Ensuring regulatory compliance would be supported. We're not going to do > anything that enables large-scale money laundering. :) > > This use case requirement is effectively: "Enable digital cash". When a > customer would transfer their cash into an anonymous wallet, all the > necessary reporting would still be done w/ the financial crimes > enforcement networks the world over. This is no different than you > taking money out of an ATM and then handing that money to someone in a > personal transaction. > > -- manu > > -- > Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) > Founder/CEO - Digital Bazaar, Inc. > blog: The Marathonic Dawn of Web Payments > http://manu.sporny.org/2014/dawn-of-web-payments/ > > -- Evan Schwartz Developer + Technology Pioneer Ripple Labs Inc.
Received on Wednesday, 21 May 2014 17:59:36 UTC