The chargeback feedback loop

When a chargeback webhook arrives, WooFraudGuard does three things in sequence. Together they form a closed feedback loop that makes detection sharper with every confirmed fraud.

1. Tag the order

The disputed WooCommerce order gets a _wfg_chargebacks meta entry and an order note: \”WooFraudGuard recorded chargeback via Stripe — reason \’fraudulent\’, amount 199.00. Linked atoms auto-blocklisted per playbook.\”

2. Auto-blocklist the linked atoms

Per the Chargeback auto-blocklist setting, the configured atom types (default: email + device) are added to the blocklist permanently. Anyone returning to your store with the same email or fingerprint hits a 100-point score on the Blocklist rule and gets auto-cancelled.

3. Feed the order graph

The Prior chargeback rule (premium) reads from the chargeback table on every future order. If a future order shares any atom with the disputed order — email, device, IP, phone, card BIN+last4 — it scores 60–80 points on this rule alone. Cluster chargebacks add another 20 per hit.

This is why the rule has a default weight of 1.0: chargebacks are the strongest, most expensive fraud signal you have. Using them to inform future scoring is essentially free accuracy.

Chargeback threshold

The Chargeback threshold before blocklisting setting controls how many chargebacks must hit the same atom before auto-blocking. Default 1 (block on the first chargeback). Some merchants prefer 2+ to require repeat offenders before permanently blocking an atom — especially for IP-based blocks where one chargeback could be a one-off legitimate dispute.