Card dispute reason codes
Every dispute is filed under a card scheme’s reason code. The code decides when the cardholder is credited and how long each party has to act. You keep the list on the Card Dispute Reason Codes settings page.
What a reason code holds
| Field | What it means |
|---|---|
| Scheme and Code | The scheme and its code as the scheme writes it, such as Visa and 10.4 |
| Key | Filled in for you from the scheme and code, such as visa-10-4 |
| Category | The scheme’s group: fraud, authorisation, processing error, or consumer dispute |
| Credit the cardholder | When raised, or When won |
| Filing limit | Days from the purchase date to raise a dispute, the last day included |
| Merchant represents | Days the merchant has to answer a raised dispute |
| Bank responds | Days the bank has to escalate or concede a representment |
| Pre-arbitration | Days the merchant has to answer an escalation |
| Arbitration | Days the scheme takes to rule |
Every window is in calendar days, as the schemes count them, from one day to two years.
The starter list credits fraud codes when raised and everything else when won. For example:
| Code | Category | Credits | Filing | Each contested stage | Arbitration |
|---|---|---|---|---|---|
| Visa 10.4 | Fraud | When raised | 120 days | 30 days | 45 days |
| Visa 13.1 | Consumer dispute | When won | 120 days | 30 days | 45 days |
Changing the list
- Select Add reason code, or Edit on a row.
- Enter the scheme and the code. The key follows them.
- Choose the category and when to credit, and set the windows.
- Select Save.
A code is refused if another row has the same scheme and code, or a window is outside one day to two years. You cannot remove a code, or change its scheme and code, while an open dispute uses it. You can relabel it and change its windows.
Deadlines and the disputes group
On the Card Disputes settings page you set:
- Warn before a deadline — how many days before the bank’s window closes a task is raised. The default is 5.
- Disputes group — the group the tasks are offered to. With no group, the tasks are offered to nobody.
What your organisation configures
Everything on this page is yours: which codes you file under, when each credits, and each window. The schemes change their windows from time to time; you keep the rows current. For an EU bank, PSD2 Article 73 expects unauthorised-use codes to credit when raised.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.