Pre-transaction fraud is the total activity that culminates in fraud before a transaction occurs. It is typically committed by third party fraudsters who misuse customers’ card details, which is known as true fraud. Another type of pre-transaction fraud is essentially first-party policy abuse, which is committed by regular customers who abuse promotional offers and subscription trials or share their credentials with unauthorized persons. For example, they may create duplicate accounts, exploit promotional incentives, or attempt re-trials of subscription services. For merchants, these fraudulent attempts imply losses in promotion-derived revenue, failure of subscription models, or losses in general.
Preventing pre-transaction fraud is easy if you can identify miscreants in real time before a transaction goes through. This helps avoid losses in revenue primarily caused by theft, lost business, and customer attrition. Moreover, it also prevents undesirable occurrences such as chargebacks. The trick is to identify who the customer is and ensure that suspicious behaviors are recognized.
Although card issuers are supposed to deny suspicious transactions, because merchants are typically financially liable for fraudulent transactions, they also proactively protect their interests by declining any suspicious transactions. One way to do that is by matching customers’ devices and billing addresses with the pre-transaction data. If they do not match, merchants can contact customers directly before approving a transaction. The easiest way to do this is by using automated tools to identify risks before approving transactions to reduce the need for damage control later.
There are a number of popular solutions on the market that not only block fraudulent transactions but identify transactions likely to be from good customers to prevent too many false positives. Falsely declining legitimate transactions reduces revenue figures and increases attrition of customers, who may be put off by not being able to complete a transaction successfully. Usually, historical transaction data tied to customers and the geolocation from where the transaction is initiated are used to determine order validity, among other technical parameters.