The Fraud Control menu contains all of the rules and information that the rest of the application uses. This is where Admins or Risk Editors can:
-
Review the default set of rules that are used to auto-decision transactions that might be fraud.
-
Create a new rule with conditions, then construct and activate a new rules snapshot based on your needs.
-
Compare the rules in two or more Rules Snapshots and decide which one fulfills your fraud detection requirements.
The Rules Engine is accessed through the Fraud Control tab in the Agent Web Console (AWC). It lets you create rules that reflect the internal policies of your business. All orders processed through us are evaluated against every rule within the active rule set.
When you create a rule for evaluation, it will have a single action associated with it: Approve, Decline, Escalate, or Review.
When one or more rules are created and saved, a rule set is built. A rule set can contain any number of rules, and each rule can be constructed with different thresholds, variables, and actions. Rules cannot be permanently saved individually. They must be saved to a rule set.
Your Customer Success Manager can provide you with guidance and best practices to assist you in rule creation. When the rule set has been generated and saved, it can then be activated and inbound orders will be evaluated against it. Based on the rules that trigger, we will respond with the respective action associated. In the event that more than one rule is triggered, we will respond with the action that has the highest priority associated to it.
The rule action priority is in the following order: Approve, Decline, Escalate, and Review. You will review the responses and then update their order management system (OMS) accordingly.
By default, orders that did not trigger any rules receive a response of Approved from us. The order is evaluated against the active rule set. If a rule is triggered, the Action is dependent on the definition of that rule. Rule Action choices are: Approve, Decline, Escalate, and Review. If there are conflicting actions between different rules that all trigger on the same order, there is an Action hierarchy that takes place. Approve is first, Decline is second, Escalate is third, and Review is fourth.
When a rule is given a priority of Important, the associated rule action overrides all other actions.
If you create rules that hold an order for a manual review by a fraud agent, the orders that trigger these rules display in Workflow in the Suspect Orders Queue. This queue is populated by the orders that have triggered at least one Escalate or Review rule. Orders that did not trigger any rules receive a response of Approved.
Comments
0 comments
Please sign in to leave a comment.