Adumo Online's Fraud Module can be configured to flag or fail transactions based on specific parameters configured. By using IP address locaters, BIN origins and shipping addresses, the Fraud Module helps merchants in identifying potential fraudulent transactions. Within the \Adumo Online Web Console, merchants can configure the Fraud Module Options to flag or fail transactions based on specific transactional behavior.
Note: This is not required to be configured if you are using the My Terminal application.
To configure the fraud module go to:
- Go to"Products" tab and click"Payment Gateway"
- Click "Settings"
- Click "Fraud Module"
Illustration: Fraud Module – Configure Fraud
Failed and Flagged Transactions
Based on the merchants specific requirements, a transaction can be failed or flagged. A failed transaction means that the transaction will be failed (declined) prior to the transaction being sent to the bank for authorization. A flagged transaction will be sent to the bank for authorization but will have a flagged status within the Fraud Module. A merchant can then analyse the transaction before delivering the goods or settling the transaction.
Notification
Within the Web Console, Merchants can configure to be notified by email of any transaction that has been flagged or failed.
Fraud Module Options
Blacklisting
Blacklisting allows you to block purchase attempts on the payment gateway. You are able to blacklist key identifiers which may be suspicious. Blacklisting also allows geographic sales targeting whereby you can configure specific countries based on BIN or IP address to purchase.
Blacklist Types:
- Blocking specific credit card numbers
- Blocking specific IP addresses
- Blocking specific countries, cities or regions
- Blocking UCI's(Unique Client Identifier)
Illustration: Blacklisting
Repeated Failure Identification (RFI)
Repeated Failure Identification works in conjunction with blacklisting and allows the merchant to set the amount of failed attempts a purchaser can make before they are blocked from making further attempts. If a purchaser makes too many purchase attempts without success, it could mean that certain card detail is trying to be guessed.
Illustration: Repeated Failure Identification
Repeated Success Identification (RSI)
Repeated Successful Identification allows the merchant to set the amount of successful transactions a purchaser can make before they’re flagged as potential fraud or blocked from making further transactions. A purchaser is defined from their IP address or credit card number.
Illustration: Repeated Success Identification
Global IP Recognition (GIR)
GIR compares the purchaser's delivery address to the global geographic location assigned to their IP address. This would aid in identifying if someone was purchasing on your website and their billing address is in the UK but their IP address is in Germany. Further investigation can be applied before delivery of goods.
Illustration: Global IP Recognition
Unique Client Index (UCI)
UCI forms a one-to-one relationship between a client and a credit card number. The merchant has the ability to provide Wirecard with a unique-client-identifier when processing a transaction. Wirecard stores the card number used by that client, and will flag or fail later transactions used by this client with a different card number. This insures that the credit card being used by the client is the card previously used for transacting.
Illustration: Unique Client Identification
Comments
0 comments
Article is closed for comments.