Poll: How do you bill recurring payments?

Post by thibaut_barrere » Thu, Feb 10, 2011, 1:36 PM UTC

primigenus wrote: post #17

We're using Spreedly on top of Ogone and Atos Worldline. The notable thing about our setup is that we're based in the Netherlands and it took us 6 months of painstaking research and headaches to figure out the combination of services that would allow us to accept subscription payments. I wrote a blog post about the ordeal last week; I recommend it to anyone in a similar situation (eg. non-UK Europe): http://blog.qupl…

Post by MicahWedemeyer » Thu, Feb 10, 2011, 2:02 PM UTC

Post by marquis » Thu, Feb 10, 2011, 2:27 PM UTC

jpallen wrote: post #4

I use Paypal's recurring billing API directly. It's not an ideal solution, but being based in the UK without a merchant account it's the only one I have available. I use ActiveMerchant and some extensions to talk to the Paypal API but I've had to write the logic to handle recurring billing myself. I'm trying to extract that logic into a gem and make it more robust. I'd like to eventually release it and possibly save…

Post by steveklabnik » Thu, Feb 10, 2011, 2:47 PM UTC

garrettdimon wrote: post #11

We use Braintree's vault, and we use ActiveMerchant to access it. We wrote all of the recurring/billing/invoicing logic ourselves. Beyond the initial implementation, we've done one sweeping overhaul of the logic to make some improvements and simplify things after learning a lot from the first pass. We built it in late 2008, and either the companies that handled recurring stuff didn't exist when we were building it, o…

Post by steveklabnik » Thu, Feb 10, 2011, 2:49 PM UTC

tzs wrote: post #10

We keep the credit card numbers on file (yes, fully complying with PCI) and handle the recurring billing ourselves.