ACI Fraud Management vs Kount comparison

"The primary value of ACI Fraud Management lies in its capability for detection and prevention of card fraud around payments, with diverse rules that automatically decline suspicious transactions and real-time detection that adds another layer of security while its API integration capabilities facilitate use across multiple channels, including mobile transactions, enhancing its versatility."

"The primary value of ACI Fraud Management lies in its capability for detection and prevention of card fraud around payments."

"It's an in-depth, all-in-one solution."

"The initial setup was absolutely straightforward. Within a week I was fully working."

"We have 100% seen ROI; it helped us quickly identify our areas of fraud, stop us from losing money, start doing business smarter, save good customers, boost our sales, and minimize fraud at the same time."

"There were other people and other departments using other software, but Kount stood out in payroll because it was already proven and even the payments division was using it."

"We avoid losses in multiple ways with Kount."

"The most valuable feature is its ability to create your own ruleset and edit it whenever you want. Their reporting functionality is very helpful. It's really robust."

"There is room for improvement in the acceleration of its artificial intelligence capabilities."

"There is room for improvement in the acceleration of its artificial intelligence capabilities."

"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."

"The rule system and automation could be expanded a little bit more."

"They could do a little bit better with chargeback management."

"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."

"The rule system and automation could be expanded a little bit more."

"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."

"I think the pricing is great — I think it's totally worth what they're charging because the benefits are great."