MID Group Routing - Load Balance

 

The MID Group Routing setting will now “Group” or “Separate” multiple transactions from the same customer according to MID Group. This can be forced or preferred, depending on the strictness you wish to set on the rule. This will prevent issues such as card sharing between corporations.

MIDGroup__LB.png

 

Within the “Load Balancer Summary” you will now see the option for ‘MID Group Routing’ where you will have 4 options to choose from.  Please see below for a description on each of the 4 options.

Force - Group: Force will be a hard rule.  If no available gateways match the MID group, the transaction will be declined.

Force – Separate: Force will be a hard rule.  If there are no available gateways that have a different MID group, the transaction will be declined.

Preferred – Group: Prefer will be a soft rule.  We will attempt to process the transaction on a gateway that matches the MID Group.   If no available gateways match the MID group, it will fall back to the next load balance process.  i.e Weighted, Round Robin, User Defined Priority. 

Preferred – Separate: Preferred will be a soft rule.  We will attempt to process the transaction on a gateway with a different MID Group.  If no available gateways match the MID group, it will fall back to the next load balance process.

This option only works with the NewOrderCardOnFile API method. Transactions from the same customer within the same day will be grouped or separated based upon the MID Group field which can be found in the Gateway Profile Merchant Account Details.

 

These options will also work with any Advanced routing. i.e Force will have to match both Advanced routing rule AND MID Group rules to process.

Have more questions? Submit a request

0 Comments

Article is closed for comments.