# Manage disputes through pre-arbitration and arbitration

Respond and appeal during the final stages of the card network dispute process.

Pre-arbitration and arbitration are the final stages of the card network dispute lifecycle.

For most disputes, pre-arbitration begins when the customer’s bank rejects your initial response and provides additional justification. Depending on the card network and dispute reason, you might be able to respond or appeal the case to arbitration.

During arbitration, the last stage, the card network (Visa or Mastercard) reviews the case under its rules and makes its final decision.

Effectively managing disputes during these stages is critical. These stages have strict deadlines and can carry high network fees. Stripe provides tools and data to help you navigate this process.

## Enable appeals 

Manual arbitration is available only to eligible businesses.

If your business is eligible, you can enable appeals in your Disputes settings. When you enable appeals, `Dispute` objects can have appeal-specific [status](https://docs.stripe.com/api/disputes/object.md#dispute_object-status) values. Before enabling appeals, review [how to manage them with the API](https://docs.stripe.com/disputes/arbitration.md#appeal-a-dispute-decision-using-the-api) so you understand how to handle appeal-specific statuses.

1. In the Dashboard, go to **Settings** > **Payments** > [Disputes](https://dashboard.stripe.com/settings/disputes).
2. In the **Appealing dispute decisions** section, next to **Appeal responses**, click **Enable**.
3. In the confirmation popup, review the fee and API information, then click **Enable**.

For [Connect integrations](https://docs.stripe.com/connect/disputes.md), enabling and managing appeals depends on the charge type:

- *Indirect charges* (A charge type where customers transact directly with your platform instead of with a connected account. Indirect charges include destination charges and separate charges and transfers) (including when `on_behalf_of` is set): You enable appeals on the platform, and the platform handles all appeal activity. Connected accounts can’t create or manage them.
- *Direct charges* (A charge type where customers transact directly with a connected account, which is always the merchant of record. With each payment, the connected account pays fees to Stripe and, optionally, to your platform): You enable appeals on connected accounts, and connected accounts can create and manage appeals using the full Stripe Dashboard or the API. They can’t work with appeals using the Express Dashboard or Connect embedded components.

The platform can also create and manage appeals for direct charges by [accessing the connected account’s full Stripe Dashboard](https://docs.stripe.com/connect/dashboard/managing-individual-accounts.md#view-the-dashboard-as-a-connected-account) or by making API calls using the connected account’s ID in the [Stripe-Account header](https://docs.stripe.com/connect/authentication.md#stripe-account-header). To manage appeals using the API, you must enable appeals on both the platform and the connected account.

## How pre-arbitration and arbitration work 

The extended dispute cycle follows a strict, rules-based mechanism defined by the card networks to determine the ultimate dispute outcome. During arbitration, the card network reviews all evidence submitted throughout the entire lifecycle and can assess technical violations.

| Stage | Description |
| --- | --- |
| Pre-arbitration | - **Visa non-fraud and Mastercard**: The issuing bank reviews your initial response and rejects it, filing pre-arbitration. The issuer provides justification for why your original evidence was invalid. You can submit a final, targeted evidence package to refute their justification within 20 days. If you don’t submit the evidence within 20 days, you implicitly assume liability.
- **Visa fraud**: Your initial response counts as filing for pre-arbitration. If the issuer rejects this response, you can appeal the case straight to arbitration. You must take action within 7 days of the issuer’s rejection. If you don’t appeal within 7 days, you implicitly assume liability. |
| Arbitration | - **Visa non-fraud and Mastercard**: The issuing bank elevates the case to the card network for a final, binding decision. Issuers have a finite window (10 days for Visa, 15 days for Mastercard) to elevate the case. If issuers don’t elevate the case within that window they implicitly assume liability.
- **Visa fraud**: You elevate the case to the card network for a final, binding decision. |

## Network fees and financial liability 

When you send an appeal, Stripe charges a nonrefundable dispute appeal fee. The fee applies regardless of the outcome, and is separate from the arbitration network fees described below. See [pricing](https://stripe.com/pricing#payments).

You’re responsible for any card network fees charged during arbitration. Stripe charges these fees to your account after the card network invoices Stripe.

1. **Case filing and ruling fees**: Card networks charge these fees for their final arbitration review, typically to the party that loses the arbitration case.

2. **Technical violation fees**: Card networks charge these fees to your business or the customer’s bank for violating procedural rules during pre-arbitration or arbitration. Some examples include missing a deadline, sending invalid documentation, or not following the requirements for a dispute reason. These fees can apply even if you win the arbitration case.

> #### Card network fee amounts
> 
> Card network arbitration fees vary, and can exceed the cost of the transaction. Filing and ruling fees can exceed 600 USD per appeal. Technical violation fees can exceed 250 USD per violation, and additional network fees might apply. Stripe might convert network fees to your local currency before charging your account.
> 
> Stripe charges network fees after they’re invoiced by the card network. This generally happens about one month after the card network rules on the arbitration case.

## Appeal a dispute decision using the API 

After you [enable appeals](https://docs.stripe.com/disputes/arbitration.md#enable-arbitration), a dispute’s [status](https://docs.stripe.com/api/disputes/object.md#dispute_object-status) changes from `under_review` to `appeal_needs_response` when it becomes eligible for appeal. Its [evidence_details](https://docs.stripe.com/api/disputes/object.md#dispute_object-evidence_details) also updates to reflect the appeal, including the appeal response deadline in `due_by`.

### Identify a dispute eligible for appeal 

To identify disputes eligible for appeal, set up a webhook to listen for [charge.dispute.updated](https://docs.stripe.com/api/events/types.md#event_types-charge.dispute.updated) snapshot events or [v1.charge.dispute.updated](https://docs.stripe.com/api/v2/core/events/event-types.md#v2_event_types-v1.charge.dispute.updated) thin events, and check the dispute’s `status`. When a dispute’s `status` changes to `appeal_needs_response`, you can submit an appeal.

A dispute’s [payment_method_details.card.case_type](https://docs.stripe.com/api/disputes/object.md#dispute_object-payment_method_details-card-case_type) remains `chargeback` throughout the appeal lifecycle, so you can’t use `case_type` to identify an appeal.

Before acting on webhook events, [verify their signatures](https://docs.stripe.com/webhooks.md#verify-events) to confirm they came from Stripe.

### Monitor appeal status and deadline 

At the appeal stage, the [evidence_details](https://docs.stripe.com/api/disputes/object.md#dispute_object-evidence_details) object’s `due_by` field changes from the dispute response deadline to the appeal response deadline.

After you submit an appeal, its `status` changes to `appeal_under_review`, and the appeal evidence becomes read-only. Continue listening for [charge.dispute.updated](https://docs.stripe.com/api/events/types.md#event_types-charge.dispute.updated) events to track lifecycle changes. When the dispute reaches a terminal `won` or `lost` status, Stripe sends a [charge.dispute.closed](https://docs.stripe.com/api/events/types.md#event_types-charge.dispute.closed) event. The `evidence_details.has_evidence` field indicates whether you’ve staged appeal evidence. The `evidence_details.past_due` and `evidence_details.submission_count` fields update when you submit the appeal.

During an appeal, you can read existing evidence unrelated to the appeal, but you can’t update it. Use `evidence.appeal.card` for your appeal response.

### Submit appeal evidence 

To submit evidence, [update the dispute](https://docs.stripe.com/api/disputes/update.md) and provide the evidence in the [evidence.appeal](https://docs.stripe.com/api/disputes/update.md#update_dispute-evidence-appeal) parameter. It must include a nonempty [card.reason_for_filing](https://docs.stripe.com/api/disputes/update.md#update_dispute-evidence-appeal-card-reason_for_filing).

The [supporting_files](https://docs.stripe.com/api/disputes/update.md#update_dispute-evidence-appeal-card-supporting_files) parameter is optional. To attach supporting files, first upload them with the [File Upload API](https://docs.stripe.com/file-upload.md) using the `dispute_evidence` purpose. You can provide up to five file IDs in `evidence.appeal.card.supporting_files`.

> #### Supported API versions
> 
> You can provide the `evidence.appeal` parameter when making a request using any GA API version. When using an SDK, use an [SDK release](https://docs.stripe.com/sdks/versioning.md) that targets API version `2026-10-28.endive` or later.

By default, Stripe immediately submits the evidence to the bank. If you want to stage evidence without submitting it (for example, if you expect to add more evidence later), see the next section.

```curl
curl https://api.stripe.com/v1/disputes/{{DISPUTE_ID}} \
  -u "<<YOUR_SECRET_KEY>>:" \
  -d "evidence[appeal][card][reason_for_filing]=The issuer decision is incorrect" \
  -d "evidence[appeal][card][supporting_files][]={{FILE_ID}}" \
  -d submit=true
```

### Stage appeal evidence 

To stage appeal evidence before submitting it, set `submit` to false. You can stage the reason and files together or in separate requests.

If you add or update evidence on the `Dispute` without explicitly specifying `submit=false`, Stripe immediately submits all staged evidence.

```curl
curl https://api.stripe.com/v1/disputes/{{DISPUTE_ID}} \
  -u "<<YOUR_SECRET_KEY>>:" \
  -d "evidence[appeal][card][reason_for_filing]=The issuer decision is incorrect" \
  -d "evidence[appeal][card][supporting_files][]={{FILE_ID}}" \
  -d submit=false
```

#### Submit staged evidence 

To submit staged evidence without otherwise updating the dispute, update the `Dispute` and set `submit` to true. If you add or update evidence, Stripe submits all existing evidence unless you explicitly set `submit` to false.

```curl
curl https://api.stripe.com/v1/disputes/{{DISPUTE_ID}} \
  -u "<<YOUR_SECRET_KEY>>:" \
  -d submit=true
```

### Accept the appeal decision 

To accept the appeal decision without submitting evidence, [close the dispute](https://docs.stripe.com/api/disputes/close.md) while its `status` is `appeal_needs_response`. Closing the dispute is irreversible and changes the dispute’s `status` to `lost`.

```curl
curl -X POST https://api.stripe.com/v1/disputes/{{DISPUTE_ID}}/close \
  -u "<<YOUR_SECRET_KEY>>:"
```

## Testing 

### Simulate a dispute eligible for appeal 

Use a test card to [simulate a disputed transaction](https://docs.stripe.com/testing.md?testing-method=card-numbers#disputes). For example, you can use card number `4000000000002685`, PaymentMethod `pm_card_createDisputeProductNotReceived`, or token `tok_createDisputeProductNotReceived`. Then respond to the dispute with the evidence value `losing_evidence_for_appeal`:

- To respond using the API, pass `losing_evidence_for_appeal` as [uncategorized_text](https://docs.stripe.com/api/disputes/update.md#update_dispute-evidence-uncategorized_text).
- To respond in the Dashboard, enter `losing_evidence_for_appeal` in the **Additional information** field, then click **Submit evidence**.

After you submit the evidence, the dispute changes from `needs_response` to `under_review`, then to `appeal_needs_response`.

### Simulate an automatic appeal 

To simulate issuer rejection followed by automatic appeal submission, create a disputed test payment using the same test card or `pm_card_createDisputeProductNotReceived`. Submit the initial dispute evidence using the API with `evidence.uncategorized_text` set to `losing_evidence_for_immediate_appeal` and `submit` set to true:

```curl
curl https://api.stripe.com/v1/disputes/{{DISPUTE_ID}} \
  -u "<<YOUR_SECRET_KEY>>:" \
  -d "evidence[uncategorized_text]=losing_evidence_for_immediate_appeal" \
  -d submit=true
```

The dispute becomes `appeal_under_review`.

### Simulate winning or losing the appeal 

Use the following values to submit appeal evidence and simulate the final outcome:

| Evidence | Description |
| --- | --- |
| `winning_evidence` | Closes the dispute as won and credits your account for the charge amount and related fees. |
| `losing_evidence` | Closes the dispute as lost without crediting your account. |

- To respond using the API, pass the value in `evidence.appeal.card.reason_for_filing`.
- To respond in the Dashboard, enter the value in the **Why do you disagree with the issuer decision?** text box, then submit the appeal.
