Transaction page

The transaction page contains all the information on the transaction and the story behind the Fraugster decision. To open a transaction page, go to Transactions → select a transaction → select See full transaction details.

The Fraugster Engine receives a transaction in the form of several datapoints via the Fraugster API. It then enriches every transaction to generate additional attributes. As a result, each transaction receives a score that contributes to the approval process.

You have access to the evidence that contributed to a specific decision. Evidence includes story points and signals that are designed to work together and provide a clear explanation on why Fraugster takes a specific decision.

Evidence

Evidence comes together in the form of the following components:

• Fraugster score
• Story
• Signals

The Fraugster score is a numeric value between 1 and 100 that represents the evaluated likelihood of a transaction being scored to be fraudulent. The Fraugster score is calculated by the Fraugster Engine that employs quantifiable variables (attributes and datapoints) in Fraugster data models. The lower the score, the less likely a transaction is fraudulent.

If you're a Fraud Management SaaS user, you decide what your blocking threshold should be according to your business needs. For example, your business may have low fraud rates. In this case, you may want to set a high default score at which Rule manager blocks a transaction. This allows more payments to go through. Alternatively, you may want to customize the score in order to decrease fraud even further. In this case, you might want to pick a rather low default score in your rules. This allows Rule manager to block potentially fraudulent transactions more aggressively.

To understand the Fraugster score better, check which parameters of the analyzed data contributed to its calculation, and to what extent.

The radar chart represents the following groups of parameters:

Group	Description
Geo	Geographical data, including online geography, such as IP address.
Payment	Payment data, including transaction currency and amount, payment method, and BIN information.
Customer	Data about the user such as name, email address, and online behavior.
Transaction	Comparison to other transactions, not necessarily of the same merchant.
Merchant	Comparison to other transactions of the same merchant.

A story is a human-readable text that represents the choices made by the Fraugster Engine. It provides insight into why the Fraugster Engine took each decision and what evidence it used to score a transaction. Stories come from the AI Engine, i.e. they are written by the AI according to the decision it took for each transaction.

Signals

A signal describes a behavioral pattern that Fraugster data models identified for a transaction. Signals come from the enrichment layer, i.e. they derive from the datapoints and attributes that represent each transaction. Fraugster Engine puts together a set of signals after analyzing each transaction and identifying it as fraudulent or legitimate.

There are 3 signal categories:

• Indicates common and legitimate user behavior.
• Indicates user behavior that is usually associated with e-commerce fraud.
• Does not indicate legitimate or fraudulent behavior on its own, but may fall into one of these categories in the context of other signals.

When you hover over a signal, transaction details that the signal is related to become highlighted. This gives you a neat overview of the data that participated the analysis.

Other details

• Transaction details

  This section includes all the statuses the transaction has had in the course of time, including the latest status you communicated to Fraugster.

Fraugster ID is a machine-readable number Fraugster assigns to each transaction when it's received via the Fraugster API. You receive this ID in the API response under frg_trans_id.

Transaction ID is a machine-readable number you assign to each transaction. You send this ID in your initial API request under trans_id.

Use to copy an ID to clipboard.

• Transaction amount

  Displayed in euro as well as the original currency.

• Transaction timestamp

  The time in UTC when the transaction took place. For your convenience, we also provide you with this timestamp translated into your local time zone.

• Linked transactions

  In this section, you see if the transaction you're examining is linked to any past transaction by means of specific datapoints or attributes. This helps you identify connections between recent and past transactions. Use this insight to create or improve your existing rules and lists.

  We show up to 100 links in the section. The linking data isn't older than one year (the maximum range available in the Dashboard). If you'd like to see all results, select See all linked transactions.

  We scan for links by the following attributes and datapoints:

  • Email address (cust_email_norm)
  • Customer name (cust_name)
  • Payment (funding_source)
  • Phone (phone)
  • Shipping address (ship_ad_line1_zip_cnct)
  • Customer ID (cust_id)
  • Device ID (device_id_mapped)
  • IP address (ip)

  We also show the status for each linked transaction. This gives you an idea of how the linked data performed across transactions. If all linked transactions are fraudulent, the one you're examining is probably fraudulent, too.

  There are several filtering options available to you. The filtering uses AND logic. If you filter by device ID and email address, the sections is going to show transactions that feature both the device ID and email address.

  Example: if you have 10 device IDs and 15 email addresses, you're most probably not going to see 25 linking results. The sections displays the transactions that have the same device ID and email address, so it's not a sum of the two.

• Customer details

  If you don't submit some of the personal data in your API request, the fields are marked as not applicable.

• Payment details

  If you accept credit card payments, the details appear in this section, including BIN details. In case of a bank account transfer or open invoice, the section is updated accordingly. To provide you with the BIN brand, category, type, and country information, we use BIN table resources. The resources for data enrichment remain within Fraugster, we don't communicate any information to third parties.

• IP address

  If you send the IP address information to Fraugster via the API, we enrich it to provide you with the IP country and IP connection type. Please note: it's not always possible to determine the IP connection type.

IP connection type	Description
isp	Connection via an internet service provider, for example a standard DSL connection.
edu	Restricted to accredited postsecondary educational institutions. Calculated based on the IP class – the first part of the IP address.
gov	Restricted to governmental entities, departments, programs, and agencies on the governmental level. Calculated based on the IP class – the first part of the IP address.
mil	Restricted to the Department of Defense and its subsidiary or affiliated organizations. The name is derived from military. Calculated based on the IP class – the first part of the IP address.
corp	Connection via a corporate network. Calculated based on the IP class – the first part of the IP address.
travel	Connection from a hotel or an airport network.
mobile	Connection from an IP address that belongs to mobile phone infrastructure.
hosting	Connection via a service that runs internet servers, for example VPN.
reserved	A rare case when an IP address is invalid, i.e. it's internal in a network, but not a part of the internet itself.
unknown	Is returned if it's not possible to determine the IP connection type.

• Billing address

• Shipping address

• Custom data

  This section appears if you're sending datapoints of the type custom to the Fraugster API. Read more about this data type in the API documentation.

• Cart items

  This section appears if you're sending the datapoint items to the Fraugster API. Read more about this datapoint in the Complete list of datapoints.

Map

The section displays the billing and shipping address on a map based on their postal codes only. We don't use personally identifiable information (PII) for this purpose and don't send any personal data to Google Maps.

The information on the map gives you an idea of the distance between the two addresses. The more the distance, the more probability there is that this transaction is suspicious.

To zoom in and out of the map, use the and icons in the bottom-right corner of the map.