PREDAX FRAUD GUARD FOR WOOCOMMERCE
Predax Fraud Guard for WooCommerce translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Predax Fraud Guard for WooCommerce does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- WooCommerce checkout IP screening via Predax API: during WooCommerce checkout validation (after a protection mode is enabled), the plugin sends the customer’s checkout IP to Predax and receives a 0–100 risk score plus classification flags (e.g., VPN/proxy/Tor/datacenter).
- Configurable protection modes that determine enforcement: after setup, the plugin can operate in tag-only mode or block/hold orders based on chosen risk levels (e.g., tag-only by default once configured; blocking requires enabling a blocking mode).
- Order handling outcomes before payment: the plugin’s screening is described as occurring before the order is created and before any payment provider is contacted; depending on configuration it can tag, hold, or block the checkout attempt.
- Caching of screening results: classification results for a given IP are cached in site transients for a stated range of 5 minutes to 1 hour per IP to reduce repeated API calls.
- Optional rule set for additional fraud signals: the plugin includes opt-in capabilities such as order velocity rules, billing-country vs IP-country mismatch checks, disposable email detection (with a fallback to a built-in local list if the API is unreachable), and an optional timezone-mismatch signal via a cookie.
- Search-engine safe exemption: verified search engine crawlers (e.g., Googlebot/Bingbot confirmed by reverse DNS) are described as exempt from the plugin’s category rules so screening does not affect how the store is crawled/indexed.
- Admin-side logging and allow-listing workflow: the plugin provides an Events Log showing flagged/blocked/held attempts and supports one-click allow-listing of an IP directly from the Events Log.
Distinctive features
WooCommerce checkout IP screening via Predax API: during WooCommerce checkout validation (after a protection mode is enabled), the plugin sends the customer’s checkout IP to Predax and receives a 0–100 risk score plus classification flags (e.g., VPN/proxy/Tor/datacenter). Configurable protection modes that determine enforcement: after setup, the plugin can operate in tag-only mode or block/hold orders based on chosen risk levels (e.g., tag-only by default once configured; blocking requires enabling a blocking mode). Order handling outcomes before payment: the plugin’s screening is described as occurring before the order is created and before any payment provider is contacted; depending on configuration it can tag, hold, or block the checkout attempt. Caching of screening results: classification results for a given IP are cached in site transients for a stated range of 5 minutes to 1 hour per IP to reduce repeated API calls. Optional rule set for additional fraud signals: the plugin includes opt-in capabilities such as order velocity rules, billing-country vs IP-country mismatch checks, disposable email detection (with a fallback to a built-in local list if the API is unreachable), and an optional timezone-mismatch signal via a cookie. Search-engine safe exemption: verified search engine crawlers (e.g., Googlebot/Bingbot confirmed by reverse DNS) are described as exempt from the plugin’s category rules so screening does not affect how the store is crawled/indexed. Admin-side logging and allow-listing workflow: the plugin provides an Events Log showing flagged/blocked/held attempts and supports one-click allow-listing of an IP directly from the Events Log.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Predax Fraud Guard for WooCommerce does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Predax Fraud Guard for WooCommerce and REEID Translate FAQ.
Does the current evidence establish translation scope for Predax Fraud Guard for WooCommerce?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.