What to do when your processor keeps quietly raising fees

Every six months it's another line item. "PCI non-compliance fee." "Regulatory compliance adjustment." "Network access and branding." "Annual rate review." The processor calls it "pass-through cost recovery." You call it what it is — margin creep. And most operators don't catch it until they line up four statements side by side.

Here is what is actually happening, what your MSA lets them do, and how to push back.

1. Why rates creep

Two reasons processors raise rates between annual reviews. (a) Visa and Mastercard raise interchange rates or add assessments, and the processor passes through plus a margin. (b) Processor margin tops out at sign-on and the internal "revenue retention" team slowly adds markup through new fee lines. The first is legitimate. The second is the one you fight.

2. Read your MSA like a lawyer

Most merchant services agreements contain a clause like "Processor may modify fees with thirty (30) days written notice." That clause is the creep-enabler. But it usually stacks with a termination clause giving you ability to exit without ETF if you reject the new fees in writing within 30 days. Most operators miss the rejection window.

3. Catch the creep

Pull the last 6 statements. Calculate effective rate (total fees / total volume) per month. If you see 10+ bps creep over 6 months, you have creep. Specific fee lines to compare quarter-over-quarter: PCI fee, regulatory fee, network access fee, statement fee, gateway fee, "compliance" line items.

4. Identify the mechanism

(a) New line item added (easier to push back on — it did not exist before). (b) Existing line item inflated (requires comparing dollar amounts quarter-over-quarter). (c) Markup on interchange increased (hardest to detect; requires line-by-line interchange analysis).

5. Get a competitive bid

Three bids from three competitors matching your volume and vertical. This is the leverage. Without a competitive bid, the processor has no reason to reduce anything because they know the friction of switching.

6. The negotiation conversation

Email the AOR rep: "My effective rate was X in Q1 and Y in Q3, representing Z bps of creep. I have competitive bids at A, B, C. I want [specific item] reduced to [specific amount] within 30 days or I am exercising my termination rights under section [X] of our MSA." Be specific. Vague complaints go nowhere.

7. What you can get

Common reversals: PCI fee waived ($15-40/month), new "compliance" lines removed, gateway fee reduced to standalone pricing, per-transaction fee reduced 2-5 cents. Harder to get: interchange markup reduction (requires volume commitment or contract extension).

8. When the processor refuses

Do not bluff. If you threaten exit, prepare to exit. Start your migration plan in parallel with the negotiation. Many operators negotiate successfully precisely because they have already started standing up the replacement rail and the processor can tell.

9. The MSA rejection letter

If the processor sends notice of new fees you reject: reply in writing within 30 days citing the MSA clause that allows rejection with exit. "Pursuant to section X, I reject the fee modifications proposed in your [date] notice and request termination without ETF effective [date]." Keep it factual. Document everything.

10. Timing around contract renewal

60-90 days before auto-renewal is the leverage window. Renewal is the natural negotiation moment. Do not let it auto-renew. Send a rate-reduction-or-termination letter 60 days out. The processor's retention team activates at 45 days.

11. What not to do

Do not call support and complain about a single line. Support cannot make pricing changes. Do not escalate without data — reps tune out operators who cannot cite specific numbers. Do not threaten without a real plan to execute.

12. The structural fix

Multi-processor orchestration is the durable answer to fee creep. When you have 3 rails and can shift volume between them, each rail has to compete continuously for your volume. Single-rail operators always eventually pay too much. See multi-brand playbook.

Negotiation template

• Pull 6-month effective rate trend.
• Identify specific creep lines with dollar amounts.
• Get 3 competitive bids.
• Send specific ask with 30-day deadline citing MSA clause.
• Begin migration planning in parallel.
• Document every communication in writing.

Expected outcomes

Processors typically reverse 30-60% of creep if the operator presents cleanly with competitive pressure. Processors rarely fully reset to sign-on rates. If the processor refuses substantially, switch — creep will continue and compound.

The quarterly cadence

Run the audit quarterly so creep never compounds more than one quarter before you push back. See quarterly audit structure. Consolidated reporting across processors makes this 60 minutes instead of 6 hours — see pricing or apply for a rate-creep audit on your current stack.

13. Processor-specific creep patterns

Fiserv and First Data notorious for "annual regulatory compliance" creep and "statement fee" inflation. Square reliably raises rates on specific verticals quietly. Stripe raises per-transaction $0.30 to $0.35 periodically on flat-rate accounts. Authorize.net inflates gateway fees through ISO partners. Pattern-recognition helps — knowing the common creep mechanisms makes auditing faster.

14. The retention team conversation

When you escalate a fee complaint, you get routed to a retention team. This is a different team than sales — they have authority to reduce fees but not dramatically. Typical retention offer: 20-40% reduction of the contested fee for a 12-24 month term extension. Evaluate the tradeoff; sometimes the extension costs more than the saving.

15. The documentation that wins

Every complaint should include: date and exact amount of the contested fee, source citation (statement, email, notice), reference to MSA section permitting or not permitting the fee, comparison to at least two competitive bids, specific ask with deadline. Vague complaints get vague answers. Documented complaints get resolved.