How Banks Handle Complaints and Disputed Transactions

Complaint handling begins by defining the question correctly

“My bank is wrong” is understandable but operationally too broad. The first useful step is to identify the object in dispute.

• Was a fee applied incorrectly?
• Was a transaction unauthorised?
• Did a transfer fail or arrive late?
• Was an interest rate calculated incorrectly?
• Did the bank fail to follow an agreed instruction?
• Was a product or risk described inadequately?
• Did the bank restrict the account without a sufficient basis?
• Was a complaint itself handled poorly?

Different questions require different evidence and different legal or contractual rules.

The complaint file is a small forensic case

A useful complaint file can include:

• customer identity and account details;
• the disputed transaction or charge;
• timestamps;
• statements;
• payment or card records;
• authentication events;
• device or channel information where relevant;
• terms and fee schedules in force at the time;
• recorded calls or secure messages where lawfully available;
• customer-submitted documents;
• earlier complaints and bank responses;
• external payment or merchant information where relevant.

The point is not to drown the case in data. It is to preserve the evidence needed to answer the actual disputed question.

The first customer statement matters because memories degrade

A customer who discovers a disputed card transaction should report what they know while details are still fresh: where they were, whether the card or device was in their possession, what messages they received and when they first noticed the event.

Later recollection can be influenced by stress, repeated conversations and new information. Early factual records therefore help both customer and bank.

The bank’s system record is evidence, not infallible truth

A system can record that a transaction used correct credentials. That does not automatically prove the legitimate customer intended the payment.

Conversely, a customer’s belief that they did not authorise a payment does not automatically establish how the transaction was executed.

Good investigation compares independent evidence rather than declaring one source unquestionable.

Read Account Takeover | How Identity Failure Becomes Banking Loss.

A disputed transaction has several possible states

Possible state	What the investigation asks
Bank processing error	Did the bank post, duplicate, route or calculate something incorrectly?
Merchant or counterparty dispute	Was the payment authorised but the underlying goods or service disputed?
Unauthorised transaction	Did someone act without the customer’s authority?
Authorised scam payment	Did the legitimate customer authorise the transfer after deception?
Contractual charge	Was the fee or interest correctly applied under the terms?
Legal restriction	Did law, sanctions, court process or another obligation constrain the transaction?
Operational delay	Did payment infrastructure or system failure cause the outcome?

One customer statement—“the bank took my money”—can therefore hide several different mechanisms.

Authorised and unauthorised are not always obvious from the screen

A transaction can pass authentication because an attacker gained control of the customer’s device or credentials. Another transaction can be genuinely authorised by the customer after a scammer deceived them about the purpose.

The legal and loss-allocation consequences can differ substantially.

who pressed confirm, who controlled the identity, and what the customer intended are related but separate questions.

Card disputes can involve a merchant, acquirer, network and issuer

A card transaction is not only between customer and bank. The merchant, acquiring bank, card network and issuing bank can all hold relevant records.

A dispute can therefore take time because the issuing bank may need information from another participant before deciding whether a refund, reversal or chargeback route is available.

Read How a Card Payment Is Reversed | Refunds, Disputes and Chargebacks.

A refund and a chargeback are different

A merchant refund is a new transaction returning value. A chargeback is a scheme-based dispute process through which a card transaction can be challenged under the applicable rules.

The customer should not assume every disagreement qualifies for chargeback or that a chargeback outcome is identical to a legal judgment about the underlying contract.

Bank transfer disputes are structurally different from card disputes

A bank transfer may become final through a payment system without a merchant-acquirer-card-network chargeback layer. Recovery can depend on whether the transfer is still pending, whether the receiving institution can recall or freeze funds, whether the recipient cooperates and what law applies.

Payment finality therefore matters to dispute options.

Read A Payment Instruction Is Not Yet Settlement.

A duplicate transaction is a reconciliation problem

If the customer is charged twice for one intended event, the bank or payment participants need to identify whether two instructions existed, whether one message was duplicated or whether a merchant submitted twice.

The correct fix depends on which ledger created the duplicate.

Read Bank Reconciliation.

Fee disputes need the terms in force at the time

A customer can see a S$30 charge and believe it is wrong. The bank needs to identify the fee trigger, applicable schedule and any waiver or promotion.

Important evidence can include notice of changes, minimum-balance calculations, payment date, card membership date and the customer’s qualification for a waiver.

Read Banking Fees.

Interest disputes are often calculation disputes

The customer can dispute an interest amount because of:

• wrong rate;
• wrong balance;
• wrong number of days;
• wrong benchmark reset;
• incorrect payment allocation;
• failure to apply a promised promotional rate;
• misunderstanding of compounding or repayment structure.

The bank should be able to reconstruct the calculation from contractual inputs.

Product-sale complaints ask what the customer was told before acceptance

A customer may allege that important risks, fees or product features were not explained, or that a representative made a misleading statement.

The investigation can therefore examine disclosure documents, call recordings, messages, signed forms and the product’s actual terms.

Read Why Banking Terms and Disclosures Matter Before a Customer Says Yes.

The complaint handler should be able to challenge the original decision

