Running Your Workflow Rules
Filing submits a dispute to the card network on behalf of the cardholder. For context on where filing fits in the dispute lifecycle, see What Are Disputes?. The recommended way to file is to run your workflow rules and let Decisionly decide. Use the run workflow endpoint:Run the workflow for a case
202 Accepted. This means Decisionly accepted the case for evaluation, not that it was filed. Three things happen from here.
Fraud cases are held briefly. A cardholder reporting fraud often reports several transactions at once. Decisionly holds fraud cases briefly. Held cases release automatically once the cardholder’s activity settles, and they release as a group per cardholder. Networks limit the number of fraud cases that can be filed, so cases are prioritized by amount. Other dispute reasons are evaluated immediately.
Your workflow rules run. The rules you configure in the dashboard decide whether the case is filed as a chargeback, held for manual review, or rejected. See Workflow Rules.
The case is queued if it is too early to file. Some card networks require a waiting period before filing for certain dispute types. If the case is blocked only by that waiting period, it is queued rather than rejected, and Decisionly files it automatically once the period passes. See Filing Timelines for the waiting period that applies to each network and dispute reason.
You can track what happens next through webhooks: case.held fires when a fraud case is held, case.queued fires when a case is queued for filing, case.chargeback_filed fires when it is filed, and case.chargeback_needs_review fires if it needs manual review.
Once a case is filed with the card network, it cannot be modified or deleted.