Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
There's a shared responsibility as Apple has publicly revealed they've been working with various financial institutions. Therefore itd be wise of Apple to stay close enough during the launch of this service to mitigate any damage.

But Apple isn't at fault. Like. At. All. I understand that they should try to be part of the solution since they're taking the PR hit but for those of us that are capable of reading through the MSM BS, don't we owe Apple an apology for stating something like...oh...I don't know...this?

Epic fundamental failures right out of the gate like this simply remind one of Apples lack of attention to detail.

On one hand they have legions of supporters quick to make excuses, on the other hand for such a well seasoned company this is unacceptable.

That said the greater majority will let Apple go as though it never happened.

It's Amazing at how much in common Apple has with another massive bumbling organization. No wonder they understand each other so well.
 
But Apple isn't at fault. Like. At. All. I understand that they should try to be part of the solution since they're taking the PR hit but for those of us that are capable of reading through the MSM BS, don't we owe Apple an apology for stating something like...oh...I don't know...this?
Besides. Bank of America isn't going to let Apple into their code. Apple should give B of A all the help it needs to fix the problem, but the fix will (and reportedly has) come from B of A.
 
It requires quite some stupidity to blame Apple for this glitch. So yes, this thread clearly is ample evidence for such stupidity :)

(and to avoid further stupidity - this post does not equal "apple cannot do any wrong")
 
Well, I *am* a software engineer, and I'm tired of the old "software-is-complex-it's-never-bug-free" excuse. We all know software is complex. But it's not a get-out-of-jail-free card, you execute honest due-diligence in testing, take responsibility for your bugs, notify your customers about the serious ones (like, ones that involve people's money), and correct them in a timely manner.


In light of updates to the story, it looks like Bank of America et al. should be doing what you suggested. Apple's in the clear for this mistake.
 
So this wasn't an Apple mistake and all the android fanatics who spend more time on MR than android sites went crazy blaming Apple?

Just another day at MR...:p
 
This story seems to put the issue on Apple pay when this really only is affecting Bank of America customers.

So isn't this really an issue with Bank of America IT

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.
 
Well, other than being the company that invented it, they have nothing to do with it.

Also, you'd make your point better if you didn't write it in a large glaring font.

Apple didn't event NFC payments. The issue isn't apple pay, but the way BOA is processing the payments, twice. So i guess even the large glaring font wasn't big enough to get the point across.
 
So this wasn't an Apple mistake and all the android fanatics who spend more time on MR than android sites went crazy blaming Apple?

Just another day at MR...:p

Must be essential to have another brand to bash, therefore you have a place to unleash unresolved anger. Without Android, throngs of victims would lack a satisfying way to deal with their issues. Luckily you have a place to dump your venom.
 
It's pretty easy to have no issues when you never use a service.

I have several coworkers at IBM with Google Wallet compatible phones. I checked and they don't use it. The one coworker that has received their iPhone 6 is already using Apple Pay. Mine hasn't arrived yet but I plan on using Apple Pay and ditching my wallet as promptly as possible (admittedly that'll probably be a few years.)

http://www.fool.com/investing/gener...-vs-google-wallet-why-apple-inc-will-win.aspx

All that proves is that many Apple users jump on ideas that other people have already dismissed as uninteresting.
 
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.

Yes it does, and they admitted it was their mistake and had nothing to do with Apple. Did you read the update?
 
My Chase card thru Apple Pay got declined yesterday in Home Depot. The actual physical card when swiped a minute later worked fine.

I went to McDonalds today to test Apple Pay again and after the wave of my phone, I selected my Amex card in Passbook and the payment went thru. However, afterwards while eating, I noticed the last transaction on the screen in Passbook showed the location and "-" where the amount should have been. It should have said $2.80. I just checked my recent transactions with Amex and there is NO activity or charges from McDonalds.
 
OK I hear you but it sounds like its still happening to a significant amount of people to be called out.

It's not the first issue that has come up since the release of iOs and the iphone 6 and 6 plus.

All these little issues just don't instil a lot of confidence for me in apple. I being someone who is debating buying an iphone 6 like many others this doesn't help convince me to do so. Then again I'm Canadian and can't use apple pay nor do I really car to since I have NFC on my credit and debit cards anyway.

Read the UPDATES. IT IS ON THE BOA SIDE, NOT APPLE!!!!!!!!!!!!!!
 
Apple didn't event NFC payments. The issue isn't apple pay, but the way BOA is processing the payments, twice. So i guess even the large glaring font wasn't big enough to get the point across.

Apple did a Phone and iPad/MAC event and WWDC. They didn't do a NFC event.
 
Read the updates, not an Apple issue, B of A has released a statement that the problem is with one of the processors, not Apple!:cool:

I new people would throw Apple under the bus and try to blame them! Even MacRumors jumped the gun with the report, before having all the facts!:eek:

It is a rumors sight, so just like the media, no time to get all sides or, wait for some answers!:cool::apple::apple::apple:

There will be some glitches at first I'm sure, with as many systems that have to communicate, I can't believe this is the only issue so far?:apple:
 
"Hundreds of customers are said to be affected."

Oh god not HUNDREDS!!!!! (out of how many??? Right, that would require someone to do some actual reporting and we can't have that in tech journalism...)

In an amusing turn of events I decided to check my transaction at Whole Foods. And yes... I got hit with this. The credit for the second charge was done the next morning.
 
Read the updates, not an Apple issue, B of A has released a statement that the problem is with one of the processors, not Apple!:cool:

I new people would throw Apple under the bus and try to blame them! Even MacRumors jumped the gun with the report, before having all the facts!:eek:

It is a rumors sight, so just like the media, no time to get all sides or, wait for some answers!:cool::apple::apple::apple:

There will be some glitches at first I'm sure, with as many systems that have to communicate, I can't believe this is the only issue so far?:apple:

Are you talking about new people that never did this before?
 
Update 1:22 PM: Bank of America has confirmed to Re/code that the problem is the result of an issue between the bank and at least one payment processor and that Apple is not involved. A fix is expected today, and roughly 1,000 customers were affected by the double billing.

Update 1:50 PM: An Apple spokesperson told Bank Innovation that Bank of America is working on a fix and that the issue is impacting only a small number of Apple Pay users.

Okay, let's close the discussion now. Nothing to see here... Move on.
 
HOLY CRAP GUYS! A brand new service with so many varying factors would run into problems in the first week? Thats unheard of...

Stop being such a spineless apologist. This is people's money. If Apple want to get in the business of replacing people's wallet they damn well better make sure they do it properly.

The glitch was apparently the result of a miscommunication between the bank’s systems and an unnamed payment network and wasn’t Apple’s fault at all, according to the report. The bank said that only about 1,000 transactions were affected by the problem, which is a relatively minute number compared to the number of transactions likely being carried out nationwide today.

Don't you feel like a big dumbo...
 
Update 1:22 PM: Bank of America has confirmed to Re/code that the problem is the result of an issue between the bank and at least one payment processor and that Apple is not involved. A fix is expected today, and roughly 1,000 customers were affected by the double billing.

Update 1:50 PM: An Apple spokesperson told Bank Innovation that Bank of America is working on a fix and that the issue is impacting only a small number of Apple Pay users.

Okay, let's close the discussion now. Nothing to see here... Move on.

If only it were that simple. Android fanatics just read the headlines and then attach the word gate to things like this and talk about it forever.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.