What is a Dispute?
- Miles Graves
A Dispute refers to an available action a cardholder can take to argue against fraudulent charges, billing errors, or issues with the product or service provided not meeting expectations, for example.
Typically, the preliminary stage to a formal Dispute is a cardholder complaint to the Merchant. The Merchant should first engage directly with the cardholder where possible to understand their concerns, address potential issues, and work with the customer to resolve any outstanding issues amicably.
Tip: Open communication between Merchants and customers is one of the best ways to avoid a formal Dispute and chargeback.
A Dispute is first initiated by the cardholder (customer of the product or service provided) through their Issuer (the card brand, such as Visa or MasterCard), and goes through a series of reviews, actions, and decisions to eventually rule in favor of the Merchant or cardholder respectively.
Dispute Stages
Dispute Stages are the primary milestones that a Merchant can expect to see when handling Disputes. These six stages
Stage | Description |
|---|---|
Retrieval | The Issuer is looking for more information about the transaction. |
First Chargeback | The cardholder is disputing the transaction payment. |
Representment | Both the Merchant and cardholder submit their first round of supporting evidence. |
Pre-Arbitration | The cardholder lost the first Dispute and both parties will submit more evidence. |
Arbitration | The cardholder lost the second Dispute and both parties will arbitrate further with the card brand. |
Reversal | The Issuer has acknowledged that the transaction is valid and will return funds to the Merchant. |
Warning: Please note that the platform does not offer steps to handle Disputes in the Arbitration stage and must be discussed directly with the Issuer’s Card Brand, such as Visa or MasterCard.
Dispute Statuses
To get started, you’ll want to get familiar with the 4 available Dispute Statuses you’ll frequently encounter:
Dispute Status | Description |
|---|---|
Needs Response | The Issuer is awaiting the Merchant’s evidence, or to Accept Liability, for the Dispute. |
In Review | The Issuer is in the process of reviewing submitted evidence to reach a decision. |
Won | The Issuer has decided in favor of the Merchant. |
Lost | The Issuer has decided in favor of the cardholder. |
When you’re ready to respond to a Chargeback Cycle and/or Dispute Stage, visit the pages below:
Supporting Documentation / Evidence
When a Dispute is initiated, the Issuer may request a detailed explanation of the problem from the cardholder to determine whether a cause for a legitimate Dispute exists.
Reasons for Disputes—those reasons that may be of assistance in an investigation include the following:
The merchant failed to get authorization
The merchant failed to obtain card imprint (electronic or manual)
The merchant accepted an expired card
Supporting documentation or evidence is the primary way for an Issuer to see the validity of the transaction during review and reach a decision. It is critical for Merchants to submit this to have the best chance to win a Dispute.
Below are the different types of evidence a Merchant can provide to help support their claims:
Evidence Type | Description |
|---|---|
Formal Evidence | This includes official documentation directly related to the transaction. Formal evidence includes, but is not limited to:
|
Informal Evidence | Informal evidence is relevant documentation that is not directly related to the transaction. Informal evidence includes, but is not limited to:
|
Note: View the current limitations for response file uploads:
Maximum of 8 documents total
A single document can’t exceed 1 MB
The total of all files cannot exceed 8MB
File Format – Must be either TIFF/TIF or PDF
Must be submitted within the Payrix portal or a Jira ticket 5 business days before the due date.
See the content below for recommendations for supporting documentation or evidence submissions for Disputes:
Card brand Suggested Receipt and/or Invoice Requirements:
Card Present: The following are the Visa requirements for all transaction receipts generated from electronic point-of-sale terminals (including cardholder-activated terminals). It is recommended that merchants provide itemized receipts when possible.
Card-not-Present Transaction Receipt Requirements: The following are the Visa requirements for all manually printed transaction receipts in the card-absent environment.
Type of Evidence | Description |
|---|---|
Credit Card Authorization Documentation | Card brands also consider the following acceptable ways of documenting a cardholder's approval for a transaction:
|
Proof of Delivery or Satisfactory Services | Cardholder goods receipt or satisfactory service rendering confirmation is one of the best protections a merchant can have. Some of the best details are indicated below:
|
Dispute Stage Processing Flows
See the diagrams available below for a visual representation of each Dispute Stage flow:
Dispute vs Chargeback
A Dispute and a Chargeback are two distinct processes related to payment Disputes.
A Dispute occurs when a customer is questioning a transaction with their issuing bank or credit card company, typically due to concerns raised around unauthorized charges, billing errors, or overall dissatisfaction with a product or service. This can be a formal process initiated through their Issuer or credit card company during the preliminary Chargeback proceeding or an informal process where concerns are raised by the cardholder directly and discussed with the Merchant to seek a resolution.
A Chargeback occurs when a cardholder bypasses the Merchant entirely to Dispute the transaction with their Issuer or credit card company to reverse a transaction. Chargebacks are typically more formal and can also incur additional fees from a Merchant perspective. Chargebacks are typically initiated due to claims of fraud, or failure to receive goods or services.
Both listed processes above require prompt response from the Merchant with compelling evidence provided to support their transaction’s validity.
Related Pages