Huge Gaps in Order Numbers
Posted: Fri Aug 09, 2019 5:36 pm
Hey all -
In my experience, a failed payment causes a gap in order numbers which is usually 1 or 2 at most. We're seeing some gaps now of 50+ numbers, which I assume is a bot trying to gain access to the site or repeatedly hitting the checkout page. We implemented Cloudflare which seemed to help slow this, however it's still occurring a few times a day.
On the /ConLib/Checkout/PaymentWidget.ascx.cs file, we see code that appears to be in place to allow 3 failures before the purchase button is disabled. In testing this, it never increments the failed payment count and therefore never deactivates the payment button. We are on Gold R10 but moving to 9 here in the next few weeks.
Has anyone else experienced this issue? I'm almost certain it is malicious traffic causing this, however the IP's change and they use VPN's from Russia (users accounts end in .ru) to connect to US states to mask their IPs.
Thanks!
Greg
In my experience, a failed payment causes a gap in order numbers which is usually 1 or 2 at most. We're seeing some gaps now of 50+ numbers, which I assume is a bot trying to gain access to the site or repeatedly hitting the checkout page. We implemented Cloudflare which seemed to help slow this, however it's still occurring a few times a day.
On the /ConLib/Checkout/PaymentWidget.ascx.cs file, we see code that appears to be in place to allow 3 failures before the purchase button is disabled. In testing this, it never increments the failed payment count and therefore never deactivates the payment button. We are on Gold R10 but moving to 9 here in the next few weeks.
Has anyone else experienced this issue? I'm almost certain it is malicious traffic causing this, however the IP's change and they use VPN's from Russia (users accounts end in .ru) to connect to US states to mask their IPs.
Thanks!
Greg