Card dispute deadlines: 4 details to record today

Key takeaways

• Save the response deadline with the dispute notice.
• Gather the invoice, written approval, and proof of delivery immediately.
• Save your submitted reply and track the disputed amount until the decision arrives.

This post sets out the timing figures in Stripe's guide to how disputes work, explains what each one means for a small business, and offers simple habits for bookkeepers who handle these cases. The figures are ranges that depend on the card network, so treat them as planning numbers rather than promises. The dates on your own payments are the ones your payment provider shows you.

How long can a customer dispute a card payment?

A cardholder can usually start a dispute within 120 days of the original payment, although card network rules allow more time in some situations. Stripe's guide describes this as a typical window rather than a hard cutoff for every case.

For a small business, the practical lesson is that a sale is not finished when the customer pays or when the job wraps up. A dispute can arrive months later, so the records that prove what you sold and delivered need to last at least as long as that window, and longer if your own retention rules say so. Keep the signed estimate, the invoice, proof of delivery or completion, and the messages that confirm what the customer asked for. Store them somewhere you can search by invoice number, not in a folder that depends on whoever did the job remembering where they saved things. Your accountant can tell you how long to keep records under your own obligations.

How many days do I have to respond to a chargeback?

Your response window starts when the chargeback is created, and its length depends on the card network, according to Stripe's guide.

The range is wide enough to matter. A seven-day window and a twenty-one-day window call for very different routines, and you will not know which one applies until you check the due date for that specific dispute. Read the date from your processor's dashboard rather than counting from the day the email reached your inbox. Plan around the shortest figure until you have confirmed the real date. If you work to the short end, a longer window is a bonus rather than a surprise.

Set a calendar reminder when the notice arrives, with a second reminder a few days before the due date. Then start collecting documents that same day. Waiting to see whether the customer backs down uses up days you cannot get back.

If you cannot gather everything in time, ask your processor what options it offers before the deadline passes. Do not assume an extension exists just because you need one.

How long does the bank take to decide after I submit evidence?

Once you submit evidence, the card issuer usually has 60 to 75 days to evaluate it and reach a decision, depending on the card network. Stripe's guide states that range.

This stage is easy to forget. Once your reply is in, the file goes quiet, and it is tempting to stop thinking about it until a result appears. Write down the date you submitted, and count forward through the range so you know the usual decision window. Silence in the meantime does not mean you won, and it does not mean you lost.

Keep the original records together in case your processor asks for more information. If it does, answer quickly and factually, and save a copy of what you sent. Note in your books that the payment is still under dispute until the outcome is known.

While you wait, keep the rest of your records in order. The habits that help you answer one dispute also help with the next, since a customer who pays by card may raise a challenge on a later invoice too.

How long does a whole card dispute take?

The full dispute lifecycle, from initiation to the final decision, can take 2 to 3 months to complete, according to Stripe's guide. That is the figure to plan around when you think about cash flow and month-end close.

The overall figure is easier to hold in your head when you split it into its two main waits: your response window and the issuer's evaluation. Your work sits mostly in the first wait, and the second is largely out of your hands.

Two to three months is a long time to carry an open amount. If you close your books monthly, one dispute can stay open across two or three closes. That means the disputed amount needs a visible place in your records, not a note in someone's inbox.

How does a dispute affect my cash flow?

A disputed amount may not be yours to keep until the outcome is known. Use the lifecycle described in Stripe's guide when planning for that uncertainty.

Avoid spending the disputed amount as if it were settled, especially on fixed costs such as rent or payroll. If your margins are thin, set the amount aside in your forecast until the decision arrives. Then update the forecast with the actual outcome, whichever way it goes.

A practical way to do this is to keep a separate line in your forecast for open disputes, with the amount and the expected decision window beside it. Review that line each week until it clears, and remove it only when the outcome is recorded in your books. That keeps the open amount in view, so it does not quietly disappear into general income.

Illustrative example: tracking an open amount

An illustrative invoice payment of 50 is disputed. The business records 50 as an open dispute in its forecast, checks the response deadline, and gathers the invoice, written approval, and proof of completion. After submitting its reply, it saves a copy and records the submission date. At month-end, the amount remains visible as disputed. When the decision arrives, the business records the outcome and updates its forecast rather than treating the money as settled while it waits.

Today, choose a recent card payment and put its invoice, written approval, and proof of delivery in one searchable folder. Use the invoice approval checklist to review the approval records you keep.

What happens to an inquiry that never becomes a chargeback?

On Stripe, an inquiry that stays open for 120 days without escalating to a chargeback is marked as closed in both the Dashboard and the API, according to Stripe's guide. Other processors may handle this stage differently, so check their rules rather than assuming Stripe's approach applies.

