Custom Rules

Custom Rules allow merchants to define the way Sales transactions are evaluated.  In addition to using common data fields associated with a sale, merchant defined Custom Fields can be used too.  The enables merchants to create very powerful and precise rules that apply to their unique way of doing business.
 
Step 1: Select Custom Rules from the FBI Tools menu.
Step 2: Click Add Custom Rule or Edit.
Step 3: Enter the following information:
    » Name – Name of the rule being created (or modified).
    » Description – Describe the rule and the reason for it.
    » Categories – The type of Rule being created.  These categories are useful for organizing rules especially when a merchant has created many of them.
 
Step 4: Enter Element 1. Element 1 can be chosen from the list of existing fields or from previously created Custom Fields (see the Admin section of this document for details on creating and managing Custom Fields).  Fields are grouped by Type to make them easier to find:
    » Transaction API Fields – Any fields passed through the API.
    » Custom Fields – Any fields defined by the merchant.
    » Passenger Fields – Any fields used in passenger transactions.
    » Rules – Any rule previously created in the system. This feature allows compound rules.
    » Customer Summary – Fields used to evaluate customers can be used in the equation. Some examples are Customer Score, Disputes, and Chargebacks.
 
 
Step 5: Choose the Operator for the transaction, the choices are:
    » Equal

    » Greater Than
    » Greater Than or Equal
    » Less Than
    » Less Than or Equal
    » Not Equal
    » Between

    » Not Between
    » Contains
    » Not Contains
    » Starts With
    » Not Starts With
    » Ends With
    » Not Ends With
    » At Least N Days Before
    » More Than N Days Before
    » Less Than N Days Before
    » No More Than N Days Before
    » At Least N Days After
    » More Than N Days After
    » Less Than N Days After
    » No More Than N Days After
    » In Speed Date
    » Not In Speed Date
Step 6: Choose Element 2.  Element 2 can be chosen from the list of existing fields or from previously created Custom Fields (see the Admin section of this document for details on creating and managing Custom Fields).  Fields are grouped by Type to make them easier to find:
    » Transaction API Fields – Any fields passed through the API.
    » Custom Fields – Any fields defined by the merchant.
    » Passenger Fields – Any fields used in passenger transactions.
    » Rules – Any rule previously created in the system.  This feature allows compound rules.
    » Customer Summary – Fields used to evaluate customers can be used in the equation.  Some examples are Customer Score, Disputes, and Chargebacks.
    » Custom Value – Any value the merchant chooses to enter. If Element 1 is a date field, a calendar with speed dates buttons (Yesterday, Today, Tomorrow) will be displayed here. Note that Speed Date values are dependent on current date.


 
Step 7: Select the Reject, Accept, Flag for Review, Limit, or Event in the Action field.
If you select the Limit action then you have to select one of the created limits. The transaction fitted to the rule and exceeded the selected limit will be rejected.
If you select the Event action and assign this custom rule to any merchant account then this rule will become available in Echo Data Exchange system and you will able to create a subscription to this rule.
Step 8: Click Enable. If not Enabled, this Rule will not be available for assignment to a merchant account.
Step 9: Click Save. [Optional] Choose a Union Operator for a compound equation, the choices are And or Or.
 
Tip: To create compound statements you may use as many Union Operators as you need. Leave the Union Operator field blank if no further statement evaluators are required.
 
 
 
 
 
 
 
Have more questions? Submit a request

Comments

Powered by Zendesk