Does it work with any payment gateway?
The card-testing guard, the early warning and the evidence recorder work with every gateway, because they work from WooCommerce's own order statuses. Disputes sync automatically from Stripe only. For other gateways, a dispute is picked up from a gateway order note mentioning a dispute or chargeback, or you mark the order yourself with Order actions → Gatemi Shield: mark as disputed (chargeback).
A real customer was blocked
They had as many failed payments as Block an IP after this many failed payments within the window — often several declined cards in a row. The block ends by itself after Block for (minutes). If customers commonly share an IP (an office, a university, a mobile carrier), raise the limit.
To lift a block early, a developer can filter gatemi_shield_is_ip_blocked to return false for that IP.
Everybody is being blocked at once
Your site is probably behind a proxy, load balancer or CDN, and WooCommerce sees the proxy's IP for every visitor. Configure your server or CDN so WordPress receives the visitor's real address, then the counts are per visitor again. Until then, untick Block card-testing attacks.
Will it block me while I test?
No. Users who can manage WooCommerce are never blocked.
Does it slow down checkout?
No. A checkout attempt reads one cached value — whether this IP is blocked.
The dashboard always says Healthy
A rate is graded only once there is enough data: 20 paid orders in 30 days for disputes and refunds, 10 checkout attempts in 24 hours for failures. Below that, the rate is shown but graded Healthy. Check the counts beside each rate.
I got no warning email
You are emailed when the overall level gets worse than at the previous scan — from Healthy to Warning, or Warning to Danger — not every hour it stays there. Check Send alerts to, that your site can send email, and that WordPress cron is running (the scan is the hourly gatemi_shield_hourly_scan event; Last checked on the dashboard shows when it last ran).
The scan stopped running
The plugin re-creates its hourly event on every page load if it is missing. If Last checked is still old, WordPress cron itself is not running — common on sites with DISABLE_WP_CRON and no server cron. Set up a real cron job.
A Stripe dispute shows "not linked to an order"
The plugin could not find the order. It looks for the PaymentIntent in _stripe_intent_id (WooCommerce Stripe Gateway), then for the order's transaction id equal to the PaymentIntent or charge id. Orders from other Stripe integrations may store something else; a developer can map them with the gatemi_shield_stripe_dispute_order filter.
The Stripe box says "Not connected"
No key is available. Paste a restricted key into Stripe key (optional), or set up the WooCommerce Stripe Gateway plugin with a key. If the sync failed, the box shows Stripe's own error message — usually an invalid key or a restricted key missing Disputes: Write.
Does it submit anything to Stripe without me?
No. Send evidence to Stripe saves the evidence on the dispute as a draft (submit=false). You review and submit it in your Stripe Dashboard.
The evidence panel says "No evidence was recorded"
The order was created before Gatemi Shield was active, or while Record dispute evidence on every order was off. Evidence cannot be recorded after the fact.
The seal says CHANGED
The stored snapshot no longer matches its SHA-256 hash, so something edited the _gatemi_shield_evidence meta after it was recorded. Do not rely on that record in a dispute without explaining the change.
Is it HPOS compatible?
Yes. It is declared to WooCommerce and tested on HPOS order tables and on the older posts storage. All order lookups go through one helper that avoids queries the posts storage does not support.
Does it work with the Checkout block?
Yes. The block checkout goes through the Store API, which is one of the three paths the guard refuses on (with HTTP 429). Evidence is sealed for block orders too.
What happens to my data if I uninstall?
Settings, the risk snapshot, the activity log, the Stripe sync status, the store-wide failure count and the hourly event are removed. The per-IP counts and blocks are short-lived and expire on their own. Everything saved on orders is kept — evidence, seals, agent flags, dispute marks and Stripe dispute records — because you may still need it for open disputes.
