Update a dispute

Changed on

When you get a dispute, contacting your customer is always the best first step. If that doesn’t work, you can submit evidence to help us resolve the dispute in your favor. You can do this in your dashboard, but if you prefer, you can use the API to submit evidence programmatically.

Depending on your dispute type, different evidence fields will give you a better chance of winning your dispute. To figure out which evidence fields to provide, see our guide to dispute types.

post/v1/disputes/{dispute}

Request

  • Base URL: https://api.stripe.com
  • URL: https://api.stripe.com/v1/disputes/{dispute}
  • Auth: one of:
    • HTTP basic
    • HTTP bearer

Path parameters

disputestring required

Response

Successful response.

amountinteger required

Disputed amount. Usually the amount of the charge, but it can differ (usually because of currency fluctuation or because only part of the order is disputed).

createdinteger required

Time at which the object was created. Measured in seconds since the Unix epoch.

currencystring currency required

Three-letter ISO currency code, in lowercase. Must be a supported currency.

enhanced_eligibility_typesstring[] required

List of eligibility types that are included in enhanced_evidence.

idstring required

Unique identifier for the object.

is_charge_refundableboolean required

If true, it's still possible to refund the disputed payment. After the payment has been fully refunded, no further funds are withdrawn from your Stripe account as a result of this dispute.

livemodeboolean required

If the object exists in live mode, the value is true. If the object exists in test mode, the value is false.

metadataobject required

Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format.

object'dispute' required

String representing the object's type. Objects of the same type share the same value.

reasonstring required

Reason given by cardholder for dispute. Possible values are bank_cannot_process, check_returned, credit_not_processed, customer_initiated, debit_not_authorized, duplicate, fraudulent, general, incorrect_account_details, insufficient_funds, noncompliant, product_not_received, product_unacceptable, subscription_canceled, or unrecognized. Learn more about dispute reasons.

status'lost' | 'needs_response' | 'prevented' | 'under_review' | 'warning_closed' | 'warning_needs_response' | 'warning_under_review' | 'won' required

The current status of a dispute. Possible values include:warning_needs_response, warning_under_review, warning_closed, needs_response, under_review, won, lost, or prevented.

Changes

  • e24a26de4188Revision changes
    • breaking

      removed the required property //////////// from the response with the status

    • breaking

      removed the required property ////////// from the response with the status

    • breaking

      removed the required property ////////// from the response with the status

    • breaking

      removed the required property // from the response with the status

    This list may be incomplete.

  • 940a58abcb3dRevision changes
    • breaking

      removed subschema #1 from the request property anyOf list

    • info

      added subschema #1: MetadataParam to the request property anyOf list

Some revisions have not been checked yet.