Welcome to Midigator's DisputeFlow user tutorials. In this guide, we will explain what you need to do if you choose not to fight a chargeback.
Obviously, if you don’t fight, you can’t recover your lost revenue. However, there are some situations where it might be best to just accept liability.
For example, you may choose not to fight if:
- It’s not cost effective.
- You don’t have enough compelling evidence to win.
- The dispute response deadline has passed.
- You could not locate the transaction in your CRM or order management system.
- You made a mistake and the dispute is legitimate.
- Your processor responded on your behalf.
- Your processor will penalize you for responding.
- You simply don’t want to respond.
In these situations, you’ll want to note your decision in DisputeFlow.
Go to the DisputeFlow data report and click on the New tab.
Review the disputes in the queue and decide whether or not you want to fight.
If you don’t want to challenge the dispute, click the menu in the actions column, and select “Do not fight”.
Select a reason from the dropdown list and click save.
This will move the dispute from the New tab of the report to Completed.
There are several reasons why it is important to use the “do not fight” feature in DisputeFlow:
- It keeps your New disputes report organized. This makes it easy to see which cases still need to be processed so you don’t miss deadlines.
- It helps you monitor ROI more accurately. You won’t be waiting on revenue for disputes that weren’t fought.
- It helps you improve your dispute management strategy. For example, you might discover you need to collect more compelling evidence throughout the customer experience so there are more opportunities to fight.
- It reduces fees. You should respond to all disputes—even if the response is to accept liability. If you don’t, your processor may issue a fine.
Please use the chat feature in Midigator to contact our team if you have any questions. You can also check other DisputeFlow tutorials in the help center.
If you don't have access to DisputeFlow and want to know why, read this article.