<?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>Recurly Blog &#187; ecommerce</title>
	<atom:link href="http://blog.recurly.com/tag/ecommerce/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.recurly.com</link>
	<description>Super Simple Subscriptions</description>
	<lastBuildDate>Tue, 24 Jan 2012 17:01:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<atom:link rel='hub' href='http://blog.recurly.com/?pushpress=hub'/>
		<item>
		<title>How many companies does it take to process a credit card?</title>
		<link>http://blog.recurly.com/2009/08/how-many-companies-does-it-take-to-process-a-credit-card/</link>
		<comments>http://blog.recurly.com/2009/08/how-many-companies-does-it-take-to-process-a-credit-card/#comments</comments>
		<pubDate>Wed, 12 Aug 2009 05:49:52 +0000</pubDate>
		<dc:creator>Isaac Hall</dc:creator>
				<category><![CDATA[Merchant Accounts]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[ecommerce]]></category>
		<category><![CDATA[merchant bank]]></category>
		<category><![CDATA[merchant service provider]]></category>
		<category><![CDATA[payment gateway]]></category>

		<guid isPermaLink="false">http://blog.recurly.com/?p=18</guid>
		<description><![CDATA[If you're launching a new site and want to accept credit cards, you'll soon learn how many companies are involved in every transaction. And, once you run into the first few declined credit cards, you'll learn about a few companies that didn't seem to be there before.  This article describes the companies that are involved in every credit card transaction.]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re launching a new site and want to accept credit cards, you&#8217;ll soon learn how many companies are involved in every transaction.  And, once you run into the first few declined credit cards, you&#8217;ll learn about a few companies that didn&#8217;t seem to be there before.  Let&#8217;s dive in.</p>
<p>When you enter your credit card on a website, it sends the credit card information over an encrypted channel to a <strong>payment gateway</strong>.  The payment gateway&#8217;s primary responsibility is to authorize payments and communicate with the <strong>merchant&#8217;s bank</strong>. Banks communicate with the payment gateway using a proprietary network and/or protocol.  Since your website is not processing billions of transactions a month, your bank does not want to integrate with you.  So, the payment gateway effectively becomes the middle man.</p>
<p>However, if the merchant bank is small (compared to a bank like CitiBank, Chase, or Bank of America), the merchant bank likely uses another company to communicate with the payment gateway.  This middle man is known as a <strong>merchant service provider</strong>.  Unless you run into some very tricky problems authorizing transactions, you are not likely to know this company exists.  In most cases, the merchant service provider does their job and stays completely in the background.</p>
<p>Now that the merchant bank has the transaction information, it routes the details to the customer&#8217;s <strong>credit card company</strong> &#8212; Visa, MasterCard, Discover, American Express, etc.  Since Discover and American Express are usually issued directly to a customer (and not through an issuing bank), these card companies return an authorization or declined message.  Otherwise, the credit card company must now connect to the <strong>customer&#8217;s credit card issuing bank</strong>.  Finally, the customer&#8217;s bank can authorize or decline the transaction and the message routes all the way back to the originating e-commerce site.  On average, the whole authorization process can take 2-3 seconds due to all the parties involved in the transaction.</p>
<p>To summaries the authorization flow, the credit card information goes from the <strong>user&#8217;s browser</strong> to the <strong>e-commerce website</strong> to the <strong>payment gateway</strong> (optionally) to the <strong>merchant service provider</strong> to the <strong>merchant bank</strong> to the <strong>credit card company</strong> to the <strong>user&#8217;s bank</strong> for approval.</p>
<p>At the end of the day, the merchant&#8217;s bank must settle the transactions (assuming the funds were captured, or approved for transfer).  The merchant bank then works with the credit card company and users&#8217; banks to transfer the funds.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.recurly.com/2009/08/how-many-companies-does-it-take-to-process-a-credit-card/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced)
Content Delivery Network via N/A

Served from: blog.recurly.com @ 2012-02-05 14:32:09 -->
