Card disputes
A cardholder who does not recognise a purchase, never received the goods, or was charged twice asks the bank to dispute it. You raise the dispute on the purchase, and the card scheme’s process runs from there. The dispute keeps the whole trail in one place: the stage, the clock, the evidence, and every amount it moved.
Raising a dispute
- Open the account the purchase posted to, and go to its transactions.
- On the card purchase, select the Dispute icon.
- Choose the Reason code the scheme files the dispute under.
- Enter the Amount disputed. It may be the whole purchase or part of it.
- Enter what the cardholder says, and select Raise.
The card’s Disputes panel then lists the dispute. Select it to open the dispute.
You can dispute a card purchase or a cash withdrawal at an ATM. You cannot dispute a refund, a reversal, or a posting no card purchase made. A cash advance fee is the bank’s own charge, so it is never part of a dispute.
A dispute is refused when:
| Refusal | Why |
|---|---|
| Another dispute is open on the purchase | One dispute at a time. A second part waits for the first to close. |
| The filing limit has passed | Each reason code is filed within its days of the purchase date, the last day included. |
| The amount is more than is left to dispute | The purchase less the scheme’s reversals and any dispute already won on it. |
| A dispute under the same reason code was lost or withdrawn | It is not raised again under that code. |
The stages
The stages are the card scheme’s. The processor reports most moves; the bank makes the rest.
stateDiagram-v2
[*] --> Raised: the bank raises
Raised --> Represented: the merchant answers with evidence
Represented --> PreArbitration: the bank escalates
PreArbitration --> Arbitration: the merchant holds its ground
Raised --> Closed
Represented --> Closed: the bank concedes, or withdraws
PreArbitration --> Closed
Arbitration --> Closed: the scheme rules
Closed --> [*]
| Stage | Whose move is next | What you can do |
|---|---|---|
| Raised | The merchant’s | Add evidence, withdraw |
| Represented | The bank’s | Escalate to pre-arbitration, Concede, add evidence, withdraw |
| Pre-arbitration | The merchant’s | Add evidence, withdraw |
| Arbitration | The scheme’s | Add evidence, withdraw |
| Closed | Nobody’s | Nothing — the trail stays |
A dispute closes as Won, Lost, Merchant accepted (the merchant conceded), or Withdrawn. It closes only on the processor’s word, never because a clock ran out.
The clock
Each stage sets the date the next move is due, from the reason code’s window for that stage. The dispute shows it as Next move due.
- When the bank’s window is close, a follow-up task goes to your disputes group.
- The day after a due date passes, the dispute reads overdue. The bank may still act.
- If the merchant lets its window lapse, the processor reports the cardholder’s win.
- If the bank lets its window lapse, the processor reports the merchant’s win.
The money
When the cardholder is credited depends on the reason code:
| Reason code credits | The cardholder is credited | If the dispute is lost or withdrawn |
|---|---|---|
| When raised | At once, as the dispute is raised | The credit is taken back by a new debit today |
| When won | When it closes won or the merchant accepts | Nothing was credited, so nothing is taken back |
The credit is always value-dated as the purchase. On a credit card, that means the interest on the disputed amount re-works to nothing, and an interest-free period lost only because of that purchase comes back.
A worked example, on a card purchase of 12,001.00 disputed under a code that credits when raised, with a case fee of 250.00 on the price list:
| Date | What happens | On the account |
|---|---|---|
| 10 September | The purchase | 12,001.00 debited |
| 20 September | The dispute is raised | 12,001.00 credited, value-dated 10 September |
| 12 November | The dispute is lost at arbitration | 12,001.00 debited again, value-dated 12 November, and the case fee of 250.00 |
A lost arbitration charges the case fee. Conceding, a loss before arbitration, and a withdrawal charge no fee.
If the account is not active when money is due — closed or frozen — nothing posts. The dispute records the amount as not posted, a task goes to your disputes group, and the dispute carries on.
When the scheme moves the money between banks, it appears on the processor’s clearing file. The dispute records it under Money as a scheme settlement. It never moves the stage and never posts to the cardholder’s account.
Evidence
Select Add evidence on the dispute’s Evidence panel to record what the bank submitted. The processor holds the submission; the dispute keeps a description, the date, who added it, and the reference. The merchant’s evidence appears there too, when the processor reports it.
Standards
- PSD2 Article 73 asks that an unauthorised payment is refunded, value-dated no later than the debit. A reason code that credits when raised does exactly that. See the standards register row “PSD2 (EU 2015/2366) Article 73”.
- The card schemes’ dispute rules give the stages, the reason codes and their windows. See the register row “Card scheme dispute rules”.
What your organisation configures
- The reason codes it files under, with each code’s category, when it credits, and its windows. See Card dispute reason codes.
- How many days ahead a deadline warns, and the group that receives the tasks.
- The case fee on each price list.
- Whether disputes are switched on at all. With disputes off, the processor handles them alone.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.