# Submit Dispute Evidence 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. Endpoint: POST /disputes/{dispute_id}/submit Version: 2022-02-01 Security: BasicAuth ## Path parameters: - `dispute_id` (string, required) ID of Dispute to move forward and submit evidence. ## Header parameters: - `Finix-Version` (string) Specify the API version of your request. For more details, see Versioning. Example: "2022-02-01" - `Content-Type` (string) The data type being sent in the request body must be application/json. Example: "application/json" ## Request fields (application/json): - `note` (string, required) Include a note to explain the evidence files and the rebuttal of the Dispute. 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) 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 Example: "TRxxxxxxxxx" - `amount` (integer,null) 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. ## Response 202 fields (application/json): - `id` (string) The ID of the resource. - `created_at` (string) Timestamp of when the object was created. - `updated_at` (string) 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` (string) 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: An issue occurred. User action is required. Any of the following issues could have occurred: - There was an error in the system and the user should retry uploading their evidence file. - There is an issue with the file and the user should retry uploading a different file. - There is an issue and the user should contact Support. Enum: "PENDING", "SUCCEEDED", "CANCELED", "FAILED" - `identity` (string) The ID of the seller's Identity resource. This is the Identity resource that was used to create the seller's Merchant. Example: "IDpYDM7J9n57q849o9E9yNrG" - `merchant` (string) The ID of the seller's Merchant resource. This is the Merchant account the Dispute was filed against. Example: "MUucec6fHeaWo3VHYoSkUySM" - `tags` (object,null) 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. - `_links.self` (object) Link to the resource that was used in the request. - `_links.self.href` (string) ## Response 400 fields (application/json): - `total` (integer, required) Total number of errors returned. - `_embedded` (object, required) Container for embedded error objects. - `_embedded.errors` (array) List of individual error objects. - `_embedded.errors.code` (string) The error code. The UNKNOWN error code is returned for a 401 Unauthorized or 403 Forbidden request. - `_embedded.errors.logref` (string) A log reference identifier for the error, useful for debugging and support purposes. - `_embedded.errors.message` (string) A human-friendly error message. - `_embedded.errors._links` (object) Links related to this error. - `_embedded.errors._links.self` (object) Link to the resource related to the error. - `_embedded.errors._links.self.href` (string) URL of the related resource. ## Response 401 fields (application/json): - `total` (integer, required) Total number of errors returned. - `_embedded` (object, required) Container for embedded error objects. - `_embedded.errors` (array) List of individual error objects. - `_embedded.errors.code` (string) The error code. The UNKNOWN error code is returned for a 401 Unauthorized or 403 Forbidden request. - `_embedded.errors.logref` (string) A log reference identifier for the error, useful for debugging and support purposes. - `_embedded.errors.message` (string) A human-friendly error message. - `_embedded.errors._links` (object) Links related to this error. - `_embedded.errors._links.self` (object) Link to the resource related to the error. - `_embedded.errors._links.self.href` (string) URL of the related resource. ## Response 403 fields (application/json): - `total` (integer, required) Total number of errors returned. - `_embedded` (object, required) Container for embedded error objects. - `_embedded.errors` (array) List of individual error objects. - `_embedded.errors.code` (string) The error code. The UNKNOWN error code is returned for a 401 Unauthorized or 403 Forbidden request. - `_embedded.errors.logref` (string) A log reference identifier for the error, useful for debugging and support purposes. - `_embedded.errors.message` (string) A human-friendly error message. - `_embedded.errors._links` (object) Links related to this error. - `_embedded.errors._links.self` (object) Link to the resource related to the error. - `_embedded.errors._links.self.href` (string) URL of the related resource. ## Response 404 fields (application/json): - `total` (integer, required) Total number of errors returned. - `_embedded` (object, required) Container for embedded error objects. - `_embedded.errors` (array) List of individual error objects. - `_embedded.errors.code` (string) The error code. The UNKNOWN error code is returned for a 401 Unauthorized or 403 Forbidden request. - `_embedded.errors.logref` (string) A log reference identifier for the error, useful for debugging and support purposes. - `_embedded.errors.message` (string) A human-friendly error message. - `_embedded.errors._links` (object) Links related to this error. - `_embedded.errors._links.self` (object) Link to the resource related to the error. - `_embedded.errors._links.self.href` (string) URL of the related resource. ## Response 406 fields (application/json): - `total` (integer, required) Total number of errors returned. - `_embedded` (object, required) Container for embedded error objects. - `_embedded.errors` (array) List of individual error objects. - `_embedded.errors.code` (string) The error code. The UNKNOWN error code is returned for a 401 Unauthorized or 403 Forbidden request. - `_embedded.errors.logref` (string) A log reference identifier for the error, useful for debugging and support purposes. - `_embedded.errors.message` (string) A human-friendly error message. - `_embedded.errors._links` (object) Links related to this error. - `_embedded.errors._links.self` (object) Link to the resource related to the error. - `_embedded.errors._links.self.href` (string) URL of the related resource.