As a reseller you can determine which fraud modules are contained in your merchants' Universal Fraud Module stack. You can add or delete modules at any time from the fraud module settings page.
Adding fraud modules to the Universal Fraud Module stack creates a default fraud prevention setting for all merchant accounts. Once you have added modules to your Universal Fraud Module stack they will automatically be applied to all of your merchants' accounts. Merchants will not be able to see or edit the fraud modules you enable here. Once added, the Fraud Modules setting page will display all current modules as shown below, along with buttons allowing you to edit the settings of each module or remove them from the stack.
To add modules to the stack of Universal Fraud Modules for inclusion in all of your merchants' fraud stacks, click on the Add Module at the top of the existing list. You will be taken to a list of all available modules, and you can add any one or more of them by clicking on the Select button to the right of the module's description. The setting options for the selected module will load and you can check the fraud settings are right for you. When you are finished, click the Apply button at the bottom of the screen to apply the new fraud module settings to the source you have selected.
Once you have applied your changes, the new module will appear on the Fraud Center page of your Merchant Console, under the heading of the source to which it has been applied. Beside the module is a Settings button and a Remove button which you can use at any time to alter or delete the fraud module from the source.
Available Fraud Modules include the following, click on any Module for a detailed description of its functionality:
This module allows you to select which transactions to accept based on the address verification system response. Check off the responses that you will accept. All others will be declined. The following is a list of all of the possible AVS response codes.
The following is a list of result codes for the Address Verification System (AVS) and what each one indicates. The codes listed in the Code column are the most common responses, but depending on the platform being used, codes listed in the Alternates column may be received.
|YYY||Y, YYA, YYD||Address: Match & 5 Digit Zip: Match|
|NYZ||Z||Address: No Match & 5 Digit Zip: Match|
|YNA||A, YNY||Address: Match & 5 Digit Zip: No Match|
|NNN||N, NN||Address: No Match & 5 Digit Zip: No Match|
|YYX||X||Address: Match & 9 Digit Zip: Match|
|NYW||W||Address: No Match & 9 Digit Zip: Match|
|XXW||Card Number Not On File|
|XXU||Address Information not verified for domestic transaction|
|XXR||R, U, E||Retry / System Unavailable|
|XXS||S||Service Not Supported|
|XXE||Address Verification Not Allowed For Card Type|
|XXG||G,C,I||Global Non-AVS participant|
|YYG||B, M||International Address: Match & Zip: Not Compatible|
|GGG||D||International Address: Match & Zip: Match|
|YGG||P||International Address: No Compatible & Zip: Match|
This module will block transactions based on a single IP address (192.0.0.1), a range of IPs (192.0.0.0-184.108.40.206), a host address (hacker.fraud.com) or an entire tld (*.jp), domain (*.fraud.jp) or subdomain (*.more.fraud.jp). To use this module your shopping cart software must pass the client ip correctly. To check if your cart is passing the client ip, view the details on a transaction. If an ip is listed next to “Client IP” then you will be able to use this module.
This module allows you to select which transactions to accept based on the result of the card id verification (CVV2, CID, etc). Check off the responses that you will accept. All others will error.
Only allow credit card types listed. Transactions that are not listed will be blocked. Please note that this does not affect whether your merchant account has support for a specific card type. If you allow a transaction in this fraud module but you do not have support for it, the transaction will still be declined by the processor. Please check with your merchant account provider for more information on which card types you may accept.
Blocks or allows transactions based on what country they originate in. The location of the customer is based on their IP address which is checked against our GeoIP database. To use this module your shopping cart must pass the ip address to the gateway.
This module detects and blocks duplicate transactions. This is useful for shopping carts that do not catch when a user has (accidentally) double clicked on the order button. The system uses the last 4 digits of the card number, the transaction amount and the invoice number to determine if a duplicate transaction has been submitted. You must specify the length of time the system will check back for a duplicate transaction.
Blocks transactions coming from free webmail servers such as Hotmail and Yahoo. It can also be configured to allow or block specific email addresses or domains.
This module performs a real time fraud risk assessment of transactions. If the resulting score is over a set threshold, the transaction is blocked.
The risk assessment is a combination of automated and human traffic pattern analysis. Any sudden changes in the number of transactions, the dollar amounts, the countries of the customers or decline rate received by a merchant are flagged and used to build a blacklist of customers by IP address.
Please note: USAePay implements this fraud module across the board for ALL merchants with the threshold that prevents large scale abuse without blocking typical transaction patters. Merchants do not need to add this module themselves unless they would like to change the error message or use a higher sensitivity.
The error reason listed in reports for transactions that are declined by this module is: “Transaction declined (fp)” By default, the end customer will see: “Your billing information does not match your credit card. Please check with your bank.”
Block transactions where more then a specified number of different card numbers are attempted on the same order number or from the same ip address. This is useful for blocking people from using your merchant account to test stolen credit card numbers. To use this module your shopping cart must pass the ip address to the gateway.
This module allows you to define allowable transaction amounts. Any transactions that are not within the defined amounts are blocked. If you only want to specify a minimum but no maximum, enter a * in the maximum field. Likewise, if you only want to specify a maximum but no minimum, enter a * in the minimum field.