Fraud protection

Sometimes, repeating transactions can occur when a customer refreshes the web page that contains click or sale tracking code.
Post Affiliate Pro offers you a tool that will recognize these fraud transactions - Fraud Protection.
You can find it in the merchant panel in Configuration > Fraud Protection.

Fraud Protection settings are divided into the following four tabs:

 
 
Explanation & Examples:
 
  • Do not track clicks when landing page is in iframe (if the landing page is in iframe, clicks will be declined / not saved).
  • Recognize multiple repeating clicks that come from the same IP address within 999999999 seconds (999999999 seconds is basically infinite, as it equals more than 30 years).
  • Click from same IP, but on different banners, don't recognize as repeating click (if the visitor clicks on multiple banners from the same IP, the repeating clicks will not be saved for that user).
  • Ban clicks from IP addresses (clicks from specified IP addresses will be declined / not saved. You can use multiple IP addresses, comma separated). 
  • Allow only clicks from IP addresses (clicks only from specified IP addresses will be registered).
  • Ban clicks from urls (HTTP_REFERER) (clicks from specified URLs will be declined / not saved. You can use multiple URLs, comma separated).
     
  • Allow only clicks from urls (HTTP_REFERER) (clicks only from specified URLs addresses will be registered).
    • and clicks from banner destination domains (this option will automatically allow clicks to be registered for all your banner destination URLs, so you don't need to specify them manually).
    • Allow empty referrer (HTTP_REFERER) (see when the referrer URL can be empty here).
       
  • Blacklist countries (select countries which should be blacklisted for clicks).
Every option can be set to either 'decline' (save the click, but with the declined status) or 'do not save' it at all).
 
 
Explanation:
 
  • Added messages will be also visible for affiliates (when the option Add message to this transaction (optional) is used, the note will also be visible to affiliates).
     
  • Recognize multiple orders from the same IP address within 999999999 seconds (999999999 seconds is basically infinite, as it equals more than 30 years).
    • Check orders only with same User Agent (Recognizes multiple orders from the same IP and the same browser).
    • Check orders only from same campaign (Recognizes multiple orders from the same IP and for the same campaign).
    • Check orders only with same order ID (Recognizes multiple orders from the same IP and for the same order ID).
    • Check orders only with same product ID (Recognizes multiple orders from the same IP and with the same product ID).
    • Add message to this transaction (add an optional message, for example reason of the declined order).
       
  • Recognize duplicate orders coming with the same order ID within 999999 hours from initial sale (999999 hours is basically infinite, as it equals more than 114 years).
    • Apply also to empty Order IDs (The rule will be applied even if the Order ID field is empty).
    • Check orders only from same campaign (Recognizes duplicate orders with the same order ID and for the same campaign).
    • Check orders only with same product ID (Recognizes duplicate orders with the same order ID and with the same product ID).
       
  • Ban sales from IP addresses (sales from specified IP addresses will be declined / not saved. You can use multiple IP addresses, comma separated).
     
  • Allow only sales from IP addresses (only sales from specified IP addresses will be registered).
  • Ban sales from urls (HTTP_REFERER) (sales from specified URLs will be declined / not saved. You can use multiple URLs, comma separated).
     
  • Allow only sales from urls (HTTP_REFERER) (only sales from specified URLs addresses will be registered).
    • and sales from banner destination domains (this option will automatically allow sales to be registered for all your banner destination URLs, so you don't need to specify them manually).
    • Allow empty referrer (HTTP_REFERER) (see when the referrer URL can be empty here).
       
  • Blacklist countries (select countries which should be blacklisted for sales).
Every option can be set to either 'decline' (save the sale, but with the declined status) or 'do not save' it at all).
 
Explanation:
 
  • Recognize multiple signups that come from the same IP address within 999999999 seconds. (999999999 seconds is basically infinite, as it equals more than 30 years).
  • Don't allow signups from following IP addresses (signups from specified IP addresses will be declined / not saved. You can use multiple IP addresses, comma separated).
  • Blacklist countries (select countries which should be blacklisted for signups).

Every option can be set to either 'decline' (save the signup, but with the declined status) or 'do not save' it at all).

 
 
Explanation:
 
  • Allowed number of unsuccessful login attempts in one hour per username (specify number).
  • Allowed number of unsuccessful login attempts in one hour per IP (specify number).
  • Block login from IP addresses (Merchant - login attempts from specified IP addresses will be blocked. You can use multiple IP addresses, comma separated).
  • Allow only login from IP addresses (Merchant - only login attempts from specified IP addresses will be allowed).
  • Block login from IP addresses (Affiliate - login attempts from specified IP addresses will be blocked. You can use multiple IP addresses, comma separated).
  • Allow only login from IP addresses (Affiliate - only login attempts from specified IP addresses will be allowed).
  • Blacklisted countries (Merchant - select countries which should be blacklisted for signups).
  • Blacklisted countries (Affiliate - select countries which should be blacklisted for signups).
×