<?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>Priceless &#187; fraud screening</title>
	<atom:link href="http://processforless.com/priceless/tag/fraud-screening/feed/" rel="self" type="application/rss+xml" />
	<link>http://processforless.com/priceless</link>
	<description>low fee merchant account,discount merchant account, wholesale merchant account</description>
	<lastBuildDate>Fri, 17 Dec 2010 20:08:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Chargebacks for Fraud</title>
		<link>http://processforless.com/priceless/2009/09/handling-merchant-chargebacks-for-fraud/</link>
		<comments>http://processforless.com/priceless/2009/09/handling-merchant-chargebacks-for-fraud/#comments</comments>
		<pubDate>Mon, 14 Sep 2009 20:26:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Charge Back Prevention]]></category>
		<category><![CDATA[Merchant Fraud Prevention, Credit Card Fraud]]></category>
		<category><![CDATA[charge back]]></category>
		<category><![CDATA[chargeback]]></category>
		<category><![CDATA[fraud]]></category>
		<category><![CDATA[fraud screening]]></category>
		<category><![CDATA[verification]]></category>

		<guid isPermaLink="false">http://processforless.com/priceless/?p=58</guid>
		<description><![CDATA[Your mail is here, and in it is a blue envelope from your Merchant Processor informing you that you&#8217;ve got a chargeback from a fraudulent order.
 
Emotions run the gamut, and you are justifiably angry that someone has stolen from you.
Here&#8217;s some tips to keep it from happening again!
1. Verify &#8211; Call the customer. Bad [...]]]></description>
			<content:encoded><![CDATA[<p><strong><img class="alignleft size-full wp-image-65" title="fraud" src="http://processforless.com/priceless/wp-content/uploads/2009/09/fraud.jpg" alt="fraud" width="291" height="281" />Your mail is here, and in it is a blue envelope from your Merchant Processor informing you that you&#8217;ve got a chargeback from a fraudulent order.</strong></p>
<p><strong> </strong></p>
<p>Emotions run the gamut, and you are justifiably angry that someone has stolen from you.</p>
<p>Here&#8217;s some tips to keep it from happening again!</p>
<p style="padding: 2px; margin: 0px;">1. Verify &#8211; Call the customer. Bad phone number = Red Flag<br />
2. Verify &#8211; Email the customer. No reply = Another Red Flag<br />
3. Zip Code Matches AVS, but not the Address = Yes, Another Red Flag<br />
4. Billing Address is a Match, but Shipping Address is Different = Red Flag</p>
<p>If you have a suspect order and any of the above criteria comes into play, you need to stop and DON&#8217;T CHARGE THE CARD until you complete further verification.</p>
<p>In many cases the &#8220;Fraudsters&#8221; will communicate with you and try to get you to complete their order.</p>
<p>A good method to verify a customer you are worried about, but with otherwise good address and contact info is to charge a low, odd amount (like .76 cents) and have the &#8220;Customer&#8221; tell you the amount of the charge and in that way you know that they have access to the highest levels of the account.</p>
<p><strong>Feel free to contact us at 800-996-6127 for further ways to combat fraud, verify or identify suspect orders, and to learn how to take action to apprehend those that commit fraud against you.</strong></p>
<p style="padding: 2px; margin: 0px;">
]]></content:encoded>
			<wfw:commentRss>http://processforless.com/priceless/2009/09/handling-merchant-chargebacks-for-fraud/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

