Disputes

Monitor and manage payment disputes from active integrations, tracking dispute statuses, response deadlines, and representment outcomes

The Disputes page in the Chargebackhit HUB displays all disputes associated with your account. You can track dispute statuses, review response deadlines, monitor outcomes, and manage dispute representment.

When you first access the page, you may see:

No integrations enabled – if you have no providers connected
No disputes found – if integrations are active but there are no disputes

Disputes displayed on this page depend on the Guide
Connect external payment providers to automate alert matching, refunds, subscription cancellation, dispute import, and representment workflows. integrations you have enabled. If an integration with a dispute network is active, disputes from that channel appear automatically.

View disputes

To explore and overview disputes, the page provides a list of dispute cases, allowing you to quickly access key details, track deadlines, and see outcomes. The list shows:

Dispute ID – unique dispute identifier
Provider dispute ID – PSP-level dispute identifier assigned by the payment provider
Deadline date – the due date for your response
Status – current dispute state
Amount – disputed transaction amount
Outcome – result after resolution
Reason – chargeback Guide
Explore chargeback reason codes across Visa, Mastercard, Amex, and Discover to navigate disputes and build prevention strategies. reason codes
Source – connected provider the dispute relates to
Dispute channel – indicates if the PayPal dispute is internal or external, shown as — for other providers
Managed by Chargebackhit – indicates whether Chargebackhit automatically handles representment for this dispute
Representment status – current stage of the representment process

To view disputes

Go to your Chargebackhit HUB account.
Navigate to Disputes.
Use Columns and Filters to customize the view by dispute ID, provider dispute ID, date, amount, status, outcome, reason, source, dispute channel, managed by Chargebackhit, or representment status.
Click on Apply to apply selected filters or Clear all to reset.

Regularly check disputes with the Needs response status and respond before the deadline to prevent automatic loss.

Dispute statuses

Disputes may have the following statuses:

Needs response – requires action and evidence submission
Processing – evidence has been submitted
Under review – dispute is being reviewed by the card scheme
Resolved – dispute has been closed and an outcome is available

When the dispute is resolved, it gets one of the outcomes:

Won – resolved in favor of the merchant
Lost – resolved in favor of the cardholder
RDR – Guide
Resolve disputed Visa transactions in real time before they escalate, using a rule-based decision engine to determine refunds or chargebacks automatically. Rapid Dispute Resolution case, closed automatically

Managed by Chargebackhit

The Managed by Chargebackhit column shows whether a dispute was automatically processed by Chargebackhit or passed to the merchant for manual handling.

Value	Meaning
Yes	The dispute meets representment conditions and was processed by Chargebackhit automatically.
No	The dispute was passed to the merchant for manual processing. This occurs when representment is turned off, a filter rule excludes the dispute, or evidence submission failed due to a PSP-side error.
None	The received dispute does not require representment.

Use the Managed by Chargebackhit filter to target disputes by one of the values above.

View dispute details

Clicking on a dispute ID opens the dispute details page, which provides information about that specific dispute case.

The dispute details page includes:

Dispute information
Contains Dispute ID, Provider Dispute ID, Provider Payment ID, amount, reason code, status, dispute creation date, deadline date, outcome, source, Dispute channel, and Managed by Chargebackhit.
Representment information
Displays the current representment status with the Provide enrichment action button. Appears only when automatic dispute representment is enabled for the connected provider.
Dispute history
Shows a chronological timeline of dispute events, such as records about dispute creation and updates on progress. If dispute representment is enabled, you can view the auto-generated representment file submitted for representment.

The Representment information section may have one of the following statuses:

Status	Description
Waiting for enrichment	The dispute is awaiting additional merchant-provided evidence before the representment file can be finalized.
Evidence generation	The evidence file is being generated.
Submission in progress	The evidence file is being submitted to the provider.
Submitted	The evidence file has been successfully submitted to the provider.
Submission failed	The evidence file was sent but rejected by the provider via API, and the merchant can attempt to submit the file manually.
Closed	The dispute cannot be challenged through representment as determined by the provider.

To view dispute details

Go to your Chargebackhit HUB account.
Navigate to Disputes.
Find the dispute you want to view.
Click on the dispute ID to open dispute details.

Evidence enrichment

While automatic Guide
Automate compelling evidence submission to card issuers, challenge invalid disputes, and recover revenue through representment workflows. dispute representment automates evidence generation and submission, disputes may still require additional merchant-specific documentation. It can include delivery confirmations, receipts, application logs, or communication history.

Enrich evidence

Evidence enrichment lets you supplement auto-generated evidence with your own files and information, supporting your case with relevant documentation. Supporting files and additional details can be uploaded before submission to the card network.

Via API

Dispute webhook Webhook notifies you when a dispute is ready for enrichment. To check the current evidence state, use get dispute evidence API . Add or update evidence data using the update dispute evidence API , then submit using the submit dispute evidence API .

Via HUB

To enrich evidence

Go to your Chargebackhit HUB account.
Navigate to Disputes.
Select the dispute to open the dispute details page.
In the Representment information block, click on Provide enrichment.
In the form:
- Select an evidence type and upload a file.
- Provide a short description of this evidence.
Click on Save to confirm the enrichment.

Evidence is auto-submitted on the deadline, or merchants can trigger early submission by clicking on the Submit button.

Upon submission, the dispute status changes to Processing.

Replace evidence

If you need to update or correct evidence files before submission, you can replace them.

To replace evidence

Go to your Chargebackhit HUB account.
Navigate to Disputes.
Select the dispute to open the dispute details page.
Click on Replace next to the file to update it.
Upload the new file and click on Save to confirm.

The new evidence replaces the previous one, and it is submitted on the deadline or when manually submitted.

Dispute representment

If you have prepared your own evidence package, you can submit it directly as a PDF file, bypassing the enrichment flow. The uploaded file is used as the complete evidence package.

Via API

Upload the file via the files upload API to get a file_id, then submit it via the represent dispute API . The operation returns 409 if the dispute is not in a representable state or a representment has already been submitted.

Via HUB

To submit a representment file

Go to your Chargebackhit HUB account.
Navigate to Disputes.
Select the dispute to open the dispute details page.
In the Representment information block, click on Replace next to File.
Upload a PDF file up to 2MB.
Click on Submit.

To learn more about the full representment flow, see the Guide
Automate compelling evidence submission to card issuers, challenge invalid disputes, and recover revenue through representment workflows. dispute representment guide.

Looking for help? Contact us

Stay informed with Changelog