Transaction Routing Settings

Transaction Routing, also known as Load Balancing, allows the Gateway to automatically route transactions across multiple processors (MIDs) based on the values you set. Once configured, routing happens automatically and you do not need to select a processor for each transaction.

Default Processor Behavior

  • The Default processor is selected using the radio button.
  • If Load Balancing is OFF, all transactions are sent to the Default processor.
  • You can change the Default processor at any time, even if you are not actively using Load Balancing.

Enable Load Balancing

When Load Balancing is turned on, you assign a monthly routing amount to each processor. These values act as ratios, not hard limits.

Even Distribution Example

  • Processor A: 10,000
  • Processor B: 10,000

Transactions are routed roughly 50/50 until each processor reaches its target.

Weighted Distribution Example

  • Processor A: 10,000
  • Processor B: 100,000

Approximately 10x more volume is routed to Processor B.

The Gateway automatically determines which processor to use for each transaction based on current totals.

Limits and Tracking

On the Transaction Routing page, you can view:

  • Max ticket limit (0 means no limit)
  • Overall monthly limit
  • Load Balance (LB) amount, which tracks how much volume has been routed so far

The LB amount resets on the first day of each month.

Reset Load Balancing Totals

If needed, you can reset routing totals mid-month:

  1. Click Reset Load Balance Amounts
  2. Confirm the warning
  3. Routing totals reset to zero

Important Notes

  • Load Balancing never splits a single transaction across multiple MIDs
  • Each transaction is routed to one processor only
  • Balancing applies to aggregate transaction volume, not individual charges

Video Walkthrough

Watch the video below for a full walkthrough of configuring Transaction Routing and Load Balancing in the EPD Gateway: