Actions

Linking actions to a rule enable post authorisation processes to be triggered.

Some actions are handled by us:

• Fees are automatically calculated and included in FAST.
• Notifications (like SMS or email) are sent directly by Paymentology to the configured recipient.
• Declines
• STIP Availability

Others are designed for your systems to handle - for example:

• Client FAST actions which can be used for:
  • Triggering internal alerts
  • Updating dashboards or reports
  • Performing custom business logic
  
  

  📘

  When creating Client FAST Actions, attributes may associated with each action, enabling the consumer to link the action to any downstream process of their choosing via the setting of custom key-value attributes.

Rule to Action Linking

Actions may be shared across rules. In the example below we have 3 rules with actions (some shared) assigned to each of them:

1. Rule 1
   1. Decline Action
   2. Client FAST Action (with an attribute of: action-analytics)
2. Rule 2
   1. Client FAST Action (with a attribute of: action-upsell)
3. Rule 3
   1. Decline Action
   2. Client FAST Action (with a attribute of: action-analytics)
   3. Fee Action

If all 3 of the rules were to be triggered, this is what it would look like:

This is what the consumer of the FAST message would receive:

{
  "DECISION_ENGINE": {
    "Actions": [
      {
        "id": 5,
        "typeName": "DECLINE",
        "details": {
          "attributes": []
        }
      },
      {
        "id": 11,
        "typeName": "CLIENT",
        "details": {
          "attributes": [
            {
              "action": "analytics",
            }
          ]
        }
      },{
        "id": 65,
        "typeName": "CLIENT",
        "details": {
          "attributes": [
            {
              "action": "upsell",
            }
          ]
        }
      },
      {
        "id": 1,
        "typeName": "FEE",
        "details": {
          "amount": 0,
          "basis": "ALWAYS_CHARGE",
          "currencyCode": "980",
          "attributes": []
        }
      }
    ],
    "DryRunActions": []
  }
}

A Little Bit More on Custom Attributes

You will notice from the example above - the existence of an attributes element. This allows you to add your own custom attributes to an action, like {"reason": "velocity-limit", "fraud-level": "0"} - which will be passed along in the FAST message whenever that action is triggered. This makes it easy to drive detailed downstream logic, reporting, or messaging.

{
      "id": 12,
      "typeName": "CLIENT",
      "details": {
        "attributes" : [
          {
            "velocity-limit": "0"
          }
        ]
      }
    }