Sr. Fraud Analyst at a tech services company with 51-200 employees
Real User
Dec 13, 2020
The user interface at first felt like it wasn't the easiest to interact with. However, this was partly due to the amount of information provided. For example, to view results of an ID card check, I needed to go through a set of windows, and it wasn't particularly intuitive. I felt that the UI itself could have been simpler and more intuitive with a little tweaking.
Senior Product Manager at a tech services company with 11-50 employees
Consultant
Nov 25, 2020
Some of the language around rules and integration can certainly be improved. Account creation rules and account creation flows were very helpful to me and very easy to understand, however, the management of transactions on the platform is not very good. The integration between the management of transactions and the management of account creation is quite low. I would love it if they could combine the two and make it a little bit more robust. Mostly the challenge that I faced is some of the limiting rules or some of the fraud-related checks or preventive measures that we were taking, if we could take that on the account creation side, the transaction side, it would not carry over. We would have to redo the same thing there. The number of rooms on the transaction side was fewer. What I want is deeper and better integration between a transaction and an actual account that's been created today. Let's say that I opened the details for the transaction to figure out something about it. The transaction is coming from a different geography. I want to know what's going on with it. If I could do that, I would ideally like to know who is doing the transaction without separately having to go and find this account through email search or whatever. Linkage between the two is pretty low and rules as well are not very integrated between the two. In terms of AML and transaction management use cases, they do aggregate transactions. For example, let's say over a period of one month I do five transactions. Their backend system knows how many transactions I've done, yet they don't expose that to me on the user's side. I cannot see that and report it. I have to do a calculation. If I'm the user, as in I'm the company that's using it, I have to run calculations on my side to figure out how much transaction has gone through.
Fraud Detection and Prevention solutions help businesses identify and mitigate fraudulent activities. They provide robust mechanisms to detect anomalies and prevent financial losses, safeguarding assets and reputation.Advanced technologies in Fraud Detection and Prevention leverage AI and machine learning to analyze vast datasets, spotting patterns indicative of fraud. These solutions utilize real-time analysis, evolving with new fraud tactics, reducing false positives, and enhancing...
The user interface at first felt like it wasn't the easiest to interact with. However, this was partly due to the amount of information provided. For example, to view results of an ID card check, I needed to go through a set of windows, and it wasn't particularly intuitive. I felt that the UI itself could have been simpler and more intuitive with a little tweaking.
Some of the language around rules and integration can certainly be improved. Account creation rules and account creation flows were very helpful to me and very easy to understand, however, the management of transactions on the platform is not very good. The integration between the management of transactions and the management of account creation is quite low. I would love it if they could combine the two and make it a little bit more robust. Mostly the challenge that I faced is some of the limiting rules or some of the fraud-related checks or preventive measures that we were taking, if we could take that on the account creation side, the transaction side, it would not carry over. We would have to redo the same thing there. The number of rooms on the transaction side was fewer. What I want is deeper and better integration between a transaction and an actual account that's been created today. Let's say that I opened the details for the transaction to figure out something about it. The transaction is coming from a different geography. I want to know what's going on with it. If I could do that, I would ideally like to know who is doing the transaction without separately having to go and find this account through email search or whatever. Linkage between the two is pretty low and rules as well are not very integrated between the two. In terms of AML and transaction management use cases, they do aggregate transactions. For example, let's say over a period of one month I do five transactions. Their backend system knows how many transactions I've done, yet they don't expose that to me on the user's side. I cannot see that and report it. I have to do a calculation. If I'm the user, as in I'm the company that's using it, I have to run calculations on my side to figure out how much transaction has gone through.