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

## How representment works {#how-representment-works}

The representment overview diagram displays the steps for the representment process. For more information, refer to the [Representments](https://developer.mastercard.com/mastercom-extended/tutorial/representment/index.md) tutorial.
Note: In the following graphics, optional steps are denoted with dashed arrows instead of solid arrows. Diagram represent_over

**Step 1:** The acquirer searches for claims within a queue from the Acquirer First Chargeback Unworked queue.  

**Step 2:** The acquirer retrieves claim details for a specific claim and its associated events.  

**Step 3:** The acquirer retrieves chargeback documentation.  

**Step 4- optional:** The acquirer acknowledges received chargebacks to move the claim from Acquirer First Chargeback Unworked queue to Acquirer Worked queue.  

**Step 5- optional:** The acquirer uploads documentation.  

**Step 6:** The acquirer creates a representment.  

**Step 7- optional:** The acquirer uploads and attaches the chargeback documentation if not uploaded when the dispute was created.  

**Step 8- optional:** The acquirer retrieves document processing details.  

**Step 9- optional:** The issuer acknowledges received representment to move the claim to the Issuer Worked queue.

## Create a representment {#create-a-representment}

Acquirers use the endpoint to create a representment.
Diagram represent_create
API Reference: `POST /claims/{claim_id}/chargebacks/{event_id}/representments`

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

Issuers use this endpoint to acknowledge a representment, which moves the claim to the Issuer Worked queue. Issuers may take further actions on acknowledged claims.

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

Acquirers use this endpoint to acknowledge a rejected representment that was previously submitted. This moves the claim from the Reject queue to the Acquirer Worked queue.
Diagram represent_update Diagram represent_update_ios
API Reference: `PUT /claims/{claim_id}/representments/{event_id}`

## Reverse a representment {#reverse-a-representment}

Acquirers use this endpoint to reverse existing representments.
Diagram represent_reverse
API Reference: `POST /claims/{claim_id}/representments/{event_id}/reversals`

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

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

Acquirers use this endpoint to acknowledge a rejected representment reversal that was previously submitted. This moves the claim from the Reject queue to the Acquirer Worked queue.
Diagram represent_updaterev
API Reference: `PUT /claims/{claim_id}/representments/{event_id}/reversals`