Re: Presentation to Web Payments IG

On 10/18/14 3:02 AM, Anders Rundgren wrote:
> On 2014-10-17 23:10, Manu Sporny wrote:
>> We have a presentation[1] to the Web Payments Interest Group at W3C TPAC
>> at 11am on Monday, October 27th 2014. The goal is to introduce the new
>> IG members to the work we've been doing over the past 4+ years in the
>> Web Payments CG. We have 60 minutes allocated, with 20 minutes of
>> presentation and 40 minutes of discussion.
>>
>> Please review the slides and let us know if there is anything that is in
>> there that shouldn't be, or something that should be in there that 
>> isn't.
>>
>> https://web-payments.org/slides/2014/tpac-wpig-wpcg/
>
> It was a nice presentation.  Personally I'm worried that messages like 
> the
> one I got yesterday from a payment specialist will turn out to be true:
>
>  "Apple Pay is very good, both systematically and cryptographically.
>   Additionally, they did their ecosystem homework, signing up MasterCard,
>   Visa and Amex, and the five largest payment processors. I believe that
>   they have in effect created the next generation of payment card.
>   Because of the ecosystem involvement, Apple will be forced to allow
>   this to be implemented by others so that this method becomes 
> ubiquitous.
>   If Apple Pay has any significant adoption in 2015, the method will 
> quickly
>   be spread everywhere. It will be very hard for any architecturally 
> competing
>   schemes to get any adoption. (Several of my friends in the payment 
> business
>   here in XXXXX helped Apple design Apple Pay. There are many years of 
> payment
>   experience embedded in its design.)"
>
> IMO, the W3C must carefully consider the value proposition of any 
> future work
> so that it has a chance of getting traction.
>
> Challenging existing payment networks (and Apple) could be such an option
> but wouldn't that be ignored/voted down by the major platform vendors?
>
> A web interface to Apple Pay could be another venue.  BTW, I think 
> this would
> be trivial since the only thing you need (AFAICT...) is opening an 
> opaque channel
> to the merchant web-server since the actual payment is dealt with in 
> the phone. 

 From my vantage point, this is what's actually going to happen (I've 
watched this movie a zillion times, in the past). Thus, I would expect 
this whole thing to simply be about making this matter open and webby. 
That's it.

Replacement isn't an option. This has to be a standardization pursuit 
that enables broad compatibility etc.

-- 
Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com
Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this