Sign in
OpenAPI 3.0.22026-08-061303782.1 MB

67e4dc871bfc

Disputes

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.

post/disputes/{dispute_id}/submit

Headers

Finix-Versionstring
Example:2022-02-01

Specify the API version of your request. For more details, see Versioning.

Content-Typestring
Example:application/json

The data type being sent in the request body must be application/json.

Request body

amountinteger 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.

notestring required

Include a note to explain the evidence files and the rebuttal of the Dispute.

refundstring 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

Example request

{
  "note": "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": "TRxxxxxxxxx"
}

Response

A single Dispute Evidence resource

idstring

The ID of the resource.

created_atstring date-time

Timestamp of when the object was created.

updated_atstring date-time

Timestamp of when the object was last updated.

applicationstring

ID of the Application the resource was created under.

disputestring

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_messagestring 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.

identitystring

The ID of the seller's Identity resource. This is the Identity resource that was used to create the seller's Merchant.

merchantstring

The ID of the seller's Merchant resource. This is the Merchant account the Dispute was filed against.

content_typestring

The MIME type of the uploaded evidence file (e.g. application/pdf, image/jpeg).

extensionstring

The file extension, a suffix at the end of a file_name (letters following last period).

file_namestring

The name of the uploaded evidence file.

tagsTags 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)

Example response

{
  "identity": "IDpYDM7J9n57q849o9E9yNrG",
  "merchant": "MUucec6fHeaWo3VHYoSkUySM",
  "content_type": "application/pdf",
  "extension": "pdf",
  "file_name": "evidence.pdf"
}