The Spreedly Blog - Latest Comments

Re: The Blog of Spreedly.com - Improved Spreedly Pricing!

ntalbott — Fri, 13 Nov 2009 06:55:26 -0000

Absolutely! All clients benefit from this new pricing - it's too good to keep for just the new folks :-)

Re: The Blog of Spreedly.com - Improved Spreedly Pricing!

cobrabyte — Fri, 13 Nov 2009 01:24:24 -0000

Curious … if we've already signed up for a kickstart, do we get the new savings?

I know it says that existing customers get the new savings and I can only assume that the kickstart early-adopters will get the savings but it's nice to get it in writing. ;)

From the wording above, it looks as though only the remaining kickstart subscribers will get the new pricing and that'd rain on our parade.

Re: The Blog of Spreedly.com - The Payments API

ntalbott — Wed, 16 Sep 2009 23:51:31 -0000

Most merchants should be able to just fill out the PCI Self-Assessment Questionnaire and sign up for quarterly network scans. Auditing is only required for the most strict levels of PCI, generally reserved for merchants with huge volume.

Re: The Blog of Spreedly.com - The Payments API

Mark Dodwell — Wed, 16 Sep 2009 23:45:41 -0000

If you use this Payment API to submit card details over SSL (via your own server) then would you need to be audited to be PCI-DSS compliant?

Re: The Blog of Spreedly.com - Ready to RUMBLE

Scott Meade — Thu, 10 Sep 2009 10:35:27 -0000

Nathaniel and Spreedly,

Thank you for the recognition of AffiliApp and for making Spreedly easy to integrate into a payment workflow. With early interest from several fronts, we are very excited about AffiliApp's future. I will be presenting it, including Spreedly integration, at the October meeting of Denver's Ruby on Rails user group, DeRailed. Thank you again for the recognition, for supporting the Rails Rumble, and for the Kickstart prize.

Scott

Re: The Blog of Spreedly.com - The Payments API

Anon — Thu, 27 Aug 2009 12:31:35 -0000

This service is getting better and better. Well done, you have stayed with the problem long enough and the results show it. I don't think there is anything as simple and as developer-friendly as Spreedly out there. As a developer sick of dealing with subscriptions code, being worried about bugs in such critical modules, I really feel glad that one company got it right and solved my problem. Now I can focus on the problems that matter to my business.

Well done guys, please keep it developer friendly and simple. Thank you so much.

Re: The Blog of Spreedly.com - The Payments API

jaknowlden — Thu, 06 Aug 2009 18:29:01 -0000

This is absolutely fantastic. This puts you way ahead of the competition.

Re: The Blog of Spreedly.com - The Payments API

twitter-50963 — Mon, 03 Aug 2009 13:59:06 -0000

This Payments API is a huge step forward - great work!

Re: The Blog of Spreedly.com - Variable Currency Support

ntalbott — Sun, 31 May 2009 18:20:38 -0000

No ¥ yet - we're waiting for you to request it! Definitely let us know when you're ready and we'll get it all hooked up for you.

Re: The Blog of Spreedly.com - Variable Currency Support

Thomas R. Koll — Sat, 30 May 2009 07:36:20 -0000

¥€$ great thing :-) Oh wait, no ¥?

I hope there's still one kickstart left for me in July.

Re: Spreedly Blog - Spreedly on the Web 2.0 Show

adamstac — Thu, 02 Apr 2009 09:57:55 -0000

Hey, it was blast talking with you. We look forward to using Spreedly with Tweetbots.

Re: Spreedly Blog - Rapid Service (With A Smile!)

Duff OMelia — Tue, 31 Mar 2009 14:54:26 -0000

Hi there Scott,

I wanted to let you know we just deployed the API call you requested.

http://spreedly.com/manual/integration-referenc...

Re: Spreedly Blog - Rapid Service (With A Smile!)

ntalbott — Thu, 12 Mar 2009 18:04:31 -0000

Scott, this is on the list now, and should roll out in the coming weeks. Thanks for the suggestion!

Re: Spreedly Blog - Rapid Service (With A Smile!)

scottmotte — Wed, 11 Mar 2009 20:39:11 -0000

I'm another that would like to see the ability to delete individual subscribers for testing purposes. The problem with destroy_all is it clears out your development test subscribers as well.

Re: Why Spreedly?

Benjamin Curtis — Sat, 28 Feb 2009 23:43:04 -0000

I do provide ongoing support and updates via email and via a private google group for SaaS Kit customers.

It's good to have options! :)

Re: Why Spreedly?

