This site requires javascript to be enabled.

Fraud risk triggers

Results for

Results for search.results.searching

Set up your Fraud Risk Triggers

Our fraud tools offer you the flexibility to customize your setup to align with the risk appetite of your business by using a combination of the following decision-making instruments available to create a strong fraud prevention strategy.

Rules 
  • Create rules using any data point you send: shipping address, IP address, and payment details
  • Set up simple to complex rules, depending on your needs
Lists 
  • Customize your lists to block a specific email, IP address, or country to stop fraudulent payments
  • Make safe lists of customers you trust to improve the customer experience
Fraud score
  • Estimate possible risks by accessing the transaction reliability information
  • Adjust your threshold to switch between blocking and authorizing transactions flagged as suspicious
Advanced Adaptive Machine Learning
  • Use algorithms and models, that continuously learn and adapt to changing fraud patterns
  • Enhance fraud detection accuracy with real-time scoring and decision-making models

Within your chosen tool, set up your fraud detection using the above strategies to evaluate the risk, proposing a specific outcome when a rule is triggered. These outcomes could be:

Accepted The payment is not fraudulent since rules are not triggered. It will be routed to Authorization. The fraudserviceResult field will be set to the value = Accepted
Denied The payment is most likely fraudulent based on the triggered rule. It will be stopped and will not proceed to Authorization. The fraudserviceResult field will be set to the value = Denied
Challenged The payment is more likely to be fraudulent, and a case will be created in a pending review queue. This will allow you to examine the transactional details associated with the payment and decide whether to proceed or deny it. The fraudserviceResult field will be set to the value = Challenged
No Advice The fraud risk evaluation could not be executed as the fraud provider did not provide a response. The value = fraudserviceResult field will be set to the value = No advice
Error There was a issue relating to the data sent in the request, the fraud risk evaluation could not be executed. The value = fraudserviceResult field will be set to the value = Error