Antiro Order Risk Screening for WooCommerce

By abdellhadi

0+ active installationsVersion 1.3.0

Protects your WooCommerce store from fake and fraudulent orders using AI-powered fraud detection.

Description

Antiro analyzes every order in real-time using IP geolocation, device fingerprinting, VPN/proxy detection, and behavioral analysis to prevent fraudulent orders before they cost you money.

Features:

  • IP Analysis — Detects non-local IP addresses, VPN connections, Tor exit nodes, and datacenter IPs.
  • Device Fingerprinting — Identifies suspicious devices using browser canvas, WebGL, and hardware signals.
  • Bot Detection — Catches headless browsers, Selenium, Puppeteer, and other automation tools.
  • WooCommerce Integration — Works with both Classic Checkout and Block Checkout (WooCommerce 8+), and with order forms of other plugins that create WooCommerce orders (one-page COD forms on product pages).
  • Actions — Automated orders are refused before they are created. Suspicious orders are created but set aside under their own status, “Suspicious (Antiro)”, out of the orders list your confirmation team works from, with a note listing the reasons. The protection mode (protect, monitor or off) is set in the Antiro dashboard.
  • Never loses an order — If Antiro is slow or unavailable, the order is accepted and screened again in the background.
  • Ad protection — Orders blocked as automated are kept out of your Meta and TikTok conversion data.
  • Order Risk Column — See risk scores directly in the WooCommerce orders list.
  • Connection check — The settings page checks your API key with Antiro each time it opens.
  • Logs — Written to wp-content/uploads/antiro-order-risk-screening/logs for troubleshooting (order IDs and Antiro’s answers, no customer details).

External services

