POST /v1/issuing/disputes/{dispute}
Updates the specified Issuing Dispute object by setting the values of the parameters passed. Any parameters not provided will be left unchanged. Properties on the evidence object can be unset by passing in an empty string.
Servers
- https://api.stripe.com/
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
dispute |
String | Yes |
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 |
|---|---|---|---|
amount |
Integer | No |
The dispute amount in the card's currency and in the smallest currency unit. |
expand[] |
Array | No |
Specifies which fields in the response should be expanded. |
metadata |
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 |
|
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:
|
How to start integrating
- Add HTTP Task to your workflow definition.
- 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.
- Click Test request to test run your request to the API and see the API's response.