> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/prism/node/dispute-service/get.md).

# Get

## Overview

The `get` method retrieves the current status of a dispute, including evidence deadlines, submitted evidence, and the final decision.

**Business Use Case:** Check which disputes need evidence submission and which are approaching their deadlines.

## Request Fields

| Field       | Type   | Required | Description                |
| ----------- | ------ | -------- | -------------------------- |
| `disputeId` | string | Yes      | The connector's dispute ID |

## Response Fields

| Field               | Type          | Description                               |
| ------------------- | ------------- | ----------------------------------------- |
| `disputeId`         | string        | Connector's dispute ID                    |
| `paymentIntentId`   | string        | Related payment transaction ID            |
| `status`            | DisputeStatus | NEEDS\_RESPONSE, UNDER\_REVIEW, WON, LOST |
| `amount`            | Money         | Disputed amount                           |
| `reason`            | string        | Customer's dispute reason code            |
| `evidenceDueBy`     | string        | ISO 8601 deadline                         |
| `evidenceSubmitted` | boolean       | Whether evidence submitted                |
| `statusCode`        | number        | HTTP status code                          |

## Example

### SDK Setup

```javascript
const { DisputeClient } = require('hyperswitch-prism');

const disputeClient = new DisputeClient({
    connector: 'stripe',
    apiKey: 'YOUR_API_KEY',
    environment: 'SANDBOX'
});
```

### Request

```javascript
const request = {
    disputeId: "dp_xxx"
};

const response = await disputeClient.get(request);
```

### Response

```javascript
{
    disputeId: "dp_xxx",
    paymentIntentId: "pi_3Oxxx...",
    status: "NEEDS_RESPONSE",
    amount: {
        minorAmount: 1000,
        currency: "USD"
    },
    reason: "fraudulent",
    evidenceDueBy: "2024-02-15T23:59:59Z",
    evidenceSubmitted: false,
    statusCode: 200
}
```

## Status Values

| Status           | Description                        | Action                    |
| ---------------- | ---------------------------------- | ------------------------- |
| `NEEDS_RESPONSE` | Dispute opened, awaiting response  | Submit evidence or accept |
| `UNDER_REVIEW`   | Evidence submitted, bank reviewing | Wait for decision         |
| `WON`            | Resolved in merchant favor         | None                      |
| `LOST`           | Resolved against merchant          | Funds debited             |

## Next Steps

* [submitEvidence](/integrations/prism/node/dispute-service/submit-evidence.md) - Upload evidence if NEEDS\_RESPONSE
* [defend](/integrations/prism/node/dispute-service/defend.md) - Submit formal defense
* [accept](/integrations/prism/node/dispute-service/accept.md) - Concede if evidence insufficient


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/prism/node/dispute-service/get.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.