How Apple Pay works and why it matters for developers
clover-developers.blogspot.com
How Apple Pay works and why it matters for developers
1–10 of 116 posts
Re: How Apple Pay works and why it matters for developers
#2One reason Apple Pay matters for developers and startups is it erodes a key advantage of leaders and incumbents. By dramatically reducing the friction around account creation and payments, Apple Pay makes it much, much easier for consumers to try new services. Ride sharing services, for example, could benefit from this. Of course, it will take a while for the effects to be felt, but increased competition in commerce is a positive long term implication of Apple Pay.
Re: How Apple Pay works and why it matters for developers
#3Pay? What about paying for decent streaming. The keynote was a more like a bum note.
Re: How Apple Pay works and why it matters for developers
#4Apple Pay uses industry-standard EMV contactless protocols over NFC (and MSD contactless for backward compatibility). This makes it compatible with a wide range of contactless payment terminals in deployment today.
So if the last section of the article is correct that means ApplePay will be compatible with Mastercard PayPass terminals? If this is true it would be really easy to roll out ApplePay as for example in Switzerland most terminals are PayPass ready.
Re: How Apple Pay works and why it matters for developers
#5Apple Pay uses industry-standard EMV contactless protocols over NFC (and MSD contactless for backward compatibility). This makes it compatible with a wide range of contactless payment terminals in deployment today. So if the last section of the article is correct that means ApplePay will be compatible with Mastercard PayPass terminals? If this is true it would be really easy to roll out ApplePay as for example in Swi…
Apple Pay is very standards compliant and the networks are very global. So I wouldn't be surprised.
Re: How Apple Pay works and why it matters for developers
#6I can haz reliable streaming of my keynote now?
Re: How Apple Pay works and why it matters for developers
#7> com.apple.WebKit.Networking.xpc wants to sign using key "Apple ID Authentication …" in your keychain. Do you want to allow access to this item?
What is this? I've never seen this before. Loading (and reloading) pages from this domain prompts this popup.
Re: How Apple Pay works and why it matters for developers
#8Apple Pay uses industry-standard EMV contactless protocols over NFC (and MSD contactless for backward compatibility). This makes it compatible with a wide range of contactless payment terminals in deployment today. So if the last section of the article is correct that means ApplePay will be compatible with Mastercard PayPass terminals? If this is true it would be really easy to roll out ApplePay as for example in Swi…
As far as hardware goes, yes - the same antenna you use for talking with a MasterCard can get used for talking to a smartphone.
However, POS software is not at all standardized. You'd likely end up rolling out support for one POS platform at a time. They'll have the hardware you need to support ApplePay, but the rest of the work is probably tricky.
tl;dr POS software systems that accept PayPass can change their software to accept ApplePay.
Re: How Apple Pay works and why it matters for developers
#9How does Apple pay differ from Google's ecosystem and whatever it provides? There, the smartphone app (Google Wallet vs passbook) and the hardware is not made by the same people (Samsung vs Apple) - so does this pose any problems?
Re: How Apple Pay works and why it matters for developers
#10So 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.