ntalbott — Sat, 24 Jan 2009 12:03:58 -0000

Steven, while we don't support ACH/Direct Deposit yet, it's something we're definitely interested in. It's a bit more work than just adding a new credit card gateway, but even so we'll prioritize it highly if we have requests for it from clients already using Spreedly. I don't know if it would be an option for you to start with credit cards and add support for ACH once it's available, but that would definitely incent us to spend time on ACH before other possibilities on the table. Definitely hit us up at support@spreedly.com if you'd like to discuss further - thanks!

Re: Why Spreedly?

Steven Wagner — Thu, 15 Jan 2009 11:32:00 -0000

Is it possible to accept or charge clients using ACH/Direct Deposit? We use authorize.net and would like to be paid immediately for enterprise level solutions.

Re: Why Spreedly?

Nathaniel Talbott — Mon, 12 Jan 2009 15:16:00 -0000

Ben, thanks for the clarification; it's great to hear that you're using the gateway provided card storage services to limit exposure.

You're still stuck with a few downsides, though: first, if a credit card ever passes through one's site, it increases the security exposure significantly. Second, using a gateway card storage service increases gateway vendor lock-in, since I don't believe the gateways make it easy to move those cards over to another proprietary store. Third, the SaaS kit is a one-time purchase, with no ongoing maintenance provided (that I know of), so once someone buys they're on their own over the long-term. And finally, SaaS is of course Rails-only, while Spreedly is language agnostic - come one come all!

To be fair, Spreedly has an ongoing cost that the SaaS kit doesn't, and I think having both options available is great. Both Spreedly and SaaS lower the barrier to getting a business off the ground, and here at Spreedly we're excited about anything that does that!

Re: Why Spreedly?

Nathaniel Talbott — Mon, 12 Jan 2009 15:04:00 -0000

Travis, we hear you, and you're not the only one. We're definitely working to put better instructions on the box.

To address your questions a bit, you *do* need to have a payment gateway and backing merchant account set up. Much as we don't like the subscription service they provide, PayPal is a pretty easy way to get a gateway setup as their "proof of business" requirements are low and they provide both gateway and merchant account rolled in to one. Of course, they also have higher fees than most other options, but the cool thing with Spreedly is that you can easily switch down the road when you have higher volume.

On the "how do I integrate it" front, definitely check out the Integration Guide. It walks you through exactly what's needed to get all the core Spreedly services hooked up, and also links you over to the Integration Reference where you can get more detail.

I hope this helps, and thanks for the feedback - every little bit makes us that much better!

Re: Why Spreedly?

Travis — Sat, 10 Jan 2009 22:15:00 -0000

Hi Nathaniel, just a little feedback. Spreedly /sounds/ great!

What's not clear from your site or blog is exactly what I need to get started. Do I need a payment gateway, a merchant gateway, what do I have to build?

The directions on the box are a little incomplete, so to speak, and because Spreedly is not clear about how I use it / integrate it, I'm not sure yet if it's the solution I need.

I have an app that wants to implement a subscription based payment model. I'm there, I want to be a Spreedly customer, but I'm just not sure yet.

Re: Why Spreedly?

Benjamin Curtis — Fri, 09 Jan 2009 18:53:00 -0000

Congrats on getting rolling with your product, guys! As the author of the SaaS Rails Kit that you linked to (thanks!), I do have to point out a possible misconception that you may have raised... the SaaS Rails Kit does not store the credit card information to do the recurring billing.

Instead of exposing my customers to that sort of risk, I implemented the Kit to use the card information storage feature of various gateways, leaving the gateway as the responsible party for managing that data.

I just wanted to make sure that was clear. :)

Again, congrats on getting started. After a year of running transactions on my SaaS code, and seeing my customers celebrating being able to skip the pain of figuring it out on their own, it's certainly a good thing to have people like us out there on the net. :)

Re: Throwing The Doors Open

Nathaniel Talbott — Thu, 08 Jan 2009 20:17:00 -0000

Aja, we do have plans to add one-time setup fee handling and to support discount/coupon codes. We're using demand from paying clients to help drive our priorities, so we'd love to have you on the platform helping us set the tempo. Thanks for the great questions!

Re: Throwing The Doors Open

Aja B. — Thu, 11 Sep 2008 12:50:00 -0000

Hey guys! This is great, we're really excited about what you're doing here! We have two questions though... could Spreedly handle charging customers a one-time setup fee on the first payment, in addition to the regular subscription fees? And would there be any way to offer customers discount codes they could use to reduce the cost?

Thanks guys, keep up the great work! :)