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

# Submit Evidence

## Overview

The `submit_evidence` method uploads supporting documentation to contest a chargeback dispute. Evidence strengthens your defense by proving the transaction was legitimate and the customer received the product or service.

**Business Use Case:** A customer disputed a charge claiming they never received their order. You have delivery confirmation and the customer's signature. Submit this evidence to prove the order was delivered.

## Purpose

**Why submit evidence?**

| Evidence Type              | Use Case                                         |
| -------------------------- | ------------------------------------------------ |
| **Delivery proof**         | Tracking info, receipt signature, GPS logs       |
| **Customer communication** | Email threads showing customer confirmed receipt |
| **Product/service proof**  | Photos, service completion reports               |
| **Terms acceptance**       | Signed contracts, terms of service agreement     |

**Key outcomes:**

* Evidence attached to dispute case
* Stronger position in bank arbitration
* Improved win rate for disputes

## Request Fields

| Field           | Type   | Required | Description                                                                |
| --------------- | ------ | -------- | -------------------------------------------------------------------------- |
| `dispute_id`    | string | Yes      | The connector's dispute ID                                                 |
| `evidence_type` | string | Yes      | Type: delivery\_proof, customer\_communication, product\_description, etc. |
| `files`         | list   | Yes      | List of file URLs or file data                                             |
| `description`   | string | No       | Description of evidence                                                    |

## Response Fields

| Field                | Type          | Description                                 |
| -------------------- | ------------- | ------------------------------------------- |
| `dispute_id`         | string        | Connector's dispute ID                      |
| `evidence_submitted` | bool          | Whether evidence was successfully submitted |
| `status`             | DisputeStatus | Current dispute status                      |
| `status_code`        | int           | HTTP-style status code (200, 422, etc.)     |

## Example

### SDK Setup

```python
from hyperswitch_prism import DisputeClient

dispute_client = DisputeClient(
    connector='stripe',
    api_key='YOUR_API_KEY',
    environment='SANDBOX'
)
```

### Request

```python
request = {
    "dispute_id": "dp_xxx",
    "evidence_type": "delivery_proof",
    "files": [
        "https://storage.example.com/delivery_receipt_001.pdf",
        "https://storage.example.com/tracking_screenshot.png"
    ],
    "description": "Package delivered to customer address on 2024-01-15. Signed by customer."
}

response = await dispute_client.submit_evidence(request)
```

### Response

```python
{
    "dispute_id": "dp_xxx",
    "evidence_submitted": True,
    "status": "NEEDS_RESPONSE",
    "status_code": 200
}
```

## Evidence Types

| Type                     | Description                                | When to Use                                |
| ------------------------ | ------------------------------------------ | ------------------------------------------ |
| `delivery_proof`         | Shipping confirmation, tracking, signature | Physical goods delivered                   |
| `customer_communication` | Emails, chat logs, support tickets         | Customer confirmed receipt or satisfaction |
| `product_description`    | Product details, screenshots, demos        | Service was as described                   |
| `cancellation_policy`    | Terms, refund policy, agreements           | Customer agreed to terms                   |
| `duplicate_charge_doc`   | Proof charges are distinct                 | Multiple legitimate charges                |
| `receipt`                | Transaction receipt, invoice               | Proof of purchase                          |

## Best Practices

* Submit evidence before the deadline (typically 7-21 days)
* Provide clear, high-quality documentation
* Include all relevant communication
* Be concise but comprehensive

## Next Steps

* [defend](/integrations/prism/python/dispute-service/defend.md) - Submit formal defense after evidence
* [get](/integrations/prism/python/dispute-service/get.md) - Check dispute status
* [accept](/integrations/prism/python/dispute-service/accept.md) - Concede if evidence is 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/python/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.