Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It's Things like this make me hope for either Bitcoin or something like it to catch on more. In an all-bitcoin transaction, this sort of thing is impossible, because of the way the network is set up...
 
Man they can't even release this right! And they still kept it back after the 8.0 release. Weak.
 
When introducing new technology and new systems, it does fall to the vendor of the payment method to assist in getting the implementation to work.

As Apple is the interface in this instance, it was up to them to insure proper interfacing had been implemented. They are the ones who convinced Bank of America to support their service. As such, Apple should have been involved in making sure that everything downstream worked and assured Bank of America that they had properly gotten all the pieces in the process working.

When I had a business accepting credit cards, it fell to that company to come to my location and set everything up for me. If they wanted me to use their service, then they need to set it up.

Apple set up a way to act as a go between for payments. It's up to them to make sure that everything works properly through the entire transaction and to have established the link to Bank of America properly.

As for why it only affected Bank of America, again could be that Apple was a little sloppy in setting up the connection with them.

Yes, Bank of America is refunding the money. Naturally. They're the ones at the end who received the charges. Just because they're at the end of the chain and the ones holding the money, doesn't mean it was their mistakes that caused the problem.

You haven't done any implementations of interfaces from the perspective of an IT professional.

Basically the interface will have to be set up on both sides between Apple Pay and whatever bank. Once this is completed and transactions are passed back and forth there is nothing Apple Pay can test in the receiving banks system. The over charge happened in Bank of Americas system which is downstream from the interface.
 
This thread sums up MacRumours readers to a tee.

Wrong Headline, Wrong Information and readers jump on it like its gospel.

MacRumours need to change the headline as it is clearly wrong as per YOUR OWN updates.

----------

Man they can't even release this right! And they still kept it back after the 8.0 release. Weak.

I don't blame you for your post as MacRumours haven't amended their headline but it will teach you to not read the whole article.
 
There should be an [UPDATE:] in the title like always when there is an update but yeah macrumors... With the update in there thats not enough click bait...
 
"A Bank of America representative contacted by CNN said that the issue was on Apple Pay's end and after some confusion about who should be contacted for a refund, Bank of America was able to refund the money."

You're missing the word incorrectly after "A Bank of America representative contacted by CNN".

Article title should also be "Bank of America Glitch Causes Apple Pay Customers to Be Charged Twice for Purchases", not the other way round as it is currently.

Sometimes I wonder why I even bother subscribing to your RSS feed anymore.
But who needs news to be factually correct hey? Much more fun to just make something up instead.
 
Last edited:
If there's something for some to learn from this thread - it's that some forum "readers" fail to read full articles, do their own research, and are too lazy to read a full thread before immediately clicking "post." There's really no excuse 14+ pages in for people to talk about this as if the glitch was on Apple's side or that it has anything to do with iOS 8.

But I imagine as soon as this post gets buried by another page - someone will still get "mad" at Apple over this. Sometimes it doesn't even take a new page.
 
If there's something for some to learn from this thread - it's that some forum "readers" fail to read full articles, do their own research, and are too lazy to read a full thread before immediately clicking "post." There's really no excuse 14+ pages in for people to talk about this as if the glitch was on Apple's side or that it has anything to do with iOS 8.

But I imagine as soon as this post gets buried by another page - someone will still get "mad" at Apple over this. Sometimes it doesn't even take a new page.

The headline surely didn't help, but it is definitely funny to see how many people went berserk on that first page and started foaming at the mouth because they thought apple messed up.

Apple messes up a lot. This wasn't one of those times.
 
The headline surely didn't help, but it is definitely funny to see how many people went berserk on that first page and started foaming at the mouth because they thought apple messed up.

Apple messes up a lot. This wasn't one of those times.

MacRumors is extremely anti-Apple. This headline proves it. It happens time and time again every day.

If MacRumors were even remotely pro-Apple, this headline would be completely different from the start.

But, it's good business to be anti-Apple. Get all the trolls to come and earn page views from them!
 
This sounds sound too bad, but the returns issue is concerning. If they want the original card, but don't actually have the real card number on file, that could be a problem.
 
Surprise Surprise. BofA charging customers improperly? Say it isn't so!

I don't know, or really care, if this is BofA's fault or Apple's. BofA screwed me over for over $1,200 in fees FOR THEIR MISTAKE.... so any time i even see the words BANK OF AMERICA... I cringe. And therefore, it's their fault in my mind.

/rant :)
 
Read the story, not just the headline

This is a BofA problem.


Bank of America Glitch causes Apple Pay Customers to be Charged Twice for Purchases
#BofAGlitch
 
MacRumors is extremely anti-Apple. This headline proves it. It happens time and time again every day.

If MacRumors were even remotely pro-Apple, this headline would be completely different from the start.

