Skip to main content

General settings

This section allows you to enter your Google API key, configure order handling behavior, and fine-tune customer geolocation settings.

The Fraud Detection settings are located at Stores -> Configuration -> Mirasvit extensions -> Fraud detection, and consist of the following section:

Geolocation preferences​

This section allows you to configure the primary IP source used in order data and set the preferred distance measurement unit. These settings are used for accurate customer geolocation and distance calculations.

  • Customer IP primary source (order data): specifies which source the system should use to retrieve the customer’s IP address when an order is placed:
    • remote_ip: the standard IP address retrieved directly from the server.
    • x_forwarded_for: the IP address forwarded by a proxy server or CDN (e.g., Cloudflare).
  • Distance unit: defines the unit of measurement used for distance-based calculations.
    • Kilometer
    • Mile
  • IP History Lookback (days): how far back the IP History indicator searches past orders by forwarded IP address (X-Forwarded-For). Bounds the lookup to a recent range instead of scanning the entire orders table, keeping fraud scoring fast on stores with large order histories. Default: 365.

Email Domain Check​

This section configures the Email domain web presence condition of custom rules, which checks whether the domain of the buyer's email address has a website.

  • Cache Lifetime (minutes): how long the answer for one domain is reused before its website is checked again, so repeat orders from the same domain don't trigger new requests. An Inconclusive answer is rechecked after 5 minutes at most, whatever this value is. Default: 60.
  • Request Timeout (seconds): how long to wait for the domain's website to respond. A website that does not answer in time makes the check Inconclusive, never No. Default: 3.
note

The condition needs your server to make outbound HTTP(S) requests to the buyer's email domain. If outbound requests are blocked by a firewall, every check ends as Inconclusive. The website is checked only when an order is evaluated by a rule that uses this condition.

Order behaviour configuration​

This section defines how the system should handle orders based on their status or origin. It helps automate decision-making for order processing and ensures consistent behavior in various scenarios.

  • Hold on review status:
    • Yes: order with the Review status will be paused and not processed further until manually approved.
    • No: order will not be paused.
  • Hold on reject status:
    • Yes: order with the Reject status will be paused and not processed further until manually approved.
    • No: order will not be paused.
  • Skip orders placed from the backend:
    • Yes: validation will not be applied to orders placed by administrators or managers through the backend.
    • No: all orders placed via the frontend or backend will be validated.
  • Skip fraud check for order statuses: orders with selected statuses will be automatically accepted without fraud evaluation.

Authorization settings​

This section allows you to connect your application to Google Maps services by providing the required API key.