Maxio

Credit card contract management/retention across three currencies. It has been a God-sent.

We came from a competing service where the tech support had devolved. We needed an API that was robust enough to let us convert our existing payment system quickly, which Chargify's did. The customer service and tech support along the way has been excellent. As PCI compliance became more rigorous, we moved to using their hosted public payment pages, which allows us to reduce/remove PCI compliance on our side. However, the public pages do come with some limitations in that customizing them requires knowledge of CSS and Javascript to control various elements. Overall, however, our transition to, and continued use of Chargify has been a great experience and I would recommend them to anyone looking for a merchant account payment processor.

I do enjoy how easy it is to raise credits/invoices & sync these transactions to Quick Books from SaaSOptics. It is also very easy to reverse revenue by raising the transaction from the contract. The main issues I have, however, with this software can be narrowed down to - Future invoices, Tax options & Client Billing (info) Profiles:
1. I keep a self-maintained spreadsheet with future invoice details due to the following: Future invoices are not always pulling when the date is current; they are not appearing in the order processing (ready to bill) list within SaaSOptics because the 'e-invoice queue' check mark is dropping off. To avoid errors, to ensure that the client receives their invoice when the date is current, I track this info on a spreadsheet outside of SaaS.
2. I keep a maintained spreadsheet with billing profile information for our clients due to the following: Inconsistencies on the billing profiles between SaaSOptics, Sales Force & Quickbooks. Billing information can not be trusted, ease of use could be improved to avoid syncing headaches. To avoid errors, to ensure that the client receives their invoice with correct billing info, I track this info on a spreadhsset, outside of Saas.
3. I keep a maintained spreadsheet with tax tables and user tax details due to the following: The inability to add multiple sales tax rates in SaaSOptics / Quickbooks. Ease of use could be improved by allowing multiple rates to be added into the system & allowing tax addresses to be saved in the system. I calculate tax outside of SaaS/QB, maintain this info for reporting purposes & manually enter tax details on the tax line in QB/SaaS. My other option would be to create line items for tax ( I have discussed this option with QB) but then it would pull into SaaSOptics as a product line (not tax) which would in turn throw the financial summary out of balance. Total invoice line items scheduled would increase by the tax amount which would not balance to the revenue.
4. I pull data & cross-compare SaaSOptics with Quickbooks to fix the tax errors due to the incorrect sales tax rate is generating on the invoice. If the sales tax is blank in Quick Books but is set to taxable in SaaSOptics, an "inactive" rate pulls onto the invoice which is not at the correct rate. At the same time, when I pull this info, I also cross-compare against my self maintained spreadsheet to correct errors on the billing profiles.
Thank you for your time!

We've been (sadly) a long-time user of Chargify. Eventually, we will switch to just using native Stripe. Chargify is just a GUI on top of native Stripe and native Stripe has come a long way over the last few years.

Anyway, Chargify got new leadership a few years ago. Their CEO told me via email and on the phone that they would not raise our prices without an adequate heads-up. Well, they did. And they raised them by 10x (TEN!!!) with one month's notice. As a consolation, they gave me $20/month off. Thanks for being so damn generous with your long-time users.

They justified it by saying their development costs have soared as they've worked to develop new and rather poorly rolled out new features that aren't as good as other tools. For example, their analytics is absolute garbage.

To make matters worse: Just recently, there was a BIG bug as they switched their API calls to Stripe where Chargify was calling the ORIGINAL card a user signed up with as opposed to the default one in Chargify. We notified them about this in late August and they passed the buck to Stripe. Well, it was NOT Stripe's fault.

After a lot more back and forth emails, they finally admitted that this was on their end and fixed the bug. But that's after we've had to process thousands of dollars in refunds.

STAY AWAY. Use Native Stripe. Chargify is a rip off.