If unauthorized activity occurs on a card, you can create a Card Dispute and we’ll work with the card networks to return the funds if appropriate.
The amount of the dispute.
The Card that the Card Dispute is associated with.
The ISO 8601 date and time at which the Card Dispute was created.
The identifier of the Transaction that was disputed.
The Card Dispute identifier.
The idempotency key you chose for this object. This value is unique across Increase and is used to ensure that a request is only processed once. Learn more about idempotency.
If the Card Dispute’s status is lost
, this will contain details of the lost dispute.
The network that the Card Dispute is associated with.
The status of the Card Dispute.
A constant representing the object’s type. For this resource it will always be card_dispute
.
The ISO 8601 date and time at which the user submission is required by. Present only if status is user_submission_required
and a user submission is required by a certain time. Otherwise, this will be nil
.
Card Dispute information for card payments processed over Visa’s network. This field will be present in the JSON response if and only if network
is equal to visa
.
If the Card Dispute’s status is won
, this will contain details of the won dispute.
Return the page of entries after this one.
Limit the size of the list that is returned. The default (and maximum) is 100 objects.
Return results after this ISO 8601 timestamp.
Return results before this ISO 8601 timestamp.
Return results on or after this ISO 8601 timestamp.
Return results on or before this ISO 8601 timestamp.
Filter Card Disputes for those with the specified status or statuses. For GET requests, this should be encoded as a comma-delimited string, such as ?in=one,two,three
.
Filter records to the one with the specified idempotency_key
you chose for that object. This value is unique across Increase and is used to ensure that a request is only processed once. Learn more about idempotency.
The monetary amount of the part of the transaction that is being disputed. This is optional and will default to the full amount of the transaction if not provided. If provided, the amount must be less than or equal to the amount of the transaction.
The files to be attached to the initial dispute submission.
The Transaction you wish to dispute. This Transaction must have a source_type
of card_settlement
.
The network of the disputed transaction. Details specific to the network are required under the sub-object with the same identifier as the network.
The Visa-specific parameters for the dispute. Required if and only if network
is visa
.
The identifier of the Card Dispute.
The identifier of the Card Dispute to submit a user submission for.
The adjusted monetary amount of the part of the transaction that is being disputed. This is optional and will default to the most recent amount provided. If provided, the amount must be less than or equal to the amount of the transaction.
The files to be attached to the user submission.
The network of the Card Dispute. Details specific to the network are required under the sub-object with the same identifier as the network.
The Visa-specific parameters for the dispute. Required if and only if network
is visa
.
The identifier of the Card Dispute to withdraw.
After a Card Dispute is created in production, the dispute will initially be in a pending_user_submission_reviewing
state. Since no review or further action happens in sandbox, this endpoint simulates moving a Card Dispute through its various states.
The dispute you would like to action.
The network of the Card Dispute. Details specific to the network are required under the sub-object with the same identifier as the network.
The Visa-specific parameters for the taking action on the dispute. Required if and only if network
is visa
.