Loading...

Knowledge Base

Overview of Payment Gateway Risk Assessment Reports

When you want to monitor potentially fraudulent payment transactions in the Reseller Control Panel. This article explains risk assessment reports, supported payment gateways, risk alert categories, report configuration, and recommended fraud prevention actions.

 

When you want to monitor and detect potentially fraudulent payment transactions in the Reseller Control Panel. This article explains how risk assessment reports work, how to enable or disable them, and how to interpret risk alerts.

We have implemented several pioneering fraud detection and prevention mechanisms for some of our Payment Gateway integration modules. This report will help you automatically detect potentially risky transactions that your Customers/Sub-Resellers have performed. This report is sent to your Billing Team on a daily basis, to allow you to identify any fraudulent transactions from any of the following Payment Gateways:

  • Authorize.Net Credit Card Gateway
  • PayPal (formerly Verisign) Payflow Pro Credit Card Gateway
  • PayPal Direct Payment API Gateway

 

Enabling / Disabling Risk Assessment Report Generation

  1. Login to your Reseller Control Panel. 

  2. In the Menu, point to Settings -> Finance & Billing and click General Settings.

You may enable/disable these reports by selecting/deselecting the Turn on the generation of Risk Assessment Reports checkbox in the Global Payment gateway settings section.

By default, We enable generation of Risk Assessment Reports for you and these Reports get daily sent to your Billing Contact Email Address.

 

We strongly recommend that you enable this report and manually verify the transactions shown therein, by contacting the corresponding Customer or Sub-Reseller. If you find any of these transactions to be suspicious, you should immediately reverse the credit for them, before your Customers/Sub-Resellers use it. If they have already used the credit you may delete their orders or suspend them or follow any process you may deem necessary.

We would also recommend you to reverse any suspicious transactions at the Payment Gateway to avoid charge-backs. Our Risk Engine assigns a Risk Score to transactions based on a vast accumulated database of information and the history of previous transactions. The Risk Report is divided into sections and special attention should be paid to the High Risk section, if it exists.

Example of a Payment Gateway Risk Report

HIGH RISK ALERT LIST - Different Credit Cards used from the Same Machine with Different Card Holder Names

UsernameRoleTransaction IdAmountCard Holder NameIP AddressStatusPayment Gateway NameDate {GMT/UTC}
somebody@domain.comResellerAddFund-R-87-76INR567.00a192.168.0.82AuthSuccessfulauthorize.net2005-10-25 22:57:49.197707
test@test.comResellerAddFund-R-269-75INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-10-25 22:56:30.059662
test@test.comCustomerAddFund-C-74-74INR123.00a192.168.0.82AuthSuccessfulauthorize.net2005-11-07 15:59:42.785879
test@test.comCustomerPayment-C-74-22INR54.21a192.168.0.82AuthSuccessfulauthorize.net2005-11-07 15:59:42.785879
test@test.comCustomerPayment-C-74-23INR54.21a192.168.0.82AuthSuccessfulauthorize.net2005-11-07 15:59:42.785879

HIGH RISK ALERT LIST - Different Credit Cards used from the Same IP Address with Different Card Holder Names

UsernameRoleTransaction IdAmountCard Holder NameIP AddressStatusPayment Gateway NameDate {GMT/UTC}
test@test.comResellerAddFund-R-269-63INR123.00test192.168.0.82AuthFailedauthorize.net2005-11-07 15:59:42.785879
test@test.comResellerAddFund-R-269-64INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-11-07 15:59:42.785879
somebody@domain.comCustomerAddFund-C-74-74INR123.00a192.168.0.82AuthSuccessfulauthorize.net2005-11-07 15:59:42.785879
somebody@domain.comCustomerPayment-C-74-22INR54.21a192.168.0.82AuthSuccessfulauthorize.net2005-11-07 15:59:42.785879
somebody@domain.comCustomerPayment-C-74-23INR54.21a192.168.0.82AuthSuccessfulauthorize.net2005-11-07 15:59:42.785879

HIGH RISK ALERT LIST - Different Credit Cards used from the Same Email Address with Different Card Holder Names

UsernameRoleTransaction IdAmountCard Holder NameIP AddressStatusPayment Gateway NameDate {GMT/UTC}
test@test.comResellerAddFund-R-269-65INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-10-25 19:01:21.878671
test@test.comResellerAddFund-R-269-75INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-10-25 22:56:30.059662
test@test.comResellerAddFund-R-269-78INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-10-26 20:16:43.838572
test@test.comResellerAddFund-R-269-79INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-10-26 20:17:14.089354
test@test.comResellerAddFund-R-269-82INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-10-26 21:00:11.752088
test@test.comResellerAddFund-R-269-63INR123.00test192.168.0.82AuthFailedauthorize.net2005-11-07 15:59:42.785879
test@test.comResellerAddFund-R-269-64INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-11-07 15:59:42.785879

MEDIUM RISK ALERT LIST - Different Credit Cards used from the Same Machine with the Same Card Holder Name

UsernameRoleTransaction IdAmountCard Holder NameIP AddressStatusPayment Gateway NameDate {GMT/UTC}
test@test.comResellerAddFund-R-269-78INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-10-26 20:16:43.838572
test@test.comResellerAddFund-R-269-79INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-10-26 20:17:14.089354
testing@test.comResellerAddFund-R-269-80INR123.00test192.168.0.82AuthFailedauthorize.net2005-10-26 20:22:01.244508
test@test.comResellerAddFund-R-269-82INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-10-26 21:00:11.752088
test@test.comResellerAddFund-R-269-65INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-10-25 19:01:21.878671
test@test.comResellerAddFund-R-269-63INR123.00test192.168.0.82AuthFailedauthorize.net2005-11-07 15:59:42.785879
test@test.comResellerAddFund-R-269-64INR123.00test192.168.0.82AuthSuccessfulauthorize.net2005-11-07 15:59:42.785879
 

Loading...