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

# Accept

## Overview

The `Accept` RPC concedes a chargeback dispute and accepts the loss. Use this when you lack sufficient evidence to defend, when the customer's claim is valid, or when the dispute amount is less than the cost of defense.

**Business Use Case:** Not all disputes are worth fighting. When you don't have delivery confirmation, the product was genuinely defective, or the dispute amount is small, accepting the chargeback avoids additional fees and administrative overhead.

## Purpose

**When to accept disputes?**

| Scenario                             | Reason                                 | Outcome                                  |
| ------------------------------------ | -------------------------------------- | ---------------------------------------- |
| **No delivery proof**                | Cannot prove product was delivered     | Accept to avoid losing defense fee       |
| **Valid customer complaint**         | Product/service issue confirmed        | Accept to maintain customer relationship |
| **Dispute amount < defense cost**    | $20 dispute vs $15 defense fee         | Accept to minimize total loss            |
| **Evidence deadline passed**         | Missed submission window               | Accept as defense is no longer possible  |
| **Fraudulent transaction confirmed** | Internal investigation confirmed fraud | Accept and write off loss                |

**Key outcomes:**

* Dispute status changes to ACCEPTED
* Chargeback processed immediately
* Funds debited from your account
* Defense process terminated

## Request Fields

| Field                      | Type   | Required | Description                    |
| -------------------------- | ------ | -------- | ------------------------------ |
| `merchant_dispute_id`      | string | Yes      | Your unique dispute reference  |
| `connector_transaction_id` | string | Yes      | Original transaction ID        |
| `dispute_id`               | string | Yes      | Connector's dispute identifier |

## Response Fields

| Field                   | Type                | Description                                   |
| ----------------------- | ------------------- | --------------------------------------------- |
| `dispute_id`            | string              | Connector's dispute identifier                |
| `dispute_status`        | DisputeStatus       | Updated status: ACCEPTED                      |
| `connector_status_code` | string              | Connector-specific status code                |
| `error`                 | ErrorInfo           | Error details if acceptance failed            |
| `status_code`           | uint32              | HTTP-style status code                        |
| `response_headers`      | map\<string,string> | Connector-specific response headers           |
| `merchant_dispute_id`   | string              | Your dispute reference (echoed back)          |
| `raw_connector_request` | SecretString        | Raw API request sent to connector (debugging) |

## 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_transaction_id": "pi_3Oxxx...",
    "dispute_id": "dp_1Oxxx..."
  }' \
  localhost:8080 \
  types.DisputeService/Accept
```

### Response

```json
{
  "dispute_id": "dp_1Oxxx...",
  "dispute_status": "ACCEPTED",
  "status_code": 200
}
```

## Next Steps

* [Get](/integrations/prism/api-reference/dispute-service/get.md) - Verify dispute status after acceptance
* [Payment Service](/integrations/prism/api-reference/payment-service.md) - Review original transaction


---

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