Chargeback Timing Basics
A chargeback is a formal dispute process between your card issuer and the merchant’s acquiring bank, routed through card networks. The network rules include time limits, but the issuer also sets its own deadlines for when you must contact them. That means the date you submit a dispute to your bank often matters as much as the network’s outer window.
Visa and Mastercard both use “reason codes” that map to different dispute categories, such as goods not received, services not rendered, or card-not-present fraud. Each category can have different evidence expectations and different timing requirements. Your bank’s dispute form may ask for the transaction date, the date you first contacted the merchant, and the date you received a final outcome from the merchant, which is where people lose track.
In practical terms, you should treat the transaction date as the starting point, then work backward from your issuer’s deadline. If your issuer accepts disputes only within a shorter window, the network limit becomes a backstop rather than your plan. I’ve seen disputes stall because the cardholder waited for a merchant refund that never arrived, then contacted the bank after the issuer’s internal cutoff.
Common Filing Mistakes
Many disputes fail on timing even when the underlying issue is real. A frequent mistake is waiting for a merchant to “look into it” without getting a written outcome, then filing after the dispute window closes. Another mistake is using the wrong date: some forms require the date of the transaction posting, while others use the date of purchase authorization.
People also confuse chargebacks with refunds. A refund reverses the transaction through the payment rails, while a chargeback is a dispute that can lead to a reversal or a denial. If you receive a partial refund, the remaining amount may still be disputable, but the evidence and reason code need to match what you’re disputing.
Timing depends on supporting steps and dependencies. For many reason codes, networks expect that you attempted resolution with the merchant first, or at least that you can explain why you did not. Your issuer may also require proof such as emails, delivery tracking, service cancellation records, or a fraud timeline. The dispute process then becomes a chain of dates: merchant contact date, merchant response date, and the date your issuer receives the dispute.
One more dependency is the card type and channel. Card-present transactions and card-not-present transactions can follow different evidence patterns, and some fraud categories have different documentation expectations. Even when the network’s outer limit is generous, your issuer may still reject a late submission because their internal workflow cannot meet the network deadline.
Visa Vs Mastercard Deadlines
Visa and Mastercard both publish network rules that include time limits for submitting disputes, but the exact “filing time limit” can vary by dispute reason code and by the stage of the process. Issuers also impose their own deadlines, which are often shorter than the network’s outer window.
Because network rulebooks are detailed and reason-code-specific, the safest consumer approach is to treat the issuer’s deadline as the controlling date. If you want to compare networks, focus on the outer windows that apply to most consumer disputes and then confirm the reason code used by your issuer. Some issuers also show the reason code in the dispute confirmation, which helps you verify that the category matches your situation.
When you read “Visa time limit” or “Mastercard time limit” online, you may see different numbers because authors may refer to different stages: the time to file the initial dispute, the time to respond to representment, or the time for evidence submission. Those stages are not interchangeable, and mixing them leads to wrong expectations.
If you have a dispute in progress, ask your issuer for the dispute stage and the reason code. A short message to support that includes the transaction date and your reason for dispute can trigger a more accurate answer than a generic “what’s the deadline?” request. I’ve noticed that support agents sometimes quote a single deadline without clarifying whether it’s for the initial filing or for evidence submission, so you may need a follow-up.
How To File On Time
Track Dates And Evidence
Start a timeline in a note app or spreadsheet: purchase date, posting date, merchant contact date, merchant reply date, and any refund or cancellation confirmation. Save screenshots of order pages, delivery status, and email threads, then export them to a single PDF if your issuer requests attachments. If you’re disputing a service cancellation, keep the cancellation confirmation and any subsequent billing emails.
For card-not-present issues, document the fraud indicators you observed, such as unfamiliar merchant descriptors, unexpected shipping addresses, or account login alerts. If you used a password manager or received a security alert, record the approximate time of the alert. I once watched a dispute lose momentum because the cardholder had evidence in multiple folders but no single timeline, which made it harder for the issuer to match documents to the reason code.
Contact Your Issuer Early
File the dispute with your card issuer as soon as you have enough information to justify the reason code. Many issuers let you start a dispute through an app or online portal, then request documents later. If your issuer offers a “dispute now” option, use it rather than waiting for a merchant refund that may take weeks.
Ask the issuer two specific questions: what deadline applies to your dispute stage, and what reason code they will use. If the agent cannot answer, request a written confirmation through email or the secure message system. On my last check of a major issuer’s portal flow (version 3.2.1 of their mobile UI, dated 2026-02-10), the portal displayed a “submit by” date for evidence, which was different from the date to open the dispute.
Use Merchant Resolution Wisely
For many non-fraud categories, issuers expect you to attempt resolution with the merchant. Keep proof of that attempt: a ticket number, email thread, or chat transcript. If the merchant refuses or stops responding, document the last contact date and the merchant’s stated reason.
If you receive a partial refund, decide whether you’re disputing the remaining balance or the entire transaction. Your reason code and amount should match the dispute you want. A mismatch can lead to a denial even when the merchant’s refund was incomplete.
Respond To Evidence Requests
After you file, your issuer may ask for additional evidence within a short window. Treat that request like a deadline, not a suggestion. Submit documents in the format requested, and include a short cover note that maps each document to the reason code category.
If you miss an evidence request, the issuer may proceed with the dispute using incomplete information, which reduces the chance of a favorable outcome. Some issuers also allow “representment” later, but representment is not guaranteed and depends on network rules and the merchant’s response.
Educational Case Examples
Goods Not Received, Delayed
A cardholder buys an item online on March 3. The merchant posts a tracking number, but the package shows no movement for several weeks. The cardholder emails the merchant on April 10 and receives no reply. On April 28, the cardholder files a dispute with their issuer using a “goods not received” reason code and attaches the order confirmation and tracking screenshots.
The issuer asks for evidence within a set timeframe. The cardholder submits the merchant email thread and a screenshot showing the tracking status. The dispute outcome depends on whether the merchant can prove delivery and whether the issuer’s reason code and evidence match the network category. In this scenario, the timing works because the cardholder filed before the issuer’s internal cutoff, even though the merchant refund had not arrived.
Subscription Billed After Cancellation
A cardholder cancels a subscription on May 6 and receives a cancellation confirmation email. A charge posts on May 30 for the next billing cycle. The cardholder contacts the merchant on June 2, provides the cancellation confirmation, and requests a refund. The merchant replies on June 12 that the cancellation “did not process,” without providing logs or a refund.
The cardholder files a dispute on June 15 with the issuer, attaching the cancellation email and the merchant’s reply. The issuer may require proof that the cancellation occurred before the billing date. This case often hinges on whether the evidence clearly shows the cancellation timestamp and whether the reason code matches “services not rendered” or “billing error” as categorized by the issuer.
Visa Vs Mastercard Checklist
Use this checklist to reduce timing errors and avoid mixing dispute stages. It does not replace your issuer’s rules, which can be stricter.
| Step | What To Do | Visa Network Timing | Mastercard Network Timing |
|---|---|---|---|
| 1. Open dispute | File with your issuer as soon as you have evidence for the reason code. | Outer window varies by reason code; issuer cutoff often comes first. | Outer window varies by reason code; issuer cutoff often comes first. |
| 2. Submit evidence | Respond to evidence requests quickly and in the requested format. | Evidence deadlines can differ from filing deadlines. | Evidence deadlines can differ from filing deadlines. |
| 3. Representment | Expect the merchant may respond; your issuer may request more documents. | Representment timing depends on the dispute stage and reason code. | Representment timing depends on the dispute stage and reason code. |
| 4. Track dates | Keep a single timeline from transaction date to issuer submission date. | Use the issuer’s “submit by” date when available. | Use the issuer’s “submit by” date when available. |
Decision rule: treat the issuer’s deadline as the controlling date, then use network rules only to understand why a late dispute might be rejected even if you contacted the issuer “soon.”
- Write down the transaction posting date and the date you opened the dispute.
- Confirm the reason code category with your issuer.
- Save evidence that matches the reason code, not just the story.
- Submit evidence before the issuer’s “submit by” date.
- Keep copies of every message and attachment you send.
Common Mistakes To Avoid
Filing after the issuer’s internal cutoff is the most common avoidable failure. Network rules may allow a longer outer window, but issuers often need time to package evidence and meet their own submission schedules.
Another mistake is using the wrong dispute category. If you dispute a billing error as fraud, the evidence expectations change, and the issuer may deny because the documentation does not match the reason code. Your issuer’s portal may show a reason code label; record it.
People also attach irrelevant documents. A screenshot of a product page may help for “goods not received,” but it does not replace delivery proof or tracking evidence. For “subscription canceled,” the cancellation confirmation and billing timeline matter more than generic terms and conditions.
Finally, avoid assuming that a merchant refund automatically resolves the dispute. If you already opened a chargeback, a refund may close the dispute or it may leave a remaining balance to dispute. Ask your issuer whether the dispute is closed, partially closed, or still pending after any refund posts.
FAQ
What date starts the limit?
Most disputes use the transaction posting date or the purchase date, but your issuer’s form may specify which one they use. Use the date shown on your statement for the transaction you’re disputing, then confirm the exact date your issuer uses.
Do Visa and Mastercard have the same deadline?
They share similar concepts but the exact outer windows can vary by reason code and dispute stage. Your issuer’s internal deadline usually controls the outcome because it must meet the network’s submission requirements.
How do I know my reason code?
Your issuer’s dispute confirmation or portal often lists a reason code category label. If it does not, request the reason code category in a secure message and record the answer.
Can I file if I already contacted the merchant?
Yes, and in many categories it helps. Keep proof of your contact and the merchant’s response, then file with your issuer using the reason code that matches the problem.
What happens if I miss the evidence deadline?
Your issuer may proceed with the dispute using incomplete information or deny it. Submit evidence quickly when the issuer requests it, and ask whether late evidence can still be added.
Author's Insight
Chargeback timing is less about memorizing a single number and more about managing a chain of dates across your issuer’s workflow. Visa and Mastercard rules include network time limits, but issuers often impose earlier cutoffs for filing and evidence submission. The most reliable consumer strategy is to open the dispute early, confirm the reason code category, and respond to evidence requests before the issuer’s “submit by” date. If you want to compare networks, treat the comparison as educational and verify the controlling deadline with your specific issuer.
Key Takeaways
- Issuer deadlines usually control chargeback outcomes, even when network rules allow more time.
- Track the transaction posting date, dispute opening date, and evidence submission deadlines in one timeline.
- Match your reason code to your evidence; a correct story with the wrong category often fails.
- Respond quickly to evidence requests and keep copies of every document you submit.
