<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>2Checkout.com &#187; CGI</title>
	<atom:link href="http://www.2checkout.com/blog/tag/cgi/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.2checkout.com</link>
	<description>merchant account / credit card processing alternative</description>
	<lastBuildDate>Thu, 09 Feb 2012 15:02:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Do you have an API that we can use to integrate 2checkout into our custom billing application?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/3rd-party-carts/do-you-have-an-api-that-we-can-use-to-integrate-2checkout-into-our-custom-billing-application/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/3rd-party-carts/do-you-have-an-api-that-we-can-use-to-integrate-2checkout-into-our-custom-billing-application/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[3rd Party Carts]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[CGI]]></category>
		<category><![CDATA[integrate]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/do-you-have-an-api-that-we-can-use-to-integrate-2checkout-into-our-custom-billing-application/</guid>
		<description><![CDATA[An API (Application Programming Interface) is used in many different contexts in this industry. 2Checkout offers a full featured Back Office API that provides suppliers and 3rd party developers with the ability to automate account, product and order management processes. Using the 2Checkout Back Office API along with the Instant Notification Service (INS) alleviates the [...]]]></description>
			<content:encoded><![CDATA[<p>An API (Application Programming Interface) is used in many different contexts in this industry. 2Checkout offers a full featured Back Office API that provides suppliers and 3rd party developers with the ability to automate account, product and order management processes. Using the 2Checkout Back Office API along with the <a href="https://www.2checkout.com/static/va/documentation/INS/index.html">Instant Notification Service (INS)</a> alleviates the necessity of logging into the standard GUI account interface on a day-to-day basis.</p>
<p>The current supported methods offered by our API allow the user to retrieve:</p>
<ul>
<li>Detailed account information including both company and contact information.</li>
<li>Detailed payment information for both pending and past payments.</li>
<li>Detailed product information including product options and coupons.</li>
<li>Detailed sales information supporting both simple and complex search queries.</li>
</ul>
<p>The current supported update calls allow the user to:</p>
<ul>
<li>Create, edit and delete products, product options and coupons.</li>
<li>Refund sales by both invoice and individual line item.</li>
<li>Stop recurring line items.</li>
<li>Reauthorize and mark sales as shipped.</li>
<li>Add order comments and send comments to the customer.</li>
</ul>
<p>If you are interested, please review our <a href="http://www.2checkout.com/documentation/api/">Back Office API documentation</a> for a full specification on each supported method and instructions on how to create an API username.</p>
<p>For site integration with 2Checkout, we offer a Common Gateway Interface (CGI). This means a site will need to contain an HTML form or link with cgi parameters appended which passes the correct parameters (and the customer) to our site for checkout. Passing in the Proper Parameters will result in the customer going through the rest of our checkout process (such as entering their credit card information), and after verification, a successful sale.</p>
<p>A site/shopping cart can pass orders into our purchase routine by using <strong>one</strong> of our supported parameter sets listed below.</p>
<ul>
<li><a href="http://www.2checkout.com/blog/knowledge-base/suppliers/tech-support/using-the-plug-n-play-cart/what-are-the-parameters-for-the-plug-n-play-cart">Plug n Play parameters</a></li>
<li><a href="http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/3rd-party-carts/parameter-sets/pass-through-product-parameter-set">Pass Through Products parameters</a></li>
<li><a href="http://www.2checkout.com/blog/knowledge-base/suppliers/tech-support/3rd-party-carts/parameter-sets/does-your-system-have-its-own-parameters-if-so-what-are-they">Third party cart parameters</a></li>
<li><a href="http://www.2checkout.com/blog/knowledge-base/suppliers/tech-support/3rd-party-carts/parameter-sets/does-your-system-support-authorizenet-parameters-if-so-what-are-they">Authorize.net parameters</a></li>
</ul>
<p><strong><em>When using a third party cart parameter set you will need to make sure that you implement the Product Identification parameters listed in the articles above. </em></strong></p>
<p>If you would like to test your integration of these parameter sets, please try using the testing tools available in our <a href="http://developers.2checkout.com/">developers area</a>.</p>
<p><em>This article was updated January 27, 2010 to include the new Back Office API information. </em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/3rd-party-carts/do-you-have-an-api-that-we-can-use-to-integrate-2checkout-into-our-custom-billing-application/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

