The Lloyds App Data Glitch triggered concern among banking customers after several users reported seeing transactions that did not belong to their accounts. The issue appeared on mobile banking apps operated by Lloyds Banking Group, including Bank of Scotland and Halifax.
Customers began reporting the problem early Thursday morning. In several cases, users said the apps displayed payments, charges, and account details belonging to other individuals.
Lloyds Banking Group acknowledged the issue shortly after the reports surfaced. The bank apologised to customers and confirmed that engineers resolved the problem quickly. Nevertheless, the group has launched a formal investigation to determine the cause of the Lloyds App Data Glitch.
So far, the bank has not confirmed how many customers experienced the error.
Reports of technical problems first appeared between 07:00 and 09:00. Downdetector, a website that tracks online outages, recorded a surge in complaints about the Bank of Scotland and Lloyds mobile apps during that period. The Halifax app also recorded a smaller spike in error reports.
Although the technical fault lasted for a limited period, the incident raised concerns about data visibility inside the banking platforms.
In response to customer questions on social media, Halifax confirmed it had detected issues affecting transaction displays and account balances. At the same time, Bank of Scotland stated that engineers had begun examining what it described as a possible technical glitch.
Meanwhile, Lloyds advised customers to remain patient while the company worked to fix the issue.
The Lloyds App Data Glitch became more troubling after one user described seeing multiple strangers’ financial information.
A woman who spoke to BBC Scotland News said she could view accounts belonging to six different individuals while using the Bank of Scotland mobile app. She said the problem lasted around 20 minutes.
According to her account, each time she logged out and logged back in, the app displayed a different set of banking details.
The transactions she saw included purchases made at a pub in Newcastle. That location sits more than 150 miles from her home in Kirkcaldy, Fife. She also reported seeing card usage fees from overseas spending and salary payments issued by a company based in England.
More concerning, she said the Lloyds App Data Glitch allowed her to view sensitive personal details connected to those transactions.
The customer said some payment references displayed National Insurance numbers. In the United Kingdom, government departments sometimes use those numbers when issuing benefits payments.
According to the woman, the data visible through the app included payments from the Department for Work and Pensions. She also said the transaction details revealed information about where individuals worked and how much they earned.
One example involved a payment of £6,000 that appeared to represent a salary deposit.
She said the experience felt alarming because the app repeatedly exposed different users’ financial records.
The customer explained that each login attempt displayed a new account profile. As a result, she said she could see information connected to several different individuals within a short period.
The Lloyds App Data Glitch therefore raised questions about how the system handled account authentication during the incident.
Digital banking apps typically rely on secure identification systems designed to isolate each customer’s account data. When those safeguards fail, even briefly, users may gain access to information that should remain private.
In this case, the bank has not yet explained what technical fault caused the problem.
However, incidents involving banking platforms often occur when system updates, server synchronisation errors, or database indexing issues disrupt how accounts connect to user sessions.
Even temporary errors can create serious privacy risks.
The current investigation will likely examine how the Lloyds App Data Glitch allowed account information to appear across unrelated user sessions. Engineers will also review whether internal safeguards responded correctly once the issue emerged.
Banking regulators in the United Kingdom treat data exposure incidents seriously. Financial institutions must maintain strict controls over customer information.
If investigators find that the error exposed sensitive financial data, regulators may request additional safeguards to prevent similar incidents in the future.
Digital banking platforms now manage millions of daily transactions. As mobile banking becomes the primary way many customers access financial services, system reliability has become increasingly critical.
The Lloyds App Data Glitch also follows earlier disruptions affecting UK banking systems.
In February 2025, several banks, including Lloyds, experienced a large service outage. That incident affected roughly 1.2 million customers across the country and disrupted online banking access for several hours.
Although the current situation appears to have been resolved quickly, it highlights the technical challenges facing large digital banking networks.
For customers, the incident reinforces concerns about the security of financial data stored within mobile banking apps.
For banks, it serves as another reminder that even brief technical errors can undermine trust in digital financial services.
As the investigation continues, Lloyds Banking Group will likely focus on determining exactly how the Lloyds App Data Glitch occurred and whether any customer data was permanently exposed.
The outcome of that review will determine whether additional security measures or system upgrades become necessary to protect users in the future.