<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Sage outage cause customers to lose &#8216;000s of pounds</title>
	<atom:link href="http://blog.kashflow.com/2009/09/08/sagepay-outage/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kashflow.com/2009/09/08/sagepay-outage/</link>
	<description>Easy to Use Accounting Software</description>
	<lastBuildDate>Fri, 12 Mar 2010 12:17:55 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Terry Froy</title>
		<link>http://blog.kashflow.com/2009/09/08/sagepay-outage/comment-page-1/#comment-13746</link>
		<dc:creator>Terry Froy</dc:creator>
		<pubDate>Wed, 14 Oct 2009 10:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kashflow.com/?p=1068#comment-13746</guid>
		<description>After reading this article and hearing enough stories from our own customers concerning SagePay, I thought we might give Iridium a go.

Registering for a trial account was very easy and personally, I *love* their API.

Can I get them to acknowledge any of my mails or respond to my requests for a quote to provide a merchant account/payment gateway services ?

I have had *zero* responses from them and our e-mail does work as we host the servers/network that handle it (we are an ISP) - not even a dicky-bird of an automated response - and the annoying thing is that we *can* receive mail from them as I personally received the signup welcome mail and all the trial account details via e-mail.

Terry Froy / Spilsby Internet Solutions</description>
		<content:encoded><![CDATA[<p>After reading this article and hearing enough stories from our own customers concerning SagePay, I thought we might give Iridium a go.</p>
<p>Registering for a trial account was very easy and personally, I *love* their API.</p>
<p>Can I get them to acknowledge any of my mails or respond to my requests for a quote to provide a merchant account/payment gateway services ?</p>
<p>I have had *zero* responses from them and our e-mail does work as we host the servers/network that handle it (we are an ISP) &#8211; not even a dicky-bird of an automated response &#8211; and the annoying thing is that we *can* receive mail from them as I personally received the signup welcome mail and all the trial account details via e-mail.</p>
<p>Terry Froy / Spilsby Internet Solutions</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DVD</title>
		<link>http://blog.kashflow.com/2009/09/08/sagepay-outage/comment-page-1/#comment-12446</link>
		<dc:creator>DVD</dc:creator>
		<pubDate>Thu, 10 Sep 2009 10:29:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kashflow.com/?p=1068#comment-12446</guid>
		<description>This reads to me like a competitor (and non-customer anyway) not wasting an opportunity to have a go at a rival and/or them bigging up a friendly alternative (perhaps for some commercial reason?) which somewhat undermines the argument for me. Yes, any outage is inconvenient and business threatening, however log it is, but Sage&#039;s reasons for bringing the system up slowly carry enough weight with me for me not to go running off to someone else. Having experienced outages and other problems with other service providers as well (PayPal anyone?!), including Google&#039;s recent outages (and look at the size of them!), I think people need to keep this kind of incident in perspective.

As long as SagePay learn the lessons we&#039;ll stick with them rather than jump out of the frying pan.</description>
		<content:encoded><![CDATA[<p>This reads to me like a competitor (and non-customer anyway) not wasting an opportunity to have a go at a rival and/or them bigging up a friendly alternative (perhaps for some commercial reason?) which somewhat undermines the argument for me. Yes, any outage is inconvenient and business threatening, however log it is, but Sage&#8217;s reasons for bringing the system up slowly carry enough weight with me for me not to go running off to someone else. Having experienced outages and other problems with other service providers as well (PayPal anyone?!), including Google&#8217;s recent outages (and look at the size of them!), I think people need to keep this kind of incident in perspective.</p>
<p>As long as SagePay learn the lessons we&#8217;ll stick with them rather than jump out of the frying pan.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Chatterley</title>
		<link>http://blog.kashflow.com/2009/09/08/sagepay-outage/comment-page-1/#comment-12424</link>
		<dc:creator>Matt Chatterley</dc:creator>
		<pubDate>Wed, 09 Sep 2009 06:23:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kashflow.com/?p=1068#comment-12424</guid>
		<description>Urgh. Not good at all.

Although, I would normally suggest having a backup payment method available - even if it is an unpopular alternative for one reason or another (on either side of the transaction - e.g. PayPal, et al).

@Martin - You&#039;d like to think any company no matter how big would at least let you know if everything went boom. Obviously this was not the case!</description>
		<content:encoded><![CDATA[<p>Urgh. Not good at all.</p>
<p>Although, I would normally suggest having a backup payment method available &#8211; even if it is an unpopular alternative for one reason or another (on either side of the transaction &#8211; e.g. PayPal, et al).</p>
<p>@Martin &#8211; You&#8217;d like to think any company no matter how big would at least let you know if everything went boom. Obviously this was not the case!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Brietsche</title>
		<link>http://blog.kashflow.com/2009/09/08/sagepay-outage/comment-page-1/#comment-12414</link>
		<dc:creator>Sean Brietsche</dc:creator>
		<pubDate>Tue, 08 Sep 2009 20:11:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kashflow.com/?p=1068#comment-12414</guid>
		<description>One thing I will say about SagePay/Protx is that when they get it wrong they do it spectacularily. I just cannot fathome how you have a degradedservice for over 24 hours in this day and age. I know a lot of the SagePay staff. I even went sailing with their sales director last summer. Its gutting to see Merchants affected this way. 

The scary bit I see on this is we preach to our merchants they should pre-auth transactions and use either in-house fraud rules, either human applied or through technical application, to decide to accept a transaction. 

Without the ability to access transactional data that even went through an minute ago I as a
merchant would probably elect to go for a full sale/capture transaction so I don&#039;t lose the sale, ie throw my company fraud rules away for a day so I don&#039;t lose a days sales. This will just mean chargebacks, fraud, and goods shipped where the merchant is going to lose out.

I quote from the SagePay website :

     &quot;&lt;em&gt;Our twin data centres and disaster recovery initiatives ensure your payments are being processed all day every day&lt;/em&gt;.&quot;

Its easy to say this but in application when a problem does happen the ability to deliver no downtime is not easy. I would be annoyed if Google went down for a couple of hours as its such an important tool in my work day. Not being able to take money for 24 hours as a business is just wrong.</description>
		<content:encoded><![CDATA[<p>One thing I will say about SagePay/Protx is that when they get it wrong they do it spectacularily. I just cannot fathome how you have a degradedservice for over 24 hours in this day and age. I know a lot of the SagePay staff. I even went sailing with their sales director last summer. Its gutting to see Merchants affected this way. </p>
<p>The scary bit I see on this is we preach to our merchants they should pre-auth transactions and use either in-house fraud rules, either human applied or through technical application, to decide to accept a transaction. </p>
<p>Without the ability to access transactional data that even went through an minute ago I as a<br />
merchant would probably elect to go for a full sale/capture transaction so I don&#8217;t lose the sale, ie throw my company fraud rules away for a day so I don&#8217;t lose a days sales. This will just mean chargebacks, fraud, and goods shipped where the merchant is going to lose out.</p>
<p>I quote from the SagePay website :</p>
<p>     &#8220;<em>Our twin data centres and disaster recovery initiatives ensure your payments are being processed all day every day</em>.&#8221;</p>
<p>Its easy to say this but in application when a problem does happen the ability to deliver no downtime is not easy. I would be annoyed if Google went down for a couple of hours as its such an important tool in my work day. Not being able to take money for 24 hours as a business is just wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily Coltman</title>
		<link>http://blog.kashflow.com/2009/09/08/sagepay-outage/comment-page-1/#comment-12402</link>
		<dc:creator>Emily Coltman</dc:creator>
		<pubDate>Tue, 08 Sep 2009 14:37:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kashflow.com/?p=1068#comment-12402</guid>
		<description>Yeurgh!

Talk about bad customer service - as you say, it&#039;s one thing to have a short outage - but when the outage lasts that long and they don&#039;t even tell their customers... they don&#039;t deserve to have customers!

M</description>
		<content:encoded><![CDATA[<p>Yeurgh!</p>
<p>Talk about bad customer service &#8211; as you say, it&#8217;s one thing to have a short outage &#8211; but when the outage lasts that long and they don&#8217;t even tell their customers&#8230; they don&#8217;t deserve to have customers!</p>
<p>M</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://blog.kashflow.com/2009/09/08/sagepay-outage/comment-page-1/#comment-12400</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Tue, 08 Sep 2009 14:31:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kashflow.com/?p=1068#comment-12400</guid>
		<description>Isn&#039;t it wonderful that I have to find out from your blog that my payment gateway is broken... 

*sigh*</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t it wonderful that I have to find out from your blog that my payment gateway is broken&#8230; </p>
<p>*sigh*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Александар</title>
		<link>http://blog.kashflow.com/2009/09/08/sagepay-outage/comment-page-1/#comment-12398</link>
		<dc:creator>Александар</dc:creator>
		<pubDate>Tue, 08 Sep 2009 13:21:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kashflow.com/?p=1068#comment-12398</guid>
		<description>This is quite funny :)

Thanks for the tip about Iridium</description>
		<content:encoded><![CDATA[<p>This is quite funny :)</p>
<p>Thanks for the tip about Iridium</p>
]]></content:encoded>
	</item>
</channel>
</rss>
