<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Data Mining and Fraud Prevention</title>
	<atom:link href="http://www.businessdataminers.com/blog/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.businessdataminers.com/blog</link>
	<description>Dr. Jay Zhou at Business Data Miners, LLC (www.businessdataminers.com)</description>
	<lastBuildDate>Thu, 04 Oct 2012 02:07:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Detect Compromised Cards Before Fraud Happens</title>
		<link>http://www.businessdataminers.com/blog/?p=174</link>
		<comments>http://www.businessdataminers.com/blog/?p=174#comments</comments>
		<pubDate>Thu, 04 Oct 2012 02:07:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.businessdataminers.com/blog/?p=174</guid>
		<description><![CDATA[Take action before fraud happens. Business Data Miners proprietary algorithm is able to detect
cards that will likely have fraudulent activities within 6 months in the future. If these cards are
reissued or closely monitored, we can reduce a significant amount of the fraud loss. In a live
testing of our algorithm at a top 15 bank, 19% [...]]]></description>
			<content:encoded><![CDATA[<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;">Take action before fraud happens. Business Data Miners proprietary algorithm is able to detect</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;">cards that will likely have fraudulent activities within 6 months in the future. If these cards are</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;">reissued or closely monitored, we can reduce a significant amount of the fraud loss. In a live</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;">testing of our algorithm at a top 15 bank, 19% of cards that we predicted as being</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;">compromised had fraudulent activities within 3 months after our prediction. We estimate that</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;">the annual fraud savings is above $1 million.  By reissuing risky cards, we prevent fraudulent</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;">activity before it happens. An added benefit of doing this is that the impact of fraud on good</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;">customers is eliminated.</div>
<p>Business Data Miners proprietary algorithm is able to detect cards that will likely have fraudulent activities within 6 months in the future. If these cards are reissued or closely monitored, we can reduce a significant amount of the fraud loss. In a live testing of our algorithm at a top 15 bank, 19% of cards that we predicted as being compromised had fraudulent activities within 3 months after our prediction. We estimate that the annual fraud savings is above $1 million.  By reissuing risky cards, we prevent fraudulent activity before it happens. An added benefit of doing this is that the impact of fraud on good customers is eliminated.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.businessdataminers.com/blog/?feed=rss2&amp;p=174</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Our bad debt model has saved the client tens of millions dollars over the past three years.</title>
		<link>http://www.businessdataminers.com/blog/?p=165</link>
		<comments>http://www.businessdataminers.com/blog/?p=165#comments</comments>
		<pubDate>Tue, 12 Jun 2012 15:05:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bad debt]]></category>
		<category><![CDATA[predictive model]]></category>

		<guid isPermaLink="false">http://www.businessdataminers.com/blog/?p=165</guid>
		<description><![CDATA[As of 6/3, our bad debt model has saved tens of millions dollars over the past three years by reducing the delinquency rate of a large bank by 50%! 
]]></description>
			<content:encoded><![CDATA[<p><span style="font-family: Arial, Helvetica, 'Nimbus Sans L', sans-serif; font-size: 14px; line-height: 13px;">As of 6/3, our bad debt model has saved tens of millions dollars over the past three years by reducing the delinquency rate of a large bank by 50%! </span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.businessdataminers.com/blog/?feed=rss2&amp;p=165</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Build Fraud Detection Model Without Historically Known Fraud Data</title>
		<link>http://www.businessdataminers.com/blog/?p=161</link>
		<comments>http://www.businessdataminers.com/blog/?p=161#comments</comments>
		<pubDate>Tue, 22 May 2012 06:00:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[card fraud]]></category>
		<category><![CDATA[claim fraud]]></category>
		<category><![CDATA[fraud detection]]></category>

		<guid isPermaLink="false">http://www.businessdataminers.com/blog/?p=161</guid>
		<description><![CDATA[When there are no historically known fraud data, we have to build unsupervised models that do not require a target variable. There are a number of such models that we can try: one-class support vector machine, principal component based compression net, etc. They are detecting data points that are abnormal, not fraudulent per se. We [...]]]></description>
			<content:encoded><![CDATA[<p>When there are no historically known fraud data, we have to build unsupervised models that do not require a target variable. There are a number of such models that we can try: one-class support vector machine, principal component based compression net, etc. They are detecting data points that are abnormal, not fraudulent per se. We only hope that  being abnormal is highly related to being fraudulent.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.businessdataminers.com/blog/?feed=rss2&amp;p=161</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Visa, MasterCard affected by &#8216;massive&#8217; data breach</title>
		<link>http://www.businessdataminers.com/blog/?p=156</link>
		<comments>http://www.businessdataminers.com/blog/?p=156#comments</comments>
		<pubDate>Sat, 31 Mar 2012 12:46:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[fraud prevention rules]]></category>
		<category><![CDATA[card fraud]]></category>
		<category><![CDATA[credit card fraud]]></category>
		<category><![CDATA[fraud detection]]></category>

		<guid isPermaLink="false">http://www.businessdataminers.com/blog/?p=156</guid>
		<description><![CDATA[On the other hand,  small data breach events (e.g, skimming) are happening on daily basis (a few hundred or thousand cards are skimmed here and there across millions of POS/ATM). They are less dramatic and wouldn&#8217;t make the headline. But their cumulative damage over a year is huge. That&#8217;s why we have developed Fraudulent Card Early [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #222222; font-family: arial, sans-serif; line-height: normal; background-color: rgba(255, 255, 255, 0.917969);">On the other hand,  small data breach events (e.g, skimming) are happening on daily basis (a few hundred or thousand cards are skimmed here and there across millions of POS/ATM). They are less dramatic and wouldn&#8217;t make the headline. But their cumulative damage over a year is huge. That&#8217;s why we have developed <strong>Fraudulent Card Early Detection Solution.</strong></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.businessdataminers.com/blog/?feed=rss2&amp;p=156</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Check Fraud Detection Model Is Put Into Production</title>
		<link>http://www.businessdataminers.com/blog/?p=153</link>
		<comments>http://www.businessdataminers.com/blog/?p=153#comments</comments>
		<pubDate>Fri, 30 Mar 2012 21:32:44 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.businessdataminers.com/blog/?p=153</guid>
		<description><![CDATA[Feedback from the client, one of the top 15 banks in US, was great. The volume of existing ASI19 check fraud alerts is reduced while more frauds are detected.
]]></description>
			<content:encoded><![CDATA[<p>Feedback from the client, one of the top 15 banks in US, was great. The volume of existing ASI19 check fraud alerts is reduced while more frauds are detected.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.businessdataminers.com/blog/?feed=rss2&amp;p=153</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stop Frauds Three Months Before They Happen</title>
		<link>http://www.businessdataminers.com/blog/?p=144</link>
		<comments>http://www.businessdataminers.com/blog/?p=144#comments</comments>
		<pubDate>Fri, 17 Feb 2012 12:58:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Common Point of Purchase]]></category>
		<category><![CDATA[credit card fraud]]></category>
		<category><![CDATA[debit card fraud]]></category>
		<category><![CDATA[fraud prevention]]></category>

		<guid isPermaLink="false">http://www.businessdataminers.com/blog/?p=144</guid>
		<description><![CDATA[BDM&#8217;s algorithm is able to produce a list of likely compromised cards, 19% of which will have fraudulent activities within 3 months in the future. If we reissue them today, we can reduce significant amount of fraud loss with least amount of impact to good customers.
]]></description>
			<content:encoded><![CDATA[<p><span style="color: #222222; font-family: arial, sans-serif; line-height: normal; background-color: rgba(255, 255, 255, 0.917969);">BDM&#8217;s algorithm is able to produce a list of </span><span style="color: #222222; font-family: arial, sans-serif; line-height: normal; background-color: rgba(255, 255, 255, 0.917969);"><span style="font-family: arial, sans-serif; color: #222222;"><span style="line-height: normal;">likely compromised cards, 19% of which will have fraudulent activities within 3 months in the future. If we reissue them today, we can reduce significant amount of fraud loss with least amount of impact to good customers.</span></span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.businessdataminers.com/blog/?feed=rss2&amp;p=144</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Optimize Debit Card Daily Transaction Limit</title>
		<link>http://www.businessdataminers.com/blog/?p=140</link>
		<comments>http://www.businessdataminers.com/blog/?p=140#comments</comments>
		<pubDate>Tue, 22 Nov 2011 05:05:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.businessdataminers.com/blog/?p=140</guid>
		<description><![CDATA[Delivered the optimal debit card signature transaction daily limit for a client bank. Performing the similar analysis to optimize PIN-based transaction daily limit. The core idea is to maximize the net of transaction fee plus overdraft fee minus fraud loss. The main technical challenge is to merge 100 million records in settlement, authorization, overdraft and [...]]]></description>
			<content:encoded><![CDATA[<p>Delivered the optimal debit card signature transaction daily limit for a client bank. Performing the similar analysis to optimize PIN-based transaction daily limit. The core idea is to maximize the net of transaction fee plus overdraft fee minus fraud loss. The main technical challenge is to merge 100 million records in settlement, authorization, overdraft and claim fuzzily and iteratively.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.businessdataminers.com/blog/?feed=rss2&amp;p=140</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Long Term Card Fraud Prediction</title>
		<link>http://www.businessdataminers.com/blog/?p=136</link>
		<comments>http://www.businessdataminers.com/blog/?p=136#comments</comments>
		<pubDate>Mon, 31 Oct 2011 03:00:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[card fraud]]></category>
		<category><![CDATA[credit card fraud]]></category>
		<category><![CDATA[fraud detection]]></category>

		<guid isPermaLink="false">http://www.businessdataminers.com/blog/?p=136</guid>
		<description><![CDATA[Most of the debit/credit card fraud detection is based on transaction level rules or scores that target the fraud transactions happening in real time. Fraud prevention operation is struggling to stop fraud in real/near real time.
If we can predict which cards will likely have fraudulent activities within the next a few months, we can either [...]]]></description>
			<content:encoded><![CDATA[<p>Most of the debit/credit card fraud detection is based on transaction level rules or scores that target the fraud transactions happening in real time. Fraud prevention operation is struggling to stop fraud in real/near real time.</p>
<p>If we can predict which cards will likely have fraudulent activities within the next a few months, we can either reissue those cards today or build transaction level rules to monitor them. The long term card fraud prediction is, just like long term weather forecast, doable.  At BDM, we have tested such a method and found the results are good and actionable.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.businessdataminers.com/blog/?feed=rss2&amp;p=136</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>&#8220;Superficial&#8221; vs. &#8220;Inherent&#8221; Fraud Detection Rules</title>
		<link>http://www.businessdataminers.com/blog/?p=132</link>
		<comments>http://www.businessdataminers.com/blog/?p=132#comments</comments>
		<pubDate>Tue, 30 Aug 2011 18:26:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[fraud detection]]></category>

		<guid isPermaLink="false">http://www.businessdataminers.com/blog/?p=132</guid>
		<description><![CDATA[There are two types of rules, &#8220;superficial&#8221; rules and &#8220;inherent&#8221; rules. Superficial rules are easier to create and they are straightforward to understand, e.g., transactions happening at certain retailers. These rules may be good for a few weeks and their performance drop quickly. Inherent rules capture more time lasting ( and usually hidden and mutli-dimensional) [...]]]></description>
			<content:encoded><![CDATA[<p>There are two types of rules, &#8220;superficial&#8221; rules and &#8220;inherent&#8221; rules. Superficial rules are easier to create and they are straightforward to understand, e.g., transactions happening at certain retailers. These rules may be good for a few weeks and their performance drop quickly. Inherent rules capture more time lasting ( and usually hidden and mutli-dimensional) patterns of fraud behaviors. To create them,we may have to use more sophisticated methods including predictive modeling. The PRM SQL statements for some of these inherent rules that we created have 5,000 characters. These rules work like magic and have very low false positives.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.businessdataminers.com/blog/?feed=rss2&amp;p=132</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Detection of Common Point of Compromise</title>
		<link>http://www.businessdataminers.com/blog/?p=128</link>
		<comments>http://www.businessdataminers.com/blog/?p=128#comments</comments>
		<pubDate>Mon, 01 Aug 2011 12:07:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.businessdataminers.com/blog/?p=128</guid>
		<description><![CDATA[About 25% of compromised good cards identified by BDM will have fraudulent activities within the next 3 months. (In comparison, usually about 1% of cards alerted by a popular point of compromise (POC) service from a big company have fraudulent within 12 months.) The common points of compromise detected by BDM are highly accurate. Identifying [...]]]></description>
			<content:encoded><![CDATA[<p>About 25% of compromised good cards identified by BDM will have fraudulent activities within the next 3 months. (In comparison, usually about 1% of cards alerted by a popular point of compromise (POC) service from a big company have fraudulent within 12 months.) The common points of compromise detected by BDM are highly accurate. Identifying POC accurately  and early and reissuing cards provide the following benefits: 1. It is better than real time fraud detection because the fraud loss can be stopped before it happens; 2. Reissuing cards  is less intrusive to good customers than blocking suspicious transactions.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.businessdataminers.com/blog/?feed=rss2&amp;p=128</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
