<?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 Authorize.net Credit Card API Data in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-Credit-Card-API-Data/m-p/23681#M12737</link>
    <description>&lt;P&gt;what is requires so we can send name address etc to the API and get some Security Settings.&lt;/P&gt;&lt;DIV&gt;For Example:&lt;/DIV&gt;&lt;DIV&gt;If Name on Card does Not match the Name submitted we can be notify and decide how to handle. &amp;nbsp;Another example Postal Code don't match.&lt;/DIV&gt;&lt;DIV&gt;which API can support me by this data and what is the requirements??&lt;/DIV&gt;&lt;DIV&gt;thanks,&lt;/DIV&gt;</description>
    <pubDate>Tue, 28 Feb 2012 06:44:11 GMT</pubDate>
    <dc:creator>stuclasivo</dc:creator>
    <dc:date>2012-02-28T06:44:11Z</dc:date>
    <item>
      <title>Authorize.net Credit Card API Data</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-Credit-Card-API-Data/m-p/23681#M12737</link>
      <description>&lt;P&gt;what is requires so we can send name address etc to the API and get some Security Settings.&lt;/P&gt;&lt;DIV&gt;For Example:&lt;/DIV&gt;&lt;DIV&gt;If Name on Card does Not match the Name submitted we can be notify and decide how to handle. &amp;nbsp;Another example Postal Code don't match.&lt;/DIV&gt;&lt;DIV&gt;which API can support me by this data and what is the requirements??&lt;/DIV&gt;&lt;DIV&gt;thanks,&lt;/DIV&gt;</description>
      <pubDate>Tue, 28 Feb 2012 06:44:11 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-Credit-Card-API-Data/m-p/23681#M12737</guid>
      <dc:creator>stuclasivo</dc:creator>
      <dc:date>2012-02-28T06:44:11Z</dc:date>
    </item>
    <item>
      <title>Re: Authorize.net Credit Card API Data</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-Credit-Card-API-Data/m-p/23697#M12745</link>
      <description>&lt;P&gt;The only way to do that is to process an actual charge, usually $0.00 for VIsa or $0.01 for other card types. You would go into your control panel and set your AVS (Address Verification Service) to decline or report triggered filters for the settings you want to cause a reject (probably everything except Y, since extended zip isn't something a lot of people know), then test for those flags on the response, or just test for failure if you're declining. Note that there is no way to verify the name on the card - credit card companies stopped using that as a security feature quite some time ago. You might look into the CCV (Card Code Verification) settings as well, however.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2012 16:22:23 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-Credit-Card-API-Data/m-p/23697#M12745</guid>
      <dc:creator>TJPride</dc:creator>
      <dc:date>2012-02-28T16:22:23Z</dc:date>
    </item>
  </channel>
</rss>

