Rules Management
A flexible rules engine that lets you adapt immediately to emerging fraud trends and modify rules in real time. Cases are created automatically based on rules, which specify the logic and thresholds for flagging fraudulent transactions.
Jumio provides hundreds of pre-built rules, which you can customize for your specific business needs.
Problem Statement
Most successful fraudsters work in an organization very similar to corporations. They have individuals specialized in acquiring stolen data, others who manufacture the cards, and still others who make purchases with those cards.
This approach allows fraudsters to move fast and at scale, presenting a formidable challenge. That’s why one of the most important anti-fraud tools a business can use is a flexible rules engine that lets you adapt immediately to emerging fraud trends and modify rules in real time.
Personas
Solution Engineers are the primary personas who have permissions to view and edit the Rule Management UI. Other user personas are able to view rules that were triggered by a workflow step in the Case Management section.
Goals
A single Rulesets & Rules library
Importing the JTM & 4Stop rules into the global rulesets for customers to utilize instead of creating their own
Use the design system and exisiting components to decrease development workload
Create backlog of upcoming features to be worked on in the future
Research
Cross analyzed the current UI for Jumio’s KYX portal and the UI from the acquired 4Stop UI to evaluate common and unique features. Also researched how other companies implemented an interface to create rules using Drools in their applications.
Information Architect (IA)
Fleshed out the IA to show how this feature related to the rest of the Unified Portal and that made flows for each type of user to make sure that all requirements were clearly identified and documented.
Also was very important to reiterate who the target personas are at this point to make sure that their needs are captured properly.
End to End user journey map
High level overview of how all of the screens are connected. This was helpful for the developers as it guided them with connecting all of the interactions and navigation based on the user actions.
Rulesets Library
We decided to use the JTM UI as a base to build out the new Rules Management UI as it was already using the latest components and following the design styles.
This was also beneficial as the team was in a hurry to start developing a POC for an upcoming event.
The first interaction with this capability is the Rulesets page where a list of pre-enabled Jumio rulesets can be duplicated and used by a tenant instead of them having to start from scratch or uploading a csv file.
Basic Rule Editor
The main goal for this capability is to provide a business user friendly UI to create a rule as tenants want to cross train their users but not require them to manually edit code.
Rules Library
Within each Ruleset is a set of rules that is specifically used for a workflow step.
Individual rules can be activated or deactivated so that they are not checked by the system when a transaction is created.
Advanced Rule Editor
Solution Developers/Engineers are the primary personas and commonly prefer to manually script expressions.
This UI provides them with pre-baked operators and a validator feature for them to check their expressions before saving and publishing the rule.
Role Based Permissions
Worked together with the Product Manager and Product Owner for Rules Management and Admin Portal to ensure that user permissions were properly recorded and communicated between the two teams.
Ended up creating two different variations based on the state of the current RBAC UI and the future version that is in the backlog for future development.
Interactive Prototype
High level overview of how all of the screens are connected. This was helpful for the developers as it guided them with connecting all of the interactions and navigation based on the user actions.
User Testing
A prototype was created and used for user testing to get feedback from internal users prior to development. Internal Solution Engineers and other stakeholders participated and provided feedback prior to development.
