Skip to main content
Back to Developer changelog

Tags:

  • Admin GraphQL API

Added support for dispute preventions

We've introduced a new DisputeStatus value, prevented, and updated the descriptions of all dispute statuses for clarity and consistency.

What Changed

You can now receive a prevented status on disputes in the Admin API (both GraphQL and REST) and in any webhooks or payloads that include dispute status. We have refreshed the descriptions of all dispute statuses to better reflect real-world outcomes and processor terminology.

Who This Is For

  • App developers and partners who read, store, or display dispute statuses.
  • Payment and operations tools that report on dispute outcomes.
  • Agencies building custom workflows around dispute lifecycle events.

Why It Matters

  • Distinguish cases where a chargeback was stopped upstream (e.g., via Visa Rapid Dispute Resolution) from other outcomes.
  • Update your UI and reporting to reflect that merchants won’t incur a chargeback fee for prevented disputes.
  • Gain clearer, more actionable status definitions across the dispute lifecycle.

How It Works

Processors may send a prevented status when a chargeback is stopped before it’s filed. Currently, Stripe may send prevented for Visa transactions covered by RDR when the merchant is enrolled through a third party.

Shopify doesn’t enroll merchants into dispute prevention services. However, if a merchant is enrolled via a third party and the processor sends prevented, you’ll see it in the Shopify admin.

Availability

  • Available now in the Admin API (GraphQL and REST) and in payloads that include dispute status.
  • This is a non-breaking change; no version pinning is required.

What You Should Do

  • Review any strict enum handling (switches, validations, database constraints) to ensure prevented is accepted.
  • Update UI copy, translations, and filters to surface prevented distinctly from open, won, or lost states.
  • Check analytics and reporting pipelines that group outcomes or calculate fees to ensure prevented is categorized correctly.
  • Verify that any webhook or event processing that reacts to dispute status changes handles prevented gracefully.

Limitations and Notes

  • You’ll only see prevented when your payment processor supplies it; availability varies by processor and merchant enrollment.
  • Prevented indicates the dispute didn’t proceed to a chargeback, and merchants won’t be charged a chargeback fee.

Documentation

For more information, please see the following resources:

Breaking Changes

None

Was this section helpful?