Table of Contents
The ATRI system, an acronym for Advanced Transaction Routing Interface, is also a kind of “load balancer” as it is also available for Merchants who have two or more processing services. It does not use amounts in the way traditional Transaction Routing does but rather works off of the Merchant Defined Fields (acronym: MDF). For any transaction source that is able to send a value via Merchant Defined Fields, the gateway can intelligently route to a specific processor based on that value.
For example, if a Merchant wants all transactions sent with a value of “international” in MDF2 to route to their GBP currency processing service, they would set up the ATRI system to look for “international” in Merchant Defined Field 2 for any transaction.
NOTE: Advanced Transaction Routing Interface will NOT work with CardEase Transactions.
How to enable ATRI for merchant accounts
The steps to enable ATRI for a merchant account are listed below.
Log into your partner account >> Click on ‘List Accounts’ >> Click on the merchant account >> In the ‘Advanced Merchant Feature’ click on ‘Edit’ >> Checkmark the option that says, ‘Enable Advanced Transaction Routing Interface’ >> Click ‘Save’
Once ATRI has been enabled from the partner account, have the merchant log into their gateway account >> click on ‘Options’ >> click on ‘Settings’ >> Click on ‘Transaction Routing’ >> The merchant should be able to see the ‘Merchant Defined Field Advanced Transaction Routing.’
Merchant wants to balance based on Merchant Defined Fields without doing 'username routing'.
Create a Merchant Defined Field (using either the 'Select' or 'Radio' options, and specify a set of values to pass. Example: Label is 'Color' and Radio/Drop Down values are 'Blue', 'Red', 'Green', and 'Yellow'.
Inside the Advanced Transaction Routing Interface, choose the Merchant Defined Field from the drop-down, specify that value (it is Case Sensitive), and tell the system what percentage to route, and click 'Save'.
Note: Percentages should be written as 100.00, not 100% or 100.
The merchant can put 50.00 in Processor A and 50.00 in Processor B if they want 'Blue' to associate with two MIDs. We'll balance 50% in each.
The Virtual Terminal and our Hosted Payment Option, QuickClick, will display actual Radio Buttons/Drop Down selections to choose from. The API requires that the program sends over merchant defined field variables and their associative values.
For Example: merchant_defined_field_1=Blue
In the ATRI interface, if 'Blue' is a valid value, the system will route the transaction to the processor specified. Note, due to case-sensitivity, if you send 'blue' the system will NOT route to the 'Blue' processor.
Advanced Transaction Routing Video Tutorial: https://vimeo.com/200722194