Custom actions

Custom actions in rules allow you to trigger processes on your end following a defined custom action. Depending on your business model or payment method, you might want to start using custom actions to integrate Fraugster in more complex workflows on your end. Custom actions give you more flexibility of a decision.

Here's a short overview of use cases that might apply to different industries or payment methods:

Industry / payment method	Potential use cases
All industries	Trigger 3DS Do not trigger 3DS Trigger an external check Trigger a review/check with a third-party provider Trigger a call by the call center to collect debt Trigger an email to an employee, partner, customer.
Retail	Set up an ID card check at delivery Require carrier to take a photo of the delivery Use a special carrier Require a call center call
Hotel	Request a POS payment during the check-in Request an ID check at the reception Trigger alert to the receptionist
Airlines	Require an ID check during the check-in Trigger a refund Require a cash payment during the check-in
Gaming	Block an account (game) Block an account (payment) Block both accounts (game and payment) Block a payment method Block a payment Verify an account
BNPL	Require an AML check Require a reseller check

Create custom actions

You create and manage custom actions through a dedicated section in the Rule manager. You have to define at least one custom action to be able to use it in rules.

To create a custom action:

1. Go to Rule manager → Custom actions. Select + Add custom action to get started.
2. Give your action a meaningful name depending on your use case. There is a length restriction of 35 characters on the name. As you type in a name, the pop-up immediately suggests the corresponding API string. We return action in the rule_hits object, so it’s important for you to communicate the custom action definition to your developers. Your integration must be updated with the corresponding API string for the custom action to work. For better usability, you can copy the API string to clipboard directly from the pop-up. Read more on the API response in Rule hits.
3. Define a priority for your custom action. Custom actions take the lowest priority among all rule actions, so the priority you're defining here determines the priority of this custom action against other custom actions. Read more on priorities in Priority.

You can create up to 6 custom actions.

View and manage custom actions

• Priority level is displayed for each custom action. Read more about custom action priority in Priority.
• The action name you define for a custom action is displayed in the dedicated column.
• The corresponding API string is displayed to the right. It’s crucial to communicate it to your developers to set up the integration accordingly.
• The Active rules column shows how many live rules use each of the custom actions.
• You can edit a custom action name or delete it. Important: this is only possible if there are no existing rules that use this action. Existing rules include active rules, drafts, and paused rules.
• You can reorder custom action priority if necessary. To do so, select REORDER PRIORITY in the upper-right corner and drag custom actions up and down using . Reordering the priority triggers a rule set deployment, so users should be careful with this action. Some rules that used to have a higher priority might not be hitting anymore as their priority has been shifted down. Changing priority is possible when a new custom action is created or an existing one is modified. In case of a conflict, we notify you accordingly with a warning.

Priority

Let’s first recap the existing priority in the Rule manager:

📌 Priorities exist at 3 levels:

1. The rule vs. list priority (not visible directly in the Dashboard, but this is why lists override rules).
2. The rule priority (low/ medium / high) as you define when creating a rule.
3. The action priority (suggested by the order of actions in the action drop-down: approve → decline → manual review → psd2 → custom.

By introducing custom actions in rules, we are introducing a concept of sub-priority – a 4th level of priority. Example:

1 approve
2 decline
3 manual_review
4 psd2
5 custom  → 5.1 custom_action_1
          → 5.2 custom_action_2
          …
          → 5.6 custom_action_6

With this in mind, here's what's important to know:

• Custom actions are only prioritized against each other, not against other available actions. In cases where more than one custom action rule hits, we check which one was given higher priority.
• If you have two high-priority rules – one with action approve and one with action custom – the approve rule wins over custom as per rule priority. If you want your rule with action custom to win over approve, you need to use the rule priority drop-down to specify that, i.e. create a custom rule with priority high and an approve rule with priority medium or low.
• In general, in cases where multiple rules within the same ruleset hit a transaction, Fraugster applies the following prioritization flow to determine which rule should take priority. The order of events is relevant here:

1. We check rule vs. list priority. Lists have priority over rules. Approve lists take priority over decline lists.
2. We look at the priority of each rule – high, medium, low.
3. We look at the action priority (high to low) – approve → decline → manual review → psd2 → custom.
4. We look at the custom priority – within the custom group only.
5. We look at the ID of the rule – the rule with the lower ID (i.e. the rule created earlier in time) takes priority over its younger counterpart.

Video demo

Our Product team prepared a video demo to help you get even more familiar with custom actions in rules. Check it out!