Checkout Shield for WooCommerce

Your CAPTCHA protects the form. This protects the API. Most store owners don't realize the attacks aren't even hitting their checkout page.

Checkout Shield Troubleshooting Blocked Orders and False Positives

If legitimate customers are blocked, reduce the protection mode temporarily and troubleshoot the checkout path before disabling protection entirely.

Common causes

  • Missing checkout session or token: usually caused by cache, optimization, or custom checkout code.
  • Strict mode is too aggressive: switch to Balanced or Learning while reviewing logs.
  • Proxy IP detection is wrong: enable or adjust Proxy/CDN Support.
  • Checkout cookies are stripped: review CDN and cache rules.
  • Custom checkout integration: use API keys for trusted server-side checkout requests.

Debug workflow

  1. Switch to Learning mode.
  2. Place a test order using the same checkout path as the affected customer.
  3. Review the latest activity entry or log reason.
  4. Check whether the shopper IP, cookies, and session are present.
  5. Fix the underlying cache, proxy, or custom checkout issue.
  6. Return to Balanced mode and retest.

When to contact support

Contact Carticy support with the protection mode, checkout type, active payment gateway, CDN/proxy details, and the relevant log entry. Do not send full customer payment details or secrets.