Advanced Transaction Routing Interface (ATRI)
Last updated
Last updated
ATRI is used to prevent processing downtime in event there is an issue with a gateway. ATRI only handles the initial sale and does not route recurring billings. Recurring billings will continue to bill against the gateway the original transaction approved against.
THIS TOOL CANNOT BE USED TO MITIGATE CHARGEBACKS
Gateways with hosted payment forms (PayPal, Mollie, Square, etc) are not compatible with ATRI.
Login to CRM and go to Gateways → ATRI, which will redirect you over to ATRI.
Click the Add A Gateway Profile button in the top right
Add a Title to the profile, select an Algorithm and add an Interval.
Interval only affects the Weighted algorithm, but an interval should still be selected if using a different algorithm.
After creating the profile, you will be redirected back to the Gateway Profiles page. From here, click on the name of the profile to edit and add gateways.
Click Add A Gateway to add gateways to the profile.
Max Total Declines: This is the maximum amount of consecutive declines that can occur against a gateway. This is a safety net in case there is ever an issue with a gateway. Once this value is reached the gateway will disable within the profile and you will receive an email notification so you can address the issue. (Rebills do not fall under this, only initial transactions)
Max Hard Declines: This is the maximum amount of consecutive hard declines that can occur against a gateway. This is a safety net in case there is ever an issue with a gateway. Once this value is reached the gateway will disable within the profile and you will receive an email notification so you can address the issue.
Limit Type: Set Limit thresholds for each gateway. Limits can be set for # of Sales (total number of sales), # of Charges (total number of approvals + declines), or # of Revenue (total $ amount that can be processed). Click the pencil icon in the Limit Column to apply/adjust a limit on a gateway.
Enable: Enables or disables the profile.
Force same category: Only use gateways that are inside the same category (from inside the crm).
Prefer same category: Try on an available gateway from same category first, if none are available use one from the profile.
Ignore category: Use any gateway from this profile.
Rebill Projections: These values affect the Projected column. Apply your own retention rates to see more accurate projections.
Gateway Category Sticky: This is used to prevent cross-corping of transactions. Your gateways must be categorized by the Corporation that they were acquired for. If your main offer transaction goes against Corp A, all upsells must go to a Corp A gateway.
Use Rebill Projections: (Only for Round Robin and Weighted) Enabling this setting will account for recurring billings when calculating projections.
Month Cap: Use this to set a lower monthly cap on the gateway for this profile. This is recommended if a gateway is added to multiple profiles.
Overall Gateway: Hover your mouse over this tile to see the overall stats of the gateway. This includes sales and rebills that did not flow through this gateway profile.
Enabled: This shows if the gateway is accepting new sales within the profile.
Actions: Click the trash can icon to remove the gateway from the profile.
Once your gateway profile is created, configured, and saved - Navigate to your campaign inside the CRM and edit the offers and/or upsells.
Alternatively, you can use the Batch Update feature within the Options button.
When complete, go back to the campaign page to see the offers/upsells and their assigned gateway account.
When using ATRI you may encounter these errors:
Error
Cause
Fix
K-20
Just a general error code to indicate it is related to ATRI
No fix, just for informing a problem.
K-22
All gateways in the profile are disabled
Enable a gateway that can accept sales
No gateways in the same category as main offer
A step 1 purchase went against a gateway category that does not exist within the step 2 gateway/cascade profile
Add a gateway of the proper gateway category (determined on checkout transaction) into the profile
No gateways in the same subaccount as the main offer
A step 1 purchase went against a subaccount that does not exist within the subsequent gateway/cascade profile
Add a gateway of the proper subaccount (determined on checkout transaction) into the profile
Please view for a description of the different algorithms.
Please view for a description how to configure each algorithm.
Cascade: Sets the cascade profile for this gateway profile. If a soft decline occurs on any gateway within the profile, that transaction will be routed to the cascade profile for immediate reattempts (up to 5). Please see for Cascade documentation.
