Archive for February, 2010

Metered Billing Support (a.k.a. Usage-based Biling)

Wednesday, February 24th, 2010
http://www.flickr.com/photos/daveknapik/ / CC BY-NC-SA 2.0The billing space is evolving and growing rapidly, and subscription billing is no exception. One of the most frequently requested features we get at Recurly is for “metered billing”. Metered billing is the act of charging customers monthly based on their usage of a service, similar to a cell phone plan or electricity bill. These models can take many forms ranging from one purely based on usage to a model that combines a monthly fee with a component of usage based/metered billing.

While listening to customer feedback, we discovered that most cases of metered billing or usage-based billing can be supported today with Recurly through a combination of a subscription and one-time charges via our API.  For technical details and code examples, please see our how to guide.

At the moment, a variety of billing scenarios can easily be supported using our API.  This is only the first iteration; we’re working on making metered billing a first class citizen in our API.  If you have any feedback or questions, please drop us a line at support@recurly.com.

Fixing our email issues

Wednesday, February 3rd, 2010

Subscription billing is a pain and we’re trying to make your life easier by simplifying it for you. Well, it turns out that email is also a pain and we’re turning to someone else for help.

Recently, there’s been a high amount of email support requests. We spool mail locally from our web application to Postfix, then deliver it out to the internet. Well, it turns out that a large amount of that email was getting dropped. Watching the postfix mail logs was a bit disheartening after seeing numerous mail servers refuse to chat with our email server. We have SPF records setup, reverse DNS, and deliver mail from a dedicated IP address — it turns out that that’s still not enough.

To our customers: I’m sorry we didn’t figure this out earlier. We haven’t done a good job delivering our billing emails to your customers. Right now, we are evaluating multiple ways to improve the email delivery rates for the emails we send to your subscribers on your behalf. There should be an immediate uptick in the delivery rate for your emails today. And over the next couple weeks, we’ll determine the best way to reliably deliver your emails with the correct domain keys, SPF records, etc so that they work even better than if you were to send the emails yourself.

To other start-ups: I hope you read this and then realize that running your own SMTP server on dedicated, non cloud-based servers can still be problematic. I thought that because we’re not in the cloud, we don’t need someone else to handle our emails — looks like I was wrong. To remedy the situation, we’re now evaluating SendGrid (shout out to another CEO named Isaac). I’ve heard great things about their service and I’ve been comparing email headers all evening. It looks like their product is doing a fantastic job handling bounced emails, invalid email addresses, ISP feedback loops, domain keys (something we didn’t have setup), SPF, and everything else. Their web UI is a little rough around the edges, but so far it looks promising. Assuming their product lives up to its marketing material, it will help us dramatically improve our email reliability.

We’re not email experts and we don’t have time to build it out ourselves — (this sounds so familiar, right?).

Once again, a big thanks to everyone for being patient as we improve our email issues.

Ruby on Rails Client Application now available

Monday, February 1st, 2010

At Recurly, we’re all about making developers lives easier. We’ve gotten some great feedback on the Ruby client library, but we thought a simple rails application would make things even easier.

I’m happy to announce an open source Ruby on Rails client application available now up on github. The client application demonstrates the REST API calls you’ll use in order to get your rails application processing subscriptions and one time payments with Recurly.

The client application depends on Recurly’s Ruby client library, which is available as a Ruby gem (via gemcutter.org) or plugin.  Please see the Ruby client documentation for installation instructions.

If you run into any problems using the app, drop us a line over in our support forums.

Cheers,
-james


Links