Not every transaction dispute starts with fraud. A surprising number start with the customer staring at their banking app thinking, ‘what on earth is that?’
When transaction details are unclear, legitimate spending can look suspicious. The customer raises a dispute, the bank investigates, and the costs start accruing before anyone confirms whether fraud has occurred.
Moneyhub categorises and enriches transactions in real-time on behalf of financial institutions, helping customers recognise their spending before confusion becomes a customer service problem.
The £23.5 million problem
The phrase confusion tax may sound informal, but the cost is real.
Moneyhub estimates that banking app transaction disputes cost UK banks around £23.5 million, just to investigate.
That figure refers to the operational costs of handling disputes, including administrative, investigative, and customer service time. It does not include the wider cost of chargebacks, payment reversals, compensation, or customer churn.
That distinction matters and shouldn’t be overlooked. The money is being spent before the bank even knows whether the transaction is fraud, friendly fraud, or simply a legitimate transaction the customer does not recognise.
The Payments Association reported that chargebacks linked to confusing billing descriptors cost UK merchants more than £128 million each year. It also cited research showing that 58% of cardholders sometimes find statement descriptions confusing, with unrecognised transactions a leading reason customers dispute charges.
It definitely gives financial institutions a clear warning. If the customer cannot connect the transaction to their memory of the purchase, the bank becomes the first port of call.
Customers pay with anxiety
For customers, an unrecognised transaction feels urgent. A strange merchant name, a vague payment description, or a delayed transaction can appear to be fraudulent.
Even if the payment is genuine, the customer has no way to know that quickly.
That creates a poor customer experience in the moment:
- They pause what they are doing
- They search old receipts or emails
- They call customer service
- They may block a card unnecessarily
- They lose confidence in the app
Our merchant identification glossary explains why this problem happens. Merchant identification is the process of associating the correct business name with a transaction in the banking app, but the information is not standardised across providers, payment gateways, and banks.
That gap matters because customers do not think in merchant IDs, legal entities, or payment references. They remember the shop, brand, or place where they spent money. When the app shows an unclear or unfamiliar name, a legitimate transaction can quickly look suspicious.
You can see this isn’t a payment problem; it’s a trust problem.
Banks absorb the operating cost
Every unnecessary dispute creates work. A customer service agent may need to take the call, reassure the customer, check the transaction, review merchant information, explain the outcome, and document the case.
If the customer escalates the issue, more teams may become involved.
The cost builds through:
- Customer service calls
- Fraud team reviews
- Dispute investigation
- Case handling and administration
- Follow-up communication
- Internal reporting
Some of those checks are essential when fraud is genuine. But when the transaction is legitimate and the problem is poor presentation, the bank is spending money to solve a data clarity issue.
Poor data can create wider customer friction
The cost does not stop at the dispute queue. If transactions are miscategorised, poorly labelled, or missing context, the same data can affect how the bank understands the customer. That can lead to weaker insight across product recommendations, affordability assessments, financial wellbeing tools, and customer segmentation.
A customer who regularly spends on travel may appear to spend heavily on ‘miscellaneous’ payments. A takeaway order may be confused with a taxi journey if the brand name alone is not enough. A subscription may appear to be from an unfamiliar merchant if the trading name is shown instead of the brand the customer remembers.
Those small data gaps can create larger problems:
- Customers receive less relevant support
- Product offers become less accurate
- Affordability analysis may miss useful context
- Customers lose trust in app-based insights
- Banks lose opportunities to build primacy
The FCA’s Consumer Duty work keeps customer understanding firmly on the table. Its 2026 good practice update says firms should make communication design, testing, monitoring, and governance a coherent end-to-end process.
Clear transaction data sits neatly inside that expectation. If the customer cannot understand their own spending, the app is not doing enough of the work.
3 scenarios that cause dispute costs
Not every transaction dispute starts in the same place. Some customers genuinely think they have been defrauded. Some know the data is weak and choose to challenge a legitimate transaction. A smaller group are dealing with true fraud.
Each route creates costs for the bank.
1. The customer genuinely thinks they have been defrauded
This is a classic example of a transaction confusion case.
The customer sees a payment they do not recognise and assumes the worst. The merchant name may be a parent company, a payment processor, an abbreviation, a trading name, or a string of letters and numbers.
From the customer’s perspective, the reaction is understandable. Their account shows money leaving, and they do not recognise the merchant. The safest option is to contact the bank.
The issue is that many of these cases are legitimate transactions. The customer may have bought something online, used a delivery app, paid through a marketplace, or shared an account with a family member.
The crux of the problem lies in poor accuracy and unrecognisable transaction displays. The customer doesn’t have all the information they need to recognise the purchase, and without added enrichment like merchant names, logos and maps, they’re left in limbo.
And the bank still has to investigate.
2. The customer knows the data is poor
This scenario is where transaction confusion overlaps with friendly fraud – the intentional dispute of a legitimate transaction. Also known as liar buyer fraud, the customer knows they made the purchase, but the transaction data is poor enough to get away with their false claim of fraud.
If the merchant name is unclear, the location is missing, the category is vague, and the payment description offers no useful clues, the customer may believe they can challenge the payment with a lower chance of being pushed back – leading to transaction fraud.
But the cost of this poor data lands with multiple parties. Merchants face chargeback losses and admin costs. Banks handle the dispute process. And ironically, customers who genuinely need help with fraudulent transactions may face slower support because teams are dealing with avoidable cases.
3. The customer disputes a true fraud transaction
True payment fraud is still a financial crime, and banks need to treat it seriously. But transaction fraud detection is only part of the story behind disputes.
If every unrecognised transaction is treated as a fraudulent transaction until proven otherwise, teams spend too much time investigating legitimate payments that could have been recognised earlier with better data.
The larger operational problem is the genuine spending question customers ask because the banking app does not provide enough context.
That is the balance banks need to strike. Better transaction data helps to protect customers from fraud without creating a system that leads to unnecessary investigations driven by poor transaction presentation.
Why customers get confused
For a deeper breakdown of the causes behind transaction confusion, read our guide to the 9 reasons why customers do not recognise their transactions. But three common patterns are worth calling out:
- Poor merchant normalisation
- Not enough context around the transaction
- Enrichment happens too late
Poor merchant normalisation
Customers remember brands, shops, locations, and moments. Banking systems often show merchant IDs, legal entities, payment processors, or trading names. That creates a recognition gap.
There is one major reason why customers struggle to recognise transactions: raw Merchant IDs can create a high cognitive load because they do not align with the customer’s mental model of the purchase.
A customer may remember buying coffee near their office, they’re less likely to remember (or even know) the café owner’s legal name.
Not enough context around the transaction
A merchant name alone is not always enough. Customers typically need category, logo, location, payment channel, and timing to connect the transaction to the purchase.
This is especially important for online transactions, delivery apps, subscriptions, marketplaces, and shared household spending, where users are not necessarily present during the purchase.
A brand name can still be ambiguous. An Uber payment could be a trip or an Uber Eats order. A customer may remember the action, not the platform.
That is why consumer clarity depends on more than surfacing a cleaner name.
Enrichment happens too late
If transaction enrichment happens in batches at the end of the day, customers are left in limbo.
The moment of recognition usually happens close to the moment of spending. If the banking app sends a real-time notification with clear purchase details, the customer can connect the payment to the transaction they just made.
If the data arrives later, confusion has more time to grow.
This is where real-time enrichment matters. It reduces the gap between payment and recognition, which limits the window for unnecessary disputes.
Stop making customers investigate their own spending
Transaction confusion is not a small user experience issue. It creates customer anxiety, unnecessary service demand, false dispute activity, and weaker insight across the bank.
The fix starts at the data layer.
Clear merchant names, better categorisation, useful context, and real-time enrichment help customers recognise legitimate transactions before they call the financial institution. That protects the customer journey and reduces the operational drag of avoidable disputes.
About Matt Barr
Matt Barr is a Product Director here at Moneyhub. He’s been working either with or for banks since the mid-00s, solving all manner of problems. From ISA transfers to corporate actions, Matt now focuses on transaction categorisation and enrichment. When he’s not solving client problems, you can find Matt buried under his children’s laundry or stomping through the Peak District.
FAQs
Banks can limit unnecessary transaction disputes by showing customers clearer merchant names, categories, locations, logos, and real-time spending notifications inside the banking app.
Transaction confusion creates direct investigation costs, increased customer service demand, avoidable dispute handling, and broader customer relationship friction when people lose trust in the transaction data their bank shows.
share
