Your Merchant Agreement Has Three Clocks. Only One of Them Is 30 Days.
How Long You Have to Dispute Processing Fees Depends on Which Clock Is Running
If you have ever tried to dispute processing fees, you were probably told some version of “you get thirty days’ notice.” It is the one number most merchants know about their agreement. It is also only one of three separate clocks written into the contract, and it is not the one that costs merchants the most money.
A merchant agreement treats three events differently. When the processor raises its own fee, one clock applies. When Visa or Mastercard change a pass-through cost, a second applies, and it usually gives you no runway at all. When a fee on your statement is simply wrong, a third clock starts on the day the money leaves your account, and it runs whether or not anyone looks at the statement.
Miss the first clock and you lose the right to leave on your terms. Miss the third and, in many program guides, the statement becomes binding: the error is yours to keep. Knowing which event you are looking at tells you which deadline governs, and how much time you have left to dispute processing fees before the door closes.
Thirty days is the notice a processor typically gives before raising its own fees. It says nothing about how long you have to challenge an error that already hit your statement, and it does not apply at all to changes the card networks make.
The Processor Raises Its Own Fee
This is the clock people know. The processor’s own charges, meaning its markup, monthly fees, PCI fees, statement fees and the like, can be raised on notice. The notice period is written into the program guide, the long terms document that sits behind the application you signed.
A bank-issued example shows how precise these clauses are. PNC Bank’s published merchant program guide lets the bank raise or add fees “for any other reason at any time, by notifying you thirty (30) days prior to the effective date.” Stripe’s services agreement also promises at least 30 days’ notice of a fee increase. Square’s payment terms commit only to “reasonable advance notice,” with no number attached.
The part most merchants miss is what the fee increase notice gives you besides warning. The same PNC guide lets a merchant terminate “without further cause or penalty” after a fee increase notice, but only by telling the bank “prior to the effective date.” That is a real exit, and it has an expiry. Once the effective date passes, the new fee is simply part of the agreement, and any early termination fee applies again the way it did before the notice arrived.
A fee increase notice is often three sentences in the footer of a statement. If your guide grants a penalty-free exit, the window to use it closes on the date the new fee takes effect. Separately, a fee raised without the notice your guide requires gives you grounds to dispute processing fees in writing. Reading the notice a month late means reading it after the exit is gone.
The Card Networks Change a Pass-Through Fee
Interchange and network assessments are pass-through fees: the processor collects them and hands them on to the card-issuing bank and the network. Program guides usually treat these differently from the processor’s own fees, because the processor does not set them.
The PNC guide is explicit that a card-organization change “shall become effective upon the date any such change or addition is implemented by the applicable Card Organization.” There is no 30-day runway for these. When Visa updates its tables, the new cost flows straight through. That is normal, and it happens on a published schedule, usually in April and October.
The trouble starts when a processor’s own increase arrives dressed as a network change. If the markup went up, that is clock one, and it needed the full notice period. A footer that blames “card brand changes” for a jump in your effective rate is worth checking against what the networks actually published. We walk through that exact test in Your Processor Said It Was Visa. It Wasn’t.
A genuine network change takes effect immediately. A processor markup increase does not. If a notice calls something a pass-through and the networks published no matching change, you are looking at clock one with the notice skipped, and that is a reason to dispute processing fees in writing.
A Fee on Your Statement Is Wrong
This is the clock that quietly costs merchants money. A duplicate charge, a PCI non-compliance fee after you filed your questionnaire, a rate that does not match your signed pricing: each of these statement errors starts a dispute window the day it happens. No notice arrives to tell you it started.
The windows are short and they vary. The PNC guide requires written notice “within sixty (60) days after any debit or credit is or should have been effected,” and if you miss it, “you conclusively waive your right to commence any related action or assert any related claims.” One ISO’s published program guide gives 60 days measured from the date of the statement instead. Square’s terms give 30 days from when an error first appears in your transaction history, after which failure to report it is “deemed a waiver.”
When you dispute processing fees, two details in those clauses matter more than the number. The first is the starting event: the date money moved and the date a statement was issued can be weeks apart. The second is the form: several guides require the dispute in writing, to a specific address, and a phone call to support does not stop the clock.
The federal billing-error rules people rely on for a personal credit card protect consumers. A merchant account is a commercial contract, so the program guide is the only rulebook. If it says 60 days and you wrote on day 75, the refund is at the processor’s discretion.
The Agreement You Signed Is Probably Not the Processor’s
Search for your processor’s terms and you will often find a clean universal agreement on its website. Most small merchants never signed that document. They signed an application from an independent sales organization, and that application points to a program guide issued by the ISO together with its processor and sponsor bank.
That matters because the clocks can differ. Two guides that sit on the same processing platform can measure the dispute window from different events, set different notice periods, and grant or withhold the penalty-free exit. The governing document is the one referenced on the page you signed, and it usually carries the ISO’s name or a version code on its confirmation page.
So before relying on any notice period, or trying to dispute processing fees under one, find three things: the application you signed, the program guide version it references, and the section numbers for fee changes, disputes and termination. If you cannot find the guide, ask for the exact version in writing. You are entitled to know which rules you agreed to.
Program guides usually print a short code on the cover or footer, something like a bank abbreviation followed by a date. Match that code to the one referenced on your application. If they do not match, the terms you are reading are not the terms you signed.
Set Your Own Clock Before the Processor’s Runs Out
You cannot dispute processing fees you never noticed, so the fix is a habit, not a fight. It takes about fifteen minutes per statement, and it keeps every window open.
- Read each statement within two weeks of its date, while you are inside even the shortest dispute window. If you have never read one line by line, start with how to read a merchant processing statement.
- Compare your effective rate month to month. A jump with no matching network change is a clock-one question.
- Put every fee increase notice on your calendar at its effective date, not the date it arrived.
- When you dispute processing fees, do it in writing, to the address the guide specifies, and keep a dated copy.
- Keep the application, the program guide version, and any pricing addendum in one folder.
If a notice has already arrived, the question is whether to negotiate, leave, or accept. Leaving is only free inside the window, so run the comparison first. Our guide to reducing your processing rate covers what a processor will usually move on, and merchant agreement red flags covers the clauses worth fixing before you sign the next one.
A written dispute sent inside the window is hard for a processor to ignore, because the guide it wrote says the claim is still live. Merchants who read statements monthly recover errors that quarterly readers forfeit.
Frequently Asked Questions
It depends on your program guide. Published guides commonly allow 30 to 60 days, measured from the date the charge posted or the statement date. After that, many guides treat the statement as accepted and waive your claim.
Its own fees usually require notice, often 30 days. Card network pass-through fees can change on the day the network implements them. A markup increase labeled as a network change is still a markup increase.
Some program guides allow it, but only if you give notice before the new fee takes effect. Check the termination section of your guide the day the notice arrives.
Send Your Last Two Statements. We’ll Tell You What Is Still Disputable.
If a fee increase notice just arrived, or a charge on your statement does not match what you signed, the deadline is already counting down. Send Brookside your last two statements and we’ll flag every fee that looks wrong, tell you whether it is a markup change or a network change, and show you your real effective rate. The review takes us about fifteen minutes, which leaves you time to act inside the window. Learn more about payment processing consumer protections from the CFPB.
Send Your Statements for Free ReviewNo obligation • No pressure • Response within one business day
See what a statement review looks like →