Skip to main content
POST
Challenge disputes

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <secret_key>, where <secret_key> is your secret_key.

Body

application/json
dispute_id
string
required

ID of the dispute

Example:

"uuid"

description
string
required

Comment for Tabby support.

Example:

"Comment for Tabby support"

reason
enum<string>
required

Reason for requesting dispute challenge:

  • merchant_reason_other - there were other problems with the order that required further clarification;
  • merchant_reason_order_on_its_way - the order has been confirmed and is in the process of being delivered;
  • merchant_reason_order_has_been_already_delivered - the order has already been delivered and is complete;
  • merchant_reason_order_amount_should_be_different - there was a problem with the amount of the order and it needed to be changed;
  • merchant_reason_problem_with_delivery - there was a problem with the order during delivery that needed to be adjusted and resolved.
Available options:
merchant_reason_other,
merchant_reason_order_on_its_way,
merchant_reason_order_has_been_already_delivered,
merchant_reason_order_amount_should_be_different,
merchant_reason_problem_with_delivery
Example:

"merchant_reason_other"

amount
string

If the dispute challenged with reason merchant_reason_order_amount_should_be_different - a new disputed amount is required.

Example:

"100"

attachment_ids
string<uuid>[]

Attachment ID that will be attached. ID can be received via upload attachment endpoint.

Response

Success. Disputes were challenged.

disputes
object[]