Skip ahead to the main page
Partner Huddle
Pages

Card dispute reply: 2 evidence limits to check first

Partner Huddle Editorial Team · Published · 11 min read

Before you answer a card dispute, check two evidence limits: a 4.5 MB combined file size and a 19-page cap on Mastercard evidence. The notice arrives from your payment processor, it starts a clock, and your reply is judged on the evidence you attach. Many operations leads open that first email, feel the pressure to answer quickly, and start pulling files without checking what the processor will accept. That is how a careful reply gets lost on a technical limit.

This post is written for operations leads and partners at small accounting firms. It covers two evidence limits to check before you write the reply. They are plain facts, not legal advice, and they are easy to miss when a deadline is close. We use Stripe's public dispute documentation as the reference because it states these limits clearly. If your processor is different, read its rules and treat the questions here as a checklist to run against them.

Start with what a dispute is

Before the limits, it helps to be exact about what you are answering. Stripe describes it this way: a dispute occurs when an account owner contacts their bank to contest a payment to you for a number of possible reasons. The customer's bank is part of the process, and the card network is part of it too. Your reply does not undo the customer's claim. It gives the processor the facts it needs to review that claim.

That framing shapes how you build the evidence. You are not writing a letter to the client, and you are not trying to win an argument. You are assembling a file that someone else will read, compare against the stated reason, and decide on. A short, organized packet that answers the stated reason is more useful than a thick folder of everything you have on the client.

Find the deadline before anything else

Stripe's guide on responding states the stakes directly: if you don't respond before the deadline, you automatically lose the dispute and can't retrieve the disputed funds. A missed deadline is not a weak reply. It is a default outcome, and no amount of good evidence can repair it after the fact.

So the first job when a notice lands is to find the response deadline in the system where the case lives and put it on a shared calendar. Do not rely on the date you first opened the email, because a notice can sit unread in a shared inbox. Stripe says it notifies you of disputes through the Stripe Dashboard, email, webhooks, and the API. Those channels can reach different people on your team, so pick one place as the record of the case, name one owner, and tell everyone else where to look.

The owner should confirm three things on day one: the deadline, the reason given for the dispute, and the card network on the payment. Those three facts tell you which limits apply to the case.

Limit one: the combined file size

The first limit is about weight. Stripe's guide on responding says to limit your evidence file size to the combined maximum of 4.5 MB. The word that matters most is "combined." The cap applies to everything you send in one reply, not to each attachment on its own. A handful of scanned files that each look small can add up past the cap quickly.

Accounting evidence is heavy by nature. Phone photos of paper invoices, full-color scans of signed engagement letters, and multi-page bank statements all add size quickly. Teams often build the packet by dragging in every file that seems relevant, then discover the total only at upload. A simple routine keeps you under the cap:

  • Add up the sizes of every file before you start uploading, not one file at a time.
  • Re-save large scans at a resolution that keeps text, dates, and signatures readable. Test one page by zooming in, because a file can shrink until the details that matter are unreadable.
  • Do not drop a document just to make the numbers fit. First decide which items answer the stated reason, then size what remains.
  • Keep full-size originals in your own records, so the only change is to the copy you send.

Limit two: the page count on Mastercard disputes

The second limit is about length, and it is more specific. Stripe's guide says to limit your Mastercard evidence file length to the combined maximum of 19 pages. The number is tied to Mastercard, so do not assume it covers a Visa dispute or a dispute on any other network. Check the requirements for the network on each case before you build the file.

Page count and file size are separate limits. A file can be well under 4.5 MB and still run past 19 pages, and the reverse can happen too. Check both every time.

LimitFigureApplies to
Combined file size4.5 MBEverything sent in one reply
Combined file length19 pagesMastercard disputes

Counting pages is easy to get wrong. A few habits help:

  • Count every page of every attachment, including any cover sheet or index you add. Those pages are part of the file.
  • Remove duplicates. Two copies of the same bank statement, or a full contract when only the signed page matters, use up pages. Cut only pages the stated reason does not call for.
  • Put the most important pages first. A reviewer should be able to find the transaction record, the client's signed agreement, and proof of the work in the first few pages.
  • Write a one-line label for each group of pages, such as "Signed engagement letter, pages 2 to 4." The label helps the reviewer and makes your count easy to check.

Write the reply as a map to the evidence

Once the limits are known, the reply itself should be easy to check. The most useful replies work like a map. Each item in the file should tie to a specific point, so the reviewer never has to guess why a document is there.

Start with a short opening paragraph that names the transaction, the date, the amount, and the reason the client gave. Then list each evidence item with one sentence saying what it shows. For example, a statement might show that the payment cleared, while a completion notice shows the date the work was delivered. Keep the sentences factual and avoid adjectives like "clearly" or "obviously." The reviewer decides what the facts mean.

