Rule Creation

Before you begin

Have these details ready:

• Scope: where the rule should apply (for example, a specific product, account group, card group, or across the entire portfolio).
• Rule name: a short, meaningful title.
• Rule description: plain-language explanation of what the rule is for.
• Current transaction conditions: what you want to check on the transaction being processed now.
• Historical conditions (optional): checks against card transaction history and/or merchant history.
• Expected action: what should happen when the rule matches (for example decline, charge a fee, block the card or merchant etc).

Tip: Start with one clear outcome and simple conditions. You can always enhance the rule later.

Step 1: Select the scope

1. Browse to the Decision Engine Configuration screen.
2. Locate the Scope selector on the left hand panel.
3. Choose the level where this rule should apply.
4. Confirm that the selected scope shown at the top of the screen is correct before continuing.

How to choose the right scope

• For more information on scopes please see here
• Remember that all child nodes of a scope will inherit the rule from the parent

Step 2: Add a rule name and description

1. In Rule Name, enter a clear title.
   • Good example: High-value e-commerce velocity check.
2. In Description, write a simple explanation with business intent.

Step 3: Add evaluation for the current transaction

This is where you define conditions based on the transaction currently being processed.

1. Open Current Transaction.
2. Add one or more conditions that should be checked on the transaction being evaluated now.
3. Use combinators (for example AND/OR) as needed between conditions.
4. Keep your first version simple: start with the minimum conditions needed.

Best practice

• Start with the minimum number of conditions needed.
• Check for overlaps with existing rules to avoid unintended duplicates.

Step 4: Add historical evaluation (optional)

Historical evaluation lets you aggregate transaction counts or amounts from past transactions.

You can add multiple instances of one or both of these:

• Card transaction history
• Merchant history

Step 5: Add card transaction history evaluation

1. Open the Card Transaction History section.
2. Click + transaction history button.
3. Select the Card Transaction History or Merchant Transaction History value from the Transaction History Type dropdown depending on which type of history you would like to evaluate against.
4. Define the history window:
   • Example windows: since last 5 minutes, 1 hour, 24 hours, 7 days.
5. Configure how you would like to identify the past transactions using the same method in Step 3
6. Choose the metric to evaluate, such as:
   • Count of transactions
   • Sum of amounts

Optional setting

• Include current transaction can be enabled when you want the current transaction included in historical aggregation logic.

Step 6: Set rule outcomes

1. Open Rule Outcomes.
2. Configure what should happen when the rule conditions are met.
3. Confirm linked action behavior is correct before saving.

Tip: Actions are preconfigured in the Actions Management Section. Please see here for information on action configuration

Step 7: Review your full rule before saving

Quick review checklist:

• Scope is correct.
• Name and description are complete and clear.
• Current Transaction conditions are correct.
• Historic Transactions include the right history type(s): card and/or merchant.
• Rule Outcomes are set.

Step 8: Save the rule

1. Click Add.