About the Transaction Risk Reasons API

The Transaction Risk Reasons API retrieves the current list of reasons a transaction may be considered risky by the Transaction Scoring API. The Transaction Scoring API returns a fraud_risk array containing enums that identify the detected risk factors. You can use the Transaction Risk Reasons API to programmatically retrieve detailed descriptions of these reasons as needed. Keeping these descriptions in a separate API prevents the Transaction Scoring API from returning unnecessary data that could increase response times.

Using the API

The Transaction Risk Reasons API can provide data in JSON or raw format.

JSON

https://www.ipqualityscore.com/api/json/transactionriskreasons/list

Raw

https://www.ipqualityscore.com/api/raw/transactioneriskreasons/list

Example Response

Below is an example of the JSON response. The raw response is similar but uses a new line delimited colon-separated list instead.

{
   "message":"Transaction Risk Reasons",
   "success":true,
   "reasons":{
      "TR_SUSPECT_IP":"IP address recently engaged in suspicious behavior.",
      "TR_ABUSIVE_IP":"IP address is frequently associated with abusive behavior.",
      "TR_EMAIL_SWAP":"User is switching their email address.",
      "TR_BILLING_SWAP":"User is switching their billing details.",
      "TR_BCOUNTRY_SWAP":"User is switching their billing country.",
      "TR_CC_SWAP":"User is switching their credit card.",
      "TR_IP_SWAP":"User is switching their IP address.",
      "TR_SUSPECT_USER":"Suspicious user details.",
      "TR_RISKY_BEHAVIOR":"High risk behavior detected.",
      "TR_SUSPECT_BEHAVIOR":"Suspicious behavior detected.",
      "TR_SUSPECT_EMAIL":"Suspicious email or associated detail mismatch.",
      "TR_RISKY_EMAIL":"User is associated with a high risk email address.",
      "TR_TYPO_EMAIL":"Email address is invalid, but is likely to be a typo.",
      "TR_EMAIL_M_I":"Email address is invalid, but an identity match was confirmed.",
      "TR_EMAIL_INVALID":"Email address is invalid.",
      "TR_EMAIL_BEHAVIOR":"High risk behavior associated with an invalid email address.",
      "TR_BILLING_SUSPECT":"Suspicious billing details detected.",
      "TR_BUSER_SUSPECT":"Suspicious behavior and user details.",
      "TR_DEVICE_SWAP":"Device swap or user mismatch detected.",
      "TR_INVALID_PHONE":"Phone number is invalid.",
      "TR_HIGH_RISK_PHONE":"Phone number is associated with very risky activity.",
      "TR_RISKY_USER_PHONE":"User is associated with a high risk phone number.",
      "TR_MATCH_RISKY_PHONE":"User is associated with a high risk phone number, although the number does match the user's identity.",
      "TR_PHONE_NAME":"Phone number is associated with a different name or individual.",
      "TR_SUSPECT_VOIP":"Suspicious virtual phone number.",
      "TR_PHONE_INACTIVE":"Billing phone number is likely inactive.",
      "TR_PHONE_FRAUD":"Suspicious or fraudulent phone number.",
      "TR_SPHONE_INACTIVE":"Shipping phone number is likely inactive.",
      "TR_BILL_INVALID":"Primary physical address is invalid.",
      "TR_SHIP_INVALID":"Secondary physical address is invalid.",
      "TR_DEVICE_RISK":"Recent high risk Device Fingerprint hit.",
      "TR_IP_RISK":"IP address recently engaged in high risk behavior.",
      "TR_BILL_EMAIL":"Abusive billing email address provider.",
      "TR_SHIP_EMAIL":"Abusive shipping email address provider.",
      "TR_BILL_EMAIL_REP":"Suspicious billing email address reputation.",
      "TR_SHIP_EMAIL_REP":"Suspicious shipping email address reputation.",
      "TR_USER_ADDR":"User is associated with a high risk physical address.",
      "TR_USER_BEHAVIOR":"User is exhibiting high risk behavior."
   }
}

j/d