Card processing fees typically run between 1.5% and 3.5% per transaction, depending on card type, region, acquirer, and how the transaction is routed. That range sounds abstract until you put revenue behind it: for a merchant processing $10 million a year, every 0.5 percentage points of processing cost is $50,000. Move from 2.8% to 2.3% in blended cost and you've funded a hire; drift the other way and you've silently lost one.
Most merchants overpay not because their negotiated rates are terrible, but because they have no flexibility in how transactions are routed.
When 100% of your volume flows through one PSP, you pay that PSP's price for every transaction, including the cross-border transactions it handles expensively, the card types where its interchange optimization is weak, and the soft declines it fails to recover. You can't route around a provider's weaknesses if there's nowhere else for traffic to go, and you can't negotiate credibly when the provider knows you can't leave.
Payment orchestration platforms like Primer change that math. Read on to find out how.
How orchestration actually reduces card fees
1. Routing each transaction to the cheaper (or better-suited) acquirer
Acquirers aren't uniformly priced. One may be cheap for domestic consumer debit but expensive for commercial cards; another may have strong pricing in one region and weak pricing elsewhere. With one provider, you get one blended reality. With orchestration, you set routing rules — by card type, transaction value, currency, or geography — that send each transaction down the most cost-effective path.
2. Local acquiring
When a transaction is processed by an acquirer outside the cardholder's region, cross-border scheme fees and higher interchange apply, and authorization rates usually suffer too, since issuers view cross-border traffic more cautiously. Routing transactions to an acquirer local to the shopper avoids the cross-border premium on cost and typically lifts approval rates, which is why local acquiring is often the single biggest lever for international merchants. Orchestration makes it practical: instead of a separate integration per regional acquirer, you connect them through one platform and let routing rules send each market's traffic to its local route.
3. Recovering soft declines instead of paying for failure
Failed payments carry costs of their own: you often still pay authorization fees on declined attempts, you lose the sale, and repeated retries against the same failing route just compound the waste. A large share of declines are "soft" — recoverable failures (issuer timeouts, risk-rule false positives, temporary technical issues) that would succeed on a different route. Automated Fallbacks retry those transactions with a secondary processor in real time, recovering previously lost revenue.
The prerequisite: seeing your costs in the first place
None of these levers can be pulled blind. Most merchants genuinely don't know their true cost per transaction by provider, card type, and market — the data is buried across settlement files in inconsistent formats.
This is the problem Primer's Costs Overview exists to solve: it consolidates fee data across providers so you can spot leakage, benchmark one acquirer against another on like-for-like traffic, and identify exactly which routes are eating margin.
Paired with Reconciliation (settlement-level truth) and Observability (performance-level truth), it turns fee reduction from guesswork into a measurable operating loop: see the expensive route, reroute it, verify the saving.
"The simplest way to think about Primer is a gateway to your payment providers. But it's also the gateway to your fraud providers, and to any third party you call to trigger a monitor or a workflow. That makes it the single source of truth for everything happening in payments." – Christophe Smol, Acceptance Product Lead at Primer.
How payment orchestration with Primer can help you reduce card fees
Primer helps merchants reduce card processing costs by giving teams more control over where transactions go, what each route costs, and how failed payments are recovered.
Route payments through better-cost paths
Primer lets you connect multiple PSPs and acquirers through one integration, then route transactions by factors like market, card type, currency, transaction value, provider performance, or cost.
That means you are not locked into sending every transaction through the same default provider. If one acquirer is cheaper for domestic debit, another performs better for international credit, and a local acquirer reduces cross-border costs in a specific market, Primer lets you reflect that in your routing logic.
See what providers are really charging
Cost reduction only works if you can see the true cost of each route.
Primer’s Costs Overview helps teams understand provider charges across processor fees, scheme fees, FX, and other payment costs. Observability shows performance across providers, while Reconciliation helps finance teams match transactions, settlements, and provider reports.
Together, these tools help merchants compare providers on both cost and performance, so routing decisions are based on real commercial impact rather than assumptions.
Recover revenue and keep optimizing
Primer Fallbacks can automatically retry soft-declined payments through another processor when the first route fails. That helps recover transactions that may otherwise be lost because of issuer timeouts, processor issues, or recoverable declines.
Primer Workflows also makes this logic editable by the payments team, without engineering support. Teams can test routes, adjust rules, add fallback logic, and keep improving as provider pricing, performance, and market conditions change.
For merchants operating across multiple markets, processors, currencies, or payment methods, Primer turns payment cost reduction into an ongoing optimization process, not a one-off integration project.
FAQs
Does orchestration route to the cheapest acquirer automatically?
Not by default — you define the rules. In Primer's Workflows you choose which factors (cost, approval rate, geography, card type) drive routing, and the platform executes the logic automatically from then on.
Do I need to add new acquirers to save money?
Not always. Many merchants find savings within their existing setup — recovering soft declines, fixing expensive default routes, or surfacing hidden fees via reconciliation — before adding providers. Even if you do need to add new providers, it’s simple with a tool like Primer.
Won't an orchestration platform's own fees offset the savings?
Platform pricing varies and should be modeled against your projected savings and recovered revenue. For merchants at meaningful volume, recovered declines alone can make a significant difference to your bottom line.
.png)
.avif)
