Use case summary
Route fees record the processing cost of each path, and analytics shows those costs alongside approval rates. Routing sends each transaction to the provider that performs, with cost deciding between providers that perform alike. Result: the fee comes down without the approval rate following it.
- Finance & CFO
- Payment Manager
Why the cheapest provider can be the expensive one
Payment costs are not one number. Each route carries its own processing fee, and the same transaction costs noticeably different amounts depending on which provider handles it.
The obvious response is to move more traffic to the cheaper provider. That works until approvals fall, because a declined payment costs the whole sale rather than a few basis points. A route that is cheaper per transaction and worse at getting approved can cost more in total than the one it replaced.
Most teams cannot see both at once. Fees live in provider statements and finance reports, approval rates live in payment analytics, and the figure that decides the question, cost per successful payment, gets assembled by hand or not at all.
How to lower cost and hold approvals
The two are only in conflict when you optimize for one of them. Measured together, most stacks have room to cut cost without touching the routes that perform.
- 1
Record what each route costs
Route fees hold the processing cost for each provider path, which turns cost from something you reconstruct from statements into an attribute the platform knows at the time of the transaction.
- 2
Put cost and approvals in the same view
Analytics includes routing fees alongside transaction outcomes, so you can estimate the margin on a transaction after fees and compare providers on what each one actually returns rather than on its rate card.
- 3
Route on performance, decide ties on cost
This is the order that protects revenue. Send each transaction to the provider with the strongest approval record for that card, issuer, and market, and where two providers perform alike, send it to the cheaper one. The approach is covered in improving approval rates.
- 4
Use volume to earn better pricing
Where a provider's pricing improves past a volume threshold, routing rules can direct volume toward it once that threshold is in reach, so your rate card improves through how you route rather than through renegotiation.
- 5
Avoid the fees a local route would not incur
Conversion markups and cross-border fees apply because of where the acquirer sits, not because of what the transaction is. Routing each currency to a provider that acquires and settles locally removes them.
- 6
Set retry limits deliberately
Cascading recovers payments that would otherwise be lost, and each additional attempt is another transaction. Caps per transaction and per card let you decide how far recovery is worth pursuing rather than leaving it open-ended.
What you get
Cost becomes one input in the routing decision, next to the approval rate it has to be weighed against.
Savings that do not show up as lost sales
Cheaper routes take traffic only where they perform, so the reduction in fees is not paid for by declines that finance never connects back to the change.
Cost per successful payment, not per attempt
Fees and outcomes sit in the same view, which lets finance compare providers on what each one delivers rather than on the rate in its contract.
Better pricing without reopening contracts
Directing volume toward providers whose pricing improves at higher tiers moves your effective rate through configuration rather than negotiation.
A number you can defend
Because each route's cost and performance are recorded, a decision to move traffic can be shown to management with the effect it had on both.
An Eastern European PSP raised conversion to 85.1% while routing on cost where it could
When an Eastern European payment service provider moved its traffic to Corefy, its conversion rate stood at 56.2%. Routing schemes were built to send each transaction to the provider with the highest approval rate for that type of payment, using card issuer, type and brand, authentication mode, customer location, and amount. Where providers performed similarly, the cheaper one was chosen. Over a year, conversion rose to 85.1% while the PSP's traffic grew threefold. Cost was the tie-breaker, not the first filter.