POST /v1/issuing/disputes

Creates an Issuing Dispute object. Individual pieces of evidence within the evidence object are optional at this point. Stripe only validates that required evidence is present during submission. Refer to Dispute reasons and evidence for more details about evidence requirements.

Servers

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/x-www-form-urlencoded"

Request body fields

Name Type Required Description
transaction String No

The ID of the issuing transaction to create a dispute for. For transaction on Treasury FinancialAccounts, use treasury.received_debit.

amount Integer No

The dispute amount in the card's currency and in the smallest currency unit. If not set, defaults to the full transaction amount.

expand[] Array No

Specifies which fields in the response should be expanded.

metadata Object No

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. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to metadata.

treasury Object No

Params for disputes related to Treasury FinancialAccounts

treasury.received_debit String Yes
evidence Object No

Evidence provided for the dispute.

evidence.duplicate No
evidence.merchandise_not_as_described No
evidence.not_received No
evidence.canceled No
evidence.service_not_as_described No
evidence.other No
evidence.fraudulent No
evidence.no_valid_authorization No
evidence.reason String No

Possible values:

  • "duplicate"
  • "no_valid_authorization"
  • "other"
  • "service_not_as_described"
  • "merchandise_not_as_described"
  • "not_received"
  • "fraudulent"
  • "canceled"

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.