# Adds support for submitting evidence to appeal dispute decisions ## What’s new Adds the [appeal](https://docs.stripe.com/api/disputes/object.md?api-version=2026-10-28.endive#dispute_object-evidence-appeal) parameter to the [evidence](https://docs.stripe.com/api/disputes/object.md?api-version=2026-10-28.endive#dispute_object-evidence) hash on the [Dispute](https://docs.stripe.com/api/disputes/object.md?api-version=2026-10-28.endive) object. Use `appeal` to stage or submit evidence when appealing an eligible dispute. Also adds the `appeal_needs_response` and `appeal_under_review` enum values to the [status](https://docs.stripe.com/api/disputes/object.md?api-version=2026-10-28.endive#dispute_object-status) property to track the appeal’s status. ## Impact To submit appeal evidence, set [reason_for_filing](https://docs.stripe.com/api/disputes/object.md?api-version=2026-10-28.endive#dispute_object-evidence-appeal-card-reason_for_filing) and [supporting_files](https://docs.stripe.com/api/disputes/object.md?api-version=2026-10-28.endive#dispute_object-evidence-appeal-card-supporting_files) when updating a Dispute. You can submit appeal evidence only for eligible disputes with a [status](https://docs.stripe.com/api/disputes/object.md?api-version=2026-10-28.endive#dispute_object-status) of `appeal_needs_response`. You can’t update other dispute evidence during the appeal stage. To submit the evidence immediately, omit [submit](https://docs.stripe.com/api/disputes/update.md?api-version=2026-10-28.endive#update_dispute-submit) or set it to `true`. To save the evidence without submitting it, set `submit` to `false`. You can save the reason and supporting files separately or submit them in the same request. Before submission, `reason_for_filing` must contain a value. You can also include up to five supporting file IDs uploaded with [purpose](https://docs.stripe.com/api/files/create.md?api-version=2026-10-28.endive#create_file-purpose?api-version=2026-10-28.endive) set to `dispute_evidence`. After submission, the dispute status changes to `appeal_under_review`, and you can’t update the appeal evidence. Listen for [charge.dispute.updated](https://docs.stripe.com/api/events/types.md?api-version=2026-10-28.endive#event_types-charge.dispute.updated) events to track appeal status changes and the evidence deadline. See [Appeal a dispute decision using the API](https://docs.stripe.com/disputes/arbitration.md#appeal-a-dispute-decision-using-the-api) for implementation details. ## Changes #### REST API | Parameter | Change | Resources or endpoints | | --- | --- | --- | | `appeal` | Added | [Dispute#update.evidence](/api/disputes/update?api-version=2026-10-28.endive#update_dispute-evidence), [Dispute.evidence](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-evidence) | | Values | Change | Enum | | --- | --- | --- | | `appeal_needs_response`, `appeal_under_review` | Added | [Dispute.status](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-status) | #### Ruby | Parameter | Change | Resources or methods | | --- | --- | --- | | `appeal` | Added | [Dispute::Evidence](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-evidence), [DisputeUpdateParams::Evidence](/api/disputes/update?api-version=2026-10-28.endive#update_dispute-evidence) | | Values | Change | Enum | | --- | --- | --- | | `appeal_needs_response`, `appeal_under_review` | Added | [Dispute.status](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-status) | #### Python | Parameter | Change | Resources or methods | | --- | --- | --- | | `appeal` | Added | [Dispute.Evidence](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-evidence), [DisputeModifyParamsEvidence](/api/disputes/update?api-version=2026-10-28.endive#update_dispute-evidence) | | Values | Change | Enum | | --- | --- | --- | | `appeal_needs_response`, `appeal_under_review` | Added | [Dispute.status](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-status) | #### PHP | Parameter | Change | Resources or methods | | --- | --- | --- | | `appeal` | Added | [Dispute.evidence](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-evidence), [Dispute.update().$params.evidence](/api/disputes/update?api-version=2026-10-28.endive#update_dispute-evidence) | | Values | Change | Enum | | --- | --- | --- | | `appeal_needs_response`, `appeal_under_review` | Added | [Dispute.status](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-status) | #### Java | Parameter | Change | Resources or methods | | --- | --- | --- | | `appeal` | Added | [Dispute.evidence](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-evidence), [DisputeUpdateParams.evidence](/api/disputes/update?api-version=2026-10-28.endive#update_dispute-evidence) | | Values | Change | Enum | | --- | --- | --- | | `appeal_needs_response`, `appeal_under_review` | Added | [Dispute.status](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-status) | #### Node.js | Parameter | Change | Resources or methods | | --- | --- | --- | | `appeal` | Added | [Dispute.evidence](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-evidence), [DisputeUpdateParams.evidence](/api/disputes/update?api-version=2026-10-28.endive#update_dispute-evidence) | | Values | Change | Enum | | --- | --- | --- | | `appeal_needs_response`, `appeal_under_review` | Added | [Dispute.status](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-status) | #### Go | Parameter | Change | Resources or methods | | --- | --- | --- | | `Appeal` | Added | [DisputeEvidence](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-evidence), [DisputeEvidenceParams](/api/disputes/update?api-version=2026-10-28.endive#update_dispute-evidence) | | Values | Change | Enum | | --- | --- | --- | | `appeal_needs_response`, `appeal_under_review` | Added | [Dispute.Status](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-Status) | #### .NET | Parameter | Change | Resources or methods | | --- | --- | --- | | `Appeal` | Added | [Dispute.Evidence](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-evidence), [DisputeEvidenceOptions](/api/disputes/update?api-version=2026-10-28.endive#update_dispute-evidence) | | Values | Change | Enum | | --- | --- | --- | | `appeal_needs_response`, `appeal_under_review` | Added | [Dispute.Status](/api/disputes/object?api-version=2026-10-28.endive#dispute_object-status) | ## Upgrade #### REST API 1. [View your current API version](https://docs.stripe.com/workbench/guides.md#view-api-versions) in Workbench. 2. If you use an SDK, upgrade to the corresponding SDK version for this API version. - If you don’t use an SDK, update your [API requests](https://docs.stripe.com/api-versions.md#how-versions-are-specified-in-requests) to include `Stripe-Version: 2026-10-28.endive` 3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 4. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Ruby 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 2. Upgrade your Ruby SDK to the latest version. 3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 4. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Python 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 2. Upgrade your Python SDK to the latest version. 3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 4. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### PHP 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 2. Upgrade your PHP SDK to the latest version. 3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 4. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Java 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 2. Upgrade your Java SDK to the latest version. 3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 4. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Node.js 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 2. Upgrade your Node SDK to the latest version. 3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 4. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Go 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 2. Upgrade your Go SDK to the latest version. 3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 4. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### .NET 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 2. Upgrade your .NET SDK to the latest version. 3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 4. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). ## Related changes - [Adds payment intent data configuration when updating Checkout Sessions](https://docs.stripe.com/changelog/endive/2026-10-28/adds-payment-intent-data-configuration-when-updating-checkout-sessions.md) - [Adds Open USD (OUSD) as a supported token currency for crypto payments](https://docs.stripe.com/changelog/endive/2026-10-28/ousd-token-currency.md) - [Adds support for requesting Scalapay Payment Links](https://docs.stripe.com/changelog/endive/2026-10-28/scalapay-payment-method-support-payment-links.md) - [Adds the evidence submission method property to Disputes](https://docs.stripe.com/changelog/endive/2026-10-28/evidence-submission-method-property-disputes.md) - [Adds the ability to specify the intended submission method for Disputes](https://docs.stripe.com/changelog/endive/2026-10-28/adds-intended-submission-method-for-disputes.md) - [Adds invoice settings parameters for Checkout Sessions and Payment Links subscriptions](https://docs.stripe.com/changelog/endive/2026-10-28/invoice-settings-parameters-checkout-sessions-payment-links-subscriptions.md) - [Adds refund reference tracking for Klarna, PayPal, and Afterpay Clearpay](https://docs.stripe.com/changelog/endive/2026-10-28/refund-reference-klarna-paypal-afterpay.md) - [Adds support for specifying card-on-file usage when saving or charging cards](https://docs.stripe.com/changelog/endive/2026-10-28/card-on-file-usage-indicators-support.md) - [Adds RTP and FedNow as US bank transfer network types for cash balance transactions](https://docs.stripe.com/changelog/endive/2026-10-28/rtp-fednow-support-us-bank-transfer-network-types.md) - [Adds webhook events and error messages for the Standalone 3DS API](https://docs.stripe.com/changelog/endive/2026-10-28/standalone-3ds-error-messages-and-webhook-events.md) - [Adds validation for Smart Disputes availability when submitting a dispute](https://docs.stripe.com/changelog/endive/2026-10-28/smart-disputes-availability-validation.md)