Live data from Hacker News

How Apple Pay works and why it matters for developers

clover-developers.blogspot.com

11–20 of 116 posts

Re: How Apple Pay works and why it matters for developers

#11
post #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? http://imgur.com/n3Ay8Ik What is this? I've never seen this before. Loading (and reloading) pages from this domain prompts this popup.

That would be SSL Client Certificates!

Re: How Apple Pay works and why it matters for developers

#12

How 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?

Apple Pay gets a token from your card issuer and uses that to pay. Google Wallet pays with their own card and charges your card the same amount. Only difference I see is that Google knows about every transaction you make. Apple doesn't.

Re: How Apple Pay works and why it matters for developers

#13
post #4

Apple 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 softw…

That sounds different than Google Wallet. With an NFC Android phone you can pay at any PayPass terminal, without them needing to change their software.

Re: How Apple Pay works and why it matters for developers

#14

Earlier quoted context omitted.

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 softw…

That sounds different than Google Wallet. With an NFC Android phone you can pay at any PayPass terminal, without them needing to change their software.

I will admit that I might be completely wrong about the technical requirements for this. I'm sure that at least the hardware will support it, and from what I understand there may be a difference in how the terminal goes from talking with a payment method to a verified payment.

Re: How Apple Pay works and why it matters for developers

#15
post #2

One 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…

It really doesn't do this. Apple Pay is not the solution to moving money between parties who aren't registered merchants, with the relevant banking setup.

Anyone can be become a merchant with a PayPass reader today. Apple Pay is not changing that, nor can it since that sector is entirely dependent on local commerce/finance laws and payment processor anti-fraud costs.

Re: How Apple Pay works and why it matters for developers

#16
post #15
post #2

One 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…

It really doesn't do this. Apple Pay is not the solution to moving money between parties who aren't registered merchants, with the relevant banking setup. Anyone can be become a merchant with a PayPass reader today. Apple Pay is not changing that, nor can it since that sector is entirely dependent on local commerce/finance laws and payment processor anti-fraud costs.

Apple Pay is focused on easing consumer pain and friction, leading to more competition among service providers and retailers since trying new services will become easier for users.

Re: How Apple Pay works and why it matters for developers

#18
post #4

Apple 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.

This is also great for us Android/GWallet/Isis/Softcard users, as more merchants will want EMV and have it implemented.

Re: How Apple Pay works and why it matters for developers

#19
post #15
post #2

One 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…

It really doesn't do this. Apple Pay is not the solution to moving money between parties who aren't registered merchants, with the relevant banking setup. Anyone can be become a merchant with a PayPass reader today. Apple Pay is not changing that, nor can it since that sector is entirely dependent on local commerce/finance laws and payment processor anti-fraud costs.

Apple Pay makes developers able to pay merchants on behalf of their customers without becoming a credit card processing middleman.

Re: How Apple Pay works and why it matters for developers

#20

Earlier quoted context omitted.

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 softw…

That sounds different than Google Wallet. With an NFC Android phone you can pay at any PayPass terminal, without them needing to change their software.

Another interesting question: If a vendor adds support specifically so that they can accept Apple Pay, will my Android phone start working for NFC payments there?
Post reply on HN