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

Re: Apple Pay

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Sun, 21 Sep 2014 14:57:13 -0400
Message-ID: <541F1F89.7070800@openlinksw.com>
To: public-webpayments@w3.org
On 9/20/14 9:44 PM, Manu Sporny wrote:
> On 09/18/2014 09:59 AM, Kingsley Idehen wrote:
>> Your response is a little confusing here. Remember the view point
>> you held re. Nigeria+Mastercard obliteration of privacy for all
>> Nigerian citizens.
> It might be confusing because we're miscommunicating. :)
> What exactly is confusing about my response?

What I gleaned from your comments on both subjects:

MasterCard+Nigerian and an anti-pattern Nigerians (initially) and others 
will have to live with.

Apple Pay is an unacceptable anti-pattern, on the assumption that its a 
closed system.
>> Look, Apple is using their clout to make a better ecosystem for
>> handling payments. I don't see how anything produced on the standards
>> front would be contrary to Apple's long-term goals in regards to
>> payments. Note, they always leverage industry standards in their
>> solutions, in many cases better than all of their competitors.
> Apple leverages industry standards in a way that wraps a proprietary
> layer or silo around them.

No, during the Job's era, they would simply drag their feet in regards 
to open APIs into their ecosystem. In Apple Pay, you are seeing the 
start of the post Job's era where open APIs are an immediate part of the 
deal. Just watch this space :-)

>   Again, good on Apple - it's led to them being
> a well respected technology company. That approach, however, is not our
> approach - we're not trying to create a silo.

And herein lies my disagreement with you, as echoed in my initial 
response and at the top of this post, you are jumping to an inaccurate 
conclusion about what Apple is doing. Basically, you are making a 
presumption about silo-fication :-)

>   Apple /may/ create a silo
> around the Web Payments stuff, and that's fine, but I'd imagine it would
> be in a larger non-silo'ed Web Payments ecosystem.

See my comments above.

>> Lesson #1 will be that Apple Pay isn't a closed system.
> Then PayPal, Square, and Stripe can integrate with Apple Pay w/o the
> blessing of Apple?

What makes them the yardstick? Not that they will be locked out since 
Apple Pay is actually a packaged solution based on EMV.

> What's your definition of "closed system"?
>> Ultimately, Bitcoins will rule, that's where the expanse of the Web
>> will ultimately kick-in and totally inflect everything :-)
> Ultimately, a set of standards will come along that tie in Apple Pay,
> Google Wallet, Square, and Bitcoin together in a way that brings about a
> much better experience wrt. exchanging value via the Web. That's what
> we're trying to do here w/ the Web Payments work.

EMV deals with the issue re., Apple Pay and wireless (NFC) based payment 
processing. The problem Apple Pay is gunning here is the "old bulging 
wallet" and solving that requires use of open standards (EMV, NFC).

[2] https://news.ycombinator.com/item?id=8292148
[5] http://dbpedia.org/describe/?url=http://dbpedia.org/resource/EMV

> -- manu


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

Received on Sunday, 21 September 2014 18:57:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:39 UTC