Support Thread for Google reCAPTCHA plugin

[lat9]

That's not a possibility, since the 'checkout_process' page is transitional ... i.e. no customer input accepted.

The order's payment is confirmed on checkout_confirmation and sent to the payment-provider, resulting in a redirect to checkout_process which results in a redirect to checkout_success on successful completion or somewhere else if an issue (like CC denial) occurs.

[zamzom]

I am sorry, I have meant adding a captcha to the checkout_confirmation page. The last page before going to the payment provider.

That's not a possibility, since the 'checkout_process' page is transitional ... i.e. no customer input accepted.

The order's payment is confirmed on checkout_confirmation and sent to the payment-provider, resulting in a redirect to checkout_process which results in a redirect to checkout_success on successful completion or somewhere else if an issue (like CC denial) occurs.

[torvista]

If a bot's got past the create account captcha already, I'd assume it'll get past any others.
Doesn't seem much point using another one, just more annoyance for real customers.

[zamzom]

They seem to pass the create account part manually.
They have tried 14000 CC's in one night and due to this activity the bank has suspended the payment system.
In order to open the system back they require extra security mesures, one of which is captcha control, either on the first fail or in all attempts.
(in checkout_process there is a CC SLAM PREVENTION, it beats me how they get passed that)

If a bot's got past the create account captcha already, I'd assume it'll get past any others.
Doesn't seem much point using another one, just more annoyance for real customers.

[carlwhat]

for every problem there is a solution.

which credit card module are you using?

in my auth.net module, look at these lines of code:

https://github.com/proseLA/authorize...im.php#L43-L46
https://github.com/proseLA/authorize...hp#L1003-L1024

this slows them down and then logs them off...

it is possible that you have a method for testing credit cards that is NOT part of the checkout process, which is why the slam protection might not work.

best

[NWCE]

I currently have this plugin installed in a v.1.5.8 and have used keys from Google for their v2 of ReCaptcha. I would like to move to v3 of ReCaptcha and I see that this plugin mentions it can be used for both v2 and v3.

To do this, do I simply get Google keys for v3 and place them in to make this change? Are there other changes that need to be made??

Thanks for your help!

[zamzom]

[ZC 1.5.8]
My google reCaptcha works but
Somewhere along the path of upgrading I have ended up with both

includes/clases/observers/auto.non_captcha_observer.php

and

includes/auto_loaders/config.google_recaptcha.php
includes/clases/observers/class.google_recaptcha.php

Aren't these contradictory load types?
I mean either one or the other.
Should the other one be removed?

[lat9]

They are contradictory load types. I'm guessing that the auto-loaded observer is more recent; if so, the auto_loader and its observer-class should be removed. If my guess isn't correct, remove (or simply rename) the auto-loaded one.

[zamzom]

Sorry my fault!
non_captcha_observer is totally something else, i.e. not a a part of google_recaptcha.
It comes with a standard ZC distribution.

[ZC 1.5.8]
My google reCaptcha works but
Somewhere along the path of upgrading I have ended up with both

includes/clases/observers/auto.non_captcha_observer.php

and

includes/auto_loaders/config.google_recaptcha.php
includes/clases/observers/class.google_recaptcha.php

Aren't these contradictory load types?
I mean either one or the other.
Should the other one be removed?