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

# Accept

## Overview

The `accept` method concedes a dispute and accepts the chargeback loss. Use this when evidence is insufficient, the cost of defense outweighs the dispute amount, or the customer's claim is valid.

**Business Use Case:** A customer disputed a charge claiming the product was never delivered. Your tracking shows it was lost in transit. Since you cannot prove delivery, you accept the dispute and issue a refund.

## Purpose

**Why accept disputes?**

| Scenario                  | Reason                               |
| ------------------------- | ------------------------------------ |
| **Insufficient evidence** | No proof of delivery or service      |
| **Cost-benefit**          | Defense cost exceeds dispute amount  |
| **Valid claim**           | Customer's dispute is legitimate     |
| **Fraudulent order**      | Order was fraud, not worth defending |

**Key outcomes:**

* Dispute closed immediately
* Funds debited from your account
* No additional fees or penalties
* Clean dispute resolution

## Request Fields

| Field        | Type   | Required | Description                   |
| ------------ | ------ | -------- | ----------------------------- |
| `dispute_id` | string | Yes      | The connector's dispute ID    |
| `reason`     | string | No       | Internal reason for accepting |

## Response Fields

| Field            | Type          | Description                             |
| ---------------- | ------------- | --------------------------------------- |
| `dispute_id`     | string        | Connector's dispute ID                  |
| `status`         | DisputeStatus | New status: LOST                        |
| `amount_debited` | Money         | Amount charged back                     |
| `status_code`    | int           | HTTP-style status code (200, 404, 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",
    "reason": "Tracking shows package lost in transit - no delivery confirmation available"
}

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

### Response

```python
{
    "dispute_id": "dp_xxx",
    "status": "LOST",
    "amount_debited": {
        "minor_amount": 1000,
        "currency": "USD"
    },
    "status_code": 200
}
```

## Decision Framework

```
┌─────────────────────────────────────────────────────────┐
│          Should I Accept This Dispute?                 │
└─────────────────────────────────────────────────────────┘
                          │
           ┌──────────────┼──────────────┐
           ▼              ▼              ▼
    ┌──────────┐   ┌──────────┐   ┌──────────┐
    │ Evidence │   │ Cost >   │   │ Valid    │
    │ Exists?  │   │ Dispute? │   │ Claim?   │
    └────┬─────┘   └────┬─────┘   └────┬─────┘
         │              │              │
        No            Yes            Yes
         │              │              │
         └──────────────┴──────────────┘
                        │
                        ▼
              ┌─────────────────┐
              │ ACCEPT DISPUTE  │
              └─────────────────┘
```

## After Acceptance

* Dispute is immediately closed
* Chargeback amount is debited
* Consider reaching out to customer for resolution
* Update internal records

## Next Steps

* [get](/integrations/prism/python/dispute-service/get.md) - Review dispute details before accepting
* Consider customer outreach for retention
* Review processes to prevent similar disputes


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperswitch.io/integrations/prism/python/dispute-service/accept.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.