Signals

A signal describes a behavioral pattern that Fraugster identified for a transaction.

Find the signals that an API response may include in Complete list of signals.

Response example

{
  "evidence": {
    "signals": [
      {
        "category": "seller",
        "id": "ff9578ab",
        "related_to": ["slr_crncy", "slr_ctry"],
        "type": "technical"
      },
      {
        "category": "user",
        "id": "85dd94qc",
        "related_to": ["cust_email", "cust_first_name", "cust_last_name"],
        "type": "bad"
      }
    ]
  },
  "fraugster_approved": 0,
  "frg_trans_id": "abc01f6ccc8a5832a7871fdb14be1211",
  "is_liable": false,
  "liability_reason": "declined",
  "score": 0.92
}

Each object contains:

Component	Description
`category`	A group this signal belongs to based on its components. One of payment_method: related to the payment method used for the transaction, i.e. a bank account number or a card number. geo: related to the geo location of the transaction and the elements that constitute it. seller: related to the seller and various aspects of seller's business activity, including but not limited to location and industry. transaction: related to the type of transaction, the amount, and the time of the day when the purchase was made. user: related to the user's personal details and online behavior.
`id`	A unique signal identifier. An 8-character alphanumeric string in lowercase.
`related_to`	The datapoints of relevance for this signal provided in the API request. An array of strings with datapoint names.
`type`	Determines the type of signal in terms of risk. One of: good: the signal shows a pattern usually found in legit transactions. bad: the signal shows a pattern usually found in fraudulent transactions. neutral: the transaction element is not good or bad on its own, but it may be considered good or bad in the context of other information. technical: the transaction element is missing critical data that may make the decision less reliable.

Response example​

Response example