Chargebacks are not just a customer service problem. They are a deadline problem.
If you miss the network window to respond, you lose by default, eat the loss, and often pay a chargeback fee. If you misunderstand the customer filing window, you can be blindsided by disputes on older transactions that you assumed were in the clear.
This guide explains the two clocks that matter: (1) how long a cardholder generally has to file a dispute and (2) how long you generally have to answer it once it lands. Then we translate that into a practical timeline, evidence checklist, and prevention tactics for ecommerce, subscription, and high-risk merchants.
They are a bundle of deadlines that sit in different places.
First, there is the customer filing window, usually measured in days from the transaction date or the expected delivery or service date.
Second, there is the merchant response window, measured from when the dispute is opened by the issuer and routed through the network to your acquirer. Your processor may set an earlier cutoff so they can package and submit on time.
Third, some networks and scenarios include extra stages (inquiry, pre arbitration, arbitration), each with its own timer.
If you want one rule of thumb: assume the cardholder can file for about 120 days and you have about 7 to 21 days to respond after your processor notifies you, unless the notification states otherwise.
Usually up to about 120 days, but the details vary by network, reason, and when the goods or services were supposed to be delivered.
A common misconception is that the clock always starts on the transaction date. For many non fraud disputes, the effective start date is later: the delivery date, the travel date, the subscription billing date, or the date the customer learned there was a problem.
In the US, the Fair Credit Billing Act (FCBA) gives consumers a baseline right to dispute certain billing errors within 60 days after the creditor sends the statement with the disputed charge. Card network rules often extend practical dispute windows for goods and services disputes beyond that baseline.
Your deadline is whatever is in the dispute notification, not what you remember from last year.
That said, merchants commonly see response windows around:
Your processor may require submission earlier than the network deadline. Treat the processor deadline as the real deadline.
Expect a filing window commonly framed as about 120 days for many disputes, with exceptions that can extend the effective window for delayed delivery or future dated services.
On the merchant side, Visa disputes run through Visa Claims Resolution (VCR). In many cases, your first response window is roughly 30 days from dispute initiation, but the exact timer can change by workflow (allocation vs collaboration) and by dispute type.
Practical merchant takeaways:
Mastercard disputes follow Mastercard rules and time limits that vary by chargeback type and message. The most reliable reference is the current Mastercard Chargeback Guide.
A practical pattern for many merchants is that Mastercard gives longer response windows than Visa in some stages, but merchants still need to move quickly because processors set earlier internal deadlines.
Practical merchant takeaways:
Amex is both the network and the issuer for many cardholders, which means the dispute flow can feel different.
You may see tighter evidence standards for certain claims and shorter deadlines for response. Amex also emphasizes clear documentation of refunds, cancellation policies, and proof of participation for digital services.
Practical merchant takeaways:
Discover often uses an inquiry or retrieval style step before a formal chargeback.
If you treat an inquiry like a low priority message, you can miss the window to resolve and prevent escalation.
Practical merchant takeaways:
Below is a simplified timeline you can use to train staff. Your actual deadlines will be the ones in the notice.
| Stage | What happens | Your job | Risk if you miss it |
|---|---|---|---|
| Transaction | Customer buys | Capture consent, AVS, CVV, device data, and clear descriptor | Weak evidence later |
| Fulfillment | You ship or deliver | Record carrier, tracking, delivery confirmation, service date | "Not received" disputes |
| Customer contact | Customer complains | Offer support, document resolution, consider refund | Dispute escalates |
| Dispute opened | Issuer files a dispute | Read reason code, map to evidence, note processor deadline | Automatic loss |
| Representment | You submit a response | Send only relevant evidence, tie it to the claim | Evidence ignored |
| Pre arbitration or escalation | Network review | Decide settle vs continue | Extra fees and time |
| Final outcome | Case closes | Update policy, fix root cause | Repeat losses |
Evidence must directly answer the reason for the dispute. More pages is not better.
Here is a practical checklist by category.
Start with a tight answer: you win by proving the transaction was authenticated or that the cardholder participated.
Use:
If you have high fraud exposure, see our guide to 3D Secure 2: https://merchantalternatives.com/3d-secure-2-merchant-guide/
Start with a tight answer: you win by proving delivery or proving the agreed service date and that it occurred.
Use:
If you operate subscription billing, see our card account updater guide so you reduce failed payments and angry customers: https://merchantalternatives.com/account-updater-vau-abu-amex-cardrefresher-merchant-guide/
Start with a tight answer: you win by showing what was promised and that the customer received it.
Use:
Start with a tight answer: you win by proving clear disclosure, consent, and a functional cancellation path.
Use:
FCBA 60 days is a consumer protection baseline tied to statement timing. Network rules and issuer policies can allow disputes later depending on the scenario, especially for future delivery.
Chargebacks are like court dates. You cannot answer late.
Build a workflow where the dispute is acknowledged the same day, assigned the same day, and drafted within 48 hours.
If the reason code is "services not provided," an AVS match does not help.
Make your response a short narrative: claim, your rebuttal, evidence list, conclusion.
Start with a tight answer: fewer disputes happen when customers recognize the charge and can reach you quickly.
Tactics that usually move the needle:
If you are dealing with excessive chargeback ratios, see our Mastercard chargeback monitoring program guide: https://merchantalternatives.com/mastercard-excessive-chargeback-program-ecm-hecm-guide/
Reason codes are the network's way of labeling why the cardholder is disputing the transaction. The reason code determines what evidence is considered relevant and can also affect the timing.
A simple example: "fraud" disputes often focus on authentication signals and cardholder participation. "Not received" disputes focus on fulfillment and delivery timelines. "Canceled recurring" disputes focus on disclosure, consent, and cancellation records.
Even when the cardholder's filing window is similar across categories, the practical risk is different. If you sell physical goods, the dispute risk spikes when your ship time is long or tracking is weak. If you sell subscriptions, risk spikes when a customer cancels but is billed again, or when the descriptor is confusing.
If you are training staff, teach them to start every case with three questions:
A retrieval request is usually a request for information, such as a copy of the receipt, invoice, or proof of delivery. Some networks or issuers use it as a first step before a formal chargeback.
A chargeback is the reversal itself. Once it is filed, fees and ratio impact are in play.
Treat retrievals as high priority anyway. Fast answers can prevent escalation, and the evidence you assemble for retrieval is usually the same evidence you will need for representment.
Most disputes resolve in weeks, not days.
A simple representment can close quickly if the issuer accepts your evidence. But if the case escalates, the timeline extends because multiple parties have to review documents and make decisions, and some stages allow back and forth.
Operationally, that means you should measure performance in two ways:
If you improve speed, you usually improve win rate because you submit cleaner evidence and you miss fewer deadlines.
Chargebacks have direct and indirect costs.
Direct costs include the disputed amount and the chargeback fee assessed by your processor. Some escalations can also include additional network fees.
Indirect costs include higher processing reserves, rolling holds, account termination, and higher fraud tool costs.
The fastest way to reduce those costs is to treat disputes as an operations function, not an occasional support task. Build a repeatable workflow, set a same day triage rule, and keep templates for your top dispute categories.
Not always. For many disputes, the effective start can be the delivery date, service date, or the date the customer learned there was a problem.
Yes. Certain scenarios such as future delivery, delayed services, or specific reason code exceptions can extend the effective filing window.
Treat your processor deadline as the real deadline and aim to submit within 48 hours. Even if the network window is longer, processors often need time to package the response.
An inquiry is a pre dispute request for information or resolution. If ignored, it can escalate into a chargeback with fees and stricter deadlines.
Yes. If the refund is late or incomplete, or if it was not processed as the customer expected, the dispute can still proceed. Save the refund receipt and the date.
You can apply for a merchant account through Easy Pay Direct or another processor that fits your model. Other options worth a look: