Lloyds Debit Card Glitch – Expert Analyses The Latest String Of Software Glitches

427

Thousands of UK consumers were charged twice for debit card payments as a glitch occured in the card terminal run by Cardnet, a joint venture between Lloyds Bank and First Data.

This is only latest IT glitch in a very long list: TSBM&SGatwick, recurring NHS glitches to name but a few of the Software glitches affecting customers, travellers and patients in the past three months.

CAST, the software intelligence company, is helping financial services organisations such as Fannie Mae, Telefonica, Credit Suisse and ING have reliable and resilient software. Experts at CAST are dedicated to improving Software quality, resilience and security.

Lev Lesokhin, EVP of Strategy and Analytics at CAST:

“Glitches such as the one that left consumers scrambling for reimbursements on double-charged purchases are commonly caused by poor interfaces or APIs between layers of complex IT systems. In this case the systems designed to process debit card transactions. Designing software to run these functions within a single organization is complicated enough, but building trustworthy systems is an even higher bar.

The financial services industry is saddled with old, complex applications that are difficult to modernize without risk of service disruption. Considering the glitch occurred in a system touched by multiple organizations, from Cardnet to Lloyds Bank to First Data, it’s likely that a change was made in the system without considering the architectural ramifications of that change. For example, Lloyds might have issued a new software release to improve the interface for online banking services without realizing how it would impact the interface to connected Cardnet terminal, therefore leading to a non-intentional double-charge of debit transactions.

The emerging practice of Software Intelligence, insight around software trustworthiness that points towards a solid understanding of software structure, was designed to help organizations to deal with such complexity. Especially in API-driven development, preventing cross-layer glitches from occurring, teams across organizations must collaborate based on a centralized understanding of software architecture and how enhancements will impact application performance in the field.”

In this article