Processing fees

Merchant processing fees explained: what can actually be negotiated?

A card-processing bill is easier to judge once you know who controls each charge. Some costs come from the card networks and issuing banks. Others come from the processor. Mixing those together is where most of the confusion starts.

Think of the bill in three layers

Most merchant processing costs can be understood in three broad groups: interchange, card-network fees and processor pricing. The first two are tied to the payment networks. The third is where the processor has the most discretion.

This distinction matters because a business can negotiate a meaningful reduction in processor markup without changing the underlying cost of accepting a particular rewards card. When someone promises to lower every part of the bill, ask exactly which part they mean.

Costs that usually sit outside the processor's control

Interchange is generally set through the card-payment system and varies by transaction. Card-network assessments and related network charges are also generally established outside the merchant's processor. A processor may display, bundle or pass those costs through differently, but it usually does not get to invent its own interchange schedule.

That does not mean those costs should be ignored. They still need to be identified correctly. If network costs are being marked up, bundled oddly or described in a confusing way, the statement deserves a closer look.

Costs that may be negotiable

Processor markup is the obvious place to start. Depending on the pricing model, that can include a basis-point markup, per-transaction markup and processor-added monthly charges. PCI fees, statement fees, account fees, annual fees, gateway-related charges and other add-ons may also be worth questioning.

Whether a fee can be reduced depends on the processor, the account, the service behind the fee and how much leverage the business has. There is no honest universal list that says every processor must remove a certain charge.

Some fees need context before they get labeled as junk

A gateway fee may be reasonable if a business is using a gateway that carries a real cost. A monthly account fee may be part of a pricing package that is otherwise strong. An annual fee can look irritating while still being smaller than the markup saved elsewhere.

That is why reviewing one line at a time can be misleading. The better comparison is the total processor-controlled cost and what the business receives for it.

A lower quoted rate can still produce a higher bill

Merchant pricing is full of rates that look good by themselves. A processor can quote a low percentage while adding per-transaction fees, monthly charges or a pricing structure that costs more for the actual card mix. The comparison that matters is how the proposed pricing would have affected real transactions.

If possible, compare a quote against an actual month of processing. That turns “our rate is lower” into a dollar comparison.

The useful question is simple

Instead of asking whether your rate is “good,” ask how much of the monthly bill is network cost, how much is processor-controlled cost, and whether the processor-controlled portion is reasonable for the account.

That question is less flashy than a promised rate reduction, but it is much more useful.

What Tenmile separates before calling a fee expensive

A processing bill is easier to judge once pass-through costs and processor-controlled costs stop being lumped together. Tenmile first separates interchange and card-network assessments from processor markup, per-transaction charges and processor-added account fees.

That keeps the negotiation focused. Arguing over a network assessment the processor does not control wastes time. Asking why the processor markup or a recurring account fee is still there is a different conversation.

Reviewed for accuracy by Braden, founder of Tenmile Ledger.Background includes merchant services, payment operations and payments enablement.