Disputes (Chargebacks)
Payments β Disputes is where you manage chargebacks: cardholder-initiated reversals of payments you processed. The Dashboard groups all activity by ARN (Acquirer Reference Number), tracks each case through its lifecycle, and lets you respond β accept the loss, contest with evidence, or accept a reversal in your favor.
Requires: view chargebacks to see the page; create chargeback event to submit responses; download chargeback evidence to download files.

The Disputes List
The list page opens with three summary widgets β Volume over time, Distribution by latest cycle, and a Reason code summary (code, description, case count, average amount) β followed by the Chargeback Details table:
ARN Β· Cases Β· Merchant Β· Agent Β· Status Β· Latest Cycle Β· Reason Β· Total CB Β· Card Β· Date Issued Β· Reply By Β· Customer Β· Phone Β· Actions
Expanding a row reveals Transaction Details, Customer & Card, Risk Signals (IP address and country, device, fingerprint, visitor ID), and the ARN Timeline across all of that ARN's cases.
Filters: ARN, External ID, Status, Cycle, Reason code, and Period (date received).
Reply By is the deadline that matters. Sort your queue by it β a dispute without a response by that date is typically lost by default.
The Dispute Lifecycle
| Stage | Meaning |
|---|---|
| Pre-Chargeback | Early notification β often resolvable by refunding before it becomes a chargeback |
| First Chargeback | The formal dispute; you respond by accepting or contesting |
| Second Chargeback | The issuer rejected your defense and re-presented the dispute |
| Arbitration | The card network decides β a non-refundable fee applies |
In the list, every dispute shows where it stands for you, and the status filter opens on Action Required:
| Status | Meaning |
|---|---|
| Action Required | Waiting for you: accept or contest the dispute before the reply-by date, or accept a chargeback reversal |
| Waiting | Your response was sent, or the case is with the issuer or the card network; nothing to do until the cycle changes |
| Won | Closed in your favour, including when the issuer recalls the chargeback or you accept a reversal |
| Lost | Closed against you: you accepted liability, the reply-by date passed with no response, or the final decision went to the cardholder |
The response buttons appear on the dispute's page only while it is Action Required. After you respond, a badge takes their place while the response is handled: Awaiting submission (recorded, not yet sent to the provider), Processing (sent, waiting for the provider), or Under review (taking longer than expected).
Responding to a Dispute
Open a dispute to see its full detail and the response actions:
| Action | What it does |
|---|---|
| Accept | Accept the chargeback and absorb the loss |
| Dispute | Contest the chargeback with supporting evidence |
| Accept Reversal | Shown instead of Accept / Dispute when the issuer reversed the chargeback in your favor β accept it to collect the funds |
If the Dashboard cannot load the dispute's response status, a Dispute status unavailable badge appears with a Retry button. Retry only loads the status again β it does not send or resend a response.
Every response dialog asks for a Description (required), an optional Call Number, and a confirmation checkbox.
Disputing requires evidence. The Dispute dialog adds:
- Evidence Type β
Receipt / Invoice,Delivery Proof,Customer Communication,Refund Policy / Terms, orOther Documentation - Evidence Description β what the files demonstrate
- File upload (drag-and-drop) β images (GIF, JPG, PNG, TIFF) and PDF, with per-file, total-size, and file-count limits shown in the dialog. At least one file is required.
What wins disputes: match the evidence to the reason code. Fraud reason codes want proof the cardholder participated (AVS/CVC matches, IP and device signals from the Risk Signals panel, delivery to the verified address). Product/service codes want delivery proof and customer communication. Duplicate/credit codes want your transaction records showing the refund or the distinct orders.
Action History and Reviewer Feedback
Each dispute's Action History timeline tracks your submissions (Not submitted β Submitted) and the review status (Pending β Reviewed). When a reviewer needs more information, their comments appear on the interaction and Add New Evidence lets you attach a follow-up response. Previously submitted files can be retrieved with Download evidences (permission-gated).
You are notified of new chargeback events and submission confirmations via the Notifications bell, which deep-links straight into the dispute.
Reducing Chargebacks
The best dispute is the one that never opens: respond to pre-chargebacks with a refund when the transaction looks unrecoverable, and see Mitigating Fraud for prevention practices.