This plugin connects to Antiro, a fraud-screening service operated by Antiro (https://antiro.io). An Antiro account is required.

  • Order screening — when a customer places an order (Classic or Block Checkout, or an order form of another plugin that creates a WooCommerce order), the plugin sends to https://api.antiro.io: the customer’s IP address (and, when Cloudflare reported it, that it did), name, phone number, wilaya/state, city, address and email; the order total, the number of items and the first product (name, link, image, SKU and product ID); the WooCommerce order ID when the order already exists, or, for a Classic Checkout order, which is checked before it exists, a one-way hash that identifies the checkout attempt (a repeated submission gets the same answer; a delayed check of the order sends both); the site address, the plugin version, how the order reached the plugin (Classic Checkout, Block Checkout, created another way, or a delayed check) and, for the last two, the “created via” value WooCommerce stores on the order; and the Antiro session reference (cookie _atr_st or the form field antiro_token).
  • The customer’s browser headers — each order check also carries these headers of the customer’s own request to the site: User-Agent, Accept-Language, Sec-CH-UA, Sec-CH-UA-Mobile, Sec-CH-UA-Platform, Sec-Fetch-Site, Sec-Fetch-Mode, Sec-Fetch-Dest, X-Requested-With, Origin, and the host name of the Referer (never the full referring address). Each header is cut to 256 characters (512 for User-Agent). No other cookie or header of the customer is sent.
  • The checkout’s script setup — the check of an order placed through the checkout also tells Antiro that the checkout page runs the Antiro script in collect-only mode (sdk_expect “collect”), so that Antiro can recognise an order sent without the script, and whether strict mode is on (sdk_required). It is left out when the plugin does not load the script on the checkout (no publishable key, or the antiro_load_sdk filter), and it is never sent for orders created another way, whose pages may not run the script.
  • Delayed screening — if Antiro does not answer in time, the plugin keeps the IP address (and whether Cloudflare reported it), the session reference, those headers and, for a checkout order, the script setup (for a Classic Checkout order also the attempt hash) in the order’s data, and sends the check again up to five times within about seven hours. It deletes them as soon as the order is screened, the retries end or protection is turned off; if the plugin is deactivated before that, they stay in the order’s data. The IP address sent with a check also stays recorded on the order, as WooCommerce records the customer’s IP address.
  • Outcomes — when the store completes, refunds or cancels a screened order, the plugin reports the outcome (delivered, returned or cancelled) of Antiro’s check to the same API. Cancellations made by Antiro itself are not reported.
  • Browser script — on the checkout page (not its order-received and order-pay pages) and on product pages, the plugin loads https://js.antiro.io/v2/antiro.js asynchronously (it never blocks the page). The script reads device and browser characteristics (screen, language, time zone, platform, processor, memory and touch support, graphics, canvas and audio rendering, automation indicators, including whether a browser automation tool is attached and whether a background worker of the page reports the same characteristics), how long its own first request to Antiro took (connection, encryption handshake and response times), and counts and timings of interactions with the page (clicks, touches and key presses, never which keys), and sends them to https://api.antiro.io with the page address without its query string (for a visit from an ad, only which network the ad belongs to and a one-way hash of its click identifier), the host name of the referring site, and the phone number typed in the order form (to link the visit to the order). Antiro also receives the IP address and the request headers the browser sends with them. When Antiro asks for it, the script can run a WebRTC check that shows Antiro the device’s network addresses; this check contacts a public STUN server (by default Google’s, stun.l.google.com), which sees the device’s IP address. When Antiro sees a VPN or proxy, the script can show the customer a short message asking to turn it off. It stores a visitor identifier in the first-party cookie _atr_v (180 days, renewed at each visit) and in a localStorage copy without expiry that restores the cookie, the session reference in the first-party cookie _atr_st (2 hours), and, for a visit identified as automated, the flag _atr_px in sessionStorage. Site owners can load it on other pages with an order form through the antiro_load_sdk filter.
  • Ad pixels — for an order Antiro refused or cancelled as automated (not one it judged too late to cancel, which is left to you), the plugin tells Facebook for WooCommerce and Pixel Manager for WooCommerce not to send the purchase, and on that order’s confirmation page prints a small inline script, ahead of the pixel code, that withholds Meta and TikTok pixel events (consent revoke) and Snap pixel events (the Snap library is then not loaded), pushes antiro_verdict “bot” to the Google Tag Manager data layer and sets the same _atr_px flag. This sends nothing anywhere.
  • Connection — when the administrator clicks “Connect”, the browser is sent to https://dashboard.antiro.io with the site’s domain and the address of the plugin’s settings page. Once the administrator approves the connection there, the plugin asks https://api.antiro.io to complete it: Antiro calls this site’s /wp-json/antiro/v1/verify endpoint to confirm the site belongs to the administrator, and answers with the store’s API key and publishable key. While the site is not connected, the settings page asks https://api.antiro.io whether the site’s domain is already registered; once it is connected, the settings page checks the API key with Antiro each time it is opened. The plugin also asks Antiro for the store’s current publishable key twice a day (with WP-Cron) and when an administrator opens wp-admin (at most every 12 hours), and keeps the key named in the answer to an order check, so that a key renewed, deleted or switched off in the Antiro dashboard reaches your pages.

  • Relay through your store — some networks cannot reach Antiro’s addresses while they reach your store. For their customers, the browser script sends the same data through your own site instead (REST route /wp-json/antiro/v1/sdk/m), only when Antiro itself does not answer: the plugin forwards each message unchanged to https://api.antiro.io/v1/sdk/r with your secret API key, the customer’s IP address (as the plugin reads it for the order check) and the request headers the browser sent (User-Agent, Accept, Accept-Language, the Sec-CH-UA and Sec-Fetch headers, Origin, X-Requested-With; never cookies). When https://js.antiro.io has not loaded the script within 3.5 seconds, the page loads the same script from your site (REST route /wp-json/antiro/v1/sdk.js), which the plugin fetches from https://js.antiro.io and keeps for 5 minutes. The plugin stores none of this: no option, no log line.

Terms of service: https://antiro.io/terms
Privacy policy: https://antiro.io/privacy

Installation

  1. Upload the plugin folder to /wp-content/plugins/.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.
  3. Go to WooCommerce → Antiro to configure your API key.
  4. Get your API key from the Antiro dashboard.

FAQ

How do I get an API key?

Sign up at antiro.io and create a store. You will receive an API key starting with bf_.

Does this work with WooCommerce Block Checkout?

Yes, the plugin supports both Classic Checkout and Block Checkout (WooCommerce 8+).

What happens when an order is blocked?

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.

What is strict mode?

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.

What happens when an order is suspicious?

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.

Can I turn off the ad pixel protection?

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.

A suspicious order was a real customer. What do I do?

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.

How do I tell Antiro an order was fake?

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.

What happens to suspicious orders if I deactivate the plugin?

They are moved to On hold, so that WooCommerce keeps showing them.

What happens when Antiro is unavailable?

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.

I use a one-page COD order form plugin. Is it protected?

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' ); } );.

Another service creates orders for my customers (a chatbot, a form service, a webhook).

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 );.

My site is behind a proxy or CDN.

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.

Screenshots

Changelog

