# Submit Dispute Evidence

You can manually submit evidence to the issuing bank to manually move a dispute forward. Use the  endpoint to submit evidence. Making a POST request lets the issuing bank know the seller has completed submitting evidence and is prepared to move forward with the dispute.

Related guides: Responding to Disputes.

Endpoint: POST /disputes/{dispute_id}/submit
Version: 2022-02-01
Security: BasicAuth

## Header parameters:

  - `Accept` (string)

  - `Finix-Version` (string)
    Specify the API version of your request. For more details, see Versioning.
    Example: "2022-02-01"

## Path parameters:

  - `dispute_id` (string, required)
    ID of  to move forward and submit evidence.

## Request fields (application/json):

  - `note` (string, required)
    Include a note to explain the evidence files and explanation for rebut of the
    Example: "Partial rebuttal is due to double charging cardholder due to technical malfunction on point of sale, but we have attached receipt as proof that cardhoder received item."

  - `refund` (string,null)
    ID of a Transfer. 
This field should be used only if you are attempting to resolve INQUIRY dispute by pro-active refund to cardholder, or a refund was made before dispute creation but cardholder did not notice it.
- Value should be the ID of the Transfer resource with a type of REVERSAL.
- Or one of operation_key , ,
    Example: "TRxxxxxxxxx"

  - `amount` (integer,null)
    Amount in cents for the partial amount of the dispute you wish to rebut. 
Use if only partial amount of the Dispute is being rebutted. 
Amount must be equal to or less than the amount of the dispute.
If you use this field please provide details in notes on reason for partial amount.

## Response 202 fields (application/json):

  - `id` (string)
    The ID of the  resource.
    Example: "DIxxxxxxxxxxxxxxxxxx"

  - `created_at` (string)
    Timestamp of when the object was created.

  - `updated_at` (string)
    Timestamp of when the object was last updated.

  - `action` (string,null)
    The next  required to move forward with the .

  - `amount` (integer,null)
    The total amount of the  (in cents).

  - `application` (string)
    The ID of the  resource that the  was created under.

  - `dispute_details` (object)
    Details about the  received by the . Any data from the processor can get included.

  - `dispute_details.case_id` (string,null)
    The case number the  has given the dispute in their internal database.

  - `dispute_details.pin_debit_adjustment_number` (string,null)
    Used by the processor to identify the funds that are getting disputed.

  - `dispute_details.reason_code` (string,null)
    Used by the processor and card networks to identify why the dispute got filed.

  - `evidence_submitted` (string)
    The status of the uploaded evidence. [See  for the next steps to move the  forward](#operation/getDispute).
    Enum: "CHARGEBACK", "NOT_SUPPORTED", "NONE", "UNKNOWN", "INQUIRY"

  - `identity` (string)
    - The ID of the seller's  resource.
- This is the  resource that was used to create the seller's .

  - `merchant` (string)
    - The ID of the seller's  resource. 
- This is the  account the  was filed against.

  - `message` (string,null)
    Message field that provides additional details. This field is typically .

  - `occurred_at` (string,null)
    Point in time when the  that's getting disputed got created.

  - `reason` (string)
    The system-defined reason for the . Available values include:INQUIRYQUALITYFRAUD
    Enum: "CLERICAL", "FRAUD", "INQUIRY", "QUALITY", "TECHNICAL"

  - `respond_by` (string,null)
    Point in time, the  needs to respond to the dispute by.

  - `response_state` (string)
    Details the state of the  and what action the  needs to take.
- : The  needs to respond to the  by . For details on how to respond to a , see [Responding to Disputes](/guides/after-the-payment/disputes/responding-to-disputes).
- : The issuing bank has received the evidence and actively reviewing it. No action needed from the .
- : The  has accepted the . When a  is accepted, you concede that the dispute is not worth challenging or representing. For details on how to accept a , see [Accepting a Dispute](/guides/after-the-payment/disputes/accepting-disputes/).
- : The final  when a  is either  or .
- :  details couldn't be submitted to the processor. Comes up when testing  in sandbox or on the  processor.
    Enum: "NEEDS_RESPONSE", "RESPONDED", "ACCEPTED", "NO_RESPONSE_ALLOWED", "UNKNOWN"

  - `state` (string)
    The current state of the .
    Enum: "INQUIRY", "PENDING", "WON", "LOST"

  - `tags` (object,null)
    Include up to 50  pairs to annotate requests with custom metadata.
- Maximum character length for individual  is 40.
- Maximum character length for individual  is 500.
(For example, , , )

  - `transfer` (string)
    ID of the  resource.
    Example: "TRxxxxxxxxxxxxxxxxxx"

  - `_links` (object)
    For your convenience, every response includes several URLs which link to resources relevant to the request. You can use these  to make your follow-up requests and quickly access relevant IDs.

  - `_links.adjustment_transfers` (object)

  - `_links.adjustment_transfers.href` (string)

  - `_links.application` (object)
    Link to the  the resource was created under.

  - `_links.evidence` (object)

  - `_links.self` (object)
    Link to the resource that was used in the request.

  - `_links.transfer` (object)
    Link to the  realted to the .

## Response 401 fields (application/json):

  - `total` (integer)

  - `_embedded` (object)

  - `_embedded.errors` (array)

  - `_embedded.errors.code` (string)
    Enum: "UNKNOWN"

  - `_embedded.errors.logref` (object)

  - `_embedded.errors.message` (string)

  - `_embedded.errors._links` (object)

  - `_embedded.errors._links.self` (object)

  - `_embedded.errors._links.self.href` (string)

  - `_embedded.errors._links.source` (object)

## Response 403 fields (application/json):

  - `total` (integer)

  - `_embedded` (object)

  - `_embedded.errors` (array)

  - `_embedded.errors.code` (string)
    Enum: "FORBIDDEN"

  - `_embedded.errors.logref` (object)

  - `_embedded.errors.message` (string)

  - `_embedded.errors._links` (object)

  - `_embedded.errors._links.source` (object)

  - `_embedded.errors._links.source.href` (string)

## Response 404 fields (application/json):

  - `total` (integer)

  - `_embedded` (object)

  - `_embedded.errors` (array)

  - `_embedded.errors.code` (string)
    Enum: "NOT_FOUND"

  - `_embedded.errors.logref` (object)

  - `_embedded.errors.message` (string)

  - `_embedded.errors._links` (object)

  - `_embedded.errors._links.source` (object)

  - `_embedded.errors._links.source.href` (string)

## Response 406 fields (application/json):

  - `total` (integer)

  - `_embedded` (object)

  - `_embedded.errors` (array)

  - `_embedded.errors.code` (string)
    Enum: "NOT_FOUND"

  - `_embedded.errors.logref` (object)

  - `_embedded.errors.message` (string)

  - `_embedded.errors._links` (object)

  - `_embedded.errors._links.source` (object)

  - `_embedded.errors._links.source.href` (string)

## Response 422 fields (application/json):

  - `total` (integer)

  - `_embedded` (object)

  - `_embedded.errors` (array)

  - `_embedded.errors.logref` (object)

  - `_embedded.errors.message` (string)

  - `_embedded.errors.code` (string)
    Enum: "UNPROCESSABLE_ENTITY"

  - `_embedded.errors._links` (object)

  - `_embedded.errors._links.self` (object)

  - `_embedded.errors._links.self.href` (string)