Promotion Rule-Based Rejection of Loyalty Transactions

Promotion rule-based rejection of loyalty transactions is a feature that allows loyalty transactions to be rejected when certain conditions are met. Some examples of business rules that a loyalty administrator can define to reject transactions include:

  • Reject a partner transaction if the mandatory Order Number (#) field is left blank.

  • Reject an airline transaction if the Origin and Destination fields for the flight are not specified (since you need these attributes to calculate distance).

Promotion rule-based rejection functionality is built into the promotion engine, does not require external processing, and is distinct from the Reject engine feature. The Reject engine feature rejects a transaction when it is unable to proceed any further with it – for example, if a member does not have sufficient points to redeem an item, when a Partner Account Debit is no longer active, if a Program is not active, or when the member does not have a tier. The promotion rule-based rejection (Reject Transaction) feature rejects a transaction if the defined conditions in the promotion criteria are met.

The benefits of using promotion rule-based rejection of loyalty transactions include the following:

  • It helps prevent the processing of fraudulent transactions.

  • It gives loyalty administrators full control over promotion rules and ability to reject unrealistic conditions.

  • It ensures that the rejection criteria is applied not only to a particular promotion but to all subsequent active promotions, thereby stopping an action sequence.

If you want to use promotion rule-based rejection of loyalty transactions, then do the following:

  1. Define the promotion criteria and conditions to reject transactions. For example:

    Reject Transaction based on the Amount value.

  2. Configure a Reject Transaction action for the promotion criteria, which will be applied when the conditions are met. For more information, see Creating a Reject Transaction Action.

    During transaction processing, the system will check if the transaction value is within the user-defined limit. If not, then the transaction is rejected. Furthermore, the system stops all further promotion evaluations.