If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
The IP is in the variable s.remote_addr. However, just blocking an IP here or there probably won't limit the attempts too much as these clowns typical cycle their IP. The real solution, provided they are humans, is to install a fraud protection feature such as Wolfpaw Fraud Detection or Sift (see app store). (Note, licensing for the Wolfpaw module is not working as of Friday.)
If they're successfully placing orders, the Urchin Log module is an easy thing to turn on to get the address of an order. You'll end up with an elf.log in the /private/mivadata/ directory and each order will result in an entry being added to it, including IP address and time. You can then block the IP. However, like Bruce said, if a particular card thief has decided your store serves their purposes of testing stolen cards because they figured out you use a real time gateway, blocking the IP will likely just delay them until they get a new hacked relay server.
We have a recaptcha module that is designed to display a captcha image on the checkout page after the first decline, so it impedes card thieves, but doesn't bother legit customers on their first attempt to pay. http://apps.miva.com/checkout-recaptcha.html
The problem with a captcha module is that many of these attempts are from actual humans (at least we'd consider them human, the folks who hire them...). The get paid pennys for each actual card they find...which, for them, is a worthwhile endeavor.
Comment