Alabama's Anniston Star newspaper is reporting today that Jacksonville, Florida-based Winn-Dixie, one of the largest US grocery store chains, suffered a major problem with its electronic credit/debit card transfer system on Wednesday that resulted in customers being double charged on their purchases.

Making matters worse, the Wednesday before the Thanksgiving holiday is a very busy food shopping day in the US, so Winn-Dixie stores were filled with shoppers.

According to the Star's story, all 485 Winn-Dixie stores were affected by the problem.

The Star also reported that, "Because banks were closed for Thanksgiving, it was impossible to determine the number of customers charged twice, sources within Winn-Dixie said." 

The story went on to say that, "Banks typically have a failsafe measure to protect against double charges, but it is not clear whether the malfunction bypassed those protective measures."

Winn-Dixie has nothing about the problem at its web site. I'll update this story when (and if) more information becomes available.

Update: An article in Saturday's Anniston Star says that Winn-Dixie is still trying to figure out what caused the problem. According to the story:

"An investigation by all three parties affected by the crash – Winn-Dixie, the processor and the banks – hasn’t definitively ruled out the possibility of the system crash being a result of an attack, but Winn-Dixie officials believe it was a communication error."

Maybe more will be known by late Monday.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less