---
title: "Fetch dispute by ID"
method: GET
path: "/disputes/{id}"
tags: ["Disputes"]
---

# Fetch dispute by ID

`GET /disputes/{id}`

Retrieve full details of a specific dispute including submitted evidence.

## Path parameters

- `id` string, required

## Response `200`

Dispute details.

- Dispute
  - `id` string — Unique dispute identifier. Prefix: disp_
  - `entity` 'dispute'
  - `payment_id` string — The payment against which the dispute was raised (pay_*).
  - `amount` integer — Disputed amount in currency subunits.
  - `currency` string
  - `amount_deducted` integer — Amount deducted from your balance when dispute is lost.
  - `reason_code` string — Code identifying the dispute reason.
  - `reason_description` string — Human-readable explanation of the dispute cause.
  - `respond_by` integer — Unix timestamp by which you must respond. Missing this forfeits the dispute.
  - `status` 'open' | 'under_review' | 'won' | 'lost' | 'closed' — open: action required. under_review: evidence submitted, awaiting bank decision. won: resolved in your favour. lost: resolved against you. closed: resolved without chargeback.
  - `phase` 'fraud' | 'retrieval' | 'chargeback' | 'pre_arbitration' | 'arbitration' — Escalation stage of the dispute process.
  - `created_at` integer
  - `evidence` DisputeEvidence
    - `amount` integer — Contested amount in currency subunits.
    - `summary` string — Your explanation of why the dispute should be resolved in your favour. Max 1000 characters.
    - `shipping_proof` string[] — Document IDs proving product shipment.
    - `billing_proof` string[] — Order confirmation document IDs.
    - `cancellation_proof` string[]
    - `customer_communication` string[]
    - `proof_of_service` string[]
    - `explanation_letter` string[]
    - `refund_confirmation` string[]
    - `access_activity_log` string[]
    - `refund_cancellation_policy` string[]
    - `term_and_conditions` string[]
    - `others` object[]
    - `submitted_at` unknown

## Other responses

- `401` — Authentication failed. Invalid or missing API key credentials.
- `404` — Resource not found.
- `429` — Rate limit exceeded. Implement exponential backoff with jitter before retrying.

---

[API](https://skmtc.net/razorpay/apis/razorpay-api.md) · [All operations](https://skmtc.net/razorpay/apis/razorpay-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/razorpay/razorpay-api/versions/824ca9e6faef/schema)