<?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: CHOOSING API in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/CHOOSING-API/m-p/19282#M10633</link>
    <description>&lt;P&gt;None of the API's involve actually storing the data locally. AIM, CIM, and ARB do involve credit card data being passed through your site, so if you don't want to get into that, you're left with DPM, SIM, and hosted CIM. You don't need hosted CIM for single payments, so it's pretty much a choice between DPM and SIM, with DPM giving you more control over the look and having the payment form display on your site (though it submits to Authorize.net and no credit card data passes through your site), and SIM requiring less work to implement and no SSL (technically, DPM doesn't require SSL either, but nobody's going to fill out credit card information on an http:// URL).&lt;/P&gt;</description>
    <pubDate>Thu, 24 Nov 2011 08:21:34 GMT</pubDate>
    <dc:creator>TJPride</dc:creator>
    <dc:date>2011-11-24T08:21:34Z</dc:date>
    <item>
      <title>CHOOSING API</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/CHOOSING-API/m-p/19158#M10611</link>
      <description>&lt;P&gt;In my legal services business, I invoice my clients via email. I want to be able to link to my site from the email, and be able to pay from there. I do not want to store any of my customers' data locally. Which API would be best?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 20 Nov 2011 19:57:57 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/CHOOSING-API/m-p/19158#M10611</guid>
      <dc:creator>marcjaco</dc:creator>
      <dc:date>2011-11-20T19:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: CHOOSING API</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/CHOOSING-API/m-p/19270#M10627</link>
      <description>&lt;P&gt;Server Integration Method (SIM)&amp;nbsp;is the API that you will want to use if you don't want to touch the customer's data at all.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2011 21:37:28 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/CHOOSING-API/m-p/19270#M10627</guid>
      <dc:creator>Trevor</dc:creator>
      <dc:date>2011-11-23T21:37:28Z</dc:date>
    </item>
    <item>
      <title>Re: CHOOSING API</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/CHOOSING-API/m-p/19282#M10633</link>
      <description>&lt;P&gt;None of the API's involve actually storing the data locally. AIM, CIM, and ARB do involve credit card data being passed through your site, so if you don't want to get into that, you're left with DPM, SIM, and hosted CIM. You don't need hosted CIM for single payments, so it's pretty much a choice between DPM and SIM, with DPM giving you more control over the look and having the payment form display on your site (though it submits to Authorize.net and no credit card data passes through your site), and SIM requiring less work to implement and no SSL (technically, DPM doesn't require SSL either, but nobody's going to fill out credit card information on an http:// URL).&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2011 08:21:34 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/CHOOSING-API/m-p/19282#M10633</guid>
      <dc:creator>TJPride</dc:creator>
      <dc:date>2011-11-24T08:21:34Z</dc:date>
    </item>
  </channel>
</rss>

