Hi All,
I wanted to get any updated forum thread started to see if anyone had new methods on how to avoid this.
We are currently dealing with someone that is testing CC #'s using our quick donate page. It seems like its one person that is testing a few cards every few days so far. All the donations are in the 2-10 dollar range.
Our website uses Adage and we would like to see if anyone has ideas that might help.
There are some older posts that I saw that are all 2+ years old so I wanted to start a new one. The original threads mentioned using Cloudflare, and setting up reCAPTCHA. Are there any other ideas on what could be used?
If you have any questions please ask. I don't currently have access to all of the technical info four our website but I can see about getting info if that will help.
Hi Zachary - sorry to hear you're dealing with this! If you or someone else has access to SQL and SSMS, you may be able to match up the fraudulent customer_nos against the T_WEB_ORDER and t_web_session_Session tables, which could get you the session keys and IP address(es) where the orders are being created from. If there's a consistent pattern, you may be able to work with Adage to block a suspicious IP address, or add it to a blocklist for a virtual waiting room if your site has one always running in the background.
This isn't a fix-all since it's pretty trivial for a fraudster to use VPNs and switch to a new IP address, but it may at least slow them down a bit - it's nearly impossible to prevent these things entirely, so the aim is to make it just irritating enough for the fraudsters so they give up and move on.
Also, in case you haven't seen this conversation thread: https://community.tessituranetwork.com/tessitura_software_forums/f/tessitura_web-9/33505/fraudulent-online-accounts-being-created-through-tnew-with-no-orders/87055?_ga=2.87587484.567492598.1694201965-596832290.1693001669
This topic was a bit different since it was about fraudulent accounts being created without any apparent suspicious credit card activity, but still had a lot of conversation on how to mitigate this sort of thing, and a big post by Nic Boling (Tessitura VP of Security) to give more context. Could be some helpful reading.
I will look through this thread. Thank you for your suggestion as well. I will see if someone in our IT team can implement that SQL code to see if we can get the IP address and do some blocking.
Hopefully if we can slow them down enough it will make them look elsewhere. Again thanks for your input!