Transaction Routing

Transaction Routing

Transaction routing is the process of directing individual payment transactions to specific merchant accounts based on preset rules configured at the payment gateway. It is the current industry term for what was historically called load balancing. Both describe the same practice: a payment gateway holds two or more merchant IDs (MIDs), and each transaction is sent to whichever MID the routing logic selects.

How transaction routing works

Routing rules are configured at the gateway level and evaluated in real time for each transaction. Typical rules include:

• Volume distribution to keep each MID under a monthly or daily cap
• Card type sorting (credit vs debit, card network, issuing country)
• Ticket size routing (small transactions to one MID, high-value to another)
• Failover routing when a MID declines or is offline
• Risk-based routing that sends flagged transactions to a MID with tighter fraud controls

Why transaction routing exists

A single merchant account has hard limits: monthly volume caps set by the acquiring bank, chargeback ratio thresholds set by the card networks, and underwriting exposure limits that determine whether a MID can be trusted with a given business type. Transaction routing sidesteps those single-point-of-failure problems by spreading volume and risk across multiple MIDs that the merchant already owns.

Who uses transaction routing

High-risk businesses use transaction routing most often. Categories like nutraceuticals, continuity billing, high-ticket coaching, firearms, vape and tobacco, and CBD are common examples. High-volume ecommerce businesses use it for redundancy and to negotiate better effective rates by concentrating certain card types on certain acquirers. Any business that has ever experienced a frozen MID is a candidate.

How to set it up

Transaction routing requires a gateway that supports multi-MID configuration, a merchant with two or more approved MIDs (either with the same processor or across acquirers), and routing rules configured at the gateway level. Some processors offer this natively; others require the merchant to layer a third-party gateway. See the Easy Pay Direct review for an example of a processor that offers transaction routing as a native feature.

Transaction routing vs payment orchestration

Payment orchestration operates one layer above transaction routing. Transaction routing directs transactions across multiple MIDs that belong to a single merchant. Payment orchestration directs transactions across multiple payment service providers, each of which may have its own MIDs behind it. Enterprise merchants often use orchestration for PSP redundancy and cross-border reach. Mid-market merchants more commonly use transaction routing for MID redundancy and chargeback management.