Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| v:2.0:fighting-fraud [2019/04/22 19:21] – [Pre-Payment Webhook] foxybrett | v:2.0:fighting-fraud [2019/05/20 07:31] – [Google's reCAPTCHA on the Foxy Checkout] foxybrett |
|---|
| - **Disabled**: turns off reCAPTCHA for your store | - **Disabled**: turns off reCAPTCHA for your store |
| - **Enabled, Always**: As it sounds, this will include reCAPTCHA on every checkout. | - **Enabled, Always**: As it sounds, this will include reCAPTCHA on every checkout. |
| - **Enabled, Automatically as Needed**: This will require reCAPTCHA for checkouts loaded by IP addresses that have triggered multiple errors in a preceding window of time. We attempt to set this so it would //very// rarely be shown to a legitimate customer, but would effectively make bot-based bulk fraud impossible. We don't publicize the exact thresholds, and may change them as needed. | - **Enabled, Automatically as Needed**: This will require reCAPTCHA only in specific situations when our systems have cause to believe your store needs extra protection. We do not reveal specific behavior here, but broadly: If we detect behavior that makes us think a bot (or botnet) is pushing transactions through without a real human behind it, we will enable reCAPTCHA either for specific IPs or for //all checkout attempts//. We attempt to set this so it would //very// rarely be shown to a legitimate customer, but would effectively make bot-based bulk fraud impossible. |
| |
| Note that reCAPTCHA isn't required for API-based or [[.:unified_order_entry|UOE]]-based transactions. | Note that reCAPTCHA isn't required for API-based or [[.:unified_order_entry|UOE]]-based transactions. |
