Thanks.
How about the human element here and there's a human on the other end this overlook something. But they are human. join the race. Nothing is Perfect in this worldExactly BofA really slipped up here.
The error was attributed to a processing glitch that occurred between the Charlotte, North Carolina-based bank and at least one payments network, said the person, who asked not to be identified because details of the malfunction arent public. The issue will be resolved today, the person said.
This is a serious issue. Apple is continuing the trend of producing half-baked, untested products and services that are diminishing it's status as a developer of premium priced/premium quality products.
My point is this whole situation is not as serious as the sensationalizing media (and trolls) would like to make it out to be.
+1Before it starts, can we not keep using the word -gate after every bad thing related to apple? It makes no sense and has long outlived its welcome as a thing.
So dumb.
That would be semantics
There is a difference between using logic and sensibility and just blatant delusion and ignorance that most Android fanboys really have, and then they also start getting real nasty too, Android users claim "iSheeps" are dumb and dont know anything and that they use the more "advanced, technical OS" but that in reality they dont really have a clue on what they are saying
Okay, MacRumors should link the actual Bloomberg article - http://www.bloomberg.com/news/2014-...tomers-double-charged-in-apple-pay-snafu.html
So it was a processing glitch between BoA and at least one particular payment network. BoA is fixing the glitch and refunding double charged customers.
The flaw here is that assumption, that "a little more" testing is all that is needed.
Consider this-- some problems occur one time in a hundred; some one in a thousand; some one in a million. The problems that occur once in a million take a lot more than "a little more" testing to find, yet will occur in the wild, where tens or hundreds of millions of instances take place.
Consider also that each instance is a combination of things, that would have to be tested in combination to be exhaustive. Each time a "degree of freedom" gets added, that increases the possible combinations of occurrences that can occur. Trying to figure out and guard against an unforeseen problem due to a particular combination is much like trying to find a needle in a haystack.
You're right, it's not. But, while I would love to try this out, I'm not in that big of a hurry. Especially since I'd have to go out of my way to try it out anyway since none of the stores I frequent have NFC readers (I've been checking since Monday). So, waiting this out is no big deal.
This story seems to put the issue on Apple pay when this really only is affecting Band of America customers.
So isn't this really and issue with Bank of America IT
Well, it would have been a surprise if there WEREN'T glitches, given the rest of iOS8
The flaw here is that assumption, that "a little more" testing is all that is needed.
Consider this-- some problems occur one time in a hundred; some one in a thousand; some one in a million. The problems that occur once in a million take a lot more than "a little more" testing to find, yet will occur in the wild, where tens or hundreds of millions of instances take place.
Consider also that each instance is a combination of things, that would have to be tested in combination to be exhaustive. Each time a "degree of freedom" gets added, that increases the possible combinations of occurrences that can occur. Trying to figure out and guard against an unforeseen problem due to a particular combination is much like trying to find a needle in a haystack.
Looks pretty reproducible to me.
That's kind of my point, although I didn't make it clear. Who cares if they aren't trained, it still works, they don't need to be trained.
I wish that were true. I tried using Pay at Panera and after 4 failed attempts I ended up swiping my card. Passbook shows 4 transactions with no value so I think it worked on my end, plus it's worked for other people on this forum.
When I swiped my card he said, "there it is," then said my last name. Maybe with Pay no name came up and he kept canceling the transaction. In any case, I wish it were true that it's completely transparent to the cashier but obviously it isn't.