| 开发者 | abdellhadi |
|---|---|
| 更新时间 | 2026年11月14日 19:18 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/.Sign up at antiro.io and create a store. You will receive an API key starting with bf_.
Yes, the plugin supports both Classic Checkout and Block Checkout (WooCommerce 8+).
The order is not created, and the customer sees the message "This order cannot be processed. Please contact support." in the site's language: Arabic and French (France) are included with the plugin, other languages come from translate.wordpress.org once the plugin is translated there. An order refused by strict mode (see below) shows "Please refresh the page and try again." instead. The messages have no setting.
Scripts that send orders straight to your checkout, without opening the page, carry no Antiro browser check. With strict mode on (the default), Antiro refuses such a checkout order instead of holding it for your confirmation team, and the customer sees "Please refresh the page and try again.": a genuine customer whose page could not run the check usually can after a reload. Orders from order-form plugins on product pages and orders created in wp-admin are never refused by strict mode, and neither is an order Antiro could not screen in time (it is checked again later without it). Turn it off under WooCommerce → Antiro → Strict mode if genuine customers report that message.
In cash on delivery your team phones every order anyway, so "call this one first" protects nothing against a wave of fake orders. A suspicious order is therefore created (the customer sees the usual thank-you page) with the status "Suspicious (Antiro)" and a note listing the reasons. It does not show in the default "All" orders list: it has its own list, "Suspicious (Antiro)", next to it. WooCommerce reserves no stock and sends no email for it, and it is not reported to your ad pixels as a purchase (Meta, TikTok and Snap on the thank-you page; server events of Facebook for WooCommerce and Pixel Manager). A suspicious order that is already paid is put On hold instead, so it stays in sight.
Yes, under WooCommerce → Antiro → Ad pixel protection. It is on by default: for visitors Antiro judges automated, and for orders it sets aside as suspicious, Antiro withdraws consent on the Meta and TikTok pixels and blocks Snapchat pixel events on your pages, and skips the server events of Facebook for WooCommerce and Pixel Manager for those orders. These pixels may come from you or from other plugins; turned off, Antiro leaves them untouched.
Open the "Suspicious (Antiro)" list and change the order's status to Processing (one order, or several with the bulk action "Change status to processing"). The order goes on as usual, stock is reserved, and Antiro is told the customer was genuine.
In the order's "Order actions" box choose "Antiro: fake order (cancel and report)". The order is cancelled and Antiro learns from it. Works on any order Antiro screened, suspicious or not.
They are moved to On hold, so that WooCommerce keeps showing them.
The order is accepted, marked with "?" in the Risk column, and screened again automatically up to five times (waiting 1, 5 and 15 minutes, 1 hour, then 6 hours between attempts). If the late answer is "suspicious" or a block and nobody has worked on the order yet (less than 15 minutes old), the order is set aside as suspicious or cancelled; otherwise Antiro only adds a note. A notice in the WooCommerce screens shows how many orders are waiting.
Yes, when the form creates a regular WooCommerce order. The order is screened right after it is created: blocked orders are cancelled, suspicious ones moved to "Suspicious (Antiro)". The Antiro script loads on product pages for these forms. If your form is on another page (a landing page built with a page builder), load the script there with the antiro_load_sdk filter, for example add_filter( 'antiro_load_sdk', function ( $load ) { return $load || is_page( 'offer' ); } );.
An order created outside the checkout is screened as if the visitor of the request that created it had placed it, so Antiro judges that service's server instead of your customer, and can set the order aside as suspicious or cancel it. Create such orders through the WooCommerce REST API with the API keys of a shop manager or an administrator: orders created by your staff are not screened. Otherwise exempt them with the antiro_screen_created_order filter, for example add_filter( 'antiro_screen_created_order', function ( $screen, $order ) { return $screen && 'my-chatbot' !== $order->get_created_via(); }, 10, 2 );.
Cloudflare is recognized automatically. For any other reverse proxy, load balancer or CDN (Sucuri, QUIC.cloud, Bunny...), an administrator adds its addresses under WooCommerce → Antiro → Trusted proxies. Antiro then reads the customer's IP address from the X-Forwarded-For / X-Real-IP headers these addresses send, and ignores those headers from anyone else; when such a proxy received the request from Cloudflare, the address Cloudflare reports is used. The settings page shows a hint when your own visit to it comes through a proxy that is not listed.