<?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: MicroISV Digest returns next week&#8230;</title>
	<atom:link href="http://47hats.com/2009/10/microisv-digest-returns-next-week/feed/" rel="self" type="application/rss+xml" />
	<link>http://47hats.com/2009/10/microisv-digest-returns-next-week/</link>
	<description>Bob Walsh</description>
	<lastBuildDate>Tue, 07 Feb 2012 15:41:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Nathaniel Talbott</title>
		<link>http://47hats.com/2009/10/microisv-digest-returns-next-week/comment-page-1/#comment-31627</link>
		<dc:creator>Nathaniel Talbott</dc:creator>
		<pubDate>Wed, 14 Oct 2009 05:00:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.47hats.com/?p=1631#comment-31627</guid>
		<description>I feel really badly for Bob - he&#039;s had a tough couple of weeks fighting with PayPal. What it boils down to is that Spreedly requires a certain risk level of PayPal account to work, and while most of our clients have either started out at the necessary level or have been able to achieve it through talking with PayPal, for whatever reason they stubbornly refused to extend it to StartupToDo.
I totally understand why he&#039;s looking for other solutions, and wish him the best of luck in finding one that works for him. At the same time I can tell you that Spreedly&#039;s working without issue for scores of other clients, and in the rare case other businesses have run into this issue with PayPal they&#039;ve been able to get around it by going with a different gateway.
FYI I am in discussions with PayPal about both making this issue more visible to their customers (the risk level is completely hidden at this point), as well as lowering the barrier and make the necessary controls accessible to more accounts. Unfortunately it&#039;s going to be too little, too late for StartupToDo, for which we&#039;re very sad.
Thanks for giving us a fair shake, Bob - we wish you the best! And if anyone has any followup questions, don&#039;t hesitate to fire them off to support@spreedly.com.</description>
		<content:encoded><![CDATA[<p>I feel really badly for Bob &#8211; he&#8217;s had a tough couple of weeks fighting with PayPal. What it boils down to is that Spreedly requires a certain risk level of PayPal account to work, and while most of our clients have either started out at the necessary level or have been able to achieve it through talking with PayPal, for whatever reason they stubbornly refused to extend it to StartupToDo.</p>
<p>I totally understand why he&#8217;s looking for other solutions, and wish him the best of luck in finding one that works for him. At the same time I can tell you that Spreedly&#8217;s working without issue for scores of other clients, and in the rare case other businesses have run into this issue with PayPal they&#8217;ve been able to get around it by going with a different gateway.</p>
<p>FYI I am in discussions with PayPal about both making this issue more visible to their customers (the risk level is completely hidden at this point), as well as lowering the barrier and make the necessary controls accessible to more accounts. Unfortunately it&#8217;s going to be too little, too late for StartupToDo, for which we&#8217;re very sad.</p>
<p>Thanks for giving us a fair shake, Bob &#8211; we wish you the best! And if anyone has any followup questions, don&#8217;t hesitate to fire them off to <a href="mailto:support@spreedly.com">support@spreedly.com</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Markiewicz</title>
		<link>http://47hats.com/2009/10/microisv-digest-returns-next-week/comment-page-1/#comment-31625</link>
		<dc:creator>Tom Markiewicz</dc:creator>
		<pubDate>Tue, 13 Oct 2009 17:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.47hats.com/?p=1631#comment-31625</guid>
		<description>I thought you were using Spreedly. How are they not working out for you? I&#039;m interested to hear as I&#039;ve been planning using them soon.</description>
		<content:encoded><![CDATA[<p>I thought you were using Spreedly. How are they not working out for you? I&#8217;m interested to hear as I&#8217;ve been planning using them soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: taylor</title>
		<link>http://47hats.com/2009/10/microisv-digest-returns-next-week/comment-page-1/#comment-31624</link>
		<dc:creator>taylor</dc:creator>
		<pubDate>Tue, 13 Oct 2009 14:04:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.47hats.com/?p=1631#comment-31624</guid>
		<description>I&#039;m interested in what you find for handling subscriptions, and why you&#039;re switching from the current one (Spreedly?).
Have you looked at the SaaS Rails Kit? (http://railskits.com/recurring_billing/)
Chargify looks kind of interesting as well, but still in beta. (http://chargify.com/)</description>
		<content:encoded><![CDATA[<p>I&#8217;m interested in what you find for handling subscriptions, and why you&#8217;re switching from the current one (Spreedly?).</p>
<p>Have you looked at the SaaS Rails Kit? (<a href="http://railskits.com/recurring_billing/" rel="nofollow">http://railskits.com/recurring_billing/</a>)</p>
<p>Chargify looks kind of interesting as well, but still in beta. (<a href="http://chargify.com/" rel="nofollow">http://chargify.com/</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Lewis</title>
		<link>http://47hats.com/2009/10/microisv-digest-returns-next-week/comment-page-1/#comment-31619</link>
		<dc:creator>Jeff Lewis</dc:creator>
		<pubDate>Tue, 13 Oct 2009 03:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.47hats.com/?p=1631#comment-31619</guid>
		<description>Please tell about your subscription issues, I&#039;m looking for one now...</description>
		<content:encoded><![CDATA[<p>Please tell about your subscription issues, I&#8217;m looking for one now&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

