Updated on 25.08.22
The Settings page allows you to adjust and finetune how your SEON implementation works. Customize the interface and rule settings to meet your needs and fit into your workflows.
The page is divided into four tabs. Each section contains options connected to various elements of the SEON system.
- The General page houses timezone and locale settings, along with default expiration timeframes.
- The System tab provides a host of options to finetune how rules work.
- Authentication houses all settings connected to Single Sign-on (SSO) and two-factor authentication.
- Machine Learning is where you can customize how AI can help your work
|Time Zone Settings||Adjust dates and times to your local time.|
|Locale||Determines the format of numbers and dates.|
|Currency||Set the default currency for transactions.|
|Default IP Expiration||When blacklisting IP addresses, it's best to create an expiration time as IP addresses can change quickly.|
|Email API / Phone API general timeout||Set the timeout threshold for the Email and Phone API responses.|
|Priority timeout toggles||Priority platform timeouts allow you to extend your timeout for the platforms that are most important to your decision-making process.|
|Priority digital and social platforms||List the platforms and social media sites that you would like to ensure return a valid response either through desired accuracy or priority platform timeout settings.|
|Priority platform timeout settings||The total amount of time you can wait for a response from priority platforms. Learn more about how to use this setting from our guide.|
|Desired automatic accuracy settings||Define your accuracy requirement for priority platforms. Enter a number between 0 and 1. Learn more about this setting from our guide.|
|Flagging Settings||Flagging allows you to share anonymized information with the entire SEON network, learn more here.|
Email API / Phone API Timeouts
API timeouts define how long you can wait to get a response from SEON's data enrichment APIs. A higher timeout improves accuracy but leads to a longer response time. We recommend that you only use these functions at the earliest user access point, e.g., user registration.
The minimum timeout is 1500 ms but we recommend using a timeout of at least 1700ms.
|Threshold||Set what scores you’d like to associate with the APPROVE, REVIEW, and DECLINE states.|
|Email weight||By default, a Fraud Score is the sum of all score rules (IP, email, phone, and custom). You can change the weight of the email rules category to emphasize its importance over other categories.|
|IP weight||By default, a Fraud Score is the sum of all score rules (IP, email, phone, and custom). You can change the weight of the IP rules category to emphasize its importance over the other categories.|
|State Conflict||A state conflict occurs when a transaction triggers multiple rules that affect its state with different results. Choose which state should be the final setting in these cases.|
|Webhook Settings||Enter the URL for the HTTP post requests here if you want to provide other systems with real-time information regarding state changes or black/whitelisting actions.|
|IP restriction for API usage||Improve security by limiting the IP addresses from which API calls using your license keys are accepted.|
|Blacklist similarity||Finetune what happens in cases when SEON recognizes data points that are very similar to data blacklisted in your SEON account.|
Fraud scores are based on default, custom, and machine learning rules. You can review the different rules in the Scoring Engine. By default, a score over ten is considered risky. However, every business has a different risk appetite, so you can adjust the different state thresholds to your needs using the slider.
In SEON, Fraud scores are the sum of the Email, IP, Phone and custom rule scores. If you need to emphasize the importance of one category over another, you can adjust the weights applied to the Email and IP scores.
For example, if you set the IP weight slider to 75%, the fraud score applied by each IP rule will only be three-quarters of the default setting.
The default thresholds for each state are:
Use the slider to change your threshold settings:
Some rules in SEON can change the state of a given transaction without directly changing its fraud score. A transaction may trigger multiple state rules with different effects in some cases. Set the preferred outcome of these conflicts using the selector.
|Turn on SSO Login toggle||Click to turn SSO on and reveal SSO details fields.|
|SSO details||Technical fields that you will have to fill out to enable SSO in your SEON instance.|
|Default user role for SSO||Set the role of any new users who sign in with SSO for the first time. This should reflect basic access to your system.|
|Enforce two-factor authentication for all users toggle||Click the toggle to enforce 2FA for your entire organization. All users will be signed out and required to set up 2FA on their next login attempt.|
SSO login can improve the security of your SEON accounts by requiring your team to sign in through an identity provider of your choice, such as G-Suite or Azure AD. Learn more about setting up SSO, and contact our Customer Success Team if you run into any problems.
Two-factor authentication – or 2FA – improves the security of all SEON accounts by adding an additional security layer when signing in.
Members of your team will be required to provide a single-use passcode generated by an authenticator app on their phone when signing in. 2FA can be used to counter account takeover attempts by requiring a second device to access SEON.
Machine Learning Settings
|Negative Labels||Create new labels to highlight the reasons you declined a transaction and send SEON's machine learning system feedback.|
|Positive Labels||Create new labels to highlight the reasons you approved a transaction and send SEON's machine learning system feedback.|
|Complex Rule Settings||Allow SEON to automatically apply complex rules to your transactions if their accuracy is above a certain percentage.|
|Heuristic Rule Settings||Allow SEON to automatically apply heuristic rules to your transactions if their accuracy is above a certain percentage.|
|Blackbox Score||Finetune how SEON's Blackbox engine helps your work.|
Set up positive or negative labels to train SEON's Machine Learning system. Labels can be set automatically and sent to the system through the Label API or applied to transactions manually on the admin panel by clicking on its state (APPROVE / REVIEW / DECLINE). The system is tied to your account and only trained on your data.
Use labels to define the reasons why you accepted or declined a transaction. Negative labels can mark why a transaction was considered fraudulent (e.g., chargeback, bonus abuse, stolen card, etc.). On the other hand, positive labels highlight proof of a valid customer (e.g., passed KYC).
You can choose to only train our Machine Learning algorithm with the feedback you provide in the form of labels by clicking this switch.
During manual reviews, you can label transactions "Marked as decline" or "Marked as approved" or any other negative or positive label you have previously set up.
SEON's machine learning system automatically generates complex rules. You can choose to automatically apply these rules to your transactions if their accuracy is above a certain threshold here.
Use the toggle to allow REVIEW or DECLINE state rules to be applied. Adjust the accuracy threshold with the slider.
When a negative tag is applied to a transaction, SEON will link the data to other previously declined transactions in your account. Heuristic rules block all future transactions from the same data point.
You can choose to turn on heuristic rules above a set accuracy automatically. Use the text field to specify which data points our system should monitor. Finetune the minimum accuracy using the slider.
The blackbox model is only available for customers with at least 1000 transactions where a minimum of 100 transactions are in the declined state. Learn more about SEON's Blackbox model.
Click to toggles to finetune how you use Blackbox scoring:
|Calculate Blackbox score for every transaction||Blackbox scores will be displayed on the transaction details page but will not automatically affect the decision to Accept or Decline a transaction.|
|APPROVE transactions below a certain Blackbox score||The higher the Blackbox score, the riskier the transaction. Set the upper limit of Blackbox scores that the system should accept automatically.|
|Decline transactions above a certain Blackbox score||The higher the Blackbox score, the riskier the transaction. Set the Blackbox score limit above which transactions should be declined automatically.|