Dispute Entity🔗

The Dispute entity has the following fields:

id

string Unique identifier of the dispute generated by Razorpay.

entity

string Indicates the type of entity. In this case, it is dispute.

payment_id

string Unique identifier of the payment against which the dispute is created.

amount

integer Amount, in currency subunits, for which the dispute is created.

currency

string 3-letter ISO currency code associated with the amount. Know more about the
list of supported currencies.

amount_deducted

integer The amount, in currency subunits, deducted from your Razorpay current balance when the dispute is lost. This amount will be 0 unless the status of dispute is updated to lost.
Know more about different states of disputes.

gateway_dispute_id

string Unique identifier of the dispute provided by the gateway.

reason_code

string Code associated with the reason for dispute.

reason_description

string Reason for raising the dispute.

respond_by

integer Timestamp (in Unix) by which a response should be sent to the customer.

status

string The status of the dispute. Possible statuses:

• open: Indicates that the dispute has been created.
• under_review: Indicates that the dispute is being reviewed by the issuing bank.
• won: Indicates that the bank has accepted the remedial documents and you have won the chargeback.
• lost: Indicates that the bank did not accept the remedial documents and you have lost the chargeback.
• closed: Indicates that the fraudulent transaction is closed after you either provided the details of the transaction or make a refund to the customer. This is seen in fraudulent transactions only.

phase

string Phase that is associated with the dispute. Possible values:

• fraud: A dispute raised by the bank when it suspects a transaction to be fraudulent based on the risk analysis.
• retrieval: A request initiated by the customer with their issuer bank for additional information about a transaction.
• chargeback: A refund claim initiated by the customers with their issuer banks. In such cases, the bank starts an official inquiry.
• pre_arbitration: A chargeback that you have won is challenged by the customer for the second time.
• arbitration: A chargeback that you have won is challenged for a third time by the customer and the card networks directly get involved.

comments

string Suggestion added by Razorpay for you to follow.

created_at

integer Timestamp (in Unix) when dispute was created.

Prerequisites🔗

All Razorpay APIs are authenticated using Basic Auth. While authenticating your API requests, you must send API Keys, a combination of Key_Id and Key_Secretin the authentication header. Generate API Keys from the Dashboard.

Fetch all Disputes🔗

All the disputes raised by your customers can be retrieved.

Fetch a Dispute🔗

You can fetch the details of a specific dispute.