<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic AVS Address Mismatch in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/AVS-Address-Mismatch/m-p/32395#M16955</link>
    <description>&lt;P&gt;I'm not the developer for our website, but our customers are getting AVS mismatches due to the wrong street address. &amp;nbsp;The customers are always positive they put in the correct info and do not get errors on other websites. &amp;nbsp;We would like to keep this security setting to make sure and verify our customers. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We noticed todays declined transactions all had the street in numeric form. &amp;nbsp;For example: 101 &lt;U&gt;&lt;STRONG&gt;10th&lt;/STRONG&gt;&lt;/U&gt; Street. &amp;nbsp;Is it possible that we are getting an AVS mismatch due to the "10th" portion when 101 is the only portion that should be verified? &amp;nbsp;We haven't noticed any issues with apartment numbers in the address that is submitted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any coding we can ask our developer to check on to keep this from happing?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this something that authorize.net can fix?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Fri, 04 Jan 2013 21:02:19 GMT</pubDate>
    <dc:creator>troypaulson</dc:creator>
    <dc:date>2013-01-04T21:02:19Z</dc:date>
    <item>
      <title>AVS Address Mismatch</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/AVS-Address-Mismatch/m-p/32395#M16955</link>
      <description>&lt;P&gt;I'm not the developer for our website, but our customers are getting AVS mismatches due to the wrong street address. &amp;nbsp;The customers are always positive they put in the correct info and do not get errors on other websites. &amp;nbsp;We would like to keep this security setting to make sure and verify our customers. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We noticed todays declined transactions all had the street in numeric form. &amp;nbsp;For example: 101 &lt;U&gt;&lt;STRONG&gt;10th&lt;/STRONG&gt;&lt;/U&gt; Street. &amp;nbsp;Is it possible that we are getting an AVS mismatch due to the "10th" portion when 101 is the only portion that should be verified? &amp;nbsp;We haven't noticed any issues with apartment numbers in the address that is submitted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any coding we can ask our developer to check on to keep this from happing?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this something that authorize.net can fix?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jan 2013 21:02:19 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/AVS-Address-Mismatch/m-p/32395#M16955</guid>
      <dc:creator>troypaulson</dc:creator>
      <dc:date>2013-01-04T21:02:19Z</dc:date>
    </item>
    <item>
      <title>Re: AVS Address Mismatch</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/AVS-Address-Mismatch/m-p/32397#M16957</link>
      <description>&lt;P&gt;It is getting reject because on the merchant account it set to reject when AVS response is W or Z? you could change it to allow those and let the customer credit card issuing bank decide to accept or decline with the billing address info you send.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Jan 2013 01:08:20 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/AVS-Address-Mismatch/m-p/32397#M16957</guid>
      <dc:creator>RaynorC1emen7</dc:creator>
      <dc:date>2013-01-05T01:08:20Z</dc:date>
    </item>
  </channel>
</rss>

