The original card info (i.e. the number stamped on the card) is NOT stored in the iPhone. The "card number" used by the iPhone is a "token" that looks exactly like a card number, but is guaranteed to not be the number of a real card.
So, for example, if you sigh up a Visa card for Apple Pay, your iPhone gets a Device Access Number (DAN) that looks exactly like a standard Visa card number. But Visa knows that it's issued to a device (your iPhone) and not to a card. So if that number is put on a card then Visa will reject it as invalid (that is, no "cloning" is possible).
During the Apple Pay transaction, the number IS passed to the NFC terminal (the DAN, that is, not your actual credit card number, because the iPhone does NOT have that). Visa recognizes this DAN and processes the transaction (it has the mapping of DAN to real card numbers, and sends the real card number to your bank).
As I understand it, your iPhone does not have your actual credit card info at all, encrypted or otherwise.
Yes they will get card-present rates. The key to LoopPay is just that it STRONGLY transmits the same magnetic stripe info that your credit card feeds through the swiper. The reader knows no difference.
The downside is that the actually mag stripe info is now stored with LoopPay AND on your phone. No tokenization.
Would it kill Samsung (or any of the other android vendors) to come up with an original idea for once?
Why are they always trying to play catch-up?
Why not come up with something new?
I think your confused. Have you forgotten that it took apple years to get on board with NFC. Google wallet was around long before apple pay.
look at the whole first page of the thread and the "COPYCATS!" comments.
There's a lot of forgetful confused people.
people who conveniently forget that Google and Samsung both had NFC based payment capabilities for a few years now in some markets.
Apple is late to the NFC / Payment party.
The more adoption of mobile payments - the better for all.
Well done on the Loop Pay execs for successfully convincing Samsung to buy their imminently obsolete tech.
So what's the purpose of the encrypted storage on the iPhone that's specifically for Apple Pay?
The problem is this something that a proliferation of "standards" doesn't help. The more adoption of incompatible mobile payment standards "standards" mean more cruft at the point of sale, more breakdowns, and more customers dumping it all in favor of obsolete-but-works "plastic".
Late perhaps, but as usual they brought the party with them.
It won't be long before ApplePay is the dominant mobile payment solution. It's already gained far more traction than any service before it.
Late perhaps, but as usual they brought the party with them.
It won't be long before ApplePay is the dominant mobile payment solution. It's already gained far more traction than any service before it.
Hey guys, remember CurrentC?
![]()
Late perhaps, but as usual they brought the party with them.
Next up, Samsung buys Coin....
First - Apple didn't come up with mobile payments
Second - why anyone would be against this is silly. The more adoption of mobile payments - the better for all.
It keeps the Device Access Number secure so it can't be cloned onto another device.
Different devices (e.g. an iPhone and an iPad) get individual DANs but I'm sure that hackers would like to clone them. The secure storage prevents that.