HOW BANKING WORKS · CARDS 16
A card payment can reach settlement and still not be the final economic outcome
Imagine a customer buys a S$240 item by card. The transaction is authorised, cleared and settled. The merchant receives value. Two weeks later the customer returns the item—or claims the transaction was fraudulent, duplicated or not fulfilled.
The card system now needs a reverse path.
That reverse path is not one thing. Refunds, disputes and chargebacks are different mechanisms. They begin from different actors, require different evidence and allocate financial liability differently.
This article completes Batch 04 under the canonical How Banking Works hub by following a card payment backward after the original purchase.
First separate the three mechanisms
| Mechanism | Who usually starts it? | Main purpose |
|---|---|---|
| Refund | Merchant | Return all or part of a completed sale voluntarily. |
| Dispute | Cardholder through issuer | Challenge a transaction or outcome under card-system rules. |
| Chargeback | Issuer through the network process | Reverse or reallocate financial liability to the acquiring side when a valid dispute condition is met. |
The words are sometimes used loosely in everyday conversation. Banking operations need the distinctions because each state triggers different rights, deadlines and ledger entries.
A refund begins with the merchant
A refund is the cleanest reverse path. The merchant agrees that some or all of the purchase value should return to the customer and submits a refund transaction through its acquiring channel.
The refund travels through the card network toward the issuer. The merchant-side settlement position is adjusted. The issuer credits the cardholder’s account according to the product and system rules.
Economically, the merchant is reversing part of the original sale voluntarily. No adversarial finding is required.
A dispute begins with uncertainty
A customer dispute says the recorded transaction does not match the customer’s understanding of what should have happened.
- The customer says the transaction was unauthorised.
- The merchant charged the wrong amount.
- The same transaction appears twice.
- Goods or services were not received.
- A promised refund did not arrive.
- The transaction description is not recognised.
- Other card-network dispute conditions may apply.
The issuer receives the claim and evaluates it under the cardholder agreement, law and network rules. The dispute does not automatically prove the merchant was wrong. It opens an evidence process.
A chargeback is a financial reversal inside that evidence process
If the dispute meets the relevant conditions, the issuer can initiate a chargeback through the card network. Financial liability is moved back toward the acquiring side, and the acquirer may debit or otherwise recover the amount from the merchant under the merchant agreement.
The merchant can often respond with evidence where the rules allow. That response may be called representment or another scheme-specific term. The transaction can therefore move through several states before liability is final.
A chargeback is not the same thing as the cardholder casually cancelling a payment. It is a governed reversal mechanism inside a multi-party contract network.
The reverse path mirrors the forward path
The forward card transaction travels:
cardholder → merchant → acquirer → network → issuer → clearing and settlement.
A dispute often travels backward:
cardholder → issuer → network → acquirer → merchant → evidence → decision → financial adjustment.
The card system therefore needs memory. It must preserve transaction identifiers, authorisation data, merchant details, timestamps, security information and evidence long enough to reconstruct the event after the original sale.
Why settlement finality does not mean economic irreversibility
This is a subtle point. The original interbank settlement can be final under the payment system while a new transaction later reverses the economic result.
The system does not necessarily “undo” history. It creates a new financial event: refund, chargeback or adjustment. The original payment remains part of the audit trail, and the later reversal is recorded separately.
This preserves accounting truth. A bank should not erase the fact that S$240 was paid on Monday merely because S$240 came back on Friday.
Why evidence decides disputes
A card dispute asks what happened. The strongest systems answer with records rather than memory.
- Was the transaction authenticated?
- What merchant and device data were recorded?
- Was the card physically present?
- What was delivered, and when?
- Was a refund promised?
- Did the merchant obtain required consent?
- Were transaction amounts and currencies presented correctly?
- Did the cardholder previously contact the merchant?
The exact evidence requirements depend on the dispute category and scheme rules. The deeper banking principle is stable: a financial claim should be reconstructable from durable evidence.
Why merchants care intensely about chargeback ratios
Chargebacks create costs for merchants and acquiring institutions. A merchant with unusually high dispute rates may indicate fraud, poor fulfilment, confusing billing, aggressive subscription practices or weak customer service.
Acquirers therefore monitor merchant chargeback behaviour. They may require reserves, delay settlement, impose controls or end the relationship if risk becomes unacceptable under contract and scheme rules.
This is merchant credit risk hiding inside payment acceptance: the acquirer may have to return value after the merchant has already received and spent it.
Why fraudulent merchants can create delayed losses
Imagine a fraudulent merchant sells expensive future travel, collects millions in card payments, receives merchant settlement and disappears before providing the service. Cardholders later dispute the transactions.
The acquirer may face chargebacks long after the original sales proceeds left the merchant. This is why acquiring banks care about business models, delivery periods, advance sales and merchant financial strength.
High transaction volume can therefore increase contingent risk rather than simply increase fee revenue.
Why customers should try the merchant route when appropriate
Many ordinary problems can be solved faster by the merchant: wrong size, cancelled service, simple refund or billing correction. A formal dispute is designed for cases that cannot be resolved normally or that fall into specific cardholder-protection categories.
The precise procedure and deadlines depend on the card issuer, card network and law. Customers should use their issuer’s official dispute process rather than assuming every dissatisfaction qualifies automatically for a chargeback.
Provisional credit is not always the final outcome
Depending on the jurisdiction, issuer and dispute type, a customer may receive temporary or provisional credit while an investigation continues. That credit can later become final or be reversed if the evidence does not support the claim.
This is another example of banking states. “Money back in the account” does not always mean the dispute process is finished.
Why refunds can take time even when the merchant approves immediately
A merchant can approve a refund today, but the refund still has to travel through acquiring, network and issuing systems. Batch processing, weekends, currency conversion and internal posting can affect timing.
The customer therefore sees another instance of the same principle developed in Batch 03: instruction and final account state are separated by infrastructure.
Recurring payments create a special dispute problem
Subscriptions and recurring card payments rely on earlier consent continuing across future billing cycles. Disputes can arise over cancellation, unclear renewal, changed amounts or use of stored credentials.
This makes consent a time-dependent object. The bank and merchant need evidence not only that the card was once valid, but that the later charge remained authorised under the agreement.
Chargebacks protect trust—but can also be abused
A dispute system protects cardholders when merchants fail or transactions are unauthorised. It also creates incentives that can be abused if customers falsely claim legitimate purchases were fraudulent or unfulfilled.
The system therefore needs evidence and balanced rules. Protecting one side without allowing the other to respond would simply move fraud rather than reduce it.
Reconciliation becomes harder after reversals
A merchant may have the original sale, processing fee, refund, partial refund, chargeback fee and later representment all connected to one customer event. Banks have their own corresponding ledger entries.
Reconciliation must preserve the chain without netting away the story. The final balance matters, but so does the path by which it was reached.
Read Bank Reconciliation for the proof layer beneath these adjustments.
Four misconceptions to remove
| Misconception | Better model |
|---|---|
| “Refund and chargeback mean the same thing.” | A refund is merchant-initiated; a chargeback is a network dispute mechanism that reallocates liability. |
| “Settlement means a card payment can never change.” | Later transactions can reverse the economic outcome while preserving the original audit trail. |
| “A customer dispute proves the merchant was wrong.” | A dispute opens an evidence process under contractual and network rules. |
| “The merchant alone bears all chargeback risk.” | The acquirer can face contingent exposure and therefore underwrites and monitors merchants. |
A mastery test
- Who normally initiates a refund?
- What starts a dispute?
- How does a chargeback move liability through the card system?
- Why can a settled transaction later be economically reversed?
- Why does an acquirer care about a merchant’s future delivery obligations?
If those answers connect, a reversed card payment stops looking like money travelling magically backward. It becomes a governed second transaction that reallocates a previously settled claim.
Batch 04 — cards
- How a Debit-Card Payment Moves From Customer to Merchant
- How a Credit-Card Payment Works Before the Monthly Bill Arrives
- Issuing Banks and Acquiring Banks | The Two Banking Sides of a Card Purchase
- How a Card Payment Is Reversed | Refunds, Disputes and Chargebacks
Return to How Banking Works to reconnect cards to deposits, credit, clearing, settlement and banking risk.
