# Case filing
source: https://developer.mastercard.com/mastercom-extended/documentation/use_cases/casefiling/index.md

The following use cases demonstrate the process of senders and receivers managing pre-arbitration, arbitration, pre-compliance or compliance cases.

For more information, refer to the [Pre-arbitration and arbitration case filing](https://developer.mastercard.com/mastercom-extended/tutorial/casefilingarb/index.md) tutorial and the [Pre-compliance and compliance case filing](https://developer.mastercard.com/mastercom-extended/tutorial/casefilingcomp/index.md) tutorial.
Note: In the following graphics, optional steps are denoted with dashed arrows instead of solid arrows.

## How pre-arbitration and arbitration case filing works {#how-pre-arbitration-and-arbitration-case-filing-works}

The pre-arbitration and arbitration overview diagram demonstrates the process of senders (issuers) and receivers (acquirers) managing pre-arbitration and arbitration cases.
Diagram cf_prearbarb_over

**Step 1-optional:** The sender (issuer) uploads documentation.  

**Step 2:** The sender (issuer) creates a pre-arbitration case.  

**Note:** If pre-arbitration is not required, see step 16 to create an arbitration case.   

**Step 3-optional:** The sender (issuer) retrieves the processing status of the documents associated with the case.  

**Step 4-optional:** The sender (issuer) retrieves the case details.   

**Step 5:** The receiver (acquirer) retrieves claims from the Receiver Case Filing queue.   

**Step 6:** The receiver (acquirer) retrieves the claim to retrieve details for a specific claim and its associated case filing. The claim includes the original chargeback and representment details and documentation.  

**Step 7:** The receiver (acquirer) retrieves case details.   

**Step 8-optional:** The receiver (acquirer) requests documentation for the case.   

**Step 9-optional:** The receiver (acquirer) uploads documentation.  

**Step 10-optional:** The receiver (acquirer) responds to the case to either accept or reject the case.   

**Step 11:** The sender (issuer) retrieves claims from the Sender Case Filing queue.   

**Step 12:** The sender (issuer) retrieves case details.   

**Step 13-optional:** The sender (issuer) retrieves the case documentation.   

**Step 14-optional:** The sender (issuer) updates the case to escalate the case.   

**Step 15-optional:** The sender (issuer) uploads documentation if creating an arbitration case.   

**Step 16:** The sender (issuer) creates an arbitration case.  

**Note:** Dispute Resolution Management is notified of an arbitration case.  

**Step 17:** The receiver (acquirer) retrieves claims from the Receiver Case Filing queue.   

**Step 18:** The receiver (acquirer) retrieves case details.   

**Step 19-optional:** The receiver (acquirer) requests documentation for the case.   

**Step 20-optional:** The receiver (acquirer) uploads documentation.  

**Step 21-optional:** The receiver (acquirer) updates the case to accept the case.  

**Step 22:** The sender (issuer) retrieves claims from the Sender Case Filing queue.   

**Step 23:** The sender (issuer) retrieves case details.   

**Step 24-optional:** The sender (issuer) updates the case to withdraw the case.  

**Note:** Dispute Resolution Management rules on the case.  

**Step 25:** The sender (issuer) retrieves claims from the Sender Case Filing queue.  

**Step 26:** The receiver (acquirer) retrieves claims from the Receiver Case Filing queue.  

**Step 27:** The sender (issuer) or receiver (acquirer) retrieves case details to verify the outcome of the case.  

## Create a new pre-arbitration or arbitration case {#create-a-new-pre-arbitration-or-arbitration-case}

Senders (issuers) use this endpoint to create a pre-arbitration or arbitration case.
Diagram cf_prearb_create
API Reference: `POST /cases/arbitrations`

## Update or respond to a pre-arbitration or arbitration case {#update-or-respond-to-a-pre-arbitration-or-arbitration-case}

Senders and receivers use this endpoint to update or respond to a pre-arbitration or arbitration case. For arbitration cases, senders (issuers) use this endpoint to withdraw an arbitration case, and receivers (acquirers) use this endpoint to accept an arbitration case.
Diagram cf_arb_update
API Reference: `PUT /cases/{case_id}/arbitrations`

## How pre-compliance and compliance case filing works {#how-pre-compliance-and-compliance-case-filing-works}

The pre-compliance and compliance overview diagram demonstrates the process of senders and receivers managing pre-compliance and compliance cases.
Diagram cf_precompcomp_over

**Step 1-optional:** The sender uploads documentation.  

**Step 2:** The sender creates a pre-compliance case.  

**Note:** If pre-compliance is not required, see step 17 to create a compliance case.   

**Step 3-optional:** The sender retrieves the processing status of the documents associated with the case.  

**Step 4-optional:** The sender retrieves case details.   

**Step 5:** The receiver retrieves claims from the Receiver Case Filing queue.   

**Step 6:** The receiver retrieves the claim to retrieve details for a specific claim and its associated case filing. The claim includes the original chargeback and representment details and documentation.   

**Step 7:** The receiver retrieves case details.   

**Step 8-optional:** The receiver requests documentation for the case.   

**Step 9-optional:** The receiver uploads documentation.  

**Step 10-optional:** The receiver responds to the case to either accept or reject the case.   

**Step 11:** The sender retrieves claims from the Sender Case Filing queue.   

**Step 12:** The sender retrieves case details.   

**Step 13-optional:** The sender retrieves the case documentation.   

**Step 14-optional:** The sender updates the case to escalate the case.   

**Step 15-optional:** The sender uploads documentation if creating a compliance case.  

**Step 16:** The sender creates a compliance case.  

**Note:** Dispute Resolution Management is notified of a compliance case.  

**Step 17:** The receiver retrieves claims from the Receiver Case Filing queue.   

**Step 18:** The receiver retrieves case details.   

**Step 19-optional:** The receiver requests documentation for the case.   

**Step 20-optional:** The receiver uploads documentation.  

**Step 21-optional:** The receiver updates the case to accept the case.  

**Step 22:** The sender retrieves claims from the Sender Case Filing queue.   

**Step 23:** The sender retrieves case details.   

**Step 24-optional:** The sender updates the case to withdraw the case.  

**Note:** Dispute Resolution Management rules on the case.  

**Step 25:** The sender retrieves claims from the Sender Case Filing queue.  

**Step 26:** The receiver retrieves claims from the Receiver Case Filing queue.  

**Step 27:** The sender or receiver retrieves case details to verify the outcome of the case.  

## Create a new pre-compliance or compliance case {#create-a-new-pre-compliance-or-compliance-case}

Senders use this endpoint to create a pre-compliance or compliance case.
Diagram cf_precomp_create
API Reference: `POST /cases/compliances`

## Update or respond to a pre-compliance or compliance case {#update-or-respond-to-a-pre-compliance-or-compliance-case}

Senders and receivers use this endpoint to update or respond to a pre-compliance or compliance case.
Diagram cf_comp_update
API Reference: `PUT /cases/{case_id}/compliances`

## Retrieve details for existing case {#retrieve-details-for-existing-case}

Senders and receivers use this endpoint to retrieve details for an existing case.
Diagram cf_retdetails
API Reference: `GET /cases/{case_id}`