User, Payment, & Transaction Fraud Detection

IPQS IP Reputation API, Email Verification API, Phone Number Validation API, and Device Fingerprint Technology support additional parameters to score payments or users, detect e-commerce fraud, and provide real-time online payment fraud detection. This transaction screening service is ideal for preventing chargeback fraud and performing advanced user scoring through our transaction risk API, which can identify even the most sophisticated fraudulent transactions on websites and apps.

IPQS can analyze additional user data for orders, payments, transactions, lead generation, and personal user information to enhance the accuracy of the transaction risk API fraud score. The fields listed below are entirely optional and provide additional data that can be used to detect fraudulent payments and suspicious behavior likely to generate chargeback fraud disputes. Any further data beyond the IP address greatly improves the detection of high-risk activity.

The transaction_details object displays transaction risk analysis. If only one address is available for the user or transaction screening process, enter the address data into the billing or shipping variables, rather than entering the same address in both variables. Passing the email address also contributes to detecting fraudulent users. However, the API will only perform a light abusive check. A full lookup with Email Verification API will provide greater detail and accuracy for email reputation. The transaction variables listed below are optional; you can ignore any irrelevant variables.

Example Request

In this example, the API will check the email address and phone number for recent abuse and validate the phone number. Only email addresses checked with our dedicated Email Verification API will be fully validated.

https://www.ipqualityscore.com/api/json/ip/YOUR_API_KEY_HERE/192.0.2.110?strictness=1&billing_email=example@example.com&billing_phone=5555555555&billing_country=US

Request Parameters

Success Response Example

This is an example success response in JSON format. Responses are also available in XML format.

{
	"message":"Success.",
	"success":true,
	"proxy":false,
	"ISP":"Cox Communications",
	"organization":"Cox Communications",
	"ASN":22773,
	"host":"ip70.lv.lv.cox.net",
	"country_code":"US",
	"city":"Nevada",
	"region":"Las Vegas",
	"is_crawler":false,
	"connection_type":"Residential",
	"latitude":36.14,
	"longitude":-115.20,
	"timezone":"America Los_Angeles",
	"vpn":false,
	"tor":false,
	"active_vpn":false,
	"active_tor":false,
	"recent_abuse":true,
	"abuse_velocity":"medium",
	"bot_status":false,
	"mobile":false,
	"fraud_score":24,
	"operating_system":"Mac 10.8",
	"browser":"Chrome 81.0",
	"device_model":"iPad",
	"device_brand":"Apple",
	"transaction_details":{
		"valid_billing_address":false,
		"valid_shipping_address":false,
		"valid_billing_email":false,
		"valid_shipping_email":false,
		"risky_billing_phone":false,
		"risky_shipping_phone":false,
		"billing_phone_carrier":"AT&T Mobility",
		"shipping_phone_carrier	":"Rogers Canada",
		"billing_phone_line_type":"Wireless",
		"shipping_phone_line_type":"Landline",
		"billing_phone_country":"US",
		"billing_phone_country_code":"1",
		"shipping_phone_country":"US",
		"shipping_phone_country_code":"1",
		"fraudulent_behavior":false,
		"bin_country":"US",
		"bin_type":"Credit",
		"bin_bank_name":"CITIBANK N.A.",
		"risk_score":17,
		"risk_factors":["Billing phone number is inactive.", "Billing email is associated with recent chargebacks."],
		"is_prepaid_card":false,
		"risky_username":false,
		"valid_billing_phone":true,
		"valid_shipping_phone":false,
		"leaked_billing_email":true,
		"leaked_shipping_email":false,
		"leaked_user_data":true,
		"user_activity":"high",
		"phone_name_identity_match":"Match",
		"phone_email_identity_match":"Mismatch",
		"phone_address_identity_match":"No Match",
		"email_name_identity_match":"Unknown",
		"name_address_identity_match":"Match",
		"address_email_identity_match":"Match"
	},
	"fraud_risk":{
      "message": "This transaction has a high risk of fraud based on the included risk factors. Treat with caution.",
      "reasons": [
        {
          "enum": "TR_SUSPECT_IP",
          "severity": "high"
        },
        {
          "enum": "TR_SUSPECT_BEHAVIOR",
          "severity": "high"
        }
      ]
	},
	"request_id":"0w8WYS"
}

Response Parameters

The Proxy Detection API returns the following variables, which provide risk analysis for users and transactions. You can also treat "billing" or "shipping" variables as a user's primary or secondary information group, even when billing is not involved, such as for lead generation or user scoring purposes.

The risk_score is a vital component in the risk analysis process. It serves as a quick and effective way to identify suspicious user behavior, with scores of 75 or higher indicating such behavior. Scores of 90 or higher point to high-risk payment details or user data.

All response variables are returned within the transaction_details object. These variables are populated when at least 1 transaction data parameter is present in the initial API request. The following transaction variables are "null" when the necessary transaction parameters are not passed with the initial API request. For example, not passing the billing_email will return valid_billing_email as null.

billing_address_distance fields

shipping_address_distance fields