A case visible in Disputes does not mean a response was filed or portal filing is available.
Investigate the case
- Open Disputes and filter by status or source. Needs attention only narrows the list.
- Open the case and match amount, posted date, masked method, and reason to the original payment.
- For a card case, review Original transaction, Timeline, and Case history. For a bank dispute, review the return code and Authorization evidence.
- Read How to respond. Confirm the actual deadline with the case notice or operator; do not infer it from a posted or last-action date.
- Gather the relevant receipt, authorization, delivery record, or other evidence requested for the case.
Summary counts reflect the selected cases. Use the attention filter to find cases that still need a response.
Use an available response route
If Respond to this chargeback is enabled, review Your written response and Evidence documents before choosing Submit response to processor. The confirmation states filing is final. Afterwards, look for the submission confirmation and filed record. Submission does not mean the case was won.
If the screen says filing is being enabled, or provides guidance only, contact the operator promptly with the case reference and deadline. Do not wait for activation before seeking the required response route.
The demo does not file evidence or contact a processor. Coordinate any separate refund on a disputed purchase with your operator before acting.
Practice the dispute workflow
In the design preview, the Disputes list includes a case that needs a response, an empty case, a bank case under review, a won case and a lost case. Status and attention filters narrow the list; summary cards update with those selections.
Open the bank case to inspect populated sample authorization evidence. Open the empty case to start with no uploaded evidence. Add the sample authorization or invoice document, review the evidence packet and written response, then submit it to simulated underwriting. The case moves to Under review and records the submission in its history. Submission requires a written response and sample evidence. A submitted response cannot be sent again.
These document choices use fictional samples. No real file is uploaded, and nothing is sent to a processor or underwriting team. Reloading or resetting the demo restores the original cases. A submitted case is not automatically won; the separate won and lost fixtures show different outcomes.