If the same person who made a decision simply repeats it without independent review, the complaint process adds little.

Good governance creates enough separation that a complaint can expose error, weak judgement or poor explanation in the original handling.

This is the conduct version of Segregation of Duties: independent challenge protects system truth.

Acknowledgement and resolution are different

A bank can acknowledge receipt quickly while the investigation takes longer. Customers should understand whether the bank is saying “we received your complaint” or “we have completed our investigation.”

The ABS Code distinguishes these stages by expecting prompt acknowledgement and a later status update if investigation is still ongoing.

Third-party evidence can extend the timeline

A bank may need a merchant, correspondent bank, card network, receiving institution or technology provider to supply information.

The customer experiences one dispute. Operationally, several institutions may need to reconcile their records.

A good status update tells the customer what is still unresolved

“We are investigating” is less useful than an explanation such as:

• the disputed transaction has been identified;
• the bank has requested merchant evidence;
• the account has been secured;
• the bank is waiting for the payment-network response;
• the customer will be updated by a stated date.

Transparency reduces uncertainty even before the outcome is final.

Temporary credit is not the same as final resolution

In some products or circumstances, a bank or payment scheme can provide a provisional or temporary credit while a dispute is investigated. That credit can be reversed if the investigation later finds the claim unsupported under the applicable rules.

Customers should distinguish temporary access to funds from a final finding of liability.

The bank’s final response should explain the reason, not only the verdict

A useful final response identifies the issue, relevant evidence, applicable terms or rules, outcome and next available escalation route.

A bare “claim rejected” leaves the customer unable to understand whether the bank misunderstood the facts or applied a rule the customer did not know existed.

The customer can strengthen a complaint by separating facts from conclusions

A strong complaint can state:

1. what happened;
2. when it happened;
3. which amount or transaction is disputed;
4. what the customer expected;
5. which evidence supports that expectation;
6. what remedy the customer is asking for.

This gives the bank a resolvable question rather than a general expression of frustration.

Preserving evidence matters more than sending twenty messages

Useful evidence can include statements, screenshots, receipts, correspondence, transaction references and the exact version of terms or promotional material.

Repeated complaints without new facts can add volume without improving the case.

Security should be handled before reimbursement debate

If an account may be compromised, the first operational priority is to prevent further unauthorised activity: secure credentials, stop cards where appropriate, review devices and contain the breach.

The liability debate can continue afterward. Leaving the account exposed while arguing about the first loss can create the second loss.

Complaint handling is also a risk-sensing system for the bank

One complaint can be individual. One thousand similar complaints can reveal a system defect, misleading disclosure, fraud pattern or broken process.

Banks should therefore aggregate complaints by product, cause, channel and outcome rather than treating every case as an isolated customer-service ticket.

complaint data is operational evidence about where the banking promise is failing in the real world.

Root-cause analysis asks why the complaint existed at all

Refunding one fee fixes one account. If the same fee was wrongly applied to ten thousand accounts because of a system error, the real repair is broader.

Root-cause analysis asks whether the failure lives in:

• product design;
• terms or disclosure;
• software;
• staff training;
• fraud controls;
• data;
• vendor operations;
• customer communication;
• governance or incentives.

The remedy should match the failure

Failure	Possible repair
Incorrect fee	Reverse or recalculate the charge and correct the system if needed.
Processing error	Correct the ledger and reconcile downstream effects.
Misleading disclosure	Address customer loss where appropriate and repair the disclosure or sales process.
Account compromise	Secure the identity state, investigate transactions and determine liability.
Service outage	Restore service, reconcile transactions and handle consequential complaints under applicable rules.
Correct bank action poorly explained	Provide a clear explanation even if no financial correction is due.

Not every complaint should end in customer reimbursement

A bank can apply a clearly disclosed fee correctly, decline credit within lawful policy or refuse a transaction because of a valid legal restriction.

Fair complaint handling does not mean the customer always wins. It means the customer receives a serious, evidence-based review and an intelligible explanation.

Not every bank rejection proves the bank was right either

Systems make mistakes. Staff misunderstand facts. Fraud detection can generate false positives. Terms can be applied incorrectly. Complaint processes exist because first decisions are not infallible.

Independent challenge is valuable precisely because correction is sometimes necessary.

External dispute resolution provides another layer

When a customer and financial institution remain in dispute after the institution’s process, an external dispute-resolution body can provide an independent route where the case falls within its jurisdiction.

In Singapore, FIDReC — the Financial Industry Disputes Resolution Centre is an independent and impartial alternative dispute-resolution institution. It encourages resolution through mediation and, for eligible disputes, adjudication.

As checked on 4 September 2026, FIDReC states that adjudication has a limit of S$150,000 per claim, subject to its Terms of Reference, eligibility requirements and exclusions. Customers should use FIDReC’s current website for live jurisdiction and filing rules.

FIDReC is not simply another bank complaint desk

The institution is external to the bank. Its role is to help resolve eligible disputes between consumers and participating financial institutions through an alternative process.

The exact route can include early resolution, mediation and adjudication depending on the matter and current rules.

Use FIDReC’s Consumer’s Guide to Banking Disputes for a public introduction to common banking-dispute categories.

