Evaluate user interactions based on predefined conditions and outcomes using transaction rules. Transaction rules apply to more than just payments – you can also use them for other activities of your users like ATM withdrawals.
The date on which the rule will start to be evaluated, in ISO 8601 extended offset date-time format. Unless you specify a value, the date is set to the time of the rule trigger, as recorded in the Transactions page.
Guide to Transaction Scoring API: Reduce Risk & Fraud
Guide to transaction scoring API will take when the rule triggers. You can select either a hard block or an outcome that assigns a score to a transaction. When you select an outcome, all services and risk signals triggered by the rule (including other transaction rules) are added up and a risk score is assigned to your transactions. This is a weighted average, with more significant services and risk signals having greater impact.
All triggered rules contribute to the final fraud score, so the higher your score is, the more suspicious it will look. You can check the breakdown of your transaction scores in the Applied Rules widget.
You can add tags to your transactions for more granular categorization. These tags are then displayed in the Transactions page for you and your team to see for enhanced collaboration and transparency. For example, if you are assessing applicants as part of your onboarding process, it might be helpful to add an applicant tag ‘Application review’, so you can easily see all the applications that have been tagged with this label.
