Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 2 of 2

Thread: Fraud Settings Question

  1. #1
    netprocity is offline Member
    Join Date
    Dec 2008
    Posts
    80

    Default Fraud Settings Question

    Hello,

    We have a customer who keeps placing fraudulent orders in our system trying to utilize stolen credit cards. This user is very sophisticated in that he always creates a new account in our system, always has a different email, and always has a different assigned IP address. How can I stop this person from utilizing our system? He is going in and trying tons of credit cards until one works. We obviously recognize his shipping address and don't send the orders, but it is very disruptive to our system and invoice numbers, etc.

    Please, any ideas?

    Thanks
    James

  2. #2
    esedirect is offline Senior Member
    Join Date
    Feb 2010
    Location
    Norfolk, UK
    Posts
    343

    Default

    It doesn't sound like you can stop them from using your store, if they are using new customer accounts and different IP addresses. If the only common data that they are using is the shipping address maybe you could write a trigger which removes the data (orders, orders_shoppingcart, address, customer, and so on) at the point of inserting the shipping address.
    http://www.esedirect.co.uk
    --------------------------------------------------------------------------
    Using MS 9.2.0.0 with the following customisations:

    Lightbox/Fancybox enlarged images;
    Auto-suggest searchbox;
    Extra product information shown only to our IP Address (such as supplier info, costs, etc.);
    Failed transactions emailed via trigger;
    Custom app to show basket contents when customer online;
    Orders pushed through to accounting systems.

    All the above without source!