Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The EMV reader probably isn't enabled at all, just like at Target and Best Buy.

If you've been following along, I was responding to a post that was responding to my post saying that I was required to use the EMV reader at WalMart. First place I've been required to do so.
 
Stereotyping, much? An Apple product customer could be a single mother with a contract iPhone, who is broke. Where DO people get these fantasy ideas from... ?

Only years of hardcore marketing research??? :eek:

iOS devices in general are used to spend a lot more money on apps and online purchases, both in total and per transaction than any other mobile OS or mobile device. It is not a stretch to assume that this is also true for this demographic in physical location situations as well.

There are many, many marketing reports, research studies, and analyst notes that show these statistics, so while your broke single mother with 10 kids and less dollars in her bank account almost certainly exists, that person is an outlier in terms of the "average" iOS user.

That's not fantasy, that is statistics...
 
Yes that is right, let us not forget that Walmart sells a lot of iPhones and all the US carriers are offering huge deals to downright free iphones with trade in and contracts. Sorry to burst your lame attempt to make yourself feel better other people.

Lighten up Francis, I was just injecting a little humor! :)

Bryan
 
The two stores I shop the most. :(

I guess I need to find retailers who will be using Apple pay...

Or you could just...pay with cash or a card like you've been doing? Apple Pay is cool and all but if I have a favorite store that doesn't support it, I'm not gonna just randomly stop shopping there lol
 
NFC is NFC. It's all the same. No matter if you're using Apple Pay or Google Wallet. It's the same thing.

Stop looking. If a retailer has NFC already set up in their POS, they can accept Apple Pay. Just as they have been accepting Google Wallet and Soft Card. It's all the same.

Correct you are. The headline should read they are not accepting NFC payments.

I gave you a +1 on all these posts, because you are the only one that seems to get it. The technology standard being used is NFC - this is the same standard in the entire world. :apple:Pay is only different in the way it implements the tokenisation of the validation and approval stage of the process - on the back end. From the Merchant's NFC PoS point of view (front end) there is no difference between GoogleWallet and :apple:Pay.

From your credit card's POV, no change either, you continue to earn your rewards and points and FF miles as normal with your credit card companies. Just won't be able to flash around that black AmEx anymore so no one will know what a baller you are :cool:
 
And I'm willing to bet that Best Buy is gonna change their tune, soon enough. Bank on it. Walmart? Who the hell knows. I personally hate going to Wally World. Between some the employees (not all but some) and the weird ass customers? Ugh..
 
Here is how it works.

1) You swipe a regular credit card, the card provides your PAN number to the machine and it gets sent out to the payment processor (VISA or Master) along with the merchant ID. Less secure as the PAN number can be captured illegally inflight and used again.

2) You swipe a card with a chip, there is an encrypted token stored and it can only be decrypted by the payment processor. This chip on the card is hard to be duplicated unlike the magnetic strip. Further as an additional feature as soon as the data is transmitted from the merchant's system it is expired and so it cannot be re-used by whoever is capturing it. This is the new requirement for which all merchants will have to buy a new POS terminal devices and show they are compliant. However note that if the merchant's system gets compromised they can still store this encrypted token and re-use it again. So this means there system will still have to be PCI compliant. Some of us know what this means to implement such a system.

3) NFC is just a communication device used to transfer the information from the card to the terminal. It changes nothing on the processing side.

4) Apple pay has taken this security to one level higher. They store the token in their special security element inside the phone and every time we use the NFC to pay a dynamic code is generated for the token stored in security element specific for that transaction. Apple has worked with the payment processors and only they can decode this dynamic code and retrieve the token. So this information is transparent even to the terminal. The terminal still thinks it is processing a PAN or a token but they don't know it is a dynamically generated code that is unique to that particular transaction. Hacking the phone is not an issue as Apple has already introduced their brilliant finger print security in 5S and made people comfortable with that. This was an excellent move.

So to make apple pay work all the merchant will have to do is to get a new device with NFC enabled and nothing else. Since the system just handles the dynamic code, by moving to Apple pay the merchants can potentially take their systems out of PCI compliance in future with huge cost savings. The compliance recommendations have not been updated for this but sure to follow.
Once the Executive nuts at Walmart understands this $$ factor they will start embracing it faster than you can imagine.

