<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: What does a fraudulent transaction look like?</title>
	<atom:link href="http://www.merchantaccountblog.com/archives/36/feed" rel="self" type="application/rss+xml" />
	<link>http://www.merchantaccountblog.com/archives/36</link>
	<description>Merchant Accounts, Ecommerce, Processing Equipment</description>
	<pubDate>Mon, 12 May 2008 14:34:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: The Merchant Account Blog &#187; Giving the right response - AVS and declined card messages</title>
		<link>http://www.merchantaccountblog.com/archives/36#comment-16644</link>
		<dc:creator>The Merchant Account Blog &#187; Giving the right response - AVS and declined card messages</dc:creator>
		<pubDate>Fri, 02 Nov 2007 13:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=36#comment-16644</guid>
		<description>[...] single response for any decline, AVS mismatch, error or otherwise because it eliminated one of the lesser-known types of online fraud. Card testing is not something that should be overlooked, because it can have severe consequences [...]</description>
		<content:encoded><![CDATA[<p>[...] single response for any decline, AVS mismatch, error or otherwise because it eliminated one of the lesser-known types of online fraud. Card testing is not something that should be overlooked, because it can have severe consequences [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jestep</title>
		<link>http://www.merchantaccountblog.com/archives/36#comment-792</link>
		<dc:creator>jestep</dc:creator>
		<pubDate>Thu, 28 Sep 2006 21:56:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=36#comment-792</guid>
		<description>&lt;blockquote cite="Fraudulent OrderVictim"&gt;As a merchant, I am a victim of a fradulent order. My Card Processor accepts the transaction even if the CVV and AVS fail - These systems are in place to protect everyone, and yet they donâ€™t use them, leaving me out in the cold, stuck with a huge chargeback.&lt;/blockquote&gt;

How are you accepting your credit cards? If you are using a payment gateway, there should be a method to specify to decline all AVS mismatches or errors. Even the use of both AVS and CVV don't prevent fraudulent transactions entirely. I do feel for your loss, and I know how frustrating it is. We probably get about 5 fraudulent orders per week, and maybe one or two get through per year. I hate to say that it's a part of doing business because that is unacceptable, but it really is a part of doing business.

The reason that a processor doesn't stop non-AVS transactions on their end is that there are circumstances where businesses don't want or need to use AVS. There are also AVS errors, and other miscellaneous issues that can create problems for legitimate transactions. It is up to a merchant to make sure that AVS is being used.</description>
		<content:encoded><![CDATA[<blockquote cite="Fraudulent OrderVictim"><p>As a merchant, I am a victim of a fradulent order. My Card Processor accepts the transaction even if the CVV and AVS fail - These systems are in place to protect everyone, and yet they donâ€™t use them, leaving me out in the cold, stuck with a huge chargeback.</p></blockquote>
<p>How are you accepting your credit cards? If you are using a payment gateway, there should be a method to specify to decline all AVS mismatches or errors. Even the use of both AVS and CVV don't prevent fraudulent transactions entirely. I do feel for your loss, and I know how frustrating it is. We probably get about 5 fraudulent orders per week, and maybe one or two get through per year. I hate to say that it's a part of doing business because that is unacceptable, but it really is a part of doing business.</p>
<p>The reason that a processor doesn't stop non-AVS transactions on their end is that there are circumstances where businesses don't want or need to use AVS. There are also AVS errors, and other miscellaneous issues that can create problems for legitimate transactions. It is up to a merchant to make sure that AVS is being used.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fraudulent OrderVictim</title>
		<link>http://www.merchantaccountblog.com/archives/36#comment-791</link>
		<dc:creator>Fraudulent OrderVictim</dc:creator>
		<pubDate>Thu, 28 Sep 2006 21:47:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=36#comment-791</guid>
		<description>As a merchant, I am a victim of a fradulent order.  My Card Processor accepts the transaction even if the CVV and AVS fail - These systems are in place to protect everyone, and yet they don't use them, leaving me out in the cold, stuck with a huge chargeback.</description>
		<content:encoded><![CDATA[<p>As a merchant, I am a victim of a fradulent order.  My Card Processor accepts the transaction even if the CVV and AVS fail - These systems are in place to protect everyone, and yet they don't use them, leaving me out in the cold, stuck with a huge chargeback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry Holt Blank</title>
		<link>http://www.merchantaccountblog.com/archives/36#comment-784</link>
		<dc:creator>Barry Holt Blank</dc:creator>
		<pubDate>Sat, 23 Sep 2006 22:15:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=36#comment-784</guid>
		<description>Merchants should also be aware that a rogue employee may possibly produce unauthorized credits to their personal credit card account at the expense of the merchant.</description>
		<content:encoded><![CDATA[<p>Merchants should also be aware that a rogue employee may possibly produce unauthorized credits to their personal credit card account at the expense of the merchant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Dwyer</title>
		<link>http://www.merchantaccountblog.com/archives/36#comment-762</link>
		<dc:creator>Michael Dwyer</dc:creator>
		<pubDate>Tue, 05 Sep 2006 20:49:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=36#comment-762</guid>
		<description>"Always use AVS and CVV/CV2/CVC (Card Verification) on every transaction you process. This will at the very least guarantee that the card holder has the card, and it is being billed to an address registered to the card."

This provides no guarantee of this at all.  Someone who presents a valid CVV only proves that they have a valid CVV.  It suggests that they did NOT skim the card from carbons (which doesn't happen much anyway), and possibly stole the entire card.

CVV may protect you, the merchant, however.  It transfers the burden of proof over the the credit card owner.</description>
		<content:encoded><![CDATA[<p>"Always use AVS and CVV/CV2/CVC (Card Verification) on every transaction you process. This will at the very least guarantee that the card holder has the card, and it is being billed to an address registered to the card."</p>
<p>This provides no guarantee of this at all.  Someone who presents a valid CVV only proves that they have a valid CVV.  It suggests that they did NOT skim the card from carbons (which doesn't happen much anyway), and possibly stole the entire card.</p>
<p>CVV may protect you, the merchant, however.  It transfers the burden of proof over the the credit card owner.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WebtrafficJunkie</title>
		<link>http://www.merchantaccountblog.com/archives/36#comment-7</link>
		<dc:creator>WebtrafficJunkie</dc:creator>
		<pubDate>Fri, 10 Feb 2006 18:19:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=36#comment-7</guid>
		<description>This is an awesome article.  I learned a lot of great tips and pointers that will help prevent fraudulent transactions.  Thanks for the information and keep up the great work!!</description>
		<content:encoded><![CDATA[<p>This is an awesome article.  I learned a lot of great tips and pointers that will help prevent fraudulent transactions.  Thanks for the information and keep up the great work!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
