We use Featurespace ARIC Fraud Hub for our client's process. First, our clients send us information on credit applications, and we monitor and score the applications. Then, we give them a score for each application so they can make approval decisions for their clients.
What is our primary use case?
How has it helped my organization?
This solution allows us to ingest any data into the platform. It is very flexible and allows us to calculate the risk of any transaction, whether it's synchronic or asynchronous.
What is most valuable?
The most valuable feature is its zero degradation model. You don't have to train the model every three to six months, and it automatically functions. In addition, compared to other platforms like MonitorPlus, or FICO Falcon Fraud Manager, the interface is quick to navigate. The interface also allows you to deploy some rules without experience with the raw language.
What needs improvement?
The rule-writing language could be improved to make it more understandable. I was familiar with the Falcon expert language to write rules, so I had to get used to the new language used in this solution.
In the next release, as an additional feature, it will be good to have the capability to sort and play visual effects in the fields. This will help to distinguish each record from the other. For example, we currently have a bar that shows if a person has a high or low score. If the score is 35%, the bar is considered low, and if the score moves to 99%, the bar increases. However, we don't have the capability as interface users to make this function appear in other fields where we want it displayed. We have only the score field, which is pre-configured with this functionality.
For how long have I used the solution?
We have used this solution for about a year. We are currently using version 3.18.28.
We deployed this solution through a hybrid cloud. It is not a cloud from Featurespace but an Amazon Web Service.
What do I think about the stability of the solution?
Featurespace ARIC Fraud Hub is very stable. We have about five people from our product, technical support, and operations departments using it. In addition, the operations department has an interface user and monitors our applications to keep them stable.
The solution works great, and we plan to hand off some users to our customers so they can also try the solution.
What do I think about the scalability of the solution?
The solution is scalable. If you have a disconnection that prevents you from using the platform, there is a log-in in the back where you can check and immediately resolve the issue.
How are customer service and support?
The technical support is great. I've used the FICO support platform, which is similar to this solution. You set up a ticket, and they immediately contact you to see how they can help you. We receive convenient and good support from them.
How would you rate customer service and support?
Positive
How was the initial setup?
It took around a year to implement, but I don't have additional details on the integration process.
The company has to align to the payload structure or schema required to integrate into the platform.
What about the implementation team?
We completed the deployment in-house. Since we gather all the information from our clients, we only need a couple of people for training and deployment. When we have new customers, we provide them with new user details so they can access the interface.
What's my experience with pricing, setup cost, and licensing?
The pricing is reasonable. It is not cheap, but it is fair.
What other advice do I have?
I rate this product a nine out of ten because there are only minor details I would change. However, we may have more opinions on the solution as we deploy it to more customers.
A good piece of advice is to pay attention to the schema. You will need a definition of the schema, so you must be aware of the planning and gather all the information you need to process on the platform and monitor real events. For example, suppose you have a specific pattern you want to prevent, such as identity theft, and have one field that lets you know it is not identity theft. In that case, you must include it in the schema to have all the information you need to process on the platform. You must correlate every value or information in your core system to the schema Featurespace has.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)

