<?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>Merchant Account Services &#187; Processing Methods</title>
	<atom:link href="http://www.merchant-account-services.org/blog/category/processing-methods/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.merchant-account-services.org/blog</link>
	<description></description>
	<lastBuildDate>Fri, 15 Jan 2010 15:34:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Handling Authorize.Net ARB Subscription Failures</title>
		<link>http://www.merchant-account-services.org/blog/handling-authorizenet-arb-subscription-failures/</link>
		<comments>http://www.merchant-account-services.org/blog/handling-authorizenet-arb-subscription-failures/#comments</comments>
		<pubDate>Thu, 01 May 2008 13:00:33 +0000</pubDate>
		<dc:creator>John Conde</dc:creator>
				<category><![CDATA[Payment Gateways]]></category>
		<category><![CDATA[Authorize.Net]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://www.merchant-account-services.org/blog/handling-authorizenet-arb-subscription-failures/</guid>
		<description><![CDATA[For more on Silent Post see All About Authorize.Net’s Silent Post and Handling Authorize.Net Silent Post with PHP. One common complaint about the Authorize.Net Automated Recurring Billing (ARB) system is that there is no way to handle subscriptions that are declined when processing a future scheduled payment. As it turns out there is a way [...]]]></description>
		<wfw:commentRss>http://www.merchant-account-services.org/blog/handling-authorizenet-arb-subscription-failures/feed/</wfw:commentRss>
		<slash:comments>45</slash:comments>
		</item>
		<item>
		<title>New Article: Integrate the Authorize.Net Recurring Billing API with PHP</title>
		<link>http://www.merchant-account-services.org/blog/new-article-integrate-the-authorizenet-recurring-billing-api-with-php/</link>
		<comments>http://www.merchant-account-services.org/blog/new-article-integrate-the-authorizenet-recurring-billing-api-with-php/#comments</comments>
		<pubDate>Tue, 26 Feb 2008 13:30:15 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Payment Gateways]]></category>
		<category><![CDATA[Programmers Toolbox]]></category>
		<category><![CDATA[Site News]]></category>

		<guid isPermaLink="false">http://www.merchant-account-services.org/blog/new-article-integrate-the-authorizenet-recurring-billing-api-with-php/</guid>
		<description><![CDATA[We are happy to announce a new article has been published today. Integrate the Authorize.Net Recurring Billing API with PHP is a follow up to our article Integrate the Authorize.net Payment Gateway with PHP. This new article expands upon our original article by explaining how the Authorize.Net recurring billing API works and walks developers through [...]]]></description>
		<wfw:commentRss>http://www.merchant-account-services.org/blog/new-article-integrate-the-authorizenet-recurring-billing-api-with-php/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Authorize.Net Releases New Customer Information Manager API</title>
		<link>http://www.merchant-account-services.org/blog/authorizenet-releases-new-customer-information-manager-api/</link>
		<comments>http://www.merchant-account-services.org/blog/authorizenet-releases-new-customer-information-manager-api/#comments</comments>
		<pubDate>Thu, 07 Feb 2008 18:09:53 +0000</pubDate>
		<dc:creator>John Conde</dc:creator>
				<category><![CDATA[Payment Gateways]]></category>
		<category><![CDATA[Programmers Toolbox]]></category>

		<guid isPermaLink="false">http://www.merchant-account-services.org/blog/authorizenet-releases-new-customer-information-manager-api/</guid>
		<description><![CDATA[Recently Authorize.Net released their API for their new Customer Information Manager (CIM) feature of their payment gateway. This feature is a boon for merchants who wish to store credit card information or do recurring billing in different amounts or varied schedules. The main features of this new service are: PCI Compliance Remove the specter of [...]]]></description>
		<wfw:commentRss>http://www.merchant-account-services.org/blog/authorizenet-releases-new-customer-information-manager-api/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Authorize.Net Removes Three Year Limit on Recurring Subscriptions</title>
		<link>http://www.merchant-account-services.org/blog/authorizenet-removes-three-year-limit-on-recurring-subscriptions/</link>
		<comments>http://www.merchant-account-services.org/blog/authorizenet-removes-three-year-limit-on-recurring-subscriptions/#comments</comments>
		<pubDate>Sun, 30 Sep 2007 18:03:06 +0000</pubDate>
		<dc:creator>Sara</dc:creator>
				<category><![CDATA[Payment Gateways]]></category>
		<category><![CDATA[Programmers Toolbox]]></category>

		<guid isPermaLink="false">http://www.merchant-account-services.org/blog/authorizenet-removes-three-year-limit-on-recurring-subscriptions/</guid>
		<description><![CDATA[One this that bothered me about the Authorize.Net ARB subscription functionality is that there was a three year limit on subscriptions. In other words, all subscriptions would expire at most three years and you could not set it to be longer. This was true whether you used their ARB API or set the subscription up [...]]]></description>
		<wfw:commentRss>http://www.merchant-account-services.org/blog/authorizenet-removes-three-year-limit-on-recurring-subscriptions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is a Payment Gateway?</title>
		<link>http://www.merchant-account-services.org/blog/what-is-a-payment-gateway/</link>
		<comments>http://www.merchant-account-services.org/blog/what-is-a-payment-gateway/#comments</comments>
		<pubDate>Mon, 09 Jul 2007 17:03:46 +0000</pubDate>
		<dc:creator>John Conde</dc:creator>
				<category><![CDATA[Payment Gateways]]></category>

		<guid isPermaLink="false">http://www.merchant-account-services.org/blog/what-is-a-payment-gateway/</guid>
		<description><![CDATA[A common question in communities around the Web is, &#8220;what exactly is a payment gateway&#8221;? According to Wikipedia: A payment gateway is an e-commerce application service provider service that authorizes payments for e-businesses, online retailers, bricks and clicks, or traditional brick and mortar. It is the equivalent of a physical POS (Point-of-sale) terminal located in [...]]]></description>
		<wfw:commentRss>http://www.merchant-account-services.org/blog/what-is-a-payment-gateway/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Authorize.Net Drops the Ball on International AVS</title>
		<link>http://www.merchant-account-services.org/blog/authorizenet-drops-the-ball-on-international-avs/</link>
		<comments>http://www.merchant-account-services.org/blog/authorizenet-drops-the-ball-on-international-avs/#comments</comments>
		<pubDate>Tue, 12 Jun 2007 19:53:39 +0000</pubDate>
		<dc:creator>John Conde</dc:creator>
				<category><![CDATA[Payment Gateways]]></category>

		<guid isPermaLink="false">http://www.merchant-account-services.org/blog/authorizenet-drops-the-ball-on-international-avs/</guid>
		<description><![CDATA[For merchants who use Authorize.Net to process their online orders if you accept orders from Canada and the UK you may be losing sales due to a flaw in how Authorize.Net handles Address Verification (AVS). (Read the blog entry The AVS Game to learn more about AVS). Apparently if the card issuing bank for a [...]]]></description>
		<wfw:commentRss>http://www.merchant-account-services.org/blog/authorizenet-drops-the-ball-on-international-avs/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Authorize.Net adds CAPTCHA to SIM Payment Form</title>
		<link>http://www.merchant-account-services.org/blog/authorizenet-adds-captcha-to-sim-payment-form/</link>
		<comments>http://www.merchant-account-services.org/blog/authorizenet-adds-captcha-to-sim-payment-form/#comments</comments>
		<pubDate>Sat, 02 Jun 2007 01:09:29 +0000</pubDate>
		<dc:creator>John Conde</dc:creator>
				<category><![CDATA[Payment Gateways]]></category>

		<guid isPermaLink="false">http://www.merchant-account-services.org/blog/authorizenet-adds-captcha-to-sim-payment-form/</guid>
		<description><![CDATA[Authorize.Net announced today that they will add a CAPTCHA security image to its Simple Integration Method (SIM) remotely hosted payment form. This security image is designed to verify the party submitting the form is human and not an automated bot. You can see a demo of the new CAPTCHA on the Authorize.Net website. This option [...]]]></description>
		<wfw:commentRss>http://www.merchant-account-services.org/blog/authorizenet-adds-captcha-to-sim-payment-form/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building a Recurring Billing System Part 4: Expiring Credit Cards</title>
		<link>http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-4-expiring-credit-cards/</link>
		<comments>http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-4-expiring-credit-cards/#comments</comments>
		<pubDate>Thu, 10 May 2007 13:00:30 +0000</pubDate>
		<dc:creator>John Conde</dc:creator>
				<category><![CDATA[Payment Gateways]]></category>
		<category><![CDATA[Programmers Toolbox]]></category>

		<guid isPermaLink="false">http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-4-expiring-credit-cards/</guid>
		<description><![CDATA[As we saw in our previous posts Building a Recurring Billing System and Building a Recurring Billing System Part 2: Storing Information, and Building a Recurring Billing System Part 3: Updating the Credit Card we can combine the Authorize.Net ARB API to build a powerful subscription system. In part three we discussed how we would [...]]]></description>
		<wfw:commentRss>http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-4-expiring-credit-cards/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Building a Recurring Billing System Part 3: Updating the Credit Card</title>
		<link>http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-3-updating-the-credit-card/</link>
		<comments>http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-3-updating-the-credit-card/#comments</comments>
		<pubDate>Mon, 07 May 2007 13:00:33 +0000</pubDate>
		<dc:creator>John Conde</dc:creator>
				<category><![CDATA[Payment Gateways]]></category>
		<category><![CDATA[Programmers Toolbox]]></category>

		<guid isPermaLink="false">http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-3-updating-the-credit-card/</guid>
		<description><![CDATA[As we saw in our previous posts Building a Recurring Billing System and Building a Recurring Billing System Part 2: Storing Information we can combine the Authorize.Net ARB API to build a powerful subscription system. In part two we discussed what information we needed to store to make our system work effectively. Now we will [...]]]></description>
		<wfw:commentRss>http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-3-updating-the-credit-card/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Building a Recurring Billing System Part 2: Storing Information</title>
		<link>http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-2-storing-information/</link>
		<comments>http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-2-storing-information/#comments</comments>
		<pubDate>Fri, 04 May 2007 13:00:19 +0000</pubDate>
		<dc:creator>John Conde</dc:creator>
				<category><![CDATA[Payment Gateways]]></category>
		<category><![CDATA[Programmers Toolbox]]></category>

		<guid isPermaLink="false">http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-2-storing-information/</guid>
		<description><![CDATA[As we saw in our previous post Building a Recurring Billing System, we will need to be responsible for providing a system to effectively manage our customers&#8217; recurring subscriptions. Authorize.Net can take care of the payment processing for us as well as the scheduling of each payment. But to take our level of management and [...]]]></description>
		<wfw:commentRss>http://www.merchant-account-services.org/blog/building-a-recurring-billing-system-part-2-storing-information/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

