> 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/submit-evidence.md).

# Submit Evidence

## Overview

The `submitEvidence` method uploads supporting documentation to contest a chargeback dispute.

**Business Use Case:** A customer disputed a charge claiming they never received their order. You have delivery confirmation and submit this evidence.

## Request Fields

| Field          | Type   | Required | Description                                             |
| -------------- | ------ | -------- | ------------------------------------------------------- |
| `disputeId`    | string | Yes      | The connector's dispute ID                              |
| `evidenceType` | string | Yes      | delivery\_proof, customer\_communication, receipt, etc. |
| `files`        | array  | Yes      | URLs to evidence files                                  |
| `description`  | string | No       | Description of evidence                                 |

## Response Fields

| Field               | Type          | Description            |
| ------------------- | ------------- | ---------------------- |
| `disputeId`         | string        | Connector's dispute ID |
| `evidenceSubmitted` | boolean       | Success status         |
| `status`            | DisputeStatus | Updated dispute status |
| `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",
    evidenceType: "delivery_proof",
    files: [
        "https://storage.example.com/delivery_receipt.pdf",
        "https://storage.example.com/tracking.png"
    ],
    description: "Package delivered on 2024-01-15 with signature"
};

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

### Response

```javascript
{
    disputeId: "dp_xxx",
    evidenceSubmitted: true,
    status: "NEEDS_RESPONSE",
    statusCode: 200
}
```

## Evidence Types

| Type                     | Use When                   |
| ------------------------ | -------------------------- |
| `delivery_proof`         | Physical goods delivered   |
| `customer_communication` | Customer confirmed receipt |
| `receipt`                | Proof of purchase          |
| `cancellation_policy`    | Customer agreed to terms   |

## Next Steps

* [defend](/integrations/prism/node/dispute-service/defend.md) - Submit formal defense after evidence
* [get](/integrations/prism/node/dispute-service/get.md) - Check dispute status


---

# 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/submit-evidence.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.