For your purposes, the practical step is the same whatever the status label says. When a customer raises a complaint about a card payment, log it the day it arrives and respond in writing. An inquiry can escalate into a chargeback, so an answer you give early may resolve the matter before any chargeback deadline begins. Do not assume a quiet inquiry has gone away. Check its status in your dashboard before you close your own file.

Can a refund stop a dispute from becoming a fraud report?

Only a refund processed as a reversal can, and according to Stripe's guide, that usually happens within 2 hours of the payment capture. A refund issued later should not be counted on for that purpose.

The same guide says that if you don't refund the charge, about 40% of Visa and Mastercard early fraud warnings (EFWs) become fraud disputes, and that the rate varies by card network and payment amount. Forty percent is an average across cases, not a forecast for your account, but it shows why a warning deserves a fast response.

That is a reason to set up an alert for any early fraud warning from your processor, and to decide quickly whether a refund is the right call for that customer. Do not refund just to beat a clock without first checking the facts.

What should I do the day a dispute notice arrives?

Start by writing down four facts: the response due date, the card network, the disputed amount, and the original payment date. Every later step depends on them, and they are the first details your processor and bookkeeper will want. Save them with the notice itself.

Next, pull the documents that show what was sold, agreed, and delivered: the invoice, any signed estimate or written approval, proof of delivery or completion, and the messages with the customer. Put them in one folder named with the invoice number. Then read the dispute reason your processor gives you and check whether your records answer that reason directly. A reply that addresses the stated reason in plain words is easier to follow than a general defense of the business.

Keep the tone factual. Describe what was agreed, what was delivered, and when, without adding claims you cannot back up. Before the due date, submit the reply through the dashboard, save a copy of what you sent, and note the submission date. Use that date to track the issuer's evaluation window in Stripe's guide.

What should I say to a customer who disputes a payment?

Ask the customer calmly what they expected from the job and where the disagreement lies. Keep your messages short, polite, and in writing so you have a record of what was said. Listen for whether the gap is about the work, the price, or the timing.

Do not promise a refund or credit before you have checked your own position and your processor's guidance. A friendly conversation also does not replace your reply in the dispute process. Keep working the response deadline in parallel, even if the customer says they will drop the matter.

Should I contest every dispute?

No, not every dispute is worth contesting, and the choice is a business decision you should make before the due date. Weigh three things: the amount at stake, the staff time it takes to gather evidence, and how strong your records are. A small amount backed by thin records may cost more in time than it is worth. A larger amount backed by a signed approval and proof of delivery is often worth the effort.

Be honest with yourself about the record. If the work was incomplete, or the customer has a fair point, it may be better to resolve the matter directly and move on. Write down what you decided and why, so the choice can be explained later to your bookkeeper or accountant.

If you decide to contest, keep the reply focused. Long replies that bury the key documents are harder to follow, so lead with the invoice, the approval, and the proof of delivery, and name each attachment clearly.

How should a bookkeeper track disputed payments?

Track each disputed payment somewhere visible, such as a flag in your accounting software, a memo on the payment entry, or a short running list tied to the invoice number. The aim is that anyone reviewing the books at month-end can see which amounts are still open without asking.

Record three dates beside the entry: the original payment date, the response due date, and your submission date. The submission date anchors the decision window described in Stripe's guide. When the decision arrives, update the entry with the result and the date, and note whether the amount stayed with the business or went back to the customer. For the surrounding payment records, see reconcile invoice payments with your bank.

Ask your accountant how to record the disputed amount while the dispute is open. The right treatment depends on your books, your reporting method, and the rules where you operate, and this post does not set that out.

Ask the same person how open disputes should appear at year-end, so the year-end figures match what your month-end records already show.

Does this timeline apply to every payment method?

No, this timeline covers card disputes only, using figures from Stripe's guide to how disputes work. Bank transfers, checks, cash, and other payment methods follow their own rules.

If a customer pays you another way and later challenges the payment, ask the bank or provider you used what the timeline is. Do not assume the card figures apply. Different providers can set different timing, so check theirs before you plan around any number.

How do I set up records before a dispute happens?

Set up your records so that any card payment can be proven within minutes, long before a dispute arrives.

A simple setup has four parts. First, put an invoice number on every card payment and keep that number on every document that relates to it. Second, save proof of delivery or completion when the work is done, not weeks later. Third, keep customer approvals in writing, even if the approval is only an email reply. Fourth, store everything in one searchable place with a folder for each invoice.

Review the setup once a quarter. Pick two or three recent card payments and check whether you could pull the complete file for each one without asking anyone to search for it. If you cannot, the gap is in your process, and it is worth fixing before a notice arrives.