200,000 Credit and Debit Card Holders Double-Billed by Lloyds TSB Cardnet System

Customers of other banks affected too by New Year's Eve glitch

1 min read
200,000 Credit and Debit Card Holders Double-Billed by Lloyds TSB Cardnet System

Reports were published this week in the UK press that some 200,000 credit and debit card holders  that used Lloyds TSBCardnet system were double-charged for their transactions on New Year's Eve.

Lloyds Bank said that there was a "technical error" in their merchant system on the 31st of December, and that all the duplicated transactions have been corrected, according to this story at ComputerWorldUK.

However, since the error may have affected non-Lloyd bank customers as well, reversing duplicate transactions may not be the end of it. The reason is that some of those non-Lloyds Bank customers may have incurred penalties from their bank or credit/debit card holder for being "over-drawn" by the duplicated transaction. Those folks are going to have to contact Lloyds directly to get the issue straightened out.

Lloyds said in its statement quoted in this story at The Scotsman that:

"Cardholders who believe they have been financially penalised by their bank or card issuer as a direct result of the duplicated transactions are advised to contact us... We will consider all reasonable and evidenced requests for reimbursement."

To those so affected, I say, "Good luck!"

Oh, before I forget, Lloyds "would like to apologise to affected individuals for any inconvenience caused."

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
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

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
{"imageShortcodeIds":["31996907"]}