National merchant dispute guidance
How Long Does a Customer Have to File a Chargeback?
There is no single filing period for every chargeback. Card-network rules commonly use a window tied to the payment, delivery, cancellation, or expected service date, but the exact deadline depends on the network, dispute reason, transaction facts, and issuer process. Merchants should treat 120 days as a useful planning reference, not a universal rule or guaranteed cutoff.
Direct answer
Many card disputes begin within about 120 days, with important exceptions
Stripe's current merchant documentation says card networks typically allow cardholders to initiate a dispute within 120 days of the original payment, while also warning that the rules allow more time in some situations. Mastercard's current merchant chargeback guide confirms that its formal time frames vary by chargeback condition and may be measured from settlement, delivery, cancellation, or an expected service date.
Starting point
The date that starts the window can change
Ordinary completed purchase
Some dispute conditions measure time from the transaction or settlement date. This is the simplest pattern, but it should not be assumed for every claim.
Future delivery or service
For travel, event tickets, appointments, preorders, and other future performance, the relevant clock may start from the expected delivery or service date rather than the earlier payment date.
Cancellation, return, or credit
A claim involving canceled services, returned goods, or an expected credit can use a cancellation, return, credit-document, or promised-refund date under the applicable condition.
Interrupted ongoing service
Some rules account for when the cardholder learned that an ongoing service stopped. Long-stop limits and special documentation can still apply.
Merchant review
How to assess a late-arriving dispute
Identify the exact claim
Record the network, reason code or dispute condition, transaction date, settlement date, delivery or service commitment, cancellation history, and any credit or refund activity. The reason determines which timing rule matters.
Read the provider's case record
The merchant portal or notice should show the case details and the merchant's response deadline. Ask the acquirer or processor which network rule and starting date were used if the timing is unclear.
Preserve date evidence
Keep order confirmations, agreed delivery dates, appointment records, cancellation requests, return tracking, refund notices, and customer communications. These records can clarify both the filing window and the underlying claim.
Respond by the displayed deadline
Do not delay a response while debating whether the cardholder waited too long. Merchant response windows are separate and often much shorter. Submit any timing objection and supporting records through the designated dispute channel before its cutoff.
Examples
Why the purchase date may not tell the whole story
Event booked months ahead
A customer pays in January for an October event. A dispute about the event not occurring may be evaluated from the expected October performance date, subject to the applicable network condition and outer limits.
Merchandise promised later
A merchant accepts payment before a product is scheduled to ship. For a non-receipt claim, the promised delivery date can matter more than the order date.
Refund promised after cancellation
A customer cancels and receives a written credit commitment. A later credit-not-processed claim may use dates connected to the cancellation or promised credit rather than only the original sale.
These examples illustrate date selection only. They do not determine whether a specific dispute is valid, timely, or winnable.
Prevention
Make transaction dates easy to prove
State fulfillment dates clearly
Show expected delivery, appointment, event, or service dates during checkout and in the confirmation. Record customer-approved changes.
Document cancellation and refunds
Timestamp cancellation requests, return receipt, refund approval, and actual refund submission. Give the customer an accurate expectation without promising bank posting times.
Monitor delayed obligations
Track preorders, deposits, subscriptions, travel, tickets, and long-running services beyond the sale date. Older transactions can still create current dispute exposure.
Retain records appropriately
Align retention with the merchant's provider guidance, business obligations, and privacy practices. Store only needed information and protect sensitive payment data.
Related resources
Continue your chargeback research
Common questions
Chargeback filing-window FAQ
Is the deadline always 120 days?
No. About 120 days is a common reference for card disputes, but network rules contain different starting dates, shorter periods, extensions, and special conditions.
Can a dispute arrive more than 120 days after payment?
Yes. That can happen when delivery or service was expected later, an ongoing service stopped, or another rule uses a date after payment. The provider should confirm the applicable condition.
Does an old dispute mean the merchant can ignore it?
No. The merchant must still protect its response deadline. If timing is relevant, raise it through the provider with records that establish the correct dates.
Are bank-account disputes governed by the same windows?
No. ACH and other payment methods use different rules. Identify the payment rail before applying any timeline.
Last editorial review: August 11, 2026. Sources reviewed: Mastercard's current merchant chargeback guide and current Stripe card-dispute documentation. Network and provider procedures can change.
Next step
Map the dates your dispute workflow needs
Payments Max can help organize transaction records, notification ownership, provider questions, and operational review steps for merchant disputes.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US