> 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/api-reference/dispute-service/get.md).

# Get

## Overview

The `Get` RPC retrieves the current status and details of a dispute from the payment processor. Use this to track dispute progress, check evidence submission deadlines, and monitor resolution status.

**Business Use Case:** When you receive a dispute notification or need to check the status of an ongoing dispute, this RPC provides real-time information about the dispute state, evidence requirements, and resolution timeline.

## Purpose

**Why retrieve dispute status?**

| Scenario                          | Information Needed                      | Action                                |
| --------------------------------- | --------------------------------------- | ------------------------------------- |
| **New dispute notification**      | Dispute reason, amount, deadline        | Determine defense strategy            |
| **Evidence deadline approaching** | Time remaining, evidence submitted      | Submit evidence before cutoff         |
| **Awaiting resolution**           | Current status, bank review progress    | Plan for potential loss/profit impact |
| **Dispute resolved**              | Final status (WON/LOST), funds movement | Update accounting records             |

**Key outcomes:**

* Current dispute status and stage
* Evidence submission deadline
* Dispute reason and amount
* Evidence already submitted
* Resolution timeline

## Request Fields

| Field                  | Type   | Required | Description                          |
| ---------------------- | ------ | -------- | ------------------------------------ |
| `merchant_dispute_id`  | string | Yes      | Your unique dispute reference        |
| `dispute_id`           | string | No       | Connector's dispute identifier       |
| `connector_dispute_id` | string | Yes      | Connector's dispute ID (alternative) |

## Response Fields

| Field                      | Type                | Description                                                         |
| -------------------------- | ------------------- | ------------------------------------------------------------------- |
| `connector_dispute_id`     | string              | Connector's unique dispute identifier                               |
| `connector_transaction_id` | string              | Original transaction ID                                             |
| `dispute_status`           | DisputeStatus       | Current status: OPENED, EXPIRED, ACCEPTED, CHALLENGED, WON, LOST    |
| `dispute_stage`            | DisputeStage        | Current stage: PRE\_DISPUTE, DISPUTE, PRE\_ARBITRATION, ARBITRATION |
| `connector_status_code`    | string              | Connector-specific status code                                      |
| `error`                    | ErrorInfo           | Error details if retrieval failed                                   |
| `status_code`              | uint32              | HTTP-style status code                                              |
| `response_headers`         | map\<string,string> | Connector-specific response headers                                 |
| `dispute_amount`           | Money               | Amount being disputed                                               |
| `dispute_date`             | int64               | Unix timestamp when dispute was filed                               |
| `service_date`             | int64               | Unix timestamp when service was provided                            |
| `shipping_date`            | int64               | Unix timestamp when product was shipped                             |
| `due_date`                 | int64               | Unix timestamp for evidence submission deadline                     |
| `evidence_documents`       | EvidenceDocument\[] | Evidence documents already submitted                                |
| `dispute_reason`           | string              | Reason code for the dispute                                         |
| `dispute_message`          | string              | Detailed dispute description                                        |

## Example

### Request (grpcurl)

```bash
grpcurl -H "x-connector: stripe" \
  -H "x-connector-config: {\"config\":{\"Stripe\":{\"api_key\":\"$STRIPE_API_KEY\"}}}" \
  -d '{
    "merchant_dispute_id": "dispute_001",
    "connector_dispute_id": "dp_1Oxxx..."
  }' \
  localhost:8080 \
  types.DisputeService/Get
```

### Response

```json
{
  "connector_dispute_id": "dp_1Oxxx...",
  "connector_transaction_id": "pi_3Oxxx...",
  "dispute_status": "OPENED",
  "dispute_stage": "DISPUTE",
  "dispute_amount": {
    "minor_amount": 10000,
    "currency": "USD"
  },
  "dispute_date": 1704067200,
  "due_date": 1706659200,
  "dispute_reason": "fraudulent",
  "dispute_message": "Customer claims they did not authorize this transaction",
  "status_code": 200
}
```

## Next Steps

* [SubmitEvidence](/integrations/prism/api-reference/dispute-service/submit-evidence.md) - Upload supporting documentation
* [Defend](/integrations/prism/api-reference/dispute-service/defend.md) - Submit formal defense
* [Accept](/integrations/prism/api-reference/dispute-service/accept.md) - Concede the dispute


---

# 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/api-reference/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.