View Tree

The TrillionPay Risk Mitigation and Fraud Report is an important tool to allow you to identify any potentially fraudulent and risky transactions. It is important to review this report on a daily basis and take appropriate measures to identify risky / fraudulent transactions. Below we describe the various aspects of the report to assist you in tracking fraudulent transactions and understanding the risk factor involved with the transactions listed.

TrillionPay investigates all transactions conducted on our gateway and assigns a risk value to each transaction. Based on this Risk Value TrillionPay generates this report. The Report is divided into three sections -

High Risk Fraud Alerts
These are transactions which are perceived to be MOST Risky. These transactions should be checked up thouroughly. There are various different types of High Risk Transactions which appear in the report.

Billing Address Mis-Match
This consists of transactions where we have found some mismatch between the Card Holders Billing Information, the Card, and the Card Holders location. For instance, if someone in India is using a Card issued in the USA, with an address that belongs to China, you will see this transaction here. Basically, any transaction that has a Billing Address MISMATCH must be screened carefully, before you deliver the product

Different Cards used from the same E-mail Address
This section checks all transactions which have been done in the last 30 days, and reports those transactions where a single E-mail Address has used multiple different Credit Cards. Transactions are shown in groups wherever possible. These groups contain information of the past transactions. For instance, check the display below -

Trackingid Description Amount Card Holder Ip Address Emailaddr Status Date
 39946  10250  5704.00  David C Larkin  202.159.4.145  drav@sek-arat.com  authfailed  2002-09-28 21:04:45
 39947  10250  5704.00  DAVID GLAZEBROOK  202.159.4.145  drav@sek-arat.com  authsuccessful  2002-09-28 21:07:40
 40300  10289  17756.00  Kiong La Sim  64.193.234.189  kim@kiong.com  authfailed  2002-10-01 18:01:40
 40301  10289  17756.00  USA GOVERNMENT I.M.P.A.C CREDIT CARD  64.193.234.189  kim@kiong.com  authsuccessful  2002-10-01 18:07:46
 39509  10025  500.00  PARTH GABBU  61.11.22.87  panky@gabbu.com  authsuccessful  2002-09-24 15:23:43
 40110  10052  1348.00  PARTH P GABBU  61.11.22.164  panky@gabbu.com  authfailed  2002-09-30 06:15:15
 40111  10052  1348.00  PARTH P GABBU  61.11.22.164  panky@gabbu.com  authfailed  2002-09-30 06:18:23
 40112  8177  472.00  PARTH P GABBU  61.11.22.164  panky@gabbu.com  authsuccessful  2002-09-30 06:25:19
 40163  10052  1348.00  PARTH P GABBU  61.11.22.164  panky@gabbu.com  authsuccessful  2002-09-30 14:03:20
 39418  10193  262.00  Venky Sahilesh  61.11.57.159  venkat@somedomain.com  authsuccessful  2002-09-24 05:59:19

Each Transaction Group is shown in the same colour. The above display shows 4 transaction groups. Take the first group. As you can see, someone by the e-mail address drav@sek-arat.com has done 2 different transactions using different cards. The first transaction failed while the second one succeeded. All details of the transactions are given in the report.

The last transaction group has only one entry. This would mean that venkat@somedomain.com has done multiple transactions with different cards in the past 30 days, however, those transactions maybe at another Merchant, and therefore, we can not show them to you. Nonetheless, you must check out this particular transaction before delivering the products/services.

Different Cards used from the same IP Address
This section checks all transactions which have been done in the last 8 days, and reports those transactions where a SINGLE IP Address has used multiple different Credit Cards. Transactions are shown in groups wherever possible. These groups contain information of the past transactions the same way as displayed above.

Different Cards used from the same Machine
This section checks all transactions which have been done in the last 30 days, and reports those transactions where a SINGLE Machine has used multiple different Credit Cards. Transactions are shown in groups wherever possible. These groups contain information of the past transactions the same way as displayed above.

Medium Risk Fraud Alerts
Medium risk Fraud alerts are similar to High Risk Fraud Alerts, EXCEPT that the Card Holder Name on the different cards is the same. Which means that, for instance, if someone uses 3 different cards of different Card Holders then the transaction is High Risk. If however, the cards used are different BUT the Card Holder Names are the same then the transaction is treated as Medium Risk.

Low Risk Fraud Alerts
When a card holder tries a transaction and it fails - it would arise suspicion. Primarily because, most fraudsters have a list of cards - some of which work, while others don't. Most of the cards that do not work would be because they have run out of funds. Therefore, any transaction that fails due to a Insufficient Funds error is SUSPICIOUS. This section consists of a list of transactions which have failed with similar suspicious errors. It is advisable to check all orders, which match these orders and have happened on the same day.

Besides this comprehensive Report, you also receive individual e-mails informing you about the Risk perception from individual transactions. These risky transactions, display various codes that are explained below:

  1. DIP - Different Credit Cards were used by a Customer, from the same IP Address, with different Credit Card Holder Names.
  2. DMC - Different Credit Cards were used by a Customer, from the same Machine, with different Credit Card Holder Names.
  3. DEM - Different Credit Cards were used by a Customer, from the same E-mail Address with different Credit Card Holder Names.
  4. DCON - Billing Address Mis-match.
  5. HAMT - Transaction Amount is higher than High Value Transaction Amount set for you.
  6. HRCP - High Risk Behaviour
  7. MRCP - Medium Risk Behaviour

Created on: Oct 5, 2002 6:22 AM GMT

Last Updated on: Oct 19, 2007 9:26 AM GMT