Is PCI compliance expensive compared to merchant credit card fees though? I know they already pay the merchant fees for credit transactions (I don't know the typical percentage of transactions that are credit though), so it would be interesting to see if they are weighing the cost savings of getting rid of PCI compliance versus the additional credit merchant fees.
 
Whoa. Tell me the secret to getting ignored at Best Buy. I'd love to be able to shop without their floor staff trying to "help" me all the time.

That's what gets me with working at best buy. If you ignore the customer and let them do their own thing, then the customer is like "curse you all for not helping me!" but if you walk up to them and talk to them and try and help them then the customer is like "curse you all for bothering me" Lol you can't win #
 
I gave you a +1 on all these posts, because you are the only one that seems to get it. The technology standard being used is NFC - this is the same standard in the entire world. :apple:Pay is only different in the way it implements the tokenisation of the validation and approval stage of the process - on the back end. From the Merchant's NFC PoS point of view (front end) there is no difference between GoogleWallet and :apple:Pay.

From your credit card's POV, no change either, you continue to earn your rewards and points and FF miles as normal with your credit card companies. Just won't be able to flash around that black AmEx anymore so no one will know what a baller you are :cool:

This is only true if the alias or token that the :apple:Pay uses works with existing protocols. Is it certain that Google Wallet uses tokenization? It states in the integration that the sensitive information is encrypted, that would mean your information is passed through the transaction. That would also mean they use separate protocols.

In my honest opinion, I had thought it is a software update at best for most major retailers, and then a hardware change for smaller merchants. But I think people are flipping a lid b/c we certainly don't have enough information about this yet.

Also, Apple was able to file for a patent for this in January, whereas Google Wallet has been out since 2011. It would be shocking to me that banks, issuers and merchants would back Apple but not Google.
 
The two systems are different.

Wrong. Not from the PoS system view. All you need is a an NFC capable terminal and you are good to go.

The systems do differ in how they handle tokenisation, and other details on the back end and from the user experience side of things, but they look exactly the same to a PayPass terminal...
 
Only years of hardcore marketing research??? :eek:

iOS devices in general are used to spend a lot more money on apps and online purchases, both in total and per transaction than any other mobile OS or mobile device. It is not a stretch to assume that this is also true for this demographic in physical location situations as well.

There are many, many marketing reports, research studies, and analyst notes that show these statistics, so while your broke single mother with 10 kids and less dollars in her bank account almost certainly exists, that person is an outlier in terms of the "average" iOS user.

That's not fantasy, that is statistics...
But all you posted was fantasy!
 
This is only true if the alias or token that the :apple:Pay uses works with existing protocols. Is it certain that Google Wallet uses tokenization? It states in the integration that the sensitive information is encrypted, that would mean your information is passed through the transaction. That would also mean they use separate protocols.

In my honest opinion, I had thought it is a software update at best for most major retailers, and then a hardware change for smaller merchants. But I think people are flipping a lid b/c we certainly don't have enough information about this yet.

Also, Apple was able to file for a patent for this in January, whereas Google Wallet has been out since 2011. It would be shocking to me that banks, issuers and merchants would back Apple but not Google.

Google doesn't make hardware and software, they don't control the whole device. That's the main reason the credit cards would decide to play ball with Apple.

For the rest, I respectfully think you are confusing what is actually happening here. Tokenisation does not mean different formats of information are trying to be passed to the NFC reader. It means that a different set of data is substituted for the sensitive information, but delivered in the same format as the NFC reader expects it. This token is decoded by the credit card companies back to your card number and approved.

So it doesn't matter how tokenisation is implemented, if at all, by different implementations, ie Softcard, GoogleWallet, or :apple:Pay. They all have to use the same format that the NFC PayPass PoS terminal expects in order to work.

It would be EXCEEDINGLY stupid for Apple to try to implement their own standard for this communication other than NFC and try to push this proprietary standard on retailers, requiring them to have a separate PoS just for :apple:Pay. It would be an instant and comical DoA proposition then.

Apple is patenting the unique way in which it handles the tokenisation and handling of the security on the back end, they are nit trying to patent the actual NFC information transfer process.
 
Wrong. Not from the PoS system view. All you need is a an NFC capable terminal and you are good to go.

The systems do differ in how they handle tokenisation, and other details on the back end and from the user experience side of things, but they look exactly the same to a PayPass terminal...

See, I used Google Wallet only a few times, and that was a while ago. Their strategy has changed significantly, so instead of spouting out false information, I am going to drop that.

With :apple:Pay, would the payment processor not have to use Apple APIs to accept their token and transmit to the bank for authorization? This was my point, that I can't just take my iPhone 6 to Walgreens next Friday and just start paying unless their system takes on at least a software update.

----------

Google doesn't make hardware and software, they don't control the whole device. That's the main reason the credit cards would decide to play ball with Apple.

For the rest, I respectfully think you are confusing what is actually happening here. Tokenisation does not mean that that different formats of information are trying to be passed to the NFC reader. It means that a different set of data is substituted for the sensitive information, but delivered in the dame format as the NFC reader expects it. This token is decoded by the credit card companies back to your card number and approved.

So it doesn't matter how tokenisation is implemented, if at all, by different implementations, ie Softcard, GoogleWallet, or :apple:Pay. They all have to use the same format that the NFC PayPass PoS terminal expects in order to work.

It would be EXCEEDINGLY stupid for Apple to try to implement their own standard for this communication other than NFC and try to push this proprietary standard on retailers, requiring them to have a separate PoS just for :apple:Pay. It would be an instant and comical DoA proposition then.

Gotcha, gotcha.
 
Last edited:
WalMart is not looking for status symbol or being a member of the Apple cult. It does business.. in large volumes and will do so without Apple even being part of their business. Its Apple's loss more than its for Wal Mart.

Not everyone dances to Apple's tunes and that's life.

Well then I think you need to take Business 101 because you're getting personal and not speaking from a business standpoint.
 
Is PCI compliance expensive compared to merchant credit card fees though? I know they already pay the merchant fees for credit transactions (I don't know the typical percentage of transactions that are credit though), so it would be interesting to see if they are weighing the cost savings of getting rid of PCI compliance versus the additional credit merchant fees.

I don't think there will be any increase to the merchant's fees on top of what they pay now. Apple very well understand that will be a no go. Apple would have signed a contract with the payment processors to get a cut from them directly. To their advantage I predict that the plastics are history and all the banks will do when you open a credit is to issue a security token to store in the iphone. This will result in huge savings for the banks and also they can sleep well that they have sort of outsourced the security to a reliable partner in the name of Apple. You can keep this as my prediction :)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.