I would say it depends from company to company and how they are integrated; however, the rule system and automation could be expanded a little bit more. Some of the variables that we can see when reviewing a transaction are not available when creating a rule. There could also be more variables that we could actually see when looking at the transaction model. It would be nice to be able to use all of them. The linked network accounts connected to the specific transactions — It would be nice to be able to use that information in rules.
In terms of what could be improved, that's a very good question. There was this layer you had to go to where I think we needed to add the frame. Then there is one turn for communication that happens with us and Kount and the response comes back again. So the time that is taken to go to Kount and come back should be in the order of around 100 milliseconds or less. And our context was taking around 200 to 300 milliseconds. We didn't want the extra load of 100 milliseconds to happen, so if the two rounds of stability could be cut to one, that would be very helpful. That was very relevant for the mobile app.
Director, Compliance Services at a tech vendor with 1,001-5,000 employees
Real User
2020-11-18T03:47:00Z
Nov 18, 2020
They could do a little bit better with chargeback management. There are other solutions out there that I've heard about, like Accertify that have a better chargeback platform where they're integrated more with the banks or in terms of how the workflow is and how you can respond to chargebacks. From my experience, Kount doesn't really have that. They had a way to assign reason codes and descriptions to the chargebacks so you can run reporting. You can flag transactions that get chargebacks on them so that you can then report your chargeback trends and create rulesets around them but there wasn't much for actual chargeback management. That was a whole separate process that we had to have in place. They should have more dashboards for data visualization. They have some capabilities there, but you really have to be a pro user. You have to be an expert user to really use it at the highest level. Otherwise, you're just exporting the data and creating it in Excel and using those visuals. It would be nice if they had some out-of-the-box dashboards where could you sign in, go to your specific dashboard and it just tell you everything in an intuitive way. That's a key area that they could work on a little bit more. The technology is there, it's a great solution, but as far as communicating the performance of the fraud department, they could make the dashboards more intuitive and insightful.
What is Fraud Detection and Prevention? It wasn’t that long ago that fraud detection and prevention involved reviewing a fair bit of historical data analysis. Data scientists would be poring over tons of credit card records in order to spot fraudulent (or with luck, potentially fraudulent) activity.
Fast forward to today and we see fraud detection systems depend on catching and stopping fraud the second it’s spotted or even before it actually occurs. Automated solutions for fraud...
I would say it depends from company to company and how they are integrated; however, the rule system and automation could be expanded a little bit more. Some of the variables that we can see when reviewing a transaction are not available when creating a rule. There could also be more variables that we could actually see when looking at the transaction model. It would be nice to be able to use all of them. The linked network accounts connected to the specific transactions — It would be nice to be able to use that information in rules.
In terms of what could be improved, that's a very good question. There was this layer you had to go to where I think we needed to add the frame. Then there is one turn for communication that happens with us and Kount and the response comes back again. So the time that is taken to go to Kount and come back should be in the order of around 100 milliseconds or less. And our context was taking around 200 to 300 milliseconds. We didn't want the extra load of 100 milliseconds to happen, so if the two rounds of stability could be cut to one, that would be very helpful. That was very relevant for the mobile app.
They could do a little bit better with chargeback management. There are other solutions out there that I've heard about, like Accertify that have a better chargeback platform where they're integrated more with the banks or in terms of how the workflow is and how you can respond to chargebacks. From my experience, Kount doesn't really have that. They had a way to assign reason codes and descriptions to the chargebacks so you can run reporting. You can flag transactions that get chargebacks on them so that you can then report your chargeback trends and create rulesets around them but there wasn't much for actual chargeback management. That was a whole separate process that we had to have in place. They should have more dashboards for data visualization. They have some capabilities there, but you really have to be a pro user. You have to be an expert user to really use it at the highest level. Otherwise, you're just exporting the data and creating it in Excel and using those visuals. It would be nice if they had some out-of-the-box dashboards where could you sign in, go to your specific dashboard and it just tell you everything in an intuitive way. That's a key area that they could work on a little bit more. The technology is there, it's a great solution, but as far as communicating the performance of the fraud department, they could make the dashboards more intuitive and insightful.