Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Okay, MacRumors should link the actual Bloomberg article - http://www.bloomberg.com/news/2014-...tomers-double-charged-in-apple-pay-snafu.html

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 aren’t public. The issue will be resolved today, the person said.

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.
 
My point is this whole situation is not as serious as the sensationalizing media (and trolls) would like to make it out to be.

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.
 
Okey Apple, please make some time for test and quality work. With the banks and every single man that is involved in the system.
 
Considering I interact with cashiers who on occasion have trouble with basic card readers (well, and cash for that matter...), there will be issues with Apple Pay. These issues will all be worked out as users, workers, Apple, banks, and the credit card issuers figure things out.

Double billing also happens on occasion in store and online. Credit card companies are great at sorting it out (usually).
 
Given the new information - it's clearly a BoA issue.

However - those that take issue with Apple's name being brought into it are being silly because it's a related story. It WAS a Apple pay glitch. Even if it was a 3rd party issue - they take the hit.
 
Before 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.
+1

It's not just Apple related news either. "-gate" is the most overused, least clever suffix in human history. If I was in charge of a media outlet and one of my reporters used it, I would fire him immediately, then re-hire him just so I could fire him for it again.
 
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

You're making a generalization. But I get it. The worst people in either of these groups are the worst regardless of what side of the fence you are on.
 
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.

Wow, that just takes the sensationalism right out of the story, doesn't it? The trolls now hate you for it. Not to mention MacRumors, considering the title of the post.
 
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.

Um, no.

If what you said was true you wouldn't be able to test anything but the most trivial software.

If you identify all the edge cases and the corner cases then you can prove that a combination (or interaction) works by just testing one set of values, extrapolating to all values between the special cases.

There are also other techniques like probabilistic testing.
 
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.

No problem there. Just like trying it out is no big deal. From what I've read it sounds like an overwhelming success so far. I haven't been able to use it yet since my 64GB AT&T iPhone 6 is backordered until November. :(
 
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.
 
Yes, it did happen...

Thankfully it was just for a bag of Combo's bought at Walgreens, literally 10 minutes after installing 8.1, and adding the debit card to :apple:Pay in my iPhone. I called BofA immediately after I saw the double charge, but at that time it was still 'Processing' so they couldn't do anything about it. Also, since it was so early on, they couldn't really diagnose where the problem was. Glad to see it wasn't simply user error on my part. :eek:

That being said, it does make me somewhat gun-shy to try it again with a larger purchase. We'll give it a few days and try again...

Peace be with you.
 
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.
 
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.

just another quality/polished app from you friends at apple lol..
think i'll just stick with my trusty old google wallet for now.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.