Loading...
FinchTrade

Interchange Fees and Payment Processor Margins: Who Keeps the Savings?

How upstream and merchant contracts determine who keeps interchange savings—and when lower payment costs improve PSP contribution.

By FinchTrade 7 min read
TL;DR Key takeaways
  • A lower interchange cost does not automatically increase PSP contribution: upstream and merchant contracts determine who keeps the saving.
  • Better qualification can preserve eligible rates; routing can help only where usable alternatives exist. Neither is a universal cost reduction.
  • Changing payouts after a card purchase does not itself remove interchange. Replacing card acceptance changes the cost structure, but is not automatically cheaper.

A fee-optimization proposal can be right about the saving and wrong about the margin. Lower interchange may improve a payment service provider’s transaction contribution, reduce its merchants’ bills, or leave the benefit with its acquiring partner.

Understanding how interchange fees affect payment processor margins therefore starts with two agreements: what the PSP pays upstream and what it charges merchants downstream. Reducing a cost is only the first step. Those agreements decide who keeps the saving—and who absorbs an increase when costs move the other way.

Interchange belongs to the issuer, not the processor

Card networks establish interchange schedules. On purchase transactions, interchange is generally paid by the acquiring institution to the card issuer. The acquirer independently sets its merchant acceptance price; interchange is an input to that price, not the whole bill.

That distinction answers the question of who pays interchange fees at two levels. The acquirer pays the issuer within the card-payment system. The merchant funds acceptance costs through the price agreed with its provider, rather than ordinarily paying interchange directly to the issuer. Network service fees compensate the network for separate services, while acquiring and processing charges cover other roles. Bundling these components into one merchant rate does not make them economically interchangeable.

A PSP is not necessarily the acquiring institution. It may provide processing while buying acquiring services from another business. Its exposure to interchange then depends on whether that upstream agreement passes through actual interchange, charges a fixed wholesale price, or uses another allocation.

Clearing records the transaction details and amounts owed; settlement discharges those obligations, potentially net of fees. Merchant payout deductions can include issuer, network and provider charges, so they do not measure the PSP’s retained contribution.

The two contracts that decide margin exposure

The first test for any proposed reduction is whether it reaches the PSP’s cost base. If an acquiring partner passes through actual interchange, a lower qualified rate can lower the PSP’s payable cost. If the PSP buys at a fixed wholesale rate, the partner’s underlying saving does not automatically change that rate.

The second test is merchant pricing. A saving that reaches the PSP is not necessarily a saving the PSP can retain. This is the consequential difference between interchange-plus and blended pricing.

Consider a hypothetical PSP whose acquiring agreement passes through actual interchange. On $10 million of monthly transactions, a 20-basis-point reduction in average interchange saves $20,000. Assuming volume and all other direct costs remain unchanged, compare two merchant-pricing arrangements:

  • Fixed blended pricing: merchant charges stay the same, so the PSP’s transaction contribution before overhead rises by $20,000.
  • Actual interchange plus a fixed markup: merchant charges fall by $20,000, while the PSP’s contribution stays the same.

The exposure also runs in reverse. A 20-basis-point interchange increase would reduce contribution by $20,000 under the unchanged blended price. Under the stated pass-through model, the merchant’s bill would rise instead. These figures illustrate the allocation of a cost change, not market rates or an expected optimization result.

Real agreements can divide these outcomes. A blended contract may permit repricing or require specified savings to be shared. A pass-through agreement may treat interchange differently from network charges, or contain minimums and other provisions that affect the final bill. Read the clauses, not just the pricing label.

For a PSP serving both kinds of merchants, the same optimization can support two business cases: retained contribution on one part of the portfolio and cheaper acceptance on another. Both are valuable, but only the retained portion belongs in the immediate margin forecast.

Which cost reductions are actually available?

Before attributing a lower average cost to optimization, look at the transaction mix. Card product, merchant category, geography and whether the card is present help determine the applicable rate. A portfolio average can also fall simply because the mix changes.

A lower portfolio average can tell two different stories. If the share of domestic, in-person payments changes relative to cross-border or remote payments, the average can move because these groups can face different applicable schedules or qualification conditions—even when pricing within each group is unchanged. That is a change in business mix, not evidence that an optimization proposal reduced like-for-like costs. Network and FX charges can also move alongside issuer interchange, so a combined cost difference does not establish which component changed. A forecast that credits the whole movement to optimization overstates what the proposal has demonstrated.

Better qualification preserves an eligible rate

Interchange optimization can mean preventing transactions from losing a favorable rate for which they are otherwise eligible. Qualification can depend on submitted transaction data, the interval between authorization and clearing, and the requirements of the relevant rate program. All applicable requirements must be satisfied.

Correcting missing data or avoidable timing failures can therefore prevent a downgrade. What a proposal calls “interchange downgrade fees” may be the additional interchange caused by less favorable qualification, rather than a separate penalty.

The limit matters: better data does not make every transaction eligible for the cheapest category. If a transaction’s card product or merchant category excludes it from a program, faster clearing alone cannot change that. The credible saving is the cost of avoidable qualification failures on eligible transactions—not a reduction applied indiscriminately across the portfolio.

Routing helps only where usable choices exist

Smart routing can reduce costs only where the merchant has usable network alternatives. The Federal Reserve describes merchant routing protections for debit transactions within Regulation II’s scope—at a U.S. merchant and involving a U.S.-located account—but accepted networks and payment technology still constrain the available routes. This is not a general ability to send any card purchase over the cheapest network.

Compare available routes by their total payable charges, not interchange alone: a lower interchange amount may be offset by another charge. Even a genuine reduction in total route cost improves PSP contribution only if the acquiring and merchant agreements allocate some of it to the PSP.

Commercial terms can reduce costs without changing interchange

A negotiated reduction in an acquiring or processing charge can be just as useful as better interchange qualification. It is simply a different saving.

This distinction prevents a forecasting error: applying the merchant contract’s interchange pass-through mechanism to a reduction that actually occurred in another fee. Identify the charge being reduced, establish what the PSP will pay after the change, and apply the corresponding merchant-pricing terms. A network schedule does not have to change for the PSP’s economics to improve.

Changing the payment rail is not the same as changing the payout

Alternative rails introduce a different question: has the original card acceptance been replaced, or are the resulting proceeds merely being handled differently?

If a customer pays by card and the PSP later converts the proceeds into stablecoins, uses OTC liquidity, or changes the merchant’s payout rail, the original purchase remains a card transaction. Those downstream choices do not by themselves eliminate its interchange. They may change conversion or settlement costs, but that is a separate business case.

If the customer instead pays directly over a non-card rail, such as an account-to-account transfer or crypto payment without a card-funded acceptance leg, the acceptance cost structure changes. Card interchange is not part of that flow, but the replacement is not automatically free. Compare its own acceptance, conversion, settlement and operating costs—and how the merchant agreement allocates them. Removing one fee is not the same as proving a lower total cost or a higher PSP margin.

Conclusion

The right question is not simply how much interchange can be reduced. It is which cost changes, whether that change reaches the PSP, and what the merchant agreement does with it. Model those links for both savings and increases, while keeping downstream settlement separate from card acceptance. That turns an optimization proposal into a defensible margin forecast.

For requesting more information about how we can help reach out to us. We're here to help and answer any questions you may have.

Contact us!

Power your growth with seamless crypto liquidity

A single gateway to liquidity with competitive prices, fast settlements, and lightning-fast issue resolution

Get started