Chargeback Time Limits: Filing, Response and Resolution

A chargeback time limit is the period allowed for a specific action in a card dispute, such as filing the dispute, submitting evidence, or waiting for a decision. There are three separate clocks: the cardholder filing period, your merchant response deadline, and the resolution timeline. Your merchant response deadline comes from the actual case notification, not from the purchase date.

That distinction matters when an old order becomes a new dispute. The age of the purchase does not tell your support or finance team how many days remain to act. This guide covers filing, merchant response, and resolution in that order. For the full process behind them, see what a chargeback is and the relevant chargeback rules.

Separate the Three Dispute Clocks

A quoted network maximum should never replace the deadline assigned by your processor. Likewise, an estimated decision date is not permission to delay a requested document. Keep those dates in separate fields in your case tracker.

Chargeback Filing Time Limits by Network and Process

Primary references are the Visa dispute rules, Mastercard Chargeback Guide, and American Express merchant response guidance. Use current case instructions to resolve an operational deadline.

A single “30/45/20 days per phase” rule is not a reliable merchant timetable across these systems. Your payment service provider is the practical contact for confirming how and when it needs the response.

How Long Do Merchants Have to Respond?

Stripe’s response documentation describes a window usually ranging from 7 to 21 days, depending on the network. It instructs merchants to respond before the case deadline. For your Stripe workflow, check the dispute details rather than calculating a new deadline from the purchase date.

The network exchange period, the case notice, and any shorter deadline set by your acquirer are different things. When they differ, work to the earliest date shown on your case.

Make the due date visible to everyone working on the case. Include the time zone when one is supplied. If your support team works in a different location from finance, agree on a single displayed deadline so the handoff does not depend on someone converting times from memory.

Set an earlier internal cutoff for gathering compelling evidence. That leaves room to correct a missing attachment or a mismatch between the order and payment.

How Long Does a Chargeback Take to Resolve?

According to Stripe’s dispute lifecycle documentation, once you submit evidence the issuer usually takes 60 to 75 days to decide, depending on the card network. The full lifecycle, from initiation to the final decision, can take 2 to 3 months, and it cannot be reliably accelerated except by accepting the dispute. Treat these as typical ranges, not guarantees. The stage-by-stage detail sits in the chargeback lifecycle guide, and fees that may apply at each stage are covered in the chargeback fees guide.

Example Case Calendar

The dates below are assumed for illustration only. Your own notice shows the real due date and time zone.

When Can a Dispute Arrive After 120 Days?

The applicable start event may be delivery, expected performance, or another event specified by the dispute condition. Visa and Mastercard both have extended provisions, including 540-day limits in particular circumstances. Those provisions do not give every cardholder 540 days, and they do not define a universal end date for the whole dispute lifecycle.

For preorders, future services, or interrupted subscriptions, preserve the dates agreed with the customer and any changes. If you believe a filing is late, ask the processor to assess the specific timing rule while you continue preparing the substantive response.

Do not ignore a case merely because the transaction is old. A timing defense needs the correct rule and start event, not just an order date.

Keep PayPal Deadlines Separate

PayPal account claims and card chargebacks use different processes. Its U.S. Purchase Protection policy gives item-not-received complaints a 180-day filing window. Description complaints use the earlier of 30 days after delivery or fulfillment and 180 days after payment. These periods are not merchant response windows.

Use the PayPal dispute process guide to distinguish filing, escalation, and review. Read each request in the active case, especially if the account has been assigned a shorter response period.

Build a Deadline Workflow Your Team Can Follow

1. Capture the notice. Record the case ID, payment, reason, due date, time zone, and owner.
2. Identify missing evidence. Assign fulfillment, support, or billing records to the team that holds them.
3. Set an internal review cutoff. Leave time for correcting incomplete or unreadable files.
4. Submit deliberately. Check the evidence against the claim, then complete the submission step. Convert the deadline once, to the time zone shown in the portal, and use that displayed time for everyone.
5. Verify receipt. Confirm the case status changed from draft to submitted or under review. Store the confirmation and submission timestamp with the case. A saved draft or a customer’s promise to withdraw the dispute is not a submission.
6. Monitor changes. Treat any follow-up request or escalation as a new task with its own deadline.

Track deadline misses by cause: unattended notice, missing data, ownership gap, or failed submission. Fixing the cause is more useful than simply telling the team to work faster.

What Happens If You Miss the Deadline?

Missing a response deadline can forfeit the opportunity to contest the case. Stripe explicitly states that an unanswered dispute is lost when its deadline expires. Check the closed case and contact your processor if you believe a submission or notification error occurred; do not assume an extension is available.

Recovery and monitoring remain separate measures. A timely response is not proof that a filed dispute disappears from your dispute ratio. Prevention and early dispute alerts address a different part of the workflow.

Frequently Asked Questions

How Long Do You Have to Dispute a Credit Card Charge?

For a billing error on a credit card, the CFPB says to send a written billing error notice within 60 calendar days after the charge appeared on the statement. Card network chargeback rules are separate, and many filing periods are 120 days from a start event that depends on the condition. Issuer practice varies, as shown in the Chase chargeback guide and the Bank of America chargeback guide.

How Long Does a Merchant Have to Respond to a Chargeback?

Use the deadline shown on your case. Stripe describes response windows usually ranging from 7 to 21 days depending on the network, and your processor may set a shorter date than a network period.

How Long Does a Chargeback Take?

Stripe says the issuer’s decision usually takes 60 to 75 days after you submit evidence, and the full lifecycle can take 2 to 3 months. These are typical ranges, not guarantees.

Is 120 Days Always the Chargeback Deadline?

A 120-day period appears in many filing rules, but the applicable condition determines the start event and exceptions. It is not your merchant response deadline.

Do Merchants Always Get the Full Network Response Window?

Merchants must follow the deadline assigned by their processor. A network exchange period is not necessarily the time available to the merchant.

Does Saving Evidence as a Draft Count as Responding?

Saving a draft is not the same as submitting evidence. Verify the case status and submission confirmation before treating the response as complete.

Can a Dispute Be Filed After 120 Days?

A dispute can be filed later when the applicable condition uses a later start event or an extended filing provision. Check the specific rule rather than applying a blanket cutoff.

Should I Wait for the Buyer to Withdraw the Dispute?

Do not let a promised withdrawal replace your response workflow. Follow the processor’s instructions and submit the required evidence before the deadline.

Make Timely Responses Repeatable

Chargeflow Automation helps collect and submit evidence from connected systems. Pair it with clear ownership for missing information and a routine check that responses were received.