# Chargebacks
source: https://developer.mastercard.com/mastercom-extended/documentation/use_cases/chargebacks/index.md

The following use cases explain how to update or reverse a chargeback.

For more information, refer to the [Chargebacks](https://developer.mastercard.com/mastercom-extended/tutorial/chargebacks/index.md) tutorial.
Note: In the following graphics, optional steps are denoted with dashed arrows instead of solid arrows.

## Update (acknowledge) a chargeback {#update-acknowledge-a-chargeback}

Acquirers use this endpoint to acknowledge a chargeback, which moves the claim to the Acquirer Worked queue. Acquirers may take further actions on acknowledged claims.

*Applicable only for customers in India processing domestic disputes* :   

Issuers use this endpoint to acknowledge a rejected chargeback that was previously submitted. This moves the claim from the Reject queue to the Issuer Worked queue.
Diagram chargeback_update Diagram chargeback_update_ios
API Reference: `PUT /claims/{claim_id}/chargebacks/{event_id}`

## Reverse a chargeback {#reverse-a-chargeback}

Issuers use this endpoint to reverse existing chargebacks.
Diagram chargeback_rev
API Reference: `POST /claims/{claim_id}/chargebacks/{event_id}/reversals`

## Update (acknowledge) a chargeback reversal {#update-acknowledge-a-chargeback-reversal}

\**Applicable only for customers in India processing domestic disputes.*

Issuers use this endpoint to acknowledge a rejected chargeback reversal that was previously submitted. This moves the claim from the Reject queue to the Issuer Worked queue.
Diagram chargeback_updaterev
API Reference: `PUT /claims/{claim_id}/chargebacks/{event_id}/reversals`