It's clear that you're having a hard time seeing it, but many of us do see how Apple's system is more secure.
Moreover, the banks can see it, too. The fingerprint scan (severed fingers excepted) will be accepted as authentication and fingerprints harder to forge than a signature (and harder to capture than a PIN) there likely won't be an arbitrary cap on transactions. As far as I know, no cap has been announced. For very large purchases, or when you buy alcohol, tobacco, marijuana, or other controlled substances, vendors may still ask to see photo ID.
Flipping hell. Enclosed OS.![]()
I think the point hes making is that once someone has your password, (which lets face it they can even get remotely if theyre good enough), you can change it. Once they get your fingerprint however ...
Then they need to hurry up and actually have Apple Pay in my country if they are not letting third parties on board.![]()
I think the banks have a hand in the secure enclave and the tokenisation system as well. At least in the requirements, what an iPhone with secure enclave can do and what it can't do. And the requirements are the hard thing.
Of course the issuing bank has your credit/debit card info. They are either loaning the money to you to make a credit card transaction, or they hold the money you are using to make a debit card transaction. And if you usepay to make the transaction, it's going to show up on your account statement. Where else do you think the money comes from: trees?
But, Apple doesn't handle the transaction. IT GOES THROUGH EXISTING PAYMENT NETWORKS. Sorry for the shouting, but if you don't comprehend anything else, hopefully you'll get this.
The one part that I'm still unclear on: how does the Device Account Number (it's called an "alias" in Apple's patent) get associated with your credit card number? During the keynote, Apple said you could enter it into your Passbook by simply snapping a picture. But, how does the issuing bank learn about the association?
Does the Passbook app send it to Apple, who then sends it to the bank? Or does the Passbook app communicate directly with the bank's servers? If I were the bank, I'd insist on the latter. Passbook would have to know which bank to contact , but that's an an easy mapping of a few numbers to a URL (it's encoded in the first digits of the credit card number).
Several years ago, I was issued a credit card (Citi Mastercard) that had some chip inside that allowed me to wave it at a terminal to pay. Was this an NFC chip? I'm guessing no, and that it was more similar to my bus transit card that uses RFID, requiring low (or no) power to operate.
Assuming they are different technologies -- I have paid with one of these cards at McDonald's before. How do we differentiate a module that accepts these old cards, versus NFC? So I don't look like an idiot waving my phone at an incompatible module.![]()
Honestly, it's okay if you go to Android land. I don't have a camera that needs NFC, so your problem doesn't affect me, but I don't deny you have an issue, and it's up to you to decide whether your issues with Apple are important enough to you to cause you to change phones.I want NFC to be able to start my iPhone talking to my Sony α7 camera. The α7 uses NFC to switch a smartphone over to the camera's WiFi. Otherwise you have to dive into the phone's settings, switch it over manually, and then get on with the business of transferring photos, remotely controlling the camera, etc. NFC makes this easy. On the iPhone, it's currently a real pain. This means Android phones, tablets, etc. with NFC are much easier to use with the α7 than iPhones, iPads, etc.
If Apple makes many more boneheaded decisions like this, I may be off to Android land.
Of course the issuing bank has your credit/debit card info. They are either loaning the money to you to make a credit card transaction, or they hold the money you are using to make a debit card transaction. And if you usepay to make the transaction, it's going to show up on your account statement. Where else do you think the money comes from: trees?
But, Apple doesn't handle the transaction. IT GOES THROUGH EXISTING PAYMENT NETWORKS. Sorry for the shouting, but if you don't comprehend anything else, hopefully you'll get this.
The one part that I'm still unclear on: how does the Device Account Number (it's called an "alias" in Apple's patent) get associated with your credit card number? During the keynote, Apple said you could enter it into your Passbook by simply snapping a picture. But, how does the issuing bank learn about the association?
Does the Passbook app send it to Apple, who then sends it to the bank? Or does the Passbook app communicate directly with the bank's servers? If I were the bank, I'd insist on the latter. Passbook would have to know which bank to contact , but that's an an easy mapping of a few numbers to a URL (it's encoded in the first digits of the credit card number).
NFC and RFID are very similar, to a point. RFID is read-only. NFC is two-way.
http://electronics.howstuffworks.com/difference-between-rfid-and-nfc.htm
If a point-of-sale terminal has the NFC symbol (it looks like the WiFi signal indicator on the iPhone, turned sideways), either your Mastercard or your iPhone should work. To the PoS terminal, both look the same.
the transaction can easily be made 100% safe... Apple could based on your hardware create a new key every time you try to access it...
the point Apple is trying to make here is your cc-number is never shown in the transfer, which is good of course... but in the end your cc will handle the communication to your bank (unless Apple starts their own credit/debit-handeling... in that case Apple would need your account-info)
you see you still pay with your VISA, only Apple will guarantee no fraud (as long as you use ApplePay)...
this way VISA (maybe) will pay a smaller fee to the makers of the terminal and Apple will get a small fee (a safe transfer)![]()
I've researched this by looking very carefully at apple's patent. Apple has a patent on the overall system - the relationship between the user, the provider (Apple) and the bank. The key to the privacy is not just that there is a token, but how it's handled and encrypted so that Apple and the merchant have no way of knowing anything about it or the user. That's what apple invented.
According to Apple's patent, a transaction counter is indeed included in the transaction security code. So, it is effectively a new key for every transaction.
Do you have a reading comprehension problem? I've already explained -- repeatedly -- that Apple isn't handling transactions between merchants and the issuing bank.
The financial terms of Apple's agreement WITH THE ISSUING BANKS, not the merchants, or the payment processors has already been disclosed: 15 cents per $100, on every transaction. The bank is giving up a small portion of their percentage in exchange for the additional protection from fraud.
I've researched this by looking very carefully at apple's patent. Apple has a patent on the overall system - the relationship between the user, the provider (Apple) and the bank. The key to the privacy is not just that there is a token, but how it's handled and encrypted so that Apple and the merchant have no way of knowing anything about it or the user. That's what apple invented.
Are you thinking that way because of all the stories youve read about security problems with NFC on android? Because I've not seen one report of security problems with NFC on android.
Stop trying to make it sound like Apple is doing something good by restricting NFC use on iphones. Apple is doing this so they have something to sell for iPhone 6S.
if you are buying something with ApplePay... what information have you given to Apple?!? your bankaccount or your credit/debit-card?!?
now try and tell me how your bank can see any transaction?!? the transaction is via VISA/MasterCard/AmEx or whatever... how would Apple bypass their fees?!?
This is fairly standard for Apple. Introduce a new feature/API release it only for Apple app use then after a while allow dev access to the API. This way they can make it exclusive to them while its all new and shiny, test it, write the developer API kit and then release it when its ready for general consumption.
Sorry for the duplicate reply, but I wanted to be sure you saw this patent application:
http://www.freepatentsonline.com/y2014/0019367.html
METHOD TO SEND PAYMENT DATA THROUGH VARIOUS AIR INTERFACES WITHOUT COMPROMISING USER DATA
It has a lot of interesting details about the actual transaction. I was hoping you might be interested.![]()
ApplePay is a nice idea and will surely bring changes. But I think it will fail outside US if the merchants have to set-up an infrastructure dedicated to ApplePay. If they can accept mobile payments from Android and IOS with the same terminal, then it might work.