W3C home > Mailing lists > Public > public-webpayments@w3.org > June 2014

Re: The Payment Identity Problem

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Thu, 26 Jun 2014 23:30:04 -0400
Message-ID: <53ACE53C.4030506@digitalbazaar.com>
To: Web Payments CG <public-webpayments@w3.org>
On 06/26/2014 04:40 PM, Adrian Hope-Bailie wrote:
> I agree 100% that identity is a major issue and needs to be solved.

Yay.

> As I dig into the Identity Credentials stuff I can see how this may
> be a great approach.

We've yet to see if it will gain adoption, but at least it's there as a
counter-point to the other identity solutions out there.

> My issue is this:
> 
> We have agreed that we want to put together a standard that uses
> push payments ( I think this is what we agreed?). I define push
> payments to mean: 1. The payer initiates the payment via their
> provider of choice (using a mobile, internet, whatever channel that
> they trust between them and the provider). 2. The provider processes
> a payment to the payee. 3. The payee gets some form of notification
> that they have been paid and they trust this.

So far, so good.

> Other steps like invoicing, exchanging identity credentials, 
> selecting/negotiating terms are not essential.

I agree that they're not essential for moving money from the payer to
the payee. We're shooting for a good UX as well, though. A commercial
purchase w/o the choice of receipt or where the result is a receipt that
provides the same experience as the receipts we are given today is not
very compelling (and will likely fail).

I don't know if we really need to discuss this stuff further, though. We
(Digital Bazaar) will implement the optional parts that you identify
because we don't believe that our products will be compelling without them.

> I will bet that 99.99999% of the people involved in the projects, 
> start-ups or initiatives you have linked to are trying to solve one
> of the following problems: 1. KYC - A payment provider getting proof
> of identity credentials for a new customer when they sign them up 2.
> Protecting identity (and payment) data of a payer when it is passed 
> via the payee and the rest of the payments ecosystem onto their
> provider (card issuer). i.e. Most payments today. 3. Generic identity
> exchange and protection issues which are important for things like
> eGovernment, privacy etc

There are two more which are 4) single sign-on for the Web, and 5)
solving the NASCAR payments problem. A simple specification that can be
implemented in a matter of days solves all five of these issues in one go.

That said, no need for us to try and convince each other of the need (or
lack thereof) for this part of the technology stack. As long as there is
an extension point that provides it, we will implement it because we see
it as a competitive advantage.

-- 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/
Received on Friday, 27 June 2014 03:30:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:32 UTC