Be honest about gaps. If a signed document does not exist, say so in plain words and point to the nearest substitute, such as an email thread that shows the client accepted the engagement terms. Do not describe a document you do not have. A reviewer who finds an overstatement will doubt everything else in the file.

Finally, date every item and keep the same client name and transaction reference throughout. Mismatched names and dates can make a reviewer stop and ask questions, and questions cost time you may not have.

Common mistakes that waste the deadline

Most late or weak replies come from a small set of habits. Watch for these:

  • Waiting for a perfect file. Teams hold the reply while they chase one more document, and the deadline passes with a nearly complete packet still unsent. Decide early what you will send, and mark anything missing as missing.
  • Counting files instead of pages or megabytes. Five small files can still break a total limit, and one long file can break a page limit.
  • Compressing a scan until the signature is unreadable. Shrinking a file is useful only if the important details still show.
  • Sending screenshots with no context. A screenshot of a message is more useful when it has the date, the sender, and a one-line label explaining what it proves.
  • Adding cover pages and indexes without counting them. They make the packet easier to read, but they still take up space under the limits.
  • Treating the refund question as an afterthought. Whether to refund changes how much work the reply needs, so decide it before you build the packet.
  • Sending everything on file. Client records are sensitive. Send the documents the reason calls for, and keep the rest in your own systems.

Avoiding these mistakes does not require special tools. It requires a short checklist and one owner who reads it before the upload button is pressed.

Check the refund numbers before you fight

Not every dispute should become a full evidence fight. Stripe's guide also discusses EFWs and offers two figures that are worth reading closely.

The first figure is this: if you don't refund the charge, about 40% of Visa and Mastercard EFWs become fraud disputes (the rate varies by card network and payment amount). The second is this: it's likely not worthwhile to refund EFWs on charges more than 35 percent higher than your dispute fee.

Read these as context, not as rules for your case. The rate varies by card network and payment amount, so do not treat 40% as the chance that your client's warning becomes a dispute. The second figure is a rule of thumb that compares the charge amount with your dispute fee. To use it, find the dispute fee in your processor's terms and compare it with the amount of the charge. If the charge is more than 35 percent higher than that fee, the guide suggests refunding may not be worthwhile. Your firm may still choose to refund for client-relationship reasons, and that is a fair business decision.

Make the refund decision before you spend time on the evidence packet. The answer changes how much work the reply needs, and it is a decision for the firm's leadership, not only for the person who received the notice.

Know the window the client had

Customers do not always file disputes right away. Stripe's guide notes that, for card payments, a 120-day window is common for a customer to file a dispute. That means a dispute can arrive months after the work was done and the payment was taken.

This timing point has a practical effect. If you have to search months of email to find a signed letter after a notice arrives, the search itself can eat the time you need for the reply. Your own record-retention policy and any professional obligations still decide how long you keep records. This section is only about being able to find them quickly when a dispute arrives.

A simple folder structure helps. When a notice comes in, the owner can open the right folder and start sorting without a hunt through old email.

A checklist before you send

Use this list on every dispute. It takes a few minutes and catches the problems that cause the most trouble.

  • Record the response deadline, the case owner, and the place where the case lives.
  • Confirm which card network the payment used, and check the requirements for that network. For Mastercard, apply the page limit described above.
  • Total the file size of all attachments and compare it with the combined size limit above.
  • Count the pages across the whole packet, including cover sheets and indexes, against the page limit for the network.
  • Open each compressed or trimmed file and confirm it still shows the dates, amounts, client names, and signatures that matter.
  • Confirm the refund decision with the right person, using the EFW figures as context.
  • Send only the documents the stated reason calls for.
  • Save an exact copy of what you submitted, with the date you sent it.

If you cannot meet a limit

Sometimes the packet will not fit. When that happens, set a clear order of priority. First come the documents that answer the stated reason. Next come proof of the payment and proof of the work. Background material comes last, and anything that does not change the answer can be left out.

Before the deadline, ask your processor's support team how they handle a packet that is over a limit, and write down the answer with the date and the name of the person who gave it. Do not assume that an over-limit file will be accepted in part, and do not assume it will be turned away. Get the answer in writing, if you can, and plan from it.

Do not let a question about a limit push the reply past the deadline. A short, on-time reply that fits the rules is worth more than a complete one that arrives late.

Make the limits part of your routine

Disputes come up irregularly, so the steps are easy to forget between one case and the next. For the intake side of the file, see Accounting Client Intake Checklist for a Clear Handoff.

Limits and terms can change, and the link to the current page is the place to check. The goal is not to memorize numbers. The goal is to make sure the first hour after a notice goes to the right checks, so the reply your firm sends is complete, on time, and easy for the reviewer to read.

Related guides: Charitable contribution limits: 6 reference entries · Form 9465 payment plan limits: 3 dollar tests · Overdue fee interest limits in 3 states to check first.

Sources