Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apple Pay

apple.com

Post reply on HN
Print view View original

171–180 of 225 posts

Re: Apple Pay

#171

Post by bluedino »

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.

Millions and millions of people did.

Re: Apple Pay

#172

Post by AaronIG »

RayLau135 wrote: post #145
jfb wrote: post #141

Earlier quoted context omitted.

Also on the watch.

iPhone 5 and 5s will be pair-able with Apple Watch, so I would assume they will have access to Apple Pay too

According to the Apple Pay site, that'll be the case for in-store purchases.

Re: Apple Pay

#173

Post by pacofvf »

mitchty wrote: post #60
pacofvf wrote: post #23

Earlier quoted context omitted.

if by similar you mean actually the same, yes they are similar

How? Google wallet basically dumps magstripe out of nfc. This doesn't do anything close to that. Can you explain how they are the same?

From the user POV, it's the same:

1. upload your Credit/Debit card info to an app(passport/wallet)

2. your phone must have NFC.

3. pay with your phone at a NFC capable terminal.

Re: Apple Pay

#174

Post by makomk »

craigching wrote: post #69
Thrymr wrote: post #61

Earlier quoted context omitted.

Sadly, US banks seem to be going with chip-and-signature rather than chip-and-PIN. It's not easy to find one that will issue chip-and-PIN.

Will a chip and sig work in Europe? That's probably my biggest issue is traveling and not having a chip.

It ought to, since some European customers have chip-and-signature cards for various reasons. There's no guarantee that shop employees will be properly trained on how to handle it though.

Re: Apple Pay

#175

Post by thrownaway2424 »

praxulus wrote: post #77
thrownaway2424 wrote: post #51

Earlier quoted context omitted.

No. Google Wallet simply blurts the magstripe information into the reader over NFC. It has no security features to speak of.

It doesn't use your card's number, it creates a virtual card and gives that number to the payment terminal. https://support.google.com/wallet/answer/2676665?rd=1

Yes and who cares? It still is not secure. Anyone who gains the virtual card number can use it and the merchant system can charge arbitrary amounts of money to it.

A payment system that wasn't cooked up by weirdos would include actual security features such as your phone's display shows the amount of the transaction and you enter pin or password or other knowledge and your phone signs the transaction. That would be nonrepudiable and you could clear such transactions at negligible cost because there's little risk.

Square, which isn't exactly winning out there, at least does include a modest security feature of displaying the picture of the authorized card user on the terminal.

Re: Apple Pay

#176

Post by thrownaway2424 »

iancarroll wrote: post #146
k-mcgrady wrote: post #96

Earlier quoted context omitted.

They use the same tech to communicate (NFC) but Apple's security features seem unique.

For what it's worth, Google Wallet never actually discloses your card. It uses a virtual MasterCard to complete the transaction.

The proxy card number doesn't change so why is this considered a feature? It discloses something which is as good as your backing real card number.

Re: Apple Pay

#177

Post by MCRed »

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?

If I recall correctly, wasn't the iOS7 update a shit show?

No, you don't recall correctly. iOS has had the ability to update via iTunes since it's very first release in 2007. iOS users have been able to update their devices regularly to the latest and the greatest without problems for many years, while on Android it's the exception rather than the rule.

This includes iOS 7, which like previous and later releases works across a variety of new and older devices.

The only thing controversial about iOS 7 was the UI was "flatter" and more colorful which some people didm't like.

Re: Apple Pay

#178

Post by thrownaway2424 »

itry wrote: post #117
eloisant wrote: post #113

Earlier quoted context omitted.

I still don't see how replacing a credit card (that can be used for contactless payment with Visa Paywave or Mastercard contactless) by a phone that may have a dead battery brings anything to the table. Really, what's the point?

1) One thing less to carry around 2) The credit card gives away data that can be used for fraud. Your phone does not have to do that.

#1 only makes sense if you ignored the word battery in the question. A phone makes a dreadful credit card. It's huge, it runs out of power, and it throws stack traces at the wrong moment.

Re: Apple Pay

#179

Post by DCKing »

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.

At first I was inclined to have the same reaction to this news, especially concerning early rumours about this. Having read some more on it however, I now realize that it is somewhat of a knee-jerk reaction.

From what I read, Apple Pay is the following things:

- A management interface to manage payment methods on your device.

- A user interface to interact with these payment methods.

- A set of APIs to interact with these payment methods from software.

- A term for hardware and software components in the iPhone that allow interaction of these payment methods with point of sale hardware.

What Apple Pay is not:

- A payment protocol.

So Apple Pay is a payment method management application. It is not a payment protocol. The payment protocol Apple Pay uses to interface with point of sale terminals is the same EMV protocol that is used for other solutions.

Any other payment method application can also use this same EMV protocol. Many do already in fact, such as Google Wallet. I would not be surprised if Wallet was able to interface with the shown POS hardware with barely any modification to the app.

I hope anyone with more knowledge of this project could confirm this interpretation is correct.

Re: Apple Pay

#180

Post by iancarroll »

thrownaway2424 wrote: post #176
iancarroll wrote: post #146

Earlier quoted context omitted.

For what it's worth, Google Wallet never actually discloses your card. It uses a virtual MasterCard to complete the transaction.

The proxy card number doesn't change so why is this considered a feature? It discloses something which is as good as your backing real card number.

Because it will only accept one charge and only be re-enabled when needed?
Post reply on HN