Deadlines matter

Bank terms, payment rules, card-scheme rules, legal limitation periods and external dispute-resolution frameworks can all contain time limits.

A customer should therefore report problems promptly and check the live deadline relevant to the particular dispute rather than assuming the issue can be raised indefinitely.

The complaint route should not become an obstacle course

Customers should be able to find where to complain, what information is needed, how the bank will communicate and how to escalate.

A process designed mainly to exhaust the customer undermines trust even if the underlying banking decision was correct.

Vulnerable customers may need a different communication approach

Language, disability, age, digital access, financial distress or emotional impact can affect a customer’s ability to present a complaint coherently.

Fair handling can require reasonable communication adjustments without changing the evidential standard of the case.

A scam victim and the bank can both have partial truths

The customer may truthfully say, “I never intended to give money to a scammer.” The bank may truthfully say, “The payment was authenticated through the customer’s device and confirmation.”

The dispute then turns on the applicable rules, warnings, control design, customer actions, transaction context and any allocation framework—not on deciding which party’s emotional account is sincere.

This is one reason scam disputes have become a major share of modern banking complaints in Singapore. FIDReC reported in November 2025 that fraud and scam-related disputes had risen sharply and were among the largest drivers of claim growth.

A worked unauthorised-card example

A customer notices three overseas card transactions they say they did not make. The bank blocks the card, reviews transaction authentication and merchant data, obtains relevant network evidence and asks the customer for supporting facts.

The investigation eventually concludes whether the transactions were unauthorised under the applicable card and legal framework and what remedy follows.

The important sequence is containment first, evidence second, liability decision third.

A worked bank-transfer example

A customer sends money to the correct account but claims the beneficiary never received it. The bank traces the payment reference, checks whether the instruction was accepted, whether interbank settlement completed and whether the receiving bank credited the beneficiary.

The complaint is a payment-state reconstruction, not initially a fraud case.

A worked fee example

A customer is charged an annual card fee despite believing a lifetime waiver was promised. The bank reviews the original promotion, application record, current terms and any communication promising the waiver.

The dispute turns on what was actually represented and contracted, not on the current standard fee schedule alone.

A worked conduct example

A customer says a banking product was sold as “capital protected” but later suffered loss. The bank reviews the product documentation, sales conversation, risk disclosures and what the customer actually bought.

If the product was misrepresented, the issue is not a market loss alone. It is whether the customer’s decision was shaped by an inaccurate description.

Complaint analytics should feed product governance

A bank that receives repeated complaints about one fee, one digital step or one fraud warning should ask whether the design itself is creating avoidable harm.

Complaint teams therefore should not be isolated from product, operations, risk, fraud and compliance teams.

The World Return: complaints are where the contract meets lived experience

A bank designs products, systems and controls in advance. Customers then use them in unpredictable reality.

Complaints are one of the strongest return channels from that reality. They show where the written promise, system behaviour and human outcome no longer agree.

a mature bank does not treat complaints only as reputation problems; it treats them as evidence about where the operating model may be wrong.

The Wintour House durability test

Cards will change. Payment rails will change. AI complaint agents will change. Fraud methods will change.

The enduring dispute questions remain:

• What exactly is being disputed?
• What evidence exists on both sides?
• Which contract, rule or legal obligation applies?
• What happened in the system, not only on the screen?
• Can the original decision be independently challenged?
• What remedy matches the failure?
• What external escalation exists if disagreement remains?
• What should the bank change if many customers report the same failure?

Eight misconceptions to remove

Misconception	Better model
“A complaint means the bank is wrong.”	A complaint asks for review; evidence determines whether correction is needed.
“The bank’s system record proves customer intention.”	Technical records are important evidence but can require context about identity and authority.
“A card dispute and bank-transfer dispute work the same way.”	Different payment rails have different reversal, settlement and evidence structures.
“A refund means the bank admitted fault.”	Refunds can arise from merchant action, goodwill, scheme rules, provisional credit or formal correction.
“A bank should resolve every complaint immediately.”	Some cases require third-party evidence; prompt acknowledgement and transparent status are different from instant resolution.
“If the first complaint is rejected, there is no further route.”	Internal escalation and eligible external dispute-resolution channels can exist.
“A customer who was scammed must have authorised the economic outcome.”	Technical authorisation and intended economic purpose can diverge.
“Complaints are only a customer-service cost.”	Complaint patterns reveal operational, conduct, fraud and product-design failures.

Observable mastery

1. Why should a complaint begin by defining the disputed object?
2. What kinds of evidence can matter in an unauthorised-transaction dispute?
3. Why can card and bank-transfer disputes follow different routes?
4. Why should complaint review be able to challenge the original decision?
5. What is the difference between acknowledgement, status update and final resolution?
6. How can complaint patterns reveal a system-wide problem?
7. What role can FIDReC play in eligible Singapore disputes?
8. Which dispute questions survive even when banking becomes fully automated?

If those answers connect, complaint handling becomes visible as the bank’s repair court before court: a structured place where records, contracts, systems and human experience are brought back together so the institution can decide whether its first representation of the event was actually correct.

---