{"id":667,"date":"2009-02-04T16:10:27","date_gmt":"2009-02-04T21:10:27","guid":{"rendered":"http:\/\/www.merchantaccountblog.com\/?p=667"},"modified":"2010-05-06T09:33:34","modified_gmt":"2010-05-06T14:33:34","slug":"spotting-large-scale-credit-card-fraud","status":"publish","type":"post","link":"https:\/\/www.merchantequip.com\/merchant-account-blog\/667\/spotting-large-scale-credit-card-fraud","title":{"rendered":"Spotting large scale credit card fraud"},"content":{"rendered":"

Card issuers have massive computer systems that handle transaction processing. These companies also have some very advanced and large scale fraud detection systems.<\/p>\n

Every time a credit card is reported as stolen, a huge amount of past data about that card is put into a big database. This database of pre-fraud activity is used in a large algorithm to look for similarities, which can signal the origination of stolen or lost credit card numbers. Since Visa and MasterCard have access to billions of transactions worth of information, they can screen for events that may signal that a business is losing card numbers.<\/p>\n

If you were to greatly simplify this system and a map from it, it would look something like this:
\n

\"Fraud<\/center><\/p>\n

In this case, the similarity is a single business where all of the stolen credit cards had been used before <\/strong>the cards had been involved in fraudulent activity. This could potentially be the sign of an employee skimming card numbers, or a breach in a database. There are always going to be coincidences involving data on a large scale, but because of the scale, it’s very difficult to end up with false positive fraud once a margin of error is established.<\/p>\n

\"Processor<\/center><\/p>\n

Let’s assume there isn’t any conclusive evidence that cards were stolen from a single business. Issuers are also looking at the processor a business is using. If there is a common processor or processing network that many businesses are using, it could be a signal of a data breach on a processor level.<\/p>\n

\"Processor<\/center><\/p>\n

The similarity in this case is the processor that many of the businesses were using. This is basically how the Heartland breach was discovered. Unfortunately, the only companies that can see fraud like this are ones that have access to huge amounts of past card usage. Their computer systems basically load billions of pieces of data about transactions, the businesses that accepted a customer’s card, and the processors who processed them. When enough lines meet up at a single point, there’s a chance that something happened there. It really doesn’t matter where in the process of a transaction the lines all cross, just that they do cross.<\/p>\n

Keep in mind that these diagrams are grossly simplified, think a billion times simplified. But, it’s easy to see that if you have the right data and know what to look for, fraud can be easy to spot.<\/p>\n

Here’s a great map of credit card fraud in the UK<\/a>. While not a processor related point, this is the best visual demonstration of visually spotting fraud hot spots on a map that I have seen.<\/p>\n","protected":false},"excerpt":{"rendered":"

Card issuers have massive computer systems that handle transaction processing. These companies also have some very advanced and large scale fraud detection systems. Every time a credit card is reported as stolen, a huge amount of past data about that card is put into a big database. This database of pre-fraud activity is used in […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,1],"tags":[],"class_list":["post-667","post","type-post","status-publish","format-standard","hentry","category-fraud","category-merchantaccounts"],"_links":{"self":[{"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/posts\/667","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/comments?post=667"}],"version-history":[{"count":29,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/posts\/667\/revisions"}],"predecessor-version":[{"id":1112,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/posts\/667\/revisions\/1112"}],"wp:attachment":[{"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/media?parent=667"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/categories?post=667"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.merchantequip.com\/merchant-account-blog\/wp-json\/wp\/v2\/tags?post=667"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}