Chargebacks And Network Deadlines
A chargeback is a dispute process run through your card issuer, using rules set by card networks such as Visa and Mastercard. The network rules include time limits for when a dispute can be filed after a transaction date or after certain earlier steps, like a failed refund attempt. Your issuer may also add its own internal deadlines, so the network deadline is a floor, not a guarantee.
For practical use, treat deadlines as a chain: transaction date, any required pre-chargeback steps, then the chargeback filing window. If you wait too long, the issuer can reject the claim for being late even when the underlying problem seems real. I’ve seen disputes stall because the cardholder submitted the form after the window, then the issuer asked for “additional documentation” that arrived too late to matter.
Because network rules can change and issuers interpret them differently, you should confirm the timeline in your issuer’s dispute portal or by calling the number on the back of your card. If you can, start the dispute as soon as you have a clear reason and supporting records.
Common Pain Points And Misreads
People often assume the chargeback window starts when they notice the problem. In many cases, the clock starts from the transaction date or from a specific event defined by the network rules, such as when the merchant’s refund process fails. That mismatch creates the most avoidable denials.
Another frequent issue is mixing up “refund requests” with “chargeback eligibility.” Some disputes require you to attempt resolution with the merchant first, and the issuer may ask for proof such as emails, ticket numbers, or screenshots of refund status. If you skip that step, the issuer can still file the dispute, but it may be treated as incomplete and delayed.
Supporting evidence matters because chargebacks are not a general complaint channel. A claim is usually evaluated against the transaction type and the reason code, such as goods not received, canceled recurring payment, or card-not-present fraud. If the reason code doesn’t match the facts, the case can be routed to the wrong evidence checklist.
Supporting technologies also shape outcomes. Issuers rely on transaction records, merchant descriptors, shipping or service logs, and sometimes fraud signals. Merchants can respond with proof such as delivery confirmation, service activation timestamps, or signed receipts. When the dispute is about a digital service, the merchant’s system timestamps can carry more weight than a customer’s recollection.
One more dependency: time zones and posting dates. A purchase can post days after authorization, and your statement may show a different date than the merchant’s receipt. That difference can affect how quickly you act, even when the network rule references the transaction date.
How To Act Within Deadlines
Start With Your Issuer’s Timeline
Open your issuer’s dispute flow and look for the “submit by” date or the earliest deadline shown in the portal. If the portal only shows a relative window, record the transaction date from your statement and count the days from that date. When I checked a major issuer’s online portal in mid-2024, it displayed a “dispute must be received by” timestamp in the confirmation email, which was more reliable than guessing from the statement.
If you can’t find a deadline, call the issuer and ask two questions: the earliest date you can file for that transaction type, and the latest date they will accept. Ask them to confirm whether they follow Visa or Mastercard network rules for your card and whether they add an internal cutoff.
Match The Reason Code To Facts
Before filing, write a short timeline: purchase date, expected delivery or service period, merchant contact attempts, and the exact failure (no delivery, refusal to refund, duplicate charge, or unauthorized use). Then choose the reason that matches that timeline. A mismatch can trigger an evidence request that you cannot satisfy, which slows the case.
For goods not received, gather order confirmation, proof of payment, and any shipping or tracking updates. For canceled services, gather cancellation confirmation and any merchant policy text you relied on. For recurring billing disputes, gather the cancellation date and the period covered by the charge.
Keep files in a single folder with filenames that include the transaction date, like “2026-10-01_order.pdf.” It sounds fussy, but it reduces back-and-forth when the issuer asks for “additional documentation” (and it rarely works the way the docs say).
Use Merchant Resolution Evidence
Many issuers expect you to attempt resolution with the merchant before escalating. Send a refund request that states the reason and includes the order number, then save the email thread. If the merchant uses a ticketing system, save the ticket ID and the final response.
When you request a refund, ask for a written confirmation of the outcome. If the merchant says “refund processed,” ask for the refund reference number and the date. If the merchant says “refund denied,” ask for the reason in writing. These details can matter when the issuer evaluates whether the dispute is timely and whether the merchant attempted resolution.
Track Deadlines After Filing
Once you submit, track the case status in the issuer portal and respond quickly to evidence requests. Dispute workflows often have internal processing steps, and delays can push you past the time when the issuer can submit the case to the network. If you receive a request for documents, submit within 24–48 hours when possible.
Also watch for “provisional credit” timelines. Some issuers grant temporary credit while the investigation runs; others wait. Either way, keep records of any credit reversal notices, because those can signal the case is moving toward a decision.
Visa vs Mastercard: Deadline Checks
Visa and Mastercard both use time limits, but the exact windows depend on the dispute reason and the sequence of steps. Public summaries often describe general ranges, while the precise deadline can vary by reason code and by whether the dispute is treated as card-present, card-not-present, or fraud. Because of that, you should compare deadlines using your issuer’s reason-code mapping rather than relying on a single generic number.
Still, you can use a practical comparison checklist: identify the transaction date, identify the reason category, confirm whether a merchant-resolution step is required, and then confirm the “latest submission date” shown by your issuer. If you have both Visa and Mastercard cards, you can compare how each issuer displays the deadline for the same type of issue.
| Dispute Step | Visa (Typical Rule Shape) | Mastercard (Typical Rule Shape) | What You Should Do |
|---|---|---|---|
| Clock Start | Often tied to transaction date or defined event | Often tied to transaction date or defined event | Use the transaction date from your statement and confirm the start event with your issuer |
| Merchant Resolution | May require evidence of attempt for some reasons | May require evidence of attempt for some reasons | Save refund request emails and merchant responses before filing |
| Latest Filing | Depends on reason code and issuer rules | Depends on reason code and issuer rules | Treat issuer “submit by” as the controlling deadline |
| Evidence Window | Issuer may request documents during investigation | Issuer may request documents during investigation | Respond within 24–48 hours when asked; keep a ready document folder |
Educational Case Examples
Online Goods Not Received
Scenario: A cardholder buys a laptop accessory online on March 3. The merchant’s site promises delivery within 7–10 business days. By March 22, no package arrives and tracking shows “label created.” The cardholder emails the merchant on March 23 and receives a reply on March 28 stating “shipment delayed.” The cardholder files a dispute on April 5 after saving the order confirmation, the tracking screenshots, and the email thread.
Lesson: The case hinges on reason-code alignment (goods not received) and evidence of merchant contact. If the cardholder waits until after the issuer’s “submit by” date, the issuer can reject the dispute for timing even when the delivery failure is plausible.
Canceled Subscription With Continued Billing
Scenario: A cardholder cancels a streaming subscription on May 10 using the app’s cancellation flow. The merchant confirms cancellation by email the same day. A charge posts on May 28 for the next billing cycle. The cardholder requests a refund on May 29 and receives a denial on June 2. The cardholder submits a chargeback on June 12 with cancellation confirmation, the denial email, and the statement showing the charge.
Lesson: Evidence of cancellation timing and the billing period matters. A dispute filed after the issuer’s deadline can be rejected even when the cancellation proof is strong.
Common Mistakes That Hurt Outcomes
Filing too late is the most common failure mode. People often count from the day the statement arrives rather than the transaction date, then discover the issuer already passed the latest submission date. A calendar reminder set for the transaction date plus a conservative buffer helps.
Using vague descriptions can also backfire. “Service not as described” without specifics forces the issuer to guess which evidence to request. A better approach lists the exact mismatch: dates, features, quantity, or the promised terms shown on the merchant page at purchase time.
Submitting screenshots without context can reduce credibility. A screenshot of a tracking page without the order number or without the merchant name can look incomplete. Include the order number, the transaction amount, and the date in the same file when possible.
Another mistake is assuming a chargeback reverses the merchant’s obligation automatically. A merchant can respond with proof, and the issuer can deny the dispute. If the dispute is denied, the cardholder may still pursue other routes such as a complaint to the merchant or, where available, a consumer protection channel.
Finally, avoid mixing multiple issues into one dispute. A single chargeback case usually maps to one reason code. If you have both unauthorized use and a refund failure, separate documentation helps the issuer route the case correctly.
FAQ
How Do I Find My Chargeback Deadline?
Check your issuer’s dispute portal for a “submit by” date or ask customer service for the latest filing date for that specific transaction and reason category.
Does The Deadline Start On The Statement Date?
Most disputes use the transaction date or a defined event tied to the network rules, so the statement date often does not control the clock.
What Evidence Helps Most For Goods Not Received?
Order confirmation, payment proof, shipping or tracking updates, and a record of merchant contact with dates and responses.
Can I Dispute A Subscription After Cancellation?
Yes when the charge matches a billing period after cancellation, but you need cancellation proof and evidence of the refund request or denial.
What Happens If My Dispute Is Late?
The issuer can reject the chargeback for timing before it reaches the network, even if the underlying problem seems legitimate.
Author's Insight
Visa and Mastercard both operate through issuer-led dispute processes with network rules that include timing limits, but the exact deadline depends on the dispute reason and the sequence of steps. Issuers also add internal cutoffs and evidence requirements, so the issuer’s “submit by” date usually matters more than a generic network summary. A careful approach focuses on matching the reason code to the facts and assembling dated documentation before filing. When deadlines are tight, starting the dispute early and responding quickly to evidence requests reduces avoidable delays.
Key Takeaways
- Use your issuer’s portal or agent to confirm the latest filing date for your specific transaction and reason category.
- Count from the transaction date and the defined event, not from when you noticed the problem.
- Match the reason code to the facts and include dated evidence of merchant contact when required.
- Respond quickly to document requests after filing; delays can affect how far the case can progress.
