---
title: "Submit dispute response"
method: POST
path: "/api/disputes/v2.0/responses"
tags: ["Dispute Responses"]
---

# Submit dispute response

`POST /api/disputes/v2.0/responses`

Submit a response for a specific dispute case, with optional text comments and supporting evidence files.

## Request body

- object
  - `ResponseType` integer — Indicates whether the merchant’s response is accepted or declined. Example: 1 for Accepted, 2 for Declined.
  - `CaseNumber` string — The unique dispute case identification number eligible for Chargeback or Retrieval cases. The dispute case must be Awaiting Response or New Activity.
  - `Response` string — The message provided by the merchant for the dispute case. Free text up to 500 characters.
  - `evidences` string[] — One or more evidence files included with the dispute case response.

## Response `202`

Accepted

- UploadEventResponse — Response containing upload event details for a submitted dispute case response.
  - `attachments` Attachment[], nullable — List of uploaded evidence file details.
    - `merchantNumber` string, nullable — The merchant's unique identification number associated with the attachment.
    - `attachmentId` integer — Unique identifier for the evidence attachment.
    - `fileName` string, nullable — The name of the uploaded evidence file.
    - `filePath` string, nullable — The storage location or path of the uploaded file.
    - `uploadedDateTime` string, nullable — The date and time when the evidence file was uploaded. Format: YYYY-MM-DDThh:mm:ss.sssZ.
  - `responseId` integer — Unique identifier for the submitted merchant response.
  - `responseMessage` string, nullable — A message confirming the status of the submitted response.
  - `caseNumber` string, nullable — Unique dispute case identification number associated with the submitted response.
  - `exchangeId` string, nullable — Identifier used to track the exchange of information with the dispute processing system.
  - `correlationId` string, nullable — Unique identifier used for tracking the request across systems.
  - `parentId` string, nullable — Identifier that links the response to a parent transaction or message.
  - `parentSystemCode` string, nullable — System code for the upstream system that originated the request.
  - `merchantNumber` string, nullable — The merchant's unique identification number.

## Other responses

- `204` — No Content
- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `406` — Not Acceptable
- `500` — Server Error

---

[API](https://skmtc.net/xplorpay/apis/external-us-onboarding-workflow.md) · [All operations](https://skmtc.net/xplorpay/apis/external-us-onboarding-workflow/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/xplorpay/external-us-onboarding-workflow/versions/f37077c24b66/schema)