Old version of Cart Throb: "Spamming" when fraudsters use site to validate Credit Card info

[jsibre]

Hi,
This is not really a current issue, but I was advised by a member of the EE support team to submit this ticket so that I could get in the queue to discuss the issue directly with the dev/onboarding team responsible for bringing CT into the EE suite.

My client recently experienced an issue with an old version of Cart Throb Lite that required them to disable CT on their site, as it was causing too much noise. This prompted them to hire me to update their site to current standards. That has been done; I've updated their site to the latest EE, and they'd now like to re-enable CT, but first want to be assured that they will not be plagued by that issue again, i.e., that it has been resolved, or can be mitigated.

The problem was that people would try to use their site (with CT installed) to validate CC info. In the process, the cc processing company (Authorize.net) would successfully block the transaction, but CT would send multiple emails out to my client's staff for each attempted transaction - perhaps hundreds of transactions per day. It would also clutter their reporting with the mostly-meaningless attempted transactions.

As a developer, I realize that the software is "just doing its job", but I understand their request - it's surely very annoying to get a ton of emails that only tell you 'that hacker tried again', and then further frustrating to have reports clogged with tons of transactions that really add no value (except as a records that someone tried to use your system for something other than intended).

Is this old issue resolved? Or is it possible for the implementer (me) to alter the way the system is configured/developed to address it?

Thanks