<?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>TerraNetwork &#187; Sage Pay</title>
	<atom:link href="http://www.terranetwork.net/blog/tag/sage-pay/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.terranetwork.net/blog</link>
	<description></description>
	<lastBuildDate>Mon, 19 Jul 2010 14:53:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Sage Pay</title>
		<link>http://www.terranetwork.net/blog/2009/05/sagepay/</link>
		<comments>http://www.terranetwork.net/blog/2009/05/sagepay/#comments</comments>
		<pubDate>Fri, 29 May 2009 15:31:38 +0000</pubDate>
		<dc:creator>Edith</dc:creator>
				<category><![CDATA[Payments]]></category>
		<category><![CDATA[eCommerce]]></category>
		<category><![CDATA[osCommerce]]></category>
		<category><![CDATA[Sage Pay]]></category>

		<guid isPermaLink="false">http://www.terranetwork.net/blog/?p=99</guid>
		<description><![CDATA[Sage Pay  is a UK payment processing service (formerly known as ProtX). In short, they handle the credit/debit card collection and authorisation process on behalf on online businesses.
SagePay is used by many shops I&#8217;ve built and they provide a reliable service with realistic fees. They&#8217;re usually top of my list when customers ask for [...]]]></description>
			<content:encoded><![CDATA[<p><a href="">Sage Pay</a>  is a UK payment processing service (formerly known as ProtX). In short, they handle the credit/debit card collection and authorisation process on behalf on online businesses.</p>
<p>SagePay is used by many shops I&#8217;ve built and they provide a reliable service with realistic fees. They&#8217;re usually top of my list when customers ask for a recommendation. An additional benefit is that they&#8217;re developer-friendly (good integration guides and test environment). </p>
<div id="attachment_152" class="wp-caption alignnone" style="width: 510px"><a href="http://www.sagepay.co.uk/"><img src="http://www.terranetwork.net/blog/wp-content/uploads/2009/05/sagepay.gif" alt="www.sagepay.co.uk - the new home for ProtX" title="Sage Pay" width="500" height="290" class="size-full wp-image-152" /></a><p class="wp-caption-text">www.sagepay.co.uk - the new home for ProtX</p></div>
<p><span id="more-99"></span></p>
<h2>Form or Direct?</h2>
<p>Sage Pay offers 2 main services: Sage Pay Form where customers go offsite to Sage Pay to pay the invoice &#038; are then returned back to your shop; and Sage Pay Direct where customers stay on your website and only the payment details are sent to Sage Pay. </p>
<p>Both options required the business to have its own internet merchant account. Sage Pay provides a list of compatible banks here: <a href="http://www.sagepay.com/developers/industry_knowledge/merchant_acquirers.asp">http://www.sagepay.com/developers/industry_knowledge/merchant_acquirers.asp</a>. </p>
<p><span  class="highlight">The form integration is very simple</span>. The website doesn&#8217;t even need an SSL certificate (although we do recommend this for all e-commerce websites). Customers go to the Sage Pay site to pay and are then redirected back to the website. Sage Pay Form comes with the added benefit of PayPal integration. </p>
<p><span class="highlight">With Sage Pay Direct</span>, customers stay on the website and only their card details are passed over to Sage Pay. Website will therefore need an SSL certificate and be PCI DSS compliant. Customers enter their card details on checkout_confirmation. If 3D Secure is required, the bank&#8217;s 3D Secure page appears. On successful autorisation, customers go the checkout_success page. Voids/Refunds can be processed from within the admin area. </p>
<h2>Taking payments </h2>
<p><span class="highlight">Multi Currency: </span> Sage Pay is in principle multi currency compatible, however accepting multiple currencies must be agreed with the merchant account provider (usually your bank) and can be expensive. If you need to take multiple currencies, check the fees carefully in advance. For smaller shops, PayPal may be a cheaper method to handle several currencies.</p>
<p><span class="highlight">MoTo: </span>Sage Pay can provide a virtual terminal for accepting payments in writing and over the phone. Very useful and doesn&#8217;t cost anything extra. </p>
<p><span class="highlight"> Cashflow:</span> Sage Pay transfers the authorised payments into your bank account at the end of each working day cycle. This makes it great for cash flow, especially when compared to PayPal where transfers can take over a week to reach you. </p>
<h2>Sage Pay Integration with osCommerce </h2>
<p>The form integration is available as standard with all osCommerce shops. It can be found &#038; activated under &#8220;Modules -> Payment&#8221;. </p>
<p>For the direct integration, we recommend <a href="http://forums.oscommerceproject.org/index.php?autocom=downloads&#038;showfile=20">http://forums.oscommerceproject.org/index.php?autocom=downloads&#038;showfile=20 </a>. The module is actively maintained and very reliable. </p>
<p>A paid installation service is also available from TerraNetwork. </p>]]></content:encoded>
			<wfw:commentRss>http://www.terranetwork.net/blog/2009/05/sagepay/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
