What Are Cascades?
A cascade sends surfers through multiple billers based on their payment option in order to encourage more customers to sign-up. If a customer is rejected from one billing processor, the cascade will put them through all available billing options until they are either accepted by a processor, or rejected by all available processors.
Cascades At A Glance
If a particular biller denies a surfer transaction, the surfer is sent to the next biller in the cascade. The diagram, Figure 1.1, provides a simple, graphical representation of this process:
Surfers are sent from one biller to the next until they complete a transaction or the surfer reaches the end of the Cascade. A cascade ends with either of the two special cascade steps: Stop Cascade or Switch Cascade step. For example: a credit card processing cascade might switch cascade to a check processing cascade.
Each Cascade has a description attribute, which is displayed to the surfer on the Join Form. Usually this description is "Join by payment type." By selecting a payment type, the surfer transparently selects the Cascade to handle their transaction.
Cascades can also geo-target whole Cascades or individual Cascade steps using the GeoIP program. Geo-targeting sends surfers from a designated location to a different cascade than surfers from another location.
NATS can also randomly choose the cascade a surfer sees. For example: you can divide your surfers between two billers to test the biller's effectiveness.
Adding/Editing a cascade
For more information on these features, please see our NATS4 Add Cascade wiki article.
Extra Cascade Rules
You can add extra cascade Rules by clicking the Edit Cascade Rules icon. These extra rules allow you to limit this cascade to certain affiliates, programs, sites, times, and tours with the ENABLE rule. You can also choose to exclude certain affiliates, programs, sites, times, and tours from your cascade with the DISABLE rule. For more information on setting up Rules, please see our NATS4 Rules wiki article.
NOTE: You MUST have at least ENABLE one rule configured for your cascade, otherwise it will not work.