# Issuing dispute codes

[Issuing disputes](https://www.checkout.com/docs/card-issuing/manage-issuing-transactions/manage-issuing-disputes.md) can have the following statuses and status reasons at the different stages of the dispute lifecycle: chargeback, pre-arbitration, and arbitration.

This page also sets out the response time limits for each dispute reason code.

---

## Chargeback statuses

At the chargeback stage, disputes can have the following `status` and `status_reason` codes from the API and in the [Dispute Lifecycle Report](https://www.checkout.com/docs/card-issuing/retrieve-issuing-reports/dispute-lifecycle-report.md):

| Status | Status reason | Description |
| --- | --- | --- |
| `processing` | `chargeback_pending` | Checkout.com and the card scheme are processing the chargeback. |
| `processing` | `chargeback_processed` | The card scheme processed the chargeback. |
| `action_required` | `chargeback_evidence_invalid_or_insufficient` | Checkout.com or the card scheme requires you to provide further evidence. |
| `action_required` | `chargeback_change_requested` | Checkout.com or the card scheme requested you to amend the chargeback details. |
| `action_required` | `chargeback_fraudulent_reason_code_invalid` | The card scheme rejected the fraud reason code. Amend the dispute with a different reason code. |
| `action_required` | `chargeback_rejected` | The merchant rejected the chargeback, provided evidence, and sent a representment. <br><br>[Review the dispute](https://www.checkout.com/docs/card-issuing/manage-issuing-transactions/manage-issuing-disputes.md#Monitor_the_dispute) and consider the merchant's evidence. <br><br>To accept the evidence, ignore the representment and the dispute is closed with `lost` status. <br><br>To reject the representment, [escalate to pre-arbitration](https://www.checkout.com/docs/card-issuing/manage-issuing-transactions/manage-issuing-disputes.md#Escalate_to_pre-arbitration). |
| `won` | `chargeback_processed` | The merchant accepted or did not respond to the chargeback within the [time limit](https://www.checkout.com/docs/card-issuing/manage-issuing-transactions/manage-issuing-disputes.md#Dispute_time_limits), so you won the dispute. |
| `lost` | `chargeback_rejected` | You did not escalate to pre-arbitration within the time limit. |
| `canceled` | `chargeback_reversed` | You did not create the dispute within the time limit, or you canceled the dispute. |
| `canceled` | `presentment_reversed` | The scheme rejected the dispute because the funds were already reversed.<br><br>**Note**: Do not re-submit the dispute. |

---

## Pre-arbitration statuses

At the pre-arbitration stage, a dispute can have the following `status` and `status_reason` codes from the API and in the Dispute Lifecycle Report:

| Status | Status reason | Description |
| --- | --- | --- |
| `processing` | `prearbitration_pending` | You successfully escalated the dispute and the card scheme is processing the pre-arbitration. |
| `processing` | `prearbitration_processed` | The card scheme processed the pre-arbitration. |
| `action_required` | `prearbitration_evidence_invalid_or_insufficient` | Checkout.com or the card scheme requires you to provide further evidence. |
| `action_required` | `prearbitration_change_requested` | Checkout.com or the card scheme requested you to amend the pre-arbitration details. |
| `action_required` | `prearbitration_fraudulent_reason_code_invalid` | The card scheme rejected the fraud reason code. Amend the dispute with a different reason code. |
| `action_required` | `prearbitration_rejected` | The merchant rejected the pre-arbitration. <br><br>[Review the dispute](https://www.checkout.com/docs/card-issuing/manage-issuing-transactions/manage-issuing-disputes.md#Monitor_the_dispute) again, and decide if you want to [escalate to arbitration](https://www.checkout.com/docs/card-issuing/manage-issuing-transactions/manage-issuing-disputes.md#Escalate_to_arbitration). |
| `won` | `prearbitration_processed` | The merchant accepted or did not respond to the chargeback within the [time limit](https://www.checkout.com/docs/card-issuing/manage-issuing-transactions/manage-issuing-disputes.md#Dispute_time_limits), so you won the dispute. |
| `lost` | `prearbitration_rejected` | You did not request arbitration within the [time limit](https://www.checkout.com/docs/card-issuing/manage-issuing-transactions/manage-issuing-disputes.md#Dispute_time_limits). |

---

## Arbitration statuses

At the arbitration stage, disputes can have the following `status` and `status_reason` codes from the API and in the Dispute Lifecycle Report:

| Status | Status reason | Description |
| --- | --- | --- |
| `processing` | `arbitration_pending` | You successfully requested arbitration and the card scheme is processing it. |
| `processing` | `arbitration_processed` | The card scheme processed the arbitration. |
| `won` | `arbitration_processed` | The card scheme decided the dispute in your favor. |
| `lost` | `arbitration_processed` | The card scheme decided the dispute in the merchant’s favor, and no further action is available. |

---

## Response time limits

The scheme-specific [reason code](https://www.checkout.com/docs/developer-resources/codes/chargeback-codes.md#Mastercard) you provide can alter the standard time limit for raising the dispute as follows:

| Reason code | Description | Time limit |
| --- | --- | --- |
| `4807` | Warning bulletin file | Within 90 calendar days after the transaction's Central Site Business Date (CSBD) |
| `4808` | Authorization-related chargeback | Within 90 calendar days after the transaction CSBD |
| `4812` | Account number not on file | Within 90 calendar days after the transaction CSBD |
| `4831` | Transaction amount differs | Within 90 calendar days after the transaction CSBD |
| `4834` | Point-of-interaction error | Within 120 calendar days after the transaction CSBD |
| `4837` | No cardholder authorization | Within 120 calendar days after the transaction CSBD |
| `4840` | Fraudulent processing of transactions | Within 120 calendar days after the transaction CSBD |
| `4841` | Canceled recurring transaction | Within 120 calendar days after the transaction CSBD |
| `4842` | Late presentment | Within 120 calendar days after the transaction CSBD |
| `4846` | Correct transaction currency code not provided | Within 120 calendar days after the transaction CSBD |
| `4849` | Questionable merchant activity | Within 30 calendar days after the transaction CSBD |
| `4850` | Instalment billing dispute | Within 120 calendar days after the transaction CSBD |
| `4853` | Cardholder dispute | Within 120 calendar days after the latest anticipated delivery or performance date specified by the merchant<br><br>This must not exceed 540 calendar days from the first presentment CSBD. |
| `4854` | Cardholder dispute – Not elsewhere classified <br>(US only) | Within 60 calendar days after first learning about the dispute from the cardholder or within 120 calendar days after the CSBD |
| `4855` | Goods or services not provided | Within 120 calendar days after the latest anticipated delivery or performance date specified by the merchant<br><br>This must not exceed 540 calendar days from the first presentment CSBD. |
| `4859` | Addendum, no-show, or ATM dispute | Within 120 calendar days after the transaction settlement date |
| `4860` | Credit not processed | Within 120-calendar days after the transaction settlement date<br><br>However, if the credit receipt or merchant advisement is dated, the 120-calender day chargeback period begins on the date that the credit was issued, the goods were returned, or the services were canceled. |
| `4863` | Cardholder does not recognize – Potential fraud | Within 120 calendar days after the transaction settlement date |
| `4870` <br> `4871` | Counterfeit transaction, chip liability shift, chip/PIN liability shift | Within 120 calendar days after the transaction settlement date |
| `4999` | Domestic chargeback dispute <br>(Europe only) | Within 120 calendar days after the transaction settlement date |