Chargeback Dispute

A customer tells their bank that an online order never arrived, and the bank dispute moves through the card network and payment processor to the seller, who needs to identify the charge, reason and response deadline before deciding how to handle it. A dispute is not identical to an ordinary refund request: a customer-service complaint can often be resolved directly, but an open card dispute follows a defined payment-network process, and issuing a separate refund at the wrong stage can create confusion or double recovery.

Stripe dispute guidance describes notifications, a debit of disputed funds and fees, evidence submission and an outcome decided by the account holder bank, with details depending on processor and network, so merchants should check their actual case record. Reason codes matter, because a fraud claim needs different evidence from 'item not received' or 'service not as described', so read the stated reason rather than sending a generic stack of documents.

Collect truthful records such as order confirmation, delivery proof, customer communication, service terms and relevant authentication information. A signature or tracking number may help but is not automatically decisive if it does not address the specific claim.

Visa publishes merchant dispute-management guidance on requirements and responses within its network, but rules and timeframes change, so a current provider notice for the actual case takes priority over an old summary document. Check the deadline and submission format, because a late response can forfeit the chance to contest and a rushed response with irrelevant or contradictory evidence can also fail, so assign an owner to review the package.

Protect private information by submitting only data relevant to the reason and permitted by the process, without exposing unrelated customer records, full card credentials or internal notes merely to make the file look substantial. Decide when to accept a valid claim: if the item was never shipped and no remedy was given, contesting can cost staff time and damage trust, so the choice should reflect evidence and customer rights, not a blanket policy to fight every dispute.

Some cases have an inquiry or pre-dispute stage rather than an immediate chargeback, with processor terminology and available actions varying, so resolve the underlying customer issue when possible without treating a preliminary alert as a final loss. Track the accounting trail as well, since disputed funds may be temporarily debited while the case is open, a final win may return them and fees can remain, so record provisional and final status rather than counting every open dispute as a permanent write-off.

An illustrative dispute rate is disputes opened divided by card transactions in the same defined cohort, so 50 of 10,000 transactions give 0.5%. Payment networks may calculate monitoring ratios differently, so do not treat this illustration as a network threshold.

Investigate patterns, because repeated non-delivery claims may point to poor address capture, warehouse delays or weak delivery evidence, and unrecognised-charge claims may reflect a confusing descriptor, so fix the cause as well as the case. Keep a case log with charge ID, reason, amount, deadline, evidence, response and outcome, linked to the original order and any customer-support ticket, to avoid duplicate handling and help later analysis.

Train support teams to respond carefully: they can explain the business evidence and options but should not pressure a customer to withdraw a legitimate bank claim, and suspected fraud or complex consumer-law issues go to the right specialist. Measure win rate only with context, since a high rate could reflect contesting only easy cases and a low one could reflect poor evidence or genuine service failures, so compare reason categories and money recovered after fees; for owners, a dispute is both a payment case and feedback about the business, and no document template can guarantee the issuer decision.