<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The costs of not using AVS (Address Verification System)!</title>
	<atom:link href="http://www.merchantaccountblog.com/84/the-costs-of-not-using-avs-address-verification-system/feed" rel="self" type="application/rss+xml" />
	<link>http://www.merchantaccountblog.com/84/the-costs-of-not-using-avs-address-verification-system</link>
	<description>Merchant Accounts, Ecommerce, Processing Equipment</description>
	<lastBuildDate>Fri, 05 Mar 2010 02:27:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: headsets</title>
		<link>http://www.merchantaccountblog.com/84/the-costs-of-not-using-avs-address-verification-system/comment-page-1#comment-20676</link>
		<dc:creator>headsets</dc:creator>
		<pubDate>Fri, 28 Aug 2009 23:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=84#comment-20676</guid>
		<description>AVS does not check for the spelling.  Only check for the street# and zip code.</description>
		<content:encoded><![CDATA[<p>AVS does not check for the spelling.  Only check for the street# and zip code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.merchantaccountblog.com/84/the-costs-of-not-using-avs-address-verification-system/comment-page-1#comment-20652</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Wed, 12 Aug 2009 04:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=84#comment-20652</guid>
		<description>AVS Sucks.  I speak from experience because I am a merchant.  I just spent hours on the phone trying to purchase an online ticket, and the problem was an address verification.  The idiot/lazy employee who made my address change typed &quot;cres&quot; instead of &quot;crescent&quot; and the AVS was failing my transaction.</description>
		<content:encoded><![CDATA[<p>AVS Sucks.  I speak from experience because I am a merchant.  I just spent hours on the phone trying to purchase an online ticket, and the problem was an address verification.  The idiot/lazy employee who made my address change typed &#8220;cres&#8221; instead of &#8220;crescent&#8221; and the AVS was failing my transaction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jestep</title>
		<link>http://www.merchantaccountblog.com/84/the-costs-of-not-using-avs-address-verification-system/comment-page-1#comment-15</link>
		<dc:creator>jestep</dc:creator>
		<pubDate>Fri, 17 Mar 2006 19:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=84#comment-15</guid>
		<description>AVS definitely is prone to error. I think that the particular gateway has a lot to do with how error prone it is. Authorize.net seems to have errors frequently compared to other gateways. Network Merchants which is a similar gateway seems to be quite a bit more reliable as far as AVS goes.

I&#039;m not sure about Verisign or Linkpoint, as I just don&#039;t have enough experience with them.

Also, most payment gateways allow you to accept transaction if there is an AVS error. This way if there is some technical malfunction, the transaction can process and your customer wont need to come to you with the your site sucks line.</description>
		<content:encoded><![CDATA[<p>AVS definitely is prone to error. I think that the particular gateway has a lot to do with how error prone it is. Authorize.net seems to have errors frequently compared to other gateways. Network Merchants which is a similar gateway seems to be quite a bit more reliable as far as AVS goes.</p>
<p>I&#8217;m not sure about Verisign or Linkpoint, as I just don&#8217;t have enough experience with them.</p>
<p>Also, most payment gateways allow you to accept transaction if there is an AVS error. This way if there is some technical malfunction, the transaction can process and your customer wont need to come to you with the your site sucks line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: erikheerlein</title>
		<link>http://www.merchantaccountblog.com/84/the-costs-of-not-using-avs-address-verification-system/comment-page-1#comment-14</link>
		<dc:creator>erikheerlein</dc:creator>
		<pubDate>Fri, 17 Mar 2006 19:15:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.merchantaccountblog.com/?p=84#comment-14</guid>
		<description>But AVS is very error prone in my experience. And the 5 cents charge is made for each attempt so if you reject a transaction based on AVS and alert the customer (I&#039;m talking online here) and they try a couple more times, you will be charged each time. And then the customer will call and complain that your site sucks or just leave the site and you are charged maybe $0.20 and no sale was made.</description>
		<content:encoded><![CDATA[<p>But AVS is very error prone in my experience. And the 5 cents charge is made for each attempt so if you reject a transaction based on AVS and alert the customer (I&#8217;m talking online here) and they try a couple more times, you will be charged each time. And then the customer will call and complain that your site sucks or just leave the site and you are charged maybe $0.20 and no sale was made.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
