Integration Tests


Once your API calls are set up, you'll have to test your integration to ensure everything is working. There are two sides to the coin. First, confirming you're getting a response consistently. Second, understanding what the results mean to make sure they're what you need.

API tests

Your development or Q&A teams will likely test your API integration. A detailed Q&A check can help uncover any small errors before they become a problem.

HTTP status codes

It's always good to start with the basics. HTTP status codes can give you an "at a glance" overview of whether communication over the API is working as intended or not.

If everything is working correctly, your API response should include a status code beginning with 2XX. If you see status codes 4XX or 5XX, then something's gone wrong. The API response should also contain a SEON error code to help you get to the bottom of things.

Check your code

It's always good practice to double-check your code and the API response you receive. Has everything been formatted correctly? Is SEON receiving and using all data you have sent our way?

Does the API response contain any error codes? Are you receiving all expected data fields within your timeout settings? Does your client-side logic for handling timeouts work correctly? Is the API response being parsed and processed as expected?

While this is a manual process, it's the only way to fix integration errors and catch any minor hiccups before SEON is a part of your everyday processes.

Sample payloads

The best way to be sure everything is working is by sending sample data over the API. We'll also preload sample payloads to your account, which you can refer to when building your own.

These payloads will also let you stress-test your request limits, timeouts, and clients' side logic. You can also use them to test SEON's performance and verify our data.

If you'd prefer to remove any sample data from your account once you've finished testing, our Customer Success team is happy to help.

Understanding results

SEON takes a handful of data points and creates hundreds to help you fight fraud. Our data enrichment tools are API-based and take time to collect and analyze the wealth of open-source data that SEON uses. All data is collected in real-time, ensuring you're always up to date.

Data enrichment

You can quickly review the results of SEON's data enrichment tools on the Admin Panel if you're using the Fraud API (or at least two data points enriched through the Manual Page). Head to the Transactions page and click on any transaction to open the Transaction Details page.

Scroll down to find the transaction details widgets that house all the information collected by SEON's APIs. For data enrichment checks, your most important sources will be the IP information widget, the Email Information widget, and the Phone Information Widget.

The results of our social and digital profile checks will be color-coded so you can quickly check them at a glance.

Result colorDescription
GreenOur data enrichment APIs found an account with the email address or phone number on the social media site or digital platform.
GreyWe didn't find an account with the provided email address or phone number on the platform.
RedThe service did not respond. Make sure you've configured your timeout settings correctly.

How rules affect transactions

Transactions in SEON can be influenced by three rule types: default, custom, and machine learning rules. Rules can change a transaction's fraud score or state.

Rule types

When you first start using SEON, we’ll add a set of rules to your account based on our global experience in fighting online fraud. These rules are known as Default rules and will help you see the benefits of using SEON from day one.

You can create custom rules from the get-go. Our team is always happy to offer advice and support on what rules to create or how to set them up properly. Machine learning rules are created by our whitebox machine learning model.

Fraud scores

In SEON, the fraud score indicates the level of risk associated with a transaction. The higher the score, the more likely a transaction is fraudulent.

Rules can add to and subtract from the fraud score depending on whether they indicate an increase or drop in trust.

For example, a simple rule could subtract 5 points from the score if at least three social profiles were found with the provided email address. Another could add 20 points if the customer is using a VPN to connect.

Transaction states

In SEON, transactions can have three states: APPROVE, REVIEW, and DECLINE. A transaction's state is primarily defined by its fraud score. You can configure the thresholds of each state depending on your risk appetite.

Rules can change the state of a transaction as well. If these are triggered, the transaction is set to ACCEPT, REVIEW, or DECLINE, regardless of its fraud score.

With your API integration tested and a basic understanding of how SEON handles transactions, you're ready to dive into customizing your setup.