# MD for: https://www.mercadopago.com.co/developers/es/docs/checkout-pro-orders/chargebacks/manage.md

\# Manage chargebacks Upon receiving a chargeback initiation notification, use the provided data to assist in managing the process. This data will be essential for preparing and submitting the necessary documentation for the dispute. In this stage, analyze the detailed information included in the \[notification\](https://www.mercadopago.com.co/developers/en/docs/checkout-pro-orders/chargebacks/notifications) to understand the specific aspects of the chargeback. Below, we present a diagram that illustrates how the document submission and receipt flow works: 


sequenceDiagram
    participant Server as Merchant server
    participant API as Mercado Pago API

    API->>Server: Chargeback notification
    Server-->>API: HTTP 200
    Server->>API: Get chargeback
    API->>Server: Chargeback response
    Server->>API: Upload supporting documentation
    API-->>Server: HTTP 200
    API->>Server: Chargeback update
    Server-->>API: HTTP 200

:::::AccordionComponent{title="Consult chargeback" pill="1"} Start the process by consulting the chargeback information using your \`case\_id\` or \`payment\_id\` returned in the body of the \[notification configured\](https://www.mercadopago.com.co/developers/en/docs/checkout-pro-orders/chargebacks/notifications) for the \`chargebacks\` topic. Based on the details obtained, prepare the supporting documentation to be submitted to proceed with the chargeback process. > WARNING > > The \`documentation\_required\` field is legacy. Regardless of whether the returned value is \`true\` or \`false\`, always \[submit supporting documentation\](https://www.mercadopago.com.co/developers/en/docs/checkout-pro-orders/chargebacks/management#bookmark\_submit\_supporting\_documentation) to substantiate the chargeback dispute and demonstrate the validity of the sale. ::::TabsComponent :::TabComponent{title="Consult by chargeback ID"} To consult more information about the chargeback, send a request to the :TagComponent{tag="GET" text="/v1/chargebacks/{id}" href="/developers/en/reference/online-payments/checkout-pro/chargebacks/get-chargeback/get" color="accent"} endpoint with your :toolTipComponent\[production Access Token\]{content="Private key of the application created in Mercado Pago, used in the \_backend\_. You can access it in \*Your integrations > Integration data > Production > Production credentials\*."}, using the chargeback \`case\_id\` received in the notification body. \`\`\`curl curl -X GET \\ 'https://api.mercadopago.com/v1/chargebacks/{id}' \\ -H 'Authorization: Bearer ' \\ -H 'X-Caller-Id: ' \`\`\` | Parameter | Type | Description and examples | Requirement | |---|---|---|---| | \`id\` | \_Path. String\_ | Numeric identifier (\`case\_id\`) of the chargeback case returned in the \_body\_ of the \[configured notification\](https://www.mercadopago.com.co/developers/en/docs/checkout-pro-orders/chargebacks/notifications) for chargebacks. For example, \`234000062890459000\`. | Required | | \`Authorization\` | \_Header. String\_ | Refers to your private key, the :toolTipComponent\[production Access Token\]{content="Private key of the application created in Mercado Pago and used in the \_backend\_. You can access it through \*Your integrations > Integration data > Production > Production credentials\*."}. | Required | | \`X-Caller-Id\` | \_Header. Integer\_ | ID of the authenticated user (\`seller ID\`) and owner of the requested resource. For example: \`123456789\`. | Required | Below is an example of a response to the request: \`\`\`json { "id": "234000062890459000", "payments": \[ 86439942806 \], "currency": "ARS", "amount": 1000.50, "reason": "unauthorized", "reason\_id": "6", "coverage\_applied": null, "coverage\_eligible": true, "documentation\_status": "not\_supplied", "documentation": \[\], "date\_documentation\_deadline": null, "date\_created": "2024-02-01T10:30:00.000-03:00", "date\_last\_updated": "2024-10-17T12:48:24.000-04:00", "live\_mode": true } \`\`\` ::: :::TabComponent{title="Consult by payment ID"} To search for all chargeback cases associated with a specific payment, send a request to the :TagComponent{tag="GET" text="/v1/chargebacks/search" href="/developers/en/reference/online-payments/checkout-pro/chargebacks/search-chargebacks/get" color="accent"} endpoint with your :toolTipComponent\[production Access Token\]{content="Private key of the application created in Mercado Pago, used in the \_backend\_. You can access it in \*Your integrations > Integration data > Production > Production credentials\*."}, passing the \`payment\_id\` as a query parameter. \`\`\`curl curl -X GET \\ 'https://api.mercadopago.com/v1/chargebacks/search?payment\_id={payment\_id}' \\ -H 'Authorization: Bearer ' \\ -H 'X-Caller-Id: ' \`\`\` | Parameter | Type | Description and examples | Requirement | |---|---|---|---| | \`payment\_id\` | \_Query. Integer\_ | Mercado Pago payment ID for which chargeback cases are to be searched. It is returned in the \_body\_ of the \[configured notification\](https://www.mercadopago.com.co/developers/en/docs/checkout-pro-orders/chargebacks/notifications) for chargebacks. For example, \`86439942806\`. | Required | | \`offset\` | \_Query. Integer\_ | Index of the first result to return. The minimum and default values are \`0\`. | Optional | | \`limit\` | \_Query. Integer\_ | Maximum number of results per page. The minimum value is \`1\` and the default value is \`10\`. | Optional | | \`Authorization\` | \_Header. String\_ | Refers to your private key, the :toolTipComponent\[production Access Token\]{content="Private key of the application created in Mercado Pago and used in the \_backend\_. You can access it through \*Your integrations > Integration data > Production > Production credentials\*."}. | Required | | \`X-Caller-Id\` | \_Header. Integer\_ | ID of the authenticated user (\`seller ID\`) and owner of the requested resource. For example: \`123456789\`. | Required | Below is an example of a response to the request: \`\`\`json { "paging": { "offset": 0, "limit": 10, "total": 1 }, "results": \[ { "id": "234000062890459000", "payments": \[ 86439942806 \], "currency": "ARS", "amount": 1000.50, "reason": "unauthorized", "reason\_id": "6", "coverage\_applied": null, "coverage\_eligible": true, "documentation\_status": "not\_supplied", "documentation": \[\], "date\_documentation\_deadline": null, "date\_created": "2024-02-01T10:30:00.000-03:00", "date\_last\_updated": "2024-10-17T12:48:24.000-04:00", "live\_mode": true } \] } \`\`\` ::: :::: Below are the possible values of the \`documentation\_status\` field: | Value | Description | |---|---| | \`pending\` | The supporting documentation has not yet been submitted by the seller. | | \`review\_pending\` | The supporting documentation was submitted and is pending review by the Mercado Pago team. | | \`valid\` | The submitted supporting documentation was reviewed and considered valid. | | \`invalid\` | The submitted supporting documentation was reviewed and considered invalid. | | \`not\_supplied\` | No supporting documentation was submitted within the established deadline. | | \`not\_applicable\` | The API classified supporting documentation as not applicable to this case. This status is independent of the legacy \`documentation\_required\` field; submit files when \`documentation\_status\` is \`pending\`. | > NOTE > > For more information about all the parameters available and involved in this chargeback process, visit our :TagComponent{tag="API" text="API Reference" href="/developers/en/reference/online-payments/checkout-pro/overview" color="accent"}. ::::: :::::AccordionComponent{title="Submit supporting documentation" pill="2"} You must always submit supporting documentation to substantiate the chargeback dispute and demonstrate the validity of the sale. These documents allow the Mercado Pago team to analyze the facts and mediate the resolution with the card brand and issuing bank. > WARNING > > Supporting documentation can only be submitted once per case. To confirm whether the case already has documentation submitted, check the :TagComponent{tag="GET" text="/v1/chargebacks/{id}" href="/developers/en/reference/online-payments/checkout-pro/chargebacks/get-chargeback/get" color="accent"} endpoint to confirm that \`documentation\_status=pending\` and that the case can receive files.  
\> Remember that the \`documentation\_required\` field is legacy, so regardless of the returned value, \*\*always submit supporting documentation to substantiate the chargeback dispute\*\*. To submit the evidence files that prove the validity of the sale, send a request to the :TagComponent{tag="POST" text="/v1/chargebacks/{id}/documentation" href="/developers/en/reference/online-payments/checkout-pro/chargebacks/upload-supporting-documentation/post" color="green"} endpoint with your :toolTipComponent\[production Access Token\]{content="Private key of the application created in Mercado Pago, used in the \_backend\_. You can access it in \*Your integrations > Integration data > Production > Production credentials\*."}, using the chargeback \`case\_id\`. \`\`\`curl curl -X POST \\ 'https://api.mercadopago.com/v1/chargebacks/{id}/documentation' \\ -H 'Authorization: Bearer ' \\ -H 'X-Caller-Id: ' \\ -H 'X-Idempotency-Key: ' \\ -F 'file=@/path/to/file/file1.png' \\ -F 'file=@/path/to/file/file2.pdf' \`\`\` | Parameter | Type | Description and examples | Requirement | |---|---|---|---| | \`id\` | \_Path. String\_ | Numeric identifier of the chargeback case (\`case\_id\`) returned in the \_body\_ of the \[configured notification\](https://www.mercadopago.com.co/developers/en/docs/checkout-pro-orders/chargebacks/notifications) for chargebacks. For example, \`234000062890459000\`. | Required | | \`Authorization\` | \_Header. String\_ | Refers to your private key, the :toolTipComponent\[production Access Token\]{content="Private key of the application created in Mercado Pago and used in the \_backend\_. You can access it through \*Your integrations > Integration data > Production > Production credentials\*."}. | Required | | \`X-Caller-Id\` | \_Header. Integer\_ | ID of the authenticated user (\`seller ID\`) and owner of the requested resource. For example: \`123456789\`. | Required | | \`file\` | \_Body. Array\_ | Evidence file(s) (invoices, shipping proofs, screenshots, etc.) in JPEG, PNG, or PDF format. Maximum 10 files with a total size of up to 10 MB. | Required | If the files are successfully submitted, the API will return an \`HTTP 200\` code and the \`documentation\_status\` of the chargeback will be changed to \`review\_pending\`. The response will include the list of uploaded files: \`\`\`json \[ { "type": "collector", "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "url": "https://storage.mlstatic.com/op/123/456789/file1.png", "description": "file1.png" }, { "type": "collector", "uuid": "b2c3d4e5-f6a7-8901-bcde-f12345678901", "url": "https://storage.mlstatic.com/op/123/456789/file2.pdf", "description": "file2.pdf" } \] \`\`\` > NOTE > > For more information about all the parameters available and involved in this chargeback process, visit our :TagComponent{tag="API" text="API Reference" href="/developers/en/reference/online-payments/checkout-pro/overview" color="accent"}. ::::: :::::AccordionComponent{title="View submitted documentation files" pill="3"} After submitting the supporting documentation, you can download the files or access each one individually through the URL available in the \`url\` field of the \`documentation\` \_array\_. To view or download a specific file, send a request to the :TagComponent{tag="GET" text="/v1/chargebacks/documentation/{type}/{uuid}" href="/developers/en/reference/online-payments/checkout-pro/chargebacks/get-supporting-documentation/get" color="accent"} endpoint with your :toolTipComponent\[production Access Token\]{content="Private key of the application created in Mercado Pago, used in the \_backend\_. You can access it in \*Your integrations > Integration data > Production > Production credentials\*."}, replacing \`{type}\` with the document category and \`{uuid}\` with the file's unique identifier. \`\`\`curl curl -X GET \\ 'https://api.mercadopago.com/v1/chargebacks/documentation/{type}/{uuid}' \\ -H 'Authorization: Bearer ' \\ -H 'X-Caller-Id: ' \`\`\` | Parameter | Type | Description and examples | Requirement | |---|---|---|---| | \`type\` | \_Path. String\_ | Document category. The only allowed value is \`collector\`, corresponding to files uploaded by the seller. | Required | | \`uuid\` | \_Path. String\_ | Unique file identifier, obtained from the \`documentation\` \_array\_ in the response of the :TagComponent{tag="GET" text="/v1/chargebacks/{id}" href="/developers/en/reference/online-payments/checkout-pro/chargebacks/get-chargeback/get" color="accent"} endpoint. For example, \`a1b2c3d4-e5f6-7890-abcd-ef1234567890\`. | Required | | \`Authorization\` | \_Header. String\_ | Refers to your private key, the :toolTipComponent\[production Access Token\]{content="Private key of the application created in Mercado Pago and used in the \_backend\_. You can access it through \*Your integrations > Integration data > Production > Production credentials\*."}. | Required | | \`X-Caller-Id\` | \_Header. Integer\_ | ID of the authenticated user (\`seller ID\`) and owner of the requested resource. For example: \`123456789\`. | Required | The file is returned with its original MIME type (\`image/jpeg\`, \`image/png\`, or \`application/pdf\`), allowing it to be rendered directly in the browser or saved locally. > NOTE > > For more information about all the parameters available and involved in this chargeback process, visit our :TagComponent{tag="API" text="API Reference" href="/developers/en/reference/online-payments/checkout-pro/overview" color="accent"}. ::::: :::::AccordionComponent{title="Chargeback resolution" pill="4"} After the supporting documentation is submitted and the analysis by the card brand and the issuing bank is completed, the chargeback resolution is determined and the involved parties are notified. Wait for the Webhook notification regarding the resolution and consult the chargeback again using the :TagComponent{tag="GET" text="/v1/chargebacks/{id}" href="/developers/en/reference/online-payments/checkout-pro/chargebacks/get-chargeback/get" color="accent"} endpoint. After the resolution, the \`coverage\_applied\` field will indicate the result: | Value | Description | |---|---| | \`true\` | The decision was in favor of the seller and the money will be refunded. | | \`false\` | The decision was against the seller and the money will be deducted. | > WARNING > > The chargeback resolution can take up to 6 months, depending on the card brand. :::::