Apple Pay • Hacker News Board

itry wrote: post #108

tfinniga wrote: post #101

Earlier quoted context omitted.

You might not remember this, but that's exactly what originally happened. You had CompuServe mail, and Prodigy mail, and AOL mail, and any number of internal mail systems at different companies. There was not a single mail format or agreed upon address space. Getting mail from one system to another was a huge pain.

Interesting. In fact, I do not remember that. I started using the internet some time in the 90s. I never used Compuserve nor AOL. I never heard about Prodigy.

I guess technically those were separate online services. They only connected up to the internet near the end of their lifetime.

Re: Apple Pay

#127

Post by tfinniga » Tue, Sep 09, 2014, 9:19 PM UTC

BlakePetersen wrote: post #106

ctz wrote: post #91

Earlier quoted context omitted.

The payments protocol is called EMV. The wireless transport protocol is ISO14443. Then we have different branding of the combination of EMV+ISO14443 for different card issuing networks (Mastercard PayPass, Visa payWave, etc.) Apple Pay and Google Wallet are further branding of the pair of standards. A possible reason Apple might succeed where Google Wallet failed: Apple have a better track record of telling MNOs to f…

Google doesn't cause bloatware, Carriers and Handset makers do. One of the many consequences of OSS, people can fork and bloat to their heart's content. Also, I haven't had one issue with software updates on my Nexus 5 (which indeed comes bloatware free). If I recall correctly, wasn't the iOS7 update a shit show?

Google doesn't write the bloatware, but its actions allow bloatware to exist on android in a few ways, as far as I understand.

- Android has an open source version (that is, a version that is completely open source). Like you mentioned, this gives carriers and OEMs the freedom to do what they want, even fork and bloat.

- Android has a mixed license version, where you get the full experience of the Google Play store, Gmail, and so forth. Google has a lot more control over who it allows to use this version, since many of the components are not free software.

Re: Apple Pay

#128

Post by PanMan » Tue, Sep 09, 2014, 9:22 PM UTC

arfrank wrote: post #112

jobu wrote: post #52

Earlier quoted context omitted.

Does Apple charge anything for the transaction?

Looks like Apple's commission is ~15-25 BPS for participating banks (from those banks): "The biggest “surprise” over last 2 months is that Apple has squeezed 15-25bps from the 5-6 participating banks at launch (C, BAC, COF, JPM, Amex and perhaps WFC)." http://blog.starpointllp.com/blog/?p=3855

BPS?

Re: Apple Pay

#129

Post by jfb » Tue, Sep 09, 2014, 9:23 PM UTC

tfinniga wrote: post #101

itry wrote: post #41

So we want to make payments via our phones. My first thought would be to create a protocol for this. Instead we get ApplePay and GoogleWallet and whatnot. If the internet was invented today, we would have AppleMail instead of email and GoogleTrans instead of http.

You might not remember this, but that's exactly what originally happened. You had CompuServe mail, and Prodigy mail, and AOL mail, and any number of internal mail systems at different companies. There was not a single mail format or agreed upon address space. Getting mail from one system to another was a huge pain.

There's a reason that sendmail exists, and that the sendmail book was so gigantic. Because it was terrible software, yes, but also because it was routing mail across a variety of different systems with different addressing rules and what have you.

RFC 822 didn't just come into existence one day.

Re: Apple Pay

#130

Post by PanMan » Tue, Sep 09, 2014, 9:24 PM UTC

wmeredith wrote: post #73

jobu wrote: post #52

Earlier quoted context omitted.

Does Apple charge anything for the transaction?

I'm REALLY curious about this. Will they charge a transaction fee and have it as another revenue stream for them (like iTunes/App store)? Or is it going to be another commoditization of their competitor's/partners products in order to move more hardware (like iMessage). If it's the latter that would be a HUGE deal. I just can't imagine they would be able to resist taking a slice of that $12 billion/day transaction pi…

For the online version they seem to work with stripe et.al. And not charge anything.