Why Comparing Merchant Statements by Percentage Alone Can Give the Wrong Answer
Expert Verified & Fact-Checked
From the Desk of: Chris DuPont, founder of Merchant Statement Analysis, with 17+ years of merchant processing experience.
The Focus: Comparing merchant statements by percentage alone can miss per-item fees, fixed charges, card mix, and transaction differences. Learn why total pricing needs context
Our Approach: Separates card mix and interchange, processor markup, transaction count and average ticket, and fixed or periodic fees so the reader can distinguish transaction or account changes from processor pricing changes without assuming that every unusual line item is an error.
Merchant A pays 2.75%.
Merchant B pays 2.95%.
Merchant A must have the better pricing.
That conclusion is tempting.
It can also be wrong.
Percentage Is Useful—but Incomplete
A percentage is a convenient way to summarize processing cost.
It becomes less useful when the accounts being compared have very different:
- card mix
- transaction counts
- average ticket
- payment channels
- fixed fees
A lower percentage does not automatically mean the processor is charging less markup.
Per-Transaction Fees Can Change the Result
Suppose Merchant A pays a lower percentage but a much higher per-item fee.
Merchant B pays a slightly higher percentage and a lower per-item charge.
For a small-ticket business, Merchant B may actually be cheaper.
The percentage comparison would point in the wrong direction.
Fixed Charges Distort Smaller Accounts
A merchant processing $20,000 per month may feel a $50 monthly charge far more than a merchant processing $500,000.
Comparing their effective rates without accounting for scale can create false conclusions.
The percentage is reporting total cost.
It is not explaining the cost structure.
Card Mix Makes Two Merchants Hard to Compare Directly
A merchant accepting many premium and commercial cards may have a higher effective rate because underlying interchange is higher.
Another merchant with mostly debit may show a lower percentage even with a larger processor markup.
Without separating those components, the second account can look better than it really is.
Transaction Count and Ticket Size Matter
Two businesses can process the same dollar volume and have completely different economics.
One runs a few large transactions.
The other runs thousands of small ones.
Per-item pricing makes that difference important.
Compare a Merchant Against Itself When Possible
One of the more useful comparisons is often:
- current pricing vs. proposed pricing
- same merchant profile
- same transaction assumptions
That removes much of the card-mix problem.
Comparing one unrelated merchant's effective rate with another's can be interesting, but it is not a reliable substitute for statement-based analysis.
A Better Comparison Looks at the Whole Structure
A useful comparison separates:
- underlying card cost
- processor markup
- per-item fees
- fixed charges
- card mix
- transaction profile
Then the percentage becomes a helpful summary rather than the entire conclusion.
An Illustrative Statement Comparison
Take a simplified example. A merchant processes $100,000 in sales. In Month A, total processing cost is $2,700. In Month B, it is $2,900. The blended result moved from 2.70% to 2.90%.
That 0.20-point increase does not tell us what changed. It could come from a higher share of premium or commercial cards, more per-item activity, a periodic fee, worse qualification, or an actual processor price change. The percentage is the symptom; the statement detail is the evidence.
This is the kind of distinction that matters in real statement review. If the analyst jumps straight from “the rate rose” to “the processor raised pricing,” the conclusion may sound confident while still being wrong.
The Statement Sections That Usually Matter
When the question involves a rate change, the useful comparison is broader than the summary page. Transaction count, card-brand mix, interchange or tier detail, processor markup, fixed charges, and any periodic fees all help explain the movement.
The purpose is not to turn the merchant into an auditor. It is to show why a rate change should be traced to a cause. Once the cause is identified, the merchant or agent can decide whether the account is behaving normally, whether a proposal is genuinely better, or whether the processor should be asked for an explanation.
What Deserves a Closer Look
The issue becomes more important when the statement shows a pattern rather than a one-time oddity.
Examples include:
How to Read the Change in Context
A useful month-to-month review separates three possibilities. First, the merchant's underlying transaction mix may have changed. Second, a fixed or periodic fee may have landed in one period but not the other. Third, the provider may actually have changed markup or added a charge.
Those possibilities can create a similar-looking increase on the summary page, but they call for very different conclusions. The statement detail is what separates them.
For an agent preparing a proposal, that distinction also protects the savings estimate. If the current month is expensive because of a temporary event, treating that event as permanent processor margin can make the proposed savings look larger than they really are.
The Bottom Line
The statement should make more sense after the analysis, not less.
That is the standard MSA should bring to every statement and proposal comparison.
How to Read This Issue in Context
For Why Merchant Statement Percentages Can Mislead, merchant statement analysis is more useful than a single headline rate or fee label. Start by comparing card mix and interchange with processor markup. Then review transaction count and average ticket and fixed or periodic fees to determine whether the result is being driven by merchant activity, pass-through cost, processor pricing, or another service.
For Why Merchant Statement Percentages Can Mislead, a multi-period view is usually stronger than a one-month snapshot. If the statement shows a change in card mix and interchange while there is no meaningful change in fixed or periodic fees, the explanation points in a different direction than a month where the merchant’s activity is stable but the pricing line changes. That distinction keeps the review tied to evidence rather than to a quick assumption.
A Practical Statement Checklist
- For Why Merchant Statement Percentages Can Mislead, compare card mix and interchange across the relevant statement periods.
- Separate processor markup from charges that are billed on a different basis.
- Check whether transaction count and average ticket changed enough to explain the movement being reviewed.
- Identify the statement label and billing basis for fixed or periodic fees, and confirm whether the statement provides enough detail to classify it confidently.
What This Does Not Prove
A statement can raise a useful question about Why Merchant Statement Percentages Can Mislead without proving the cause. The better test is whether card mix and interchange, processor markup, transaction count and average ticket, and fixed or periodic fees explain the result. When they do not, the missing answer may sit in the merchant agreement, processor terminology, network rules, or business operations rather than on the statement itself.
For Why Merchant Statement Percentages Can Mislead, the distinction between “shown” and “inferred” matters. Keep confirmed statement evidence separate from interpretations, and verify any classification or cause that the document itself does not establish.
How This Affects a Quote or Review
Carry Why Merchant Statement Percentages Can Mislead into the quote model instead of treating it as a footnote. A shift in card mix and interchange or transaction count and average ticket can distort a one-period comparison, while blending fixed or periodic fees with processor markup can hide the real source of cost. Reconcile those inputs before presenting the savings number.
The final check for Why Merchant Statement Percentages Can Mislead is reproducibility: another reviewer should be able to follow the historical inputs, assumptions, and statement totals to the same conclusion.
Primary Sources to Check
Rates, network rules, and compliance requirements can change. Verify the current primary documentation before publication and before relying on a specific rule or amount.
