<?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 Desktop Integration with CIM in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Desktop-Integration-with-CIM/m-p/54322#M29326</link>
    <description>&lt;P&gt;I am working with a client whose POS software runs on a desktop platform, not web. Would it still be possible to integrate with the CIM system? Would it be possible to form the XML string by hand and POST it to the authorize.net API URL through an HTTPS socket type of object? My hands are a bit tied here in terms of the language I use because they need it done in a langauage they support, which is not one included in your examples.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it seems like this will work, would I do the authorization posts first, then the creatCustomer/getCustomerInfo type of calls after?&lt;/P&gt;</description>
    <pubDate>Wed, 13 Apr 2016 15:21:33 GMT</pubDate>
    <dc:creator>8Ball</dc:creator>
    <dc:date>2016-04-13T15:21:33Z</dc:date>
    <item>
      <title>Desktop Integration with CIM</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Desktop-Integration-with-CIM/m-p/54322#M29326</link>
      <description>&lt;P&gt;I am working with a client whose POS software runs on a desktop platform, not web. Would it still be possible to integrate with the CIM system? Would it be possible to form the XML string by hand and POST it to the authorize.net API URL through an HTTPS socket type of object? My hands are a bit tied here in terms of the language I use because they need it done in a langauage they support, which is not one included in your examples.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it seems like this will work, would I do the authorization posts first, then the creatCustomer/getCustomerInfo type of calls after?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2016 15:21:33 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Desktop-Integration-with-CIM/m-p/54322#M29326</guid>
      <dc:creator>8Ball</dc:creator>
      <dc:date>2016-04-13T15:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: Desktop Integration with CIM</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Desktop-Integration-with-CIM/m-p/54326#M29330</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/19930"&gt;@8Ball﻿&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Our gateway will work with any application that can send and receive XML requests using our API.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How you sequence your transactions depends on your requirements. &amp;nbsp;For example, you can use &lt;A href="http://developer.authorize.net/api/reference/index.html#payment-transactions-charge-a-credit-card" target="_self"&gt;Create Transaction&lt;/A&gt; to process a payment AND also create a customer profile if the payment was successful.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Richard&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2016 16:44:30 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Desktop-Integration-with-CIM/m-p/54326#M29330</guid>
      <dc:creator>RichardH</dc:creator>
      <dc:date>2016-04-13T16:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: Desktop Integration with CIM</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Desktop-Integration-with-CIM/m-p/54328#M29332</link>
      <description>&lt;P&gt;Richard,&lt;/P&gt;&lt;P&gt;Thank you for your timely response. I guess I am a little confused. When you say "useing our API" do you mean posting information to &lt;A href="https://secure.authorize.net/gateway/transact.dll%29" target="_blank" rel="nofollow"&gt;https://secure.authorize.net/gateway/transact.dll&lt;/A&gt;? If so, can the XML request be posted as a single long string? I am not sure what happens under the hood with many of these built in POST commands, but I can specify my own message/data to post, will posting the raw XML work? Or is there some kind of processing that needs to happen?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2016 18:54:17 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Desktop-Integration-with-CIM/m-p/54328#M29332</guid>
      <dc:creator>8Ball</dc:creator>
      <dc:date>2016-04-13T18:54:17Z</dc:date>
    </item>
    <item>
      <title>Re: Desktop Integration with CIM</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Desktop-Integration-with-CIM/m-p/54329#M29333</link>
      <description>&lt;P&gt;The correct endpoints when using XML are as follows:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sandbox URL: &amp;nbsp;&lt;A href="https://apitest.authorize.net/xml/v1/request.api" target="_blank"&gt;https://apitest.authorize.net/xml/v1/request.api&lt;/A&gt; &amp;nbsp;&lt;/P&gt;
&lt;P&gt;Production URL: &amp;nbsp;&lt;A href="https://api.authorize.net/xml/v1/request.api" target="_blank"&gt;https://api.authorize.net/xml/v1/request.api&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The &lt;A href="http://developer.authorize.net/api/reference/" target="_self"&gt;API Reference&lt;/A&gt; includes a live console where you can test transactions in our sandbox.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Richard&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2016 18:59:28 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Desktop-Integration-with-CIM/m-p/54329#M29333</guid>
      <dc:creator>RichardH</dc:creator>
      <dc:date>2016-04-13T18:59:28Z</dc:date>
    </item>
  </channel>
</rss>

