# Chargeback Lifecycle & Timelines

A chargeback follows a set path from the moment a customer questions a transaction to the final decision. Names and timelines vary by network and acquirer, but the steps are similar. Acting early and meeting every deadline are the keys to good results.

#### Main stages

* Inquiry or pre dispute. The issuer asks for more details. This can happen through data sharing tools. You respond in near real time with a clear receipt and order data. Many cases end here if the customer recognizes the charge.
* Alerts. You receive an early alert that a dispute was raised. You have a short window to refund and stop shipment or access. If you resolve the alert in time, a network chargeback is usually not created.
* First chargeback or dispute. Funds are debited and a reason code is set. You choose to accept the loss or submit evidence that the charge was valid.
* Representment. You send order, delivery, and policy proof. The issuer reviews and either reverses the chargeback or upholds it.
* Pre arbitration or second chargeback. If one side disagrees with the representment result, the case can move to this stage. You can accept or continue.
* Arbitration. The card network makes a final decision. This is slower and adds fees.

#### Typical timing

* Inquiry responses are real time or within hours.
* Alerts often require action within 24 to 72 hours.
* First chargeback responses are commonly due within a few weeks from the date your acquirer receives the case.
* First chargeback responses are commonly due within a few weeks from the date your acquirer receives the case.
* Issuer review after representment often takes a few weeks.
* Pre arbitration responses are usually due within one to two weeks.
* Arbitration can take one to three months.

#### Operational tips

Stop shipment or access when you refund on an alert. For subscriptions, cancel future rebills. Track every deadline by merchant ID. Watch for duplicates so you do not refund twice. Review outcomes by reason, product, and channel to fix root causes.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.chargebase.co/chargebacks-knowledge-base/chargeback-lifecycle-and-timelines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.