iulights
Forum Replies Created
-
Hello,
I wasn’t responding because I assumed I was waiting for you to come up with a correction to the most up to date version.
Our company needs the security feature of banning cards if there are multiple failed attempts on one order. We just need this function to work properly.
This problem was never resolved and no solution other than download a previous version was given.
Please let me know what I should do to make sure this topic continues to be on your priority list.
Best Regards,
Hello Rexak,
What security features are available on version 3.3.2?
How do I download the older version?
Hello Rexak,
Isn’t Google ReCaptcha a part of the WooCommerce CardPointe Payment Processing Plugin?
I have that box checked in my CardPointe payment plugin settings to use Google ReCaptcha at checkout. Is this not a good Captcha to use?
Is there another Captcha plugin you recommend?
What is the difference between the updated version and the 3.3.2 version? I definitely need the feature that bans cards for multiple failed attempts because our website was hacked by a brute force credit card attack earlier in the year.
Thank you for your help.
Forum: Plugins
In reply to: [CardPointe Payment Gateway for WooCommerce] Tokenization too strict!Ok Thanks! I started a new topic with this issue.
Forum: Plugins
In reply to: [CardPointe Payment Gateway for WooCommerce] Tokenization too strict!Hello,
I am having a similar issue.
I set the “Maximum Credit Card Attempts” to 5. This is supposed to limit the number of credit card attempts PER ORDER that a customer can try to 5 for one credit card.
What it actually does it limit the number of uses our customers can have with one credit card to 5 attempts across all orders.
Basically if any of our customers try to place 5 orders in one day, the first 4 orders will process through without a problem then the 5th order will ban their card. Then I have to go delete it from the BANNED cards list.
I need this feature fixed so that the credit card attempts are only limited to a PER ORDER basis. This is how the feature explains that it is supposed to work.
Please advise on when I can expect this fix to take place.
Best Regards,