1.3.0

  • Changed: a suspicious order is no longer put On hold “to call first”. It gets its own status, “Suspicious (Antiro)”, out of the default orders list, with no stock reserved and no email sent; the customer still sees the usual thank-you page. A paid order is put On hold as before. Orders already On hold from earlier versions are not touched.
  • New: a suspicious order is kept out of your ad data, like a blocked one, until you restore it.
  • New: setting “Ad pixel protection” (WooCommerce → Antiro), on by default, to leave your ad pixels untouched.
  • New: moving a suspicious order to Processing, On hold or Completed tells Antiro the customer was genuine.
  • New: order action “Antiro: fake order (cancel and report)” on every screened order.
  • Deactivating or deleting the plugin moves the remaining suspicious orders to On hold.

1.2.0

  • New: strict mode, on by default (WooCommerce → Antiro → Strict mode). A checkout order that never ran Antiro’s browser check, as scripts that post orders directly send them, is refused instead of held for review; the customer sees “Please refresh the page and try again.” (Arabic and French included). An order checked again after Antiro did not answer in time is never refused by it.
  • New: customers whose network cannot reach Antiro (measured on part of Algérie Télécom) are verified through your own site: the browser script falls back to the plugin’s relay and loads from your site when js.antiro.io does not load (see External services). Before, their orders arrived without the browser check and were held for review.

1.1.0

  • Security: the connect flow verifies domain ownership and the API key is delivered server-to-server (never in a URL).
  • Security: the connect callback requires an administrator and a one-time state token (CSRF protection).
  • Security: the customer IP is read from CF-Connecting-IP only when the request comes from Cloudflare (directly or through a listed proxy), and from X-Forwarded-For / X-Real-IP only when it comes from a proxy listed in the new “Trusted proxies” setting.
  • Security: removed the legacy collector script and its antiro_fp / antiro_signals cookies; device data written by the browser is no longer sent from the server.
  • Fix: monitor mode is respected — orders are blocked only when Antiro returns an explicit block decision.
  • Fix: screening runs after WooCommerce validates the checkout fields, and retries are de-duplicated.
  • Fix: a new order from the same session, cart and phone is screened again instead of reusing the previous order’s decision, and so is a new try after a refused order.
  • Fix: Block Checkout no longer screens draft updates, or an existing order being paid, as new orders (a refused one could be deleted).
  • Fix: very long name, phone, city or address values no longer make the order skip screening.
  • Fix: delivery and cancellation outcomes are reported for every screened order; cancellations made by Antiro itself are not.
  • Fix: Block Checkout shows the block message instead of a generic error.
  • Fix: the block message is shown in the site’s language (Arabic and French translations included), and saving the settings no longer empties it.
  • New: optional manual API key connection.
  • New: the Antiro browser script (device intelligence and bot detection) on the checkout page and on product pages, where COD order forms live; never on the order-received and order-pay pages. Its session reference is sent with the order check, and its publishable key follows the Antiro dashboard (renewed, deleted or switched off).
  • New: the check of a checkout order tells Antiro that the checkout runs the Antiro script (collect only), so that an order sent without the script is recognised. Orders created by other plugins do not carry this statement.
  • New: doubtful orders (review, VPN notice) are put On hold with a note listing the reasons, in Classic and Block Checkout.
  • New: orders created outside the checkout (COD order-form plugins, wc_create_order) are screened: blocked ones are cancelled, doubtful ones put On hold. The antiro_screen_created_order filter exempts orders another service creates for your customers.
  • New: orders Antiro could not screen (timeout, rate limit, server error) are screened again in the background with Action Scheduler; an admin notice shows how many are waiting (counted at most every five minutes, not on every screen).
  • New: the browser request headers Antiro needs to verify the browser are sent with the order check (see External services).
  • New: Facebook for WooCommerce and Pixel Manager for WooCommerce do not send the purchase of an order refused or cancelled as automated, and its confirmation page withholds Meta, TikTok and Snap pixel events.
  • Tested with WordPress 7.1 and WooCommerce 11.2.

1.0.2

  • Simplified connected state: removed diagnostics table and logs viewer.

1.0.1

  • Auto-connect flow: connect to Antiro dashboard in one click.
  • Auto-detection: plugin detects stores already connected on Antiro.
  • Simplified settings: protection managed from Antiro dashboard.
  • Removed manual API URL and action configuration.

1.0.0

  • Initial release.
  • IP analysis with VPN/proxy/Tor detection.
  • Device fingerprinting and bot detection.
  • Classic and Block Checkout support.
  • Configurable block/flag/log actions.
  • Risk score column in orders list.
  • Built-in diagnostics and logging.