<?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 Re: My New Authorize.net API Coldfusion CFC in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/My-New-Authorize-net-API-Coldfusion-CFC/m-p/82781#M52167</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/18439"&gt;@kabutotx&lt;/a&gt;. Do you know what PCI compliance rules may apply if we post credit card authorization information to the API, but don't store it anywhere on our systems? It would be in memory when the form was posted to our servers and then while the transaction processed. Any guidance is appreciated.&lt;/P&gt;</description>
    <pubDate>Thu, 19 May 2022 22:43:06 GMT</pubDate>
    <dc:creator>ericdavis902</dc:creator>
    <dc:date>2022-05-19T22:43:06Z</dc:date>
    <item>
      <title>My New Authorize.net API Coldfusion CFC</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/My-New-Authorize-net-API-Coldfusion-CFC/m-p/70918#M43609</link>
      <description>&lt;P&gt;I created a new Coldfusion CFC that supports Authorize API for payments, CIM, ARB, and Accept Suite.&amp;nbsp; Would love for people to give it a test and give feedback. This was based on TWCreations old&amp;nbsp; AuthNetTools. I updated it for API support and new functions and they donated their code I re-used.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/kabutotx/AuthNetToolsAPI" target="_self"&gt;https://github.com/kabutotx/AuthNetToolsAPI&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Mar 2020 02:00:04 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/My-New-Authorize-net-API-Coldfusion-CFC/m-p/70918#M43609</guid>
      <dc:creator>kabutotx</dc:creator>
      <dc:date>2020-03-05T02:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: My New Authorize.net API Coldfusion CFC</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/My-New-Authorize-net-API-Coldfusion-CFC/m-p/82781#M52167</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/18439"&gt;@kabutotx&lt;/a&gt;. Do you know what PCI compliance rules may apply if we post credit card authorization information to the API, but don't store it anywhere on our systems? It would be in memory when the form was posted to our servers and then while the transaction processed. Any guidance is appreciated.&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 22:43:06 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/My-New-Authorize-net-API-Coldfusion-CFC/m-p/82781#M52167</guid>
      <dc:creator>ericdavis902</dc:creator>
      <dc:date>2022-05-19T22:43:06Z</dc:date>
    </item>
    <item>
      <title>Re: My New Authorize.net API Coldfusion CFC</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/My-New-Authorize-net-API-Coldfusion-CFC/m-p/82782#M52168</link>
      <description>&lt;P&gt;Yes. PCI will apply.&amp;nbsp; The easiest is Accept API which will be only &lt;A href="https://developer.authorize.net/api/reference/features/accept.html" target="_self"&gt;SAQ A&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;If you do your own form I think that would fall under at least SAQ C .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 23:02:20 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/My-New-Authorize-net-API-Coldfusion-CFC/m-p/82782#M52168</guid>
      <dc:creator>kabutotx</dc:creator>
      <dc:date>2022-05-19T23:02:20Z</dc:date>
    </item>
  </channel>
</rss>

