---
title: "Submit Dispute Evidence"
method: POST
path: "/disputes/{dispute_id}/submit"
tags: ["Disputes"]
---

# Submit Dispute Evidence

`POST /disputes/{dispute_id}/submit`

You can submit evidence to the issuing bank, confirming that the `Merchant` has completed submitting evidence and is ready to proceed with the `Dispute`.

Related guides: [Responding to Disputes](/guides/after-the-payment/disputes/responding-to-disputes).

## Headers

- `Finix-Version` string
- `Content-Type` string

## Request body

- SubmitDisputeEvidence
  - `amount` integer, nullable — Enter the amount in cents for the partial dispute you wish to rebut. Use this field only if you are rebutting part of the `Dispute`. The amount must be equal to or less than the disputed amount. If you use this field, provide details in the notes explaining the reason for the partial amount.
  - `note` string, required — Include a note to explain the evidence files and the rebuttal of the `Dispute`.
  - `refund` string, nullable — The ID of a `Transfer`. Use this field only if you are resolving an `INQUIRY` dispute with a proactive refund to the cardholder, or if a refund was made before the `Dispute` but the cardholder did not notice. The value should be the ID of the `Transfer` resource with type `REVERSAL`, or one of the `operation_key` values: - `UNREFERENCED_REFUND` - `CARD_NOT_PRESENT_UNREFERENCED_REFUND` - `CARD_PRESENT_UNREFERENCED_REFUND`

## Response `202`

A single `Dispute Evidence` resource

- DisputeEvidence
  - `id` string — The ID of the resource.
  - `created_at` string, date-time — Timestamp of when the object was created.
  - `updated_at` string, date-time — Timestamp of when the object was last updated.
  - `application` string — ID of the `Application` the resource was created under.
  - `dispute` string — The ID of the `Dispute` associated with the evidence.
  - `state` 'PENDING' | 'SUCCEEDED' | 'CANCELED' | 'FAILED' — The result after uploading evidence. - `PENDING`: The evidence file has not yet been submitted to the processor. No user action is required. - `SUCCEEDED`: The evidence file has been successfully sent to the processor. No further user action is required. - `CANCELED`: The evidence file upload was not completed due to user action. - `FAILED`: The evidence file could not be processed. Check `failure_code` for the specific reason and `failure_message` for a user-safe description of the issue.
  - `failure_code` 'MALWARE_DETECTED' | 'GENERIC_FAILURE' | 'FILE_SIZE_LIMIT_EXCEEDED' | 'TOTAL_COMBINED_FILE_SIZE_LIMIT_EXCEEDED' | 'TOTAL_PAGE_COUNT_LIMIT_EXCEEDED', nullable — The reason the evidence file failed processing. Populated when `state` is `FAILED`; `null` otherwise. - `MALWARE_DETECTED`: The file was flagged for suspicious content and cannot be accepted. - `GENERIC_FAILURE`: An unexpected error occurred. Contact support for details. - `FILE_SIZE_LIMIT_EXCEEDED`: The file exceeds the maximum allowed file size. - `TOTAL_COMBINED_FILE_SIZE_LIMIT_EXCEEDED`: The total size of all uploaded evidence exceeds the maximum combined file size limit. - `TOTAL_PAGE_COUNT_LIMIT_EXCEEDED`: The total number of pages across all uploaded evidence exceeds the maximum allowed page count.
  - `failure_message` string, nullable — A human-readable message explaining why the evidence file failed processing. Populated when `state` is `FAILED`; `null` otherwise. Safe to surface directly in a UI.
  - `identity` string — The ID of the seller's `Identity` resource. This is the `Identity` resource that was used to create the seller's `Merchant`.
  - `merchant` string — The ID of the seller's `Merchant` resource. This is the `Merchant` account the `Dispute` was filed against.
  - `content_type` string — The MIME type of the uploaded evidence file (e.g. `application/pdf`, `image/jpeg`).
  - `extension` string — The file extension, a suffix at the end of a `file_name` (letters following last period).
  - `file_name` string — The name of the uploaded evidence file.
  - `tags` Tags, nullable — Include up to 50 `key: value` pairs to annotate requests with custom metadata. - Maximum character length for individual `keys` is 40. - Maximum character length for individual `values` is 500. (For example, `order_number: 25`, `item_type: produce`, `department: sales`)
  - `_links` object — For your convenience, every response includes several URLs which link to resources relevant to the request. You can use these `_links` to make your follow-up requests and quickly access relevant IDs.
    - `self` object — Link to the resource that was used in the request.
      - `href` string

## Other responses

- `400` — Bad Request. The server cannot process the request due to malformed syntax or invalid data.
- `401` — Unauthorized. Authentication is required and has failed or has not been provided.
- `403` — Forbidden. The client is authenticated but does not have permission to access the resource.
- `404` — Not Found. The requested resource could not be found on the server.
- `406` — Not Acceptable. The server could not accept the submitted request. Confirm how the request was formatted and submitted.

---

[API](https://skmtc.net/finix/apis/finix-api-reference.md) · [All operations](https://skmtc.net/finix/apis/finix-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/finix/finix-api-reference/versions/67e4dc871bfc/schema)