Two credit card processing statements sit side by side on a restaurant owner's desk. One is from the month he signed his merchant agreement, and the other is from nine months later. The numbers do not match, and the advice he followed, "read your contract before you sign," did nothing to stop the gap.
He did read the contract. He signed it. The deal changed after the ink dried.
The Suspicion Has a Name
"Read the fine print" is the most common advice small operators get about vendor agreements. It sounds right. It is not. Not because reading is bad, but because the advice treats the contract as a fixed thing. A shield you build once and carry forward. The research on this is worth reading, because it names the force that makes that shield fail.
In 1988, William Samuelson at Boston University and Richard Zeckhauser at Harvard ran a series of tests on how people make choices when one option is already in place. They found a pattern so strong they gave it a formal name: status quo bias. People stick with what they have even when the terms are being changed beneath them. The bias runs on habit, on switching costs, and on a quiet belief that what exists must still be close to what was agreed. That belief is wrong.
The pattern shows up in merchant processing with a precision that looks designed. Fiserv, one of the largest payment processors in the world (it bought First Data for roughly $22 billion in 2019), is now the subject of a class action lawsuit. The plaintiffs, a class of investors, allege securities fraud related to Fiserv's merchant migrations and pricing. Class certification proceedings were under way in 2026. This is not one investor's complaint. It is a class of them.
"Read your contract" does not fail the person. It fails the system the person is trying to run.
The Flaw Is Structural
The problem is not that operators skip the fine print. The problem is that "read the contract" replaces "audit the billing." A contract is a snapshot. The billing is a moving target. And the gap between the two grows without a new signature.
Look at the 2025 fee cadence for Fiserv merchants. In early March, the discount rate went up 0.30% per transaction. By early June, a new $35 chargeback fee appeared on statements. In September and November, another 0.10% plus $0.10 per transaction hit some accounts. Four changes in nine months. None required a new agreement. Each one, on its own, looks like a rounding error. Together, they rewrite the deal.
The plaintiffs' lawyers argue that this is not an accident. They claim the statement format itself is part of the pattern: fees, interchange charges, and service charges are all mixed in ways that make single line items hard to spot. A large firm with a finance team catches this in the first month. A restaurant owner running ten tables does not. That gap in attention is what the lawsuit says Fiserv used.
For a business processing $500,000 a year in card volume, the cost of these mid-contract additions runs between $3,000 and $8,000 per year. That is money the owner never agreed to spend. There is a name for this in the literature. Rate creep. And the only tool that catches it is the one the platitude never mentions.
The Replacement: An Effective-Rate Audit
The better rule is simple. Do not trust the contract to hold. Trust the math to show you when it does not. Once that is clear, three moves follow from it.
Move 1: Calculate your effective rate every month
The formula: total fees divided by total card volume, times 100. That gives you a single number. Write it down. Do it the same week each month. Most operators have never run this once. Doing it twelve times a year turns a guess into a trend line, and that trend line is the only thing that tells you whether your deal is still your deal.
Move 2: Compare line items against your original contract each quarter
Pull the signed agreement out of whatever drawer it sits in. Set it next to the latest statement. Go line by line. The contract says what you agreed to pay. The statement says what you are paying. The gap between them is the creep. If a fee on the statement does not appear in the contract, mark it.
Move 3: Flag any month-over-month effective rate increase above 0.1 percentage points
That threshold is small enough to catch the kind of quiet additions that processors use. A single 0.1 point drift might be a seasonal shift in card mix. Two months in a row is a pattern. Three is a billing structure that needs to be challenged.
What the Audit Shows
Running this for one quarter does something the advice never did:
Fee insertions that looked like rounding errors become visible as a sequence.
The true cost gap between what was signed and what is being billed gets a dollar figure.
The statement formatting that hid charges stops working, because you are reading by line item, not by total.
The processor's grip weakens, because you now have the data to call and renegotiate, or to leave.
Three Questions at the End of Each Quarter
At the end of each quarter, ask three things.
→ Which line item moved the effective rate the most?
→ Which charges looked normal but had no match in the original contract?
→ Did the same type of fee increase show up more than once?
That is the difference between advice that sounds right and a system that proves itself.
Where You Stand
The two statements are still on the desk. The gap between them is no longer a mystery. It has a name: rate creep. It has a mechanism: status quo bias. And it has a counter, a ten-minute monthly audit that costs nothing to run.
The contract was never the protection. The audit is.
