4 ms·
My information may be out-dated, but Freshbooks seemed like it wouldn't have been a good fit for subscription billing back when we were looking. Basically, it
by mrkurt 17y ago
My information may be out-dated, but Freshbooks seemed like it wouldn't have been a good fit for subscription billing back when we were looking.
Basically, it wasn't possible to create a signup form that resulted in a recurring invoice with credit card data attached. So you'd end up with janky situations where you're either invoicing people and waiting for them to pay, or charging them through another gateway, then hoping they enter payment information before the next cycle.
There's also no callback mechanism from Freshbooks to an outside site, making it extremely difficult to keep track of expiring subscriptions/cancellations/etc.
I would love, love, love for Freshbooks to also be a drop in subscription billing platform. It seems like most of the bits are there, but there's no guiding force trying to make sure it works well for that purpose.
- sunir 17y agoThanks for your help! Callbacks and credit cards are the top two problems with the existing API. At least callbacks are a problem with a clear solution (HTTP postback, aka webhooks). As for credit cards through the API, we debate about that one extensively. The concern we have is that ideally, our customers would prefer not to touch credit cards because of the liability of credit cart theft. That's why for now we take on the risk of managing credit cards by letting you punt the customer to our invoice page. What's preferable to you? 1. Never touching the credit card ever, but redirecting the customer to a good payment experience 2. Taking the credit card on your own sign up form and sending it through our API 3. Taking the credit card through a FreshBooks https iframe on your website Or any other solutions?