Skip to content
CHADA Store

Troubleshooting common issues

If something\’s not working as expected, start here. Most issues fall into one of these buckets.

\”Orders scored\” stays at 0

The engine isn\’t running. Check, in order:

  • Is WooCommerce active? WFG silently deactivates itself if WC is missing.
  • Is the order total above the Order amount bypass? Tiny test orders may be skipping the pipeline.
  • Check the WP error log for WooFraudGuard entries — exceptions inside the engine are logged but don\’t bubble to the customer.

Legitimate customer just got refused

Open Flagged Orders, find the order, click View detail. The rule contributions tell you exactly which rules fired. Common false-positive sources:

  • Address mismatch at country level on gift orders — lower the rule weight to 0.3.
  • IP risk on customers behind corporate VPNs — consider lowering or disabling.
  • Behavioural on customers using password managers — the email-pasted signal alone shouldn\’t flag, but combined with autofill it can. Tune accordingly.

\”License server unreachable\”

Your store can\’t reach the CHADA license server. The cached validation lets you keep running for up to 7 days. Common causes:

  • Firewall blocking outbound HTTPS to chada-license.example.com.
  • Server clock drift — license tokens are time-bounded; off-by-an-hour is enough.
  • Temporary CHADA outage — check the status page.

Webhook returns 401

For Stripe: the signing secret in your settings doesn\’t match the secret in Stripe\’s dashboard. Re-copy from Stripe and paste into Settings → Privacy & API keys → Stripe webhook signing secret.

For PayPal: the webhook ID or REST credentials are wrong. PayPal\’s verification endpoint will return VERIFIED only when all three (webhook ID + client ID + secret) match the same app.