When a customer disputes a card transaction, the merchant may receive a notice asking for information or supporting evidence. A good response process focuses on the dispute reason, accurate records, relevant evidence, provider requirements, and the stated deadline.
What Is a Chargeback?
A chargeback is a card-payment reversal that may follow when a cardholder disputes a transaction through the financial institution that issued the card. The dispute may involve suspected fraud, an unrecognized charge, a product or service concern, a cancellation, a refund issue, or a processing error.
The issuer, acquirer, processor, and card network may all have roles in the dispute process. Payment Circle does not make the final decision.
Review Payment Circle’s chargeback management solutions for a general overview of dispute workflows and prevention practices.
Start With the Dispute Reason
Do not submit the same evidence package for every case. The most useful records are those that directly answer the stated concern.
For example, a dispute about non-delivery may require shipping or service-completion records. An unrecognized-transaction dispute may require a recognizable business descriptor, customer history, authorization information, or proof that the customer used the service.
Check the Response Deadline
Review the deadline shown in the provider portal, notice, or communication. Chargeback response windows vary. A business should follow the specific deadline for the individual case rather than relying on a general timeframe.
Assign responsibility to a team member and begin gathering records as soon as the notice is received.
Evidence That May Be Relevant
Transaction Receipt or Order Record
Include the transaction date, amount, product or service, customer details, and order reference when these details are relevant to the dispute.
Customer Authorization
Depending on the payment and provider requirements, authorization information may include signed terms, checkout acceptance, recurring-billing consent, or other evidence showing the customer approved the transaction.
Shipping and Delivery Information
For physical goods, relevant records may include tracking, delivery confirmation, shipping address, carrier information, and customer communication about delivery.
Service Completion or Access Records
For digital or service businesses, records may include appointment attendance, signed completion documents, login activity, download history, course access, project delivery, or support interactions.
Customer Communication
Email and support messages may show that the customer recognized the purchase, requested service, received help, discussed delivery, or agreed to a resolution.
Refund and Cancellation Records
Include the published policy, the customer’s request, the business response, any refund confirmation, and the date of the action.
Organize the Evidence Clearly
A large collection of unrelated documents may be less useful than a smaller, well-organized response. Present the records in a logical order and explain how each item addresses the dispute reason.
Use readable files, clear labels, and accurate dates. Do not alter documents, hide information that changes the meaning, or submit claims that cannot be supported.
Decide Whether to Challenge or Accept
A business should review whether it has relevant evidence and whether a response is appropriate under the provider’s process. Some disputes may be accepted when the transaction was incorrect, the customer was entitled to a refund, or sufficient evidence is not available.
Challenging every dispute automatically can waste time and may not improve outcomes.
Common Evidence Mistakes
- Missing the response deadline
- Submitting evidence unrelated to the dispute reason
- Using unreadable screenshots or incomplete documents
- Providing inconsistent dates or transaction details
- Including long explanations without supporting records
- Submitting altered or misleading information
- Failing to show customer authorization
- Ignoring cancellation or refund communication
- Sending sensitive payment details through unsecured channels
Use Disputes to Improve the Business Process
After each case, record the dispute reason and outcome. Review whether similar cases involve the same product, service, billing descriptor, customer-support issue, fulfillment delay, refund process, or recurring-billing arrangement.
Possible improvements may include clearer checkout language, recognizable descriptors, faster support, better delivery records, accurate renewal notices, or stronger verification tools.