Cascade Profiles

Within ATRI you can create cascade profiles which are used to reattempt soft declined initial transactions.

Hard Declines or Insufficient Funds will not cascade.

---

Create Cascade Profile

Inside ATRI, click on the Cascade menu option on the left side of the page. Then click Add Cascade.

Add a title to the profile, select an algorithm and add an Interval.

Interval only affects the Weighted algorithm, but still choose an interval if using a different algorithm.

Please view this article for a description of the different algorithms.

Intelligent is not an option inside the cascade profile.

Add Gateways to Profile

After initially creating the profile, you will be redirected back to the Cascade 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.

Adjust Settings

Please see this article for descriptions on how to configure each algorithm. Intelligent is not an option inside the cascade profile.

Interval: Sets the time frame that the system uses to determine the overall weights (only for weighted algorithm)

Attempts: The amount of times the cascade will reattempt a soft declined transaction. You cannot attempt against the same gateway multiple times. The maximum attempts allowed is 5.

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.

Actions: Click the trash can icon to remove the gateway from the profile.

Apply Cascade Profile

Once your cascade profile is created, configured, and saved - Navigate to your gateway profile inside ATRI and set the cascade selector to the cascade profile.

You also have the ability to apply a cascade directly to a gateway inside the CRM. This will override any other cascade settings that the gateway is set to follow (via ATRI gateway profiles).

When a cascade occurs, the transaction tables will display multiple transactions from one import order call, and only a single history note on the customer profile will be recorded saying "New order could not be created due to declined transactions."

If you see the "New order could not be created due to declined transactions." message multiple times on the customer history, this means the customer clicked the submit button multiple times.