Thanks 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 p

Thanks 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?