Card testing happens when an attacker "tests" a card number that was either made up or obtained through phishing or spyware software, or from the dark web. The objective of the test is not necessarily to purchase a product or service, but to see if the details of the card are valid by attempting small purchases online on the site of an unsuspecting vendor and then checking to see if the card was approved.1
Make sure your checkout pages include technologies for detection and prevention of sending transactions coming from automated scripts such as:
Firewalls. Tools for detecting, preventing and eliminating botnets.
CAPTCHA. A challenge-response visual test to distinguish a human from an automated script.
Device fingerprinting. Identifies multiple contacts with the same device.
Velocity thresholds. Limits the number of transactions permitted within a specified timeframe.
Anomaly Detection. Detection of unusual peaks in the traffic of a web page, unusual patterns during purchase or when filling out forms.
If your site accepts donations or free text payment amounts, it is especially important that you include measures to avoid automatic scripts for card testing. These sites are vulnerable.
In addition to the previous steps, keep the following in mind:
Set thresholds for minimum amounts. Fraudsters seek to know if the card is valid, avoiding the possibility of the cardholder noticing and reporting. The smaller the purchase amount, the lesser probability that it will attract attention.
Avoid transactions for small amounts. It is often common to see transactions for very small amounts, even equal to zero. It is better to set a higher minimum amount.
Stay alert and identify any anomalies in advance:
Investigate any changes in daily transactions.
Pay attention to sudden increases in the number of card rejections.
Use velocity tools to track totals and other data specs.