<?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; credit card</title>
	<atom:link href="http://blog.recurly.com/tag/credit-card/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>Announcing The Recurly Payment Gateway and New Pricing</title>
		<link>http://blog.recurly.com/2011/11/announcing-the-recurly-payment-gateway-and-new-pricing/</link>
		<comments>http://blog.recurly.com/2011/11/announcing-the-recurly-payment-gateway-and-new-pricing/#comments</comments>
		<pubDate>Wed, 30 Nov 2011 18:36:51 +0000</pubDate>
		<dc:creator>Dan Burkhart</dc:creator>
				<category><![CDATA[Billing]]></category>
		<category><![CDATA[Merchant Accounts]]></category>
		<category><![CDATA[New Features]]></category>
		<category><![CDATA[Payment Gateway]]></category>
		<category><![CDATA[Recurly]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[optimization]]></category>
		<category><![CDATA[PCI-DSS]]></category>
		<category><![CDATA[recurring billing]]></category>
		<category><![CDATA[renewal]]></category>
		<category><![CDATA[retention rate]]></category>
		<category><![CDATA[Saas]]></category>
		<category><![CDATA[subscription]]></category>

		<guid isPermaLink="false">http://blog.recurly.com/?p=1674</guid>
		<description><![CDATA[Over the past two years, we have become increasingly aware that payment gateways have been designed to serve traditional e-commerce (one-time transactions) as their primary use case. In many instances, the features and capabilities needed to process payments on a recurring basis are sorely lacking. We have viewed this as both a challenge and an [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.recurly.com/2011/11/announcing-the-recurly-payment-gateway-and-new-pricing/recurly-gateway-icon/"   rel="attachment wp-att-1718" ><img class="alignright size-full wp-image-1718" title="Recurly Gateway Icon" src="http://blog.recurly.com/wp-content/uploads/2011/11/Recurly-Gateway-Icon.png" style="border:0;padding-left:20px;" alt="Recurly Payment Gateway" width="150" height="147" /></a>Over the past two years, we have become increasingly aware that payment gateways have been designed to serve traditional e-commerce (one-time transactions) as their primary use case. In many instances, the features and capabilities needed to process payments on a recurring basis are sorely lacking. <strong>We have viewed this as both a challenge and an opportunity. </strong></p>
<h2>The Recurly Payment Gateway</h2>
<p>We are proud to announce that we have built the first payment gateway designed to support recurring billing as the primary use-case. This means that we access rich error messages from the payment processor to optimize many different common credit card decline types. As we have communicated recently, <a href="http://blog.recurly.com/2011/11/subscriber-economics-why-customer-retention-matters/" title="Subscriber Economics: Why Customer Retention MATTERS"   target="_blank" >credit card declines lead to painful customer churn</a>, which is one of the most important and sensitive metrics for any subscription business.</p>
<p>During beta testing, our trials demonstrated a range of <strong>10-27% incremental lift in recovered invoices</strong> for a variety of different kinds of businesses (Both B2B and B2C).</p>
<p><strong>The new <a href="http://recurly.com/gateway" title="Recurly Payment Gateway"   target="_blank" >Recurly Payment Gateway</a> is now bundled with the Recurly service</strong>. In addition, we are adding critical customer retention reports so that our customers can track the long term trends of their customers by cohort month, and by subscription plan.</p>
<h2>New Recurly Pricing</h2>
<p>As of today&#8217;s announcement, <a href="http://recurly.com/pricing" title="Recurly Pricing"   target="_blank" >Recurly&#8217;s pricing</a> structure has also changed.</p>
<p>We now charge a simple <strong>1.25% and $0.10 per transaction per month</strong>, with a <strong>$69 monthly minimum</strong> (as there has been for some time).</p>
<h2>Grandfathered Pricing</h2>
<p>Existing Recurly &#8216;live production&#8217; customers will remain on their original pricing unless they choose to take advantage of the Recurly Payment Gateway, or any of our premium features &#8211; such as Retention Reports, Salesforce Integration, PayPal Payments or Multi-Currency support. We will continue to support other payment gateways to offer the broadest choice to our customers, but the cost of other payment gateways are not inclusive with our new pricing.</p>
<h2>No Merchant Account, No Problem</h2>
<p>All you need to take advantage of the Recurly service is your own merchant bank account. If you don&#8217;t have one already, we can help you apply and get set up with an account offering extremely competitive rates.</p>
<p>We&#8217;re excited about our role in helping companies to optimize their subscriber renewal rates. Our ambition is to make the Recurly service a distinct competitive advantage for our customers.</p>
<p>If you have any questions about the Recurly service, or the Recurly Payment Gateway, please contact sales@recurly.com.</p>
<p>We can help.</p>
<p>Cheers,<br />
The Recurly Team.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.recurly.com/2011/11/announcing-the-recurly-payment-gateway-and-new-pricing/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>How To Reduce Customer Churn With Better Payment Processing</title>
		<link>http://blog.recurly.com/2011/07/how-to-reduce-customer-churn-with-better-payment-processing/</link>
		<comments>http://blog.recurly.com/2011/07/how-to-reduce-customer-churn-with-better-payment-processing/#comments</comments>
		<pubDate>Wed, 13 Jul 2011 18:53:02 +0000</pubDate>
		<dc:creator>Dan Burkhart</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Billing]]></category>
		<category><![CDATA[Payment Gateway]]></category>
		<category><![CDATA[Recurly]]></category>
		<category><![CDATA[Subscriptions]]></category>
		<category><![CDATA[churn]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[LTV]]></category>
		<category><![CDATA[metrics]]></category>
		<category><![CDATA[recurring]]></category>
		<category><![CDATA[renewals]]></category>
		<category><![CDATA[retention]]></category>
		<category><![CDATA[subscribers]]></category>
		<category><![CDATA[subscription]]></category>

		<guid isPermaLink="false">http://blog.recurly.com/?p=1463</guid>
		<description><![CDATA[Q: Who in your company is responsible for customer churn? If you had to pause and ponder the answer, or if you felt that it was everybody’s responsibility…then you’re not alone. When I was with eBay, it was far easier for marketing teams to focus on acquiring new customers than to identify an effective means [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.recurly.com/2011/07/how-to-reduce-customer-churn-with-better-payment-processing/credit_card_churn_recurly/"   rel="attachment wp-att-1480" ><img src="http://blog.recurly.com/wp-content/uploads/2011/07/Credit_Card_Churn_Recurly.png" style="border: 0px;" alt="Remediate Credit Card Errors and Declines" title="Credit_Card_Churn_Recurly" width="198" height="145" class="alignright size-full wp-image-1480" /></a><strong>Q: Who in your company is responsible for customer churn?</strong></p>
<p>If you had to pause and ponder the answer, or if you felt that it was everybody’s responsibility…then you’re not alone.<br />
<br />When I was with eBay, it was far easier for marketing teams to focus on acquiring new customers than to identify an effective means to address customer churn. Customer churn is a &#8216;wet bar of soap&#8217; problem, and therefore always seems to be ‘somebody else’s responsibility’, because it is a difficult problem to attack.</p>
<p><strong>Consider these factoids:</strong></p>
<li>“It costs 6-7 times more to acquire a new customer than to retain an existing one”<br />
- <em>Bain &#038; Company</em></li>
<li>“A 2% increase in customer retention has the same effect as decreasing costs by 10%”<br />
- <em>Edge of Chaos, Emmet Murphy &#038; Mark Murphy</em></li>
<li>&#8220;55% of current marketing spend is on new customer acquisition. 33% of current marketing spend is on brand awareness. 12% of current marketing spend is on customer retention.&#8221;<br />
 – <em>McKinsey</em></li>
<p></p>
<h2><strong>Most Executives Have No Idea What Drives Their Churn</strong></h2>
<p>Identifying the drivers of customer churn can be extremely difficult. Additionally, customer acquisition is infinitely more fun for marketers than retention marketing. [It is much more interesting and profitable for Ad Agencies to focus on driving brand awareness, positioning and expanding appeal than driving retention metrics.]</p>
<p>In our business of providing subscription billing, we frequently discuss the topic of customer retention and churn with our customers.  Through this, we’ve learned that executives generally have a clear sense for their own customer retention and churn metrics, but they have very little idea what is driving it. Most will cite Net Promoter Scores (NPS), or customer satisfaction rates as the broad and diffuse driver of customer churn, but they have difficulty pinning down any single reason why their customers leave them.  </p>
<h2><strong>Subscription Businesses &#8211; Plug That Leaky Bucket!</strong></h2>
<p>For subscription businesses, customer retention is driven by renewal rates. Improving renewal rates extends the ‘T’ in Lifetime Value (LTV), and this is an extremely sensitive variable in the overall calculation.  The enemy of the renewal rate is your churn rate.</p>
<p><strong>Q: What drives customer churn in subscription-based businesses? </strong> </p>
<p><strong>A:</strong> [Assuming your product/service delivers good value] If you are a subscription-based business, the most immediately addressable, passive culprit is: <em><strong>Credit card errors and declines.</strong>  </em></p>
<h2><strong>What Can You Do? </strong></h2>
<p><strong>Examine Your Credit Card Decline Logs!</strong></p>
<li>Ask your billing department to give you an output of the most frequently encountered error types being received by your payment gateway. [Every payment gateway is different, so you will have to locate the error code definitions for your particular payment gateway]</li>
<li>Sort the error codes so that you can rank errors in order of frequency.</li>
<li>Bucket them into ‘Hard Declines’ and ‘Soft Declines’ (‘Hard Decline’ meaning that the card has been declined because it has been reported lost or stolen). </li>
<li>Focus on identifying the most common ‘Soft Declines’, which are frequently – Expired Card, or ‘AVS Mis-match’ errors, etc.</li>
<p>Many commonly experienced credit card errors can be successfully remediated. Results will vary depending on your payment gateway/payment processor combination, but by beginning with your credit card error logs, and working backwards towards the solve, you will find that you can dramatically reduce your customer churn with proper error and decline remediation. However, if your customer credit cards are stored within a payment gateway, you will be limited in your ability to remediate many common errors.</p>
<p>If you have questions about Recurly’s standard error handling practices, and how we might help your business reduce customer churn, please contact us.  </p>
<p>Email sales ‘at’ recurly.com or call 415-800-2042.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.recurly.com/2011/07/how-to-reduce-customer-churn-with-better-payment-processing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>When to collect credit card numbers</title>
		<link>http://blog.recurly.com/2010/03/when-to-collect-credit-card-numbers/</link>
		<comments>http://blog.recurly.com/2010/03/when-to-collect-credit-card-numbers/#comments</comments>
		<pubDate>Sun, 28 Mar 2010 17:00:10 +0000</pubDate>
		<dc:creator>Isaac Hall</dc:creator>
				<category><![CDATA[Billing]]></category>
		<category><![CDATA[Subscriptions]]></category>
		<category><![CDATA[conversion]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[freemium]]></category>
		<category><![CDATA[trial]]></category>

		<guid isPermaLink="false">http://blog.recurly.com/?p=236</guid>
		<description><![CDATA[This question recently came up at the Freemium Summit on a pricing panel where I spoke; if you are offering a trial or a freemium service, when should you ask your users for a credit card number?  Asking for a credit card number is a significant hurdle for most people.]]></description>
			<content:encoded><![CDATA[<p>This question recently came up at the Freemium Summit on a pricing panel where I spoke; if you are offering a trial or a freemium service, when should you ask your users for a credit card number?</p>
<p>Asking for a credit card number is a significant hurdle for most people.  High fall off rates are to be expected.  But once someone gives you a card number and starts a trial, they are more likely to convert to a paid subscriber at the end of the trial.  So, if you are optimizing for your conversion numbers from trial to paid, then collect the credit card at the beginning of the trial.</p>
<p>If you offer a trial period and require your users to upgrade before the end of the trial, you will get more people in the door and trying your service.  However, it&#8217;s very difficult to get someone to come back before the end of the trial to enter their card number.  At least the number of total users will be much higher; use this as an opportunity to collect more feedback from your free users, especially the ones that declined to upgrade.</p>
<p>If you are able to offer your users an indefinite, free version, then you can wait to collect the credit card number when the user is ready to upgrade and convert to a paid subscriber.  You benefit from getting the most people in the door and will have the most opportunities to ask the user to consider upgrading.</p>
<p>At the end of the day, you need to factor in the costs associated with the free trial, the viral-ity of your product, and the likeliness of a conversion when deciding when to collect their credit card number.  You&#8217;ll get the highest retention rate when you can reach the customer the most (while providing value, not annoyance).</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.recurly.com/2010/03/when-to-collect-credit-card-numbers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lessons learned in online subscription billing</title>
		<link>http://blog.recurly.com/2010/01/lessons-learned-in-online-subscription-billing/</link>
		<comments>http://blog.recurly.com/2010/01/lessons-learned-in-online-subscription-billing/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 19:35:32 +0000</pubDate>
		<dc:creator>Isaac Hall</dc:creator>
				<category><![CDATA[Billing]]></category>
		<category><![CDATA[Merchant Accounts]]></category>
		<category><![CDATA[address verification]]></category>
		<category><![CDATA[billing support]]></category>
		<category><![CDATA[card authorization]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[expiration dates]]></category>
		<category><![CDATA[merchant account]]></category>
		<category><![CDATA[payment gateway]]></category>
		<category><![CDATA[pricing]]></category>
		<category><![CDATA[subscription]]></category>

		<guid isPermaLink="false">http://blog.recurly.com/?p=89</guid>
		<description><![CDATA[Pivotal Labs recently invited Recurly to present a TechTalk to a room of developers. Developers are smart people and can quickly figure out how to run credit card transactions using the numerous payment gateway APIs out there. So, we decided to a range of topics that you won't learn from reading documentation -- advice you'll only learn from experience.]]></description>
			<content:encoded><![CDATA[<p>Pivotal Labs recently invited Recurly to present a TechTalk to a room of developers.  Developers are smart people and can quickly figure out how to run credit card transactions using the numerous payment gateway APIs out there.  So, we decided to present a range of topics that you won&#8217;t learn from reading documentation &#8212; advice you&#8217;ll only learn from experience.</p>
<p>In the next several weeks, the TechTalk video should become available.  Until then, let me share a few of the key points with you.</p>
<h2>The Basics: How a Payment is Routed</h2>
<p>The credit card network is a crazy network in and of itself &#8212; lots of banks, credit card networks, and payment gateways &amp; they all need to talk to eachother.  That&#8217;s where your <strong>payment gateway</strong> comes in; your site communicates with the gateway and the gateway routes the credit card transaction to the right credit card company (who in turn routes it to the customer&#8217;s bank).  In the end, there&#8217;s about 5-6 hops before an authorization is made &#8212; see our article <a href="http://blog.recurly.com/2009/08/how-many-companies-does-it-take-to-process-a-credit-card/"   >How many companies does it take to process a credit card? </a>for more information.</p>
<p>In addition to a payment gateway, you will need a <strong>merchant account</strong>.  The merchant account is best described as a special checking account for your business.  This is where all the money you collect from your subscribers will be deposited.  The payment gateway, through the credit card interchange network, coordinates withdrawing money from the customers bank account and deposits these funds in your merchant account.</p>
<h2>Getting a Merchant Account</h2>
<p>I think of merchant accounts as special checking accounts because they really are special.  Special as in time consuming to open and full of headaches.  When you collect money via credit cards, the transaction doesn&#8217;t end when the money is deposited in your account.  You can be liable for that money for months after the transaction is over because the credit cards want to protect the consumer. For example, if you sell $1 million of goods but then go out of business before you deliver those goods those consumers will ask the credit cards for their money back and all of a sudden you better have $1 million still in your merchant account.</p>
<p>If you&#8217;re working a side project, or your business is going to scale up slowly, then I don&#8217;t want you to waste much time on opening up a merchant account.  Instead, you should look at using a service like PayPal Website Payments Pro &#8212; it combines a merchant account and payment gateway in one, and is easier to apply for.  But if you&#8217;re incorporated and this is your revenue stream, you should open a merchant account with a proper bank.  And, you should budget about a month for the full process of opening a merchant account and getting the credit card agreements in place.</p>
<p>For internet start-ups in the San Francisco area, we strongly recommend <a href="http://www.svb.com/"   >Silicon Valley Bank</a> for merchant accounts.  They understand start-ups like nobody else.  Recurly spent a month trying to open a merchant account with Bank of America.  Ultimately, B of A denied us because they don&#8217;t understand e-commerce.  This is pretty common among traditional brick-and-mortar banks.</p>
<h2>Payment Gateways</h2>
<p>Not every bank (merchant account) will work with every payment gateway.  If there&#8217;s a gateway you really want to use, make sure it works with your bank first.  Along those same lines, not all integration is equal.  Some banks have first class integration with some payment gateways.  When a bank has a strong integration, you&#8217;ll get access to your money faster, possibly better transaction rates, and better error messages.</p>
<p>One word of advice, be careful signing up for your payment gateway through your bank&#8217;s reseller program.  When your bank resells a payment gateway account, you cannot keep your gateway and switch merchant accounts!  This is so incredibly important.  If you store your credit cards with your payment gateway and your bank decides to close your account for any number of reasons, you no longer have access to your credit card information.  It&#8217;s totally not worth the $200 savings off the payment gateway setup fee.  Seriously, this happened to me and nearly killed the company&#8217;s revenue.</p>
<p>If you&#8217;re looking for a gateway that understand technology well, take a look at <a href="http://www.braintreepaymentsolutions.com/"   >Braintree Payment Solutions</a>.</p>
<h2>Maximizing Acceptance Rates</h2>
<h3>Address Verification</h3>
<p>Address Verification (AVS) is old school.  Perhaps it works differently across different payment gateways but my experience with Authorize.Net&#8217;s AVS suggests that this is old school 1960&#8242;s string matching technology.  <strong>Zip code validation only works reliably inside the US &#8212; it almost always fails on alpha characters.</strong> So, if you accept international payments, make sure your AVS will succeed on street address matches OR zip code matches, if the customer&#8217;s bank supports AVS.  That setting will help you minimize fraud and maximize acceptance rates.</p>
<p>If you&#8217;re only conducting business in the US, you can turn up AVS more if you like.  This advice is critical if you want to accept international transactions and minimize headaches.</p>
<h3>Expiration Dates</h3>
<p>Here&#8217;s an <strong>industry secret </strong>&#8211; expiration dates usually don&#8217;t matter as long as they&#8217;re in the future.  Several years ago, the credit card companies and utility companies came to an understanding about expiration dates &#8212; it&#8217;s much easier to setup auto-pay for recurring payments if the expiration date doesn&#8217;t matter.  The banks understand that if your card is stolen, they can just change the number &#8212; there&#8217;s no point in having it stop working because of an expiration date.</p>
<p>If you store the expiration date with the credit card information in a payment gateway (e.g. Authorize&#8217;s CIM), that card will stop working after the expiration date.  You cannot move it forward unless you collect the user&#8217;s credit card number again.  But if your billing system is smart enough, perhaps it can try moving the current expiration date forward before asking the user to update their payment details when the card expires.</p>
<h3>1 Cent Authorizations</h3>
<p>If your payment gateway allows you to test a credit card with a 1 cent authorization, don&#8217;t use it.  Seriously.  It will fail 2-5% of the time.  Some banks can&#8217;t believe anyone would want a 1 cent payment so they will deny it for being too small.  Instead, either use a $1 authorization or authorize the transaction for the amount you want to collect in the future (if you know exactly how much that is).  And finally, void the authorization afterwards.  If you don&#8217;t, the credit card companies may hit you with a fine &#8212; this is becoming more common since an authorization effectively puts a hold on funds in the customer&#8217;s account and they want you to release it if you don&#8217;t intend to collect.</p>
<h2>Keep Your Pricing Simple</h2>
<p>If you have a great product, your customers will want to pay you.  But if your pricing is too complicated, three things happen:</p>
<ul>
<li>Your sales guy can&#8217;t explain pricing,</li>
<li>Your programmers (you) will spend too much time figuring out how to bill your users, and</li>
<li>Your customers will complain that they&#8217;re paying too much.</li>
</ul>
<p>Simplify your pricing, perhaps replace overage fees with auto-upgrading tiers, and magic happens:</p>
<ul>
<li>Your sales guys can explain it in a minute,</li>
<li>Your programmers (you) will spend less time on billing, and</li>
<li>Your customers will be happy to pay.</li>
</ul>
<p><strong>Minimize Your Time Handling Billing Support</strong></p>
<p>Billing support will overwhelm you if you&#8217;re not ready.  Make sure your users can self service their accounts the moment you start charging.  If you offer more than one billing cycle or pricing plan, allow your users to change their plan with minimal hassle &#8212; otherwise they&#8217;re going to write to your support and you&#8217;ll have to do it for them, and often.</p>
<p>Make it easy for your subscribers to cancel.  They should not have to contact you to stop paying you &#8212; in the end they&#8217;ll just be more likely to call their credit card company and dispute the charge (that&#8217;s a chargeback).  And if you collect enough chargebacks, say goodbye to your merchant account.</p>
<p>Finally, if you build your own subscription billing system, you&#8217;re going to spend disproportionate amounts of your time handling past-due accounts.  You&#8217;ll get up and running quickly with your payment gateway&#8217;s recurring billing API, but you&#8217;ll spend 10x more time trying to figure out how to handle an account when a payment fails.  That&#8217;s precisely why we created <a href="http://recurly.com"   >Recurly</a>.</p>
<h2>TechTalk Slides</h2>
<div style="width:425px;text-align:left" id="__ss_2985873"><a href="http://www.slideshare.net/Recurly/lessons-learned-in-online-billing" style="font:14px Helvetica,Arial,Sans-serif;display:block;margin:12px 0 3px 0;text-decoration:underline;"   title="Lessons Learned in Online Billing" >Lessons Learned in Online Billing</a><object style="margin:0px" width="425" height="355"><param name="movie" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=recurlytechtalk-100125021643-phpapp02&#038;stripped_title=lessons-learned-in-online-billing" /><param name="allowFullScreen" value="true"/><param name="allowScriptAccess" value="always"/><embed src="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=recurlytechtalk-100125021643-phpapp02&#038;stripped_title=lessons-learned-in-online-billing" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355"></embed></object></div>
]]></content:encoded>
			<wfw:commentRss>http://blog.recurly.com/2010/01/lessons-learned-in-online-subscription-billing/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<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 13:45:00 -->
