=== Brickmoat for WooCommerce ===
Contributors: brickmoat
Tags: woocommerce, card testing, fraud prevention, checkout security, bot protection
Requires at least: 6.5
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Stops card-testing attacks at your WooCommerce checkout, locks down by itself during an attack, and clears the fake orders afterwards.

== Description ==

Card testing is when bots try hundreds of stolen card numbers on your checkout to find the ones that still work. It leaves you with failed orders, a flood of emails, card fees for every attempt, and sometimes a warning from Stripe or PayPal.

Brickmoat stops it where it happens: on every route that can charge a card, on your own server, before your payment provider is ever called.

**Everything below is free and works on its own. No account is needed.**

* **Protects every way to pay.** The block checkout, the classic checkout, the Store API, pay-for-order links and "add payment method". Bots skip your shop pages and post straight to these routes, which is why a CAPTCHA on the checkout page is not enough.
* **Tells real shoppers from scripts.** A real shopper browses before paying; a bot does not. Brickmoat checks for that quietly, with nothing for the shopper to do.
* **Counts failed cards.** Too many attempts or declines from the same visitor, network, email or device and they are stopped, long before a working card is found.
* **Locks down by itself during an attack.** When declines spike, Brickmoat tightens every check, asks guests a quick "I'm human" question, and relaxes again after an hour of calm. It never switches your checkout off.
* **Clears the fake orders in one click.** Failed and unpaid orders left by an attack go to Trash in the background. Paid orders, orders with staff notes and returning customers are never touched, and it can be undone.
* **One email, not hundreds.** Failed-order emails from an attack are held back and replaced by one summary.
* **A plain reason for every decision.** The event log says why each attempt was allowed, checked or blocked, in words a shop owner can read.
* **Works with HPOS and the Cart and Checkout blocks.**

= Brickmoat Pro (optional, paid) =

Pro is a hosted service, unlocked with a licence key. Nothing in the free plugin is locked or time-limited.

* **Protection from other stores.** A bot caught on any Brickmoat store is blocked on yours before it tries a single card.
* **A ready-made report for Stripe or PayPal** after an attack, as a web page and a PDF.
* **Slack, Discord and text-message alerts.**
* **90 days of history**, and an agency dashboard for people who look after several stores.

= Built to stay out of the way =

* Checks run on your server and take a few milliseconds.
* If anything inside Brickmoat fails, the order is allowed and the error is logged. Brickmoat is never the reason a checkout breaks.
* Card numbers never reach Brickmoat. Your payment provider handles them, as before.

== Installation ==

1. Install and activate WooCommerce if you have not already.
2. Install Brickmoat from Plugins → Add New, or upload the ZIP, and activate it.
3. That is all. Protection is on. Open **Brickmoat** in the admin menu to choose where attack alerts are sent and how careful Brickmoat should be.

== Frequently Asked Questions ==

= Do I need an account or an API key? =

No. The free plugin works completely on its own. A licence key is only needed for the optional Pro service.

= Will it block real customers? =

It is built not to. Returning customers and logged-in staff skip the checks. An unsure case is asked a quick "I'm human" question rather than blocked, and blocks expire on their own. If a real customer is ever stopped, open the event log, select the attempt and choose "Mark as real customer".

= Does it slow down my checkout? =

No. The decision is made on your server from data already at hand, in a few milliseconds. The event log is written after the page has been sent to the shopper.

= Which payment providers does it work with? =

All of them. Brickmoat guards WooCommerce's own checkout routes, so it does not depend on the gateway. It works with the block checkout and the classic checkout whichever gateway you use.

= What happens during lockdown? =

Guests answer a quick "I'm human" question, anything even slightly suspicious is stopped, payments that did not come through your shop pages are stopped, and failed-order emails are paused. Lockdown ends by itself after 60 quiet minutes. You can start or end it yourself at any time.

= Can I undo a cleanup? =

Yes. Orders are moved to Trash, never deleted. Use Undo on the Cleanup screen, or restore any order from Trash.

= What data does Brickmoat store? =

For each checkout attempt: the time, the decision and its reasons, the visitor's internet address, a one-way coded version of the email address and of the browser's details, and the order number. It is kept for 7 days (90 with Pro) and then deleted. Brickmoat adds suggested text for your privacy policy, and supports WordPress's "Export personal data" and "Erase personal data" tools.

= Does the plugin work without JavaScript in the shopper's browser? =

Yes. A shopper without JavaScript looks a little more suspicious but is not blocked for that alone outside an attack.

== External services ==

The free plugin makes no calls to outside services unless you turn on one of the following.

= Brickmoat service (only with a Pro licence key) =

If you enter a licence key, the plugin talks to the Brickmoat service at `https://woo.brickmoat.com` from your server. It is used to check the licence, to download the list of bots caught on other stores, to report bots caught on yours, and to send Pro alerts and reports.

* **On saving the key and every 5 minutes after:** your licence key, your store's address, the plugin, WooCommerce and WordPress versions, whether lockdown is on, and totals for the last 24 hours (attempts, allowed, checked, blocked, declined).
* **When a checkout attempt is blocked or a card is declined:** the visitor's internet address and network, a one-way coded version of the browser's details, the email address used (turned into a one-way code on arrival and then discarded), the payment method and route, and the basket total. Ordinary shoppers are never reported, and card details are never sent.
* **For a guest checkout that already looks suspicious:** the email address, to ask whether it has been seen attacking other stores.
* **When an attack starts and ends:** its start and end times and its totals, used for alerts and the payment-provider report.

The service is provided by Brickmoat: [terms of service](https://brickmoat.com/terms), [privacy policy](https://brickmoat.com/privacy).

= Cloudflare Turnstile (only if you add Turnstile keys) =

By default the "I'm human" check is Brickmoat's own and contacts no one. If you enter Cloudflare Turnstile keys in Settings, shoppers who are asked to prove they are human load Turnstile from `challenges.cloudflare.com`, and your server sends the result and the shopper's internet address to Cloudflare to verify it. Turnstile is provided by Cloudflare: [terms](https://www.cloudflare.com/website-terms/), [privacy policy](https://www.cloudflare.com/privacypolicy/).

== Screenshots ==

1. Overview: checkout attempts, bots blocked and why they were stopped.
2. An attack in progress, with lockdown on.
3. Junk-order cleanup after an attack.
4. The event log: a plain reason for every decision.
5. Settings: protection level, who is always allowed, and alerts.

== Changelog ==

= 1.0.0 =
* First release: protection on every checkout route, failed-card limits, automatic lockdown, junk-order cleanup, email alerts, the event log, and the optional Pro service.

== Upgrade Notice ==

= 1.0.0 =
First release.