But, it's good business to be anti-Apple. Get all the trolls to come and earn page views from them!

This site is not anti-Apple. This site is a business. And to make money, that requires visitors. The headline wasn't sensationalist. It was provocative. The headline also isn't false. It's leading.
 
BofA story

Surprise Surprise. BofA charging customers improperly? Say it isn't so!

I don't know, or really care, if this is BofA's fault or Apple's. BofA screwed me over for over $1,200 in fees FOR THEIR MISTAKE.... so any time i even see the words BANK OF AMERICA... I cringe. And therefore, it's their fault in my mind.

/rant :)

Here's one for ya... I received a check from BofA for $8.10
It was a settlement check for something. Turns out they delayed sending it to me so when I deposited it into my account I not only didn't get the $8.10, I also got charged a $10 fee. Thanks BofA. :mad:
 
It's Things like this make me hope for either Bitcoin or something like it to catch on more. In an all-bitcoin transaction, this sort of thing is impossible, because of the way the network is set up...

That's nonsense. Sure, one transaction will be only one transaction, but it is always possible to have a software glitch where say pressing the "buy" button starts two transactions.
 
This site is not anti-Apple. This site is a business. And to make money, that requires visitors. The headline wasn't sensationalist. It was provocative. The headline also isn't false. It's leading.

The headline IS intentionally false and misleading.

The headline will have MOST people believe that Apple is responsible, not Bank of America. MacRumors knowingly wrote the headline this way, which is horrible journalism. It's not just MacRumors, it's practiced a lot today, by many news sources, and it's just plain wrong.

It seems as if you're just numb to these journalistic practices. It causes people to believe the wrong things, and the wrong people to be hurt.

For example, we had a local news story for the past few weeks, where there was a white car going around trying to pull little kids into the car to abduct them. The white car was on camera, the police finally found the white car and the owner. The news lead story teaser said, 'Police find driver of white car, release owner and do not press charges'. The headline was meant not to tell the news, but instead provoke anger and outrage at the police force - 'How dare they release this person! The cops are corrupted!'. It turns out that the white car we've been seeing in the news was not connected to the white car in the abductions. The news is doing a huge disservice to the police for people who did not actually wait for the 11:00 news to tune in and find out about the story. The same is happening here to Apple Pay. It's wrong, and there is no justification for it except 'well, everyone does it'
 
Some jerk deleted my post.
(Reposting)
1314029819767.png



What I am dismayed is the obvious lack of awareness and training on this.
While only a few dozen had the double charge issue, the far, far greater issue of people cannot being able to use it because the cashier had no idea, that is the issue.

Especially those that had no idea what it was.
 
I believe what you are seeing is one email telling you the first one was deleted. Then another email when you add it back with the new virtual number. At least thats how mine has worked.

No, both emails came in one right after the other (less than 1 minute apart), letting me know that my card was added to Apple Pay. Both emails contained the exact same information.
 
Man they can't even release this right! And they still kept it back after the 8.0 release. Weak.

Even worse-- some people can't even read the entire article before commenting. That's certainly "weak"; but is it the product of weak eyes, or weak mind? ;)

----------

Come on Apple stop it please. If a new feature, or gimmick isn't quite ready for the real world, just wait until you get it right. If it's a new feature, people aren't going to miss it anyways, as they haven't seen it yet. People are losing confidence in you. Better off making people wait a little longer and release something that really "Just works", rather than creating a big mess. :rolleyes:


Seriously, is the problem that you can't read, or you just don't think before you write? The updates made it clear this is not on Apple, and something Apple could not possibly have tested for or prevented. Is that a difficult concept?

We know you can paste an :rolleyes: icon; perhaps that's the important thing to you. Do you get an endorphin rush when you do that? I'm serious, as I'd like to understand posts like this.

----------

Precisely? :confused: I think your confused.

According to this link:

https://www.fdic.gov/consumers/consumer/information/ncpw/cardstopten.html

5. Your liability for an unauthorized debit card transaction may vary. The maximum legal liability is $50 if you notify the bank within two business days after learning of the loss or theft of your debit card. Otherwise, your losses could be greater. You must also notify your bank within 60 days of your bank’s transmittal of your periodic statement on which an unauthorized transfer appears, in order to avoid liability for subsequent unauthorized transfers.

It's not automatic in every case. Disputing charges isn't always a slam dunk.

That seems irrelevant. It was a perfectly valid authorized transaction, which got messed up by a mechanism in the automated handling between the POS terminal and BoA. Which means, BoA will credit 100% of the detected problems, regardless of whether someone hits the reporting window.

----------

Okey Apple, please make some time for test and quality work. With the banks and every single man that is involved in the system.

LOL. Great comment, assuming that was satire.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.