Introducing the Prevented DisputeStatus for Clarity

Executive summary:

• New DisputeStatus value 22prevented22.
• Clarifies when chargebacks stop upstream.
• Beneficial for developers and merchants27 operations.

What changed

A new DisputeStatus value, prevented, has been introduced for disputes in the Admin API. Merchants can now distinguish charges stopped before being filed, and the status descriptions are updated for better alignment with real processor outcomes.

Why it matters

This change provides clarity, helping merchants recognize when a chargeback doesn't proceed, thus avoiding fees. It ensures merchants can align their reporting with actual payment scenarios.

Role-specific impact

• Marketers: Modify communication strategies to highlight the benefits of avoided chargeback fees.
• Developers: Update API scripts to handle the new status and refresh automated reports and notifications.
• Store admins: Revise internal dashboards to correctly categorize disputes and manage financial predictions.

Use-case example

Real-world scenario 26 metric

A large retail merchant enrolled through a third-party service sees a 20% reduction in chargeback fees by identifying prevented disputes, aligning operations to reflect this status.

Implementation checklist

1. Inspect API implementations for enum handling to accept 22prevented22.
2. Revise UI components to display the prevented status clearly.
3. Adjust analytics to factor in prevented statuses when calculating fees and dispute resolution success rates.
4. Ensure that any automated workflows or notifications capture and react positively to the new status.

FAQ

Q: What triggers a prevented status?
A: It occurs when a chargeback is halted upstream due to resolution protocols.

Q: Will this affect existing dispute data?
A: No, the change is forward-enabling, affecting new disputes only.

Resources

Refer to the Admin GraphQL DisputeStatus enum for complete insights.

Need guidance? Talk to Makro.