or Connect
New Posts  All Forums:

Posts by plovell

The merchant gets some data from the transaction, but certainly not your credit card account number.  I would guess that, in your example of a return to Home Depot, you would still have your paper receipt that they can scan the way they do today. Or maybe with Apple Pay you would get a receipt on your phone that could be used  to bring up HD's transaction record. The issue of what number/token is used is an internal issue with Visa/MasterCard. Whatever it is, it links back...
I'm not sure of your question. It will compile source to either x86 or to ARM. But it won't convert, for example, x86 binary to ARM binary. Is that what you meant? But that's what Rosetta2 would be for :)
Xcode is easy. It already does both x86 and ARM. But getting major apps recompiled is insufficient. Just with the PPC -> x86 transition, this would need Rosetta. That was built by Transitive and licensed by Apple, but the company was acquired and the new owners did not want to renew the license. It's interesting that the new owner just happens to be IBM. With whom Apple recently made a deal. Very interesting indeed.
The terminal upgrade is ALREADY required, and under way. The driving force behind it is the switch to chip cards. After October 2015, any merchant still using swipe cards will be liable for fraud loss - not the bank. And these terminals will include NFC (many trade articles already confirm this). That does NOT mean that you will be able to use ApplePay at all of them - that requires agreements, and software in the merchant system. But the terminals will be capable of...
There's a difference between chip+PIN and paywave, and that is that paywave isn't authenticated (i.e. no PIN). So the transaction limit is lower. The advantage of chip cards is that the information on the chip can't be copied, as happens a lot with today's mag-stripe cards. And the paywave implementation in the U.S. is such that the card info can actually be read at a distance of about 3 feet (1 m.) with a sensitive antenna. That info can then go onto a mag stripe card and...
The current NFC usage is PIN-less and therefore has low limits. As far as we know, ApplePay is ALWAYS authenticated so I do not expect that the "pay wave" limits will be in effect. I can't believe that Apple would ever agree to such a limitation given the security in ApplePay.
We don't know yet but if the terminals have NFC hardware then it should be easy. It would just require software changes to the merchant and bank systems. If those terminals do not support NFC then that would be a problem. But what I hear from friends outside the U.S. is that NFC is common. However, I expect that Apple will take a while to roll this out to other countries. One reason is because there are agreements that must be negotiated. A second reason is to give the...
I've seen reports (Bank Innovations, for one) that said that Apple would pick up some of the fraud liability. Not all, but some, as part of the deal. Of course, the banks are ultimately on the hook for fraud. But the deal might include some contribution from Apple (hold back part of the fee). But we don't know - either way could be right.
This is the problem of the record labels. They control the copyrights, country by country. This is part of the reason EU has pushed for EU-wide licensing but it hasn't happened yet.
Apple gets a portion of the fee and, in return, accepts some of the liability for fraud.   Because the security is good, fraud should be quite low. Hopefully zero.    But what this does is create a competitive weapon against Samsung which so far doesn't have a decent fingerprint reader of secure enclave. If Samsung wants to copy this then they will have to do a much better job than they've done so far. Even then it will take time. Or Samsung could copy the deal Apple...
New Posts  All Forums: