A Chargeback Debits the Merchant First—Then the Evidence Clock Starts

A chargeback can remove a disputed payment—and often a fee—from a merchant’s balance before the customer’s bank makes its final decision. The merchant then has a limited opportunity to accept the loss or challenge it with evidence tailored to the stated dispute reason.

The basic sequence remains stable in current card-industry guidance: the cardholder approaches the issuing bank, the dispute travels through the payment chain, and the issuer ultimately decides whether the debit stands. What merchants need to understand is that response windows, fees and evidence rules are not universal; they depend on the network, processor, location and type of claim.

How the money and the claim move

A chargeback is not an ordinary refund. A refund is initiated by the merchant, while a chargeback begins when a cardholder asks the card issuer to contest a payment. The issuer may grant provisional credit during its investigation, but that does not by itself determine the final result.

The process involves the cardholder, merchant, issuing bank, acquiring bank or payment provider, and card network. The issuer receives the complaint, assigns or communicates a reason for it, and sends the dispute through the network. The acquirer or processor notifies the merchant and normally debits the disputed amount under its applicable terms.

Visa’s current chargeback guidance describes the same core path: the issuer reviews the claim, the merchant can send supporting material through its bank, and the issuer decides whether to uphold or reverse the chargeback. That makes the issuing bank—not the merchant’s processor—the principal decision-maker in a standard card dispute.

What the merchant must do after receiving notice

The first task is to read the notice rather than immediately uploading every document connected with the customer. Check the disputed amount, transaction, reason code, response deadline and any attached cardholder statement. A claim of an unauthorized purchase requires a different answer from a claim that goods never arrived or that a promised refund was not processed.

The merchant then chooses between accepting and challenging the dispute. Acceptance is generally sensible when the customer’s claim is accurate, the available records cannot answer it, or the cost of preparing a defensible response exceeds the amount realistically recoverable. Acceptance does not create a second refund: the disputed funds have ordinarily already been removed or reserved through the chargeback process.

Challenging the claim is commonly called representment. The merchant submits its account and supporting records through the acquirer or processor, which formats or transmits the response through the card network. Missing the displayed deadline normally means losing the opportunity to recover the debit, even when the underlying sale was legitimate.

The deadline shown in the case controls

There is no single response period that every merchant can safely place on a calendar. Network rules, local requirements and processor handling can shorten the time available to the business. The operational deadline in the dispute notice or processor dashboard should therefore control.

As one current processor example, Stripe’s card-dispute lifecycle documentation says merchants usually receive 7–21 days to respond, while issuer review commonly takes 60–75 days and the full process can last two to three months. It also notes that cardholders are typically allowed to initiate disputes within 120 days of payment, with longer periods possible in some circumstances, including purchases for future services.

Those figures explain the broad rhythm, not a promise for every payment provider. Merchants should also check whether receiving or contesting a dispute carries a fee, whether that fee can be returned after a win, and whether the particular dispute is challengeable at all. These conditions can vary by market and contract.

Evidence should answer the reason code

A strong response is a short, coherent account supported by contemporaneous business records. The reviewer should be able to identify the transaction, understand what the customer alleged and see why the attached material contradicts that allegation. A large, unsorted archive can obscure the decisive fact.

Useful evidence depends on the claim:

• For an unauthorized-payment claim, relevant records may include authentication results, device or account information, prior undisputed transactions and communications showing the cardholder’s participation.
• For merchandise not received, use the order record, shipment date, carrier tracking, delivery confirmation and the address supplied at checkout.
• For a product described as defective or materially different, provide the listing or agreed specification, dated customer correspondence and records showing how the complaint was handled.
• For a cancelled service or unprocessed credit, include the cancellation or refund policy accepted at purchase, the customer’s request, the merchant’s response and any refund transaction record.
• For a duplicate charge, identify each transaction separately and show that the payments covered distinct orders; if they did not, the dispute should not be challenged merely to delay the loss.

The submission should be chronological, legible and self-contained. External links, a request that the reviewer contact the business, or unexplained screenshots force the issuer to reconstruct the case. Merchants should preserve the original records and verify the complete packet before submission because some processor workflows allow only one final response.

What winning or losing actually means

If the issuer finds the response persuasive, it overturns the chargeback and the disputed amount moves back through the payment chain to the merchant. A win does not necessarily return every processor or dispute fee; the applicable pricing and contract determine that.

If the issuer upholds the claim, the debit becomes final at the ordinary dispute stage. Further escalation may exist under particular network procedures, but it can involve additional requirements, deadlines and costs. A merchant should not assume that every processor supports arbitration or that every lost case can be reopened.

A customer saying that they withdrew the dispute also does not automatically restore the money. The merchant should follow the processor’s instructions and submit any required proof while the case remains open. Informal assurances from the customer are not a substitute for completing the formal workflow.

The customer’s deadline is a separate question

Merchant response windows should not be confused with a consumer’s legal rights. Those rights depend on jurisdiction, account type and the nature of the complaint rather than one worldwide chargeback rule.

For example, the US Consumer Financial Protection Bureau’s billing-error instructions tell credit-card users to send written notice no later than 60 days after the issuer sent the statement containing the error. The guidance also says the issuer has 30 days to acknowledge the letter and another two billing cycles to investigate. That statutory billing-error route is distinct from the network and processor deadlines governing a merchant’s response.

Prevention begins before checkout

The most defensible chargeback is one supported by records created before any complaint. Merchants should use a recognizable billing descriptor, present prices and recurring-payment terms clearly, preserve proof that policies were accepted, and send prompt order and cancellation confirmations. Delivery and service-completion records should be retrievable by transaction rather than assembled from memory after notice arrives.

Customer support also matters because some disputes begin with an unfamiliar statement entry or an unanswered refund request. A clear contact channel and timely resolution can prevent an inquiry from becoming a formal chargeback. Once a dispute has opened, however, the merchant must use the formal response process and treat its displayed